PfileStream error in DR

[noel_hocquet]

Hi,

I just set up DR, but each time I'm rendering with DR, I got a black RGB image (zdeph i.e is fine).
The log file says:
"V-Ray : Cannot send asset texture.png Error opening file: [PFileStream::Open] (2) The system cannot find the file specified. //"
The texture is fine. When rendering locally, it renders properly.
It's just when using DR, V-ray can't open & copy texture.png to the slave machine (Transfer missing assets checked)
Any ideas?

Thanks!
noel.

[ivan.slavchev]

What's your 3dsMax and V-Ray version? Also - is there backburner installed and all machines?

Also - what user you use to launch the spawner on the slave machine? An admin one, a normal one, or it runs with a Local system account as a service?
Does the scene rum locally if you copy it onto the render slave computer?

[unknowsncript]

I had same error yesterday.
mine was looking like happening because of empty bitmap nodes.
I deleted all empty bitmap nodes there is not an error now.

But two weeks ago , i find an interesting error. Vray Gpu rendered some black areas on an plane which has a jpg texture assigned.
I've converted jpg to png and its working as it should be.

[unknowsncript]

Hi,
I have an interesting error today.
I'm rendering an animation with Vray Next GPU update2 via backburner.

Backburner error message :
[V-Ray] Cannot send asset Error opening file:[PFileStream::Open]Empty file name[RenderClient::getStream]

I checked file, there is not any missing texture or empty bitmap node.
I get similar errors for different scenes.
This error is strated to show after Update 2.

Help please.

[ivan.slavchev]

Does this error disappear if you revert to the previous build? Is it possible to send us an example scene at support@chaosgroup.com if it does?

[Streetwise]

I too, have been getting this error for some time now. Very frustrating. It renders fine locally, but if I send the job to DR/BB, I get the error. What's odd is that before I sent the job, I made sure there were no blank Paths in Asset Tracking. However when I re-open the file, there they are again, even after saving... I tried using "Include Maps" but then max hangs (I think because the scene is so large).

Since the scene does complete and save out to PSD Manager before it throws the error and re-starts, is there a way to either ignore the error, or limit it to zero retries instead of 4 (a scene will render out 4 times with the error before it will give up and move on to the next scene). I know this isn't really fixing the issue, but at least it would keep production moving along.

Thanks.

[Streetwise]

Okay, so I found where I can turn off the failed attempts, so at least now the jobs render out and save even with an error, but it would sure be nice if we could figure out what's causing it to begin with.

[unknowsncript]

Does this error disappear if you revert to the previous build? Is it possible to send us an example scene at support@chaosgroup.com if it does?

After several tests i found a vray ies light cause this error. Deleting ies light solved my problem.

[Svetlozar Draganov]

Would it be possible to pack that project and send it over to support@chaosgroup.com for inspection?

[Martin.Minev]

We have reproduced the issue here and its logged into our bug-tracker. We will notify you when we have any progress.

[glorybound]

Same problem here. MAX 2019 and the latest V-Ray NEXT

[unknowsncript]

Same problem here. MAX 2019 and the latest V-Ray NEXT

Problem solved for me.

open bitmap/photometric Paths utility https://knowledge.autodesk.com/suppo...AFC2F-htm.html
Click Edit Resources button. It will take a while if you have too many textures.
Find empty rows from the list.
Click info; this will show you which objects have that empty textures.
Find those objects and correct bitmap files.

[joelly3d]

I am also having this issue. Max 2020 latest VRay Next. Appeared suddenly. I looked around, no missing image issue. The issue it is returning for me is that the file I am writing to cannot be found. If I change the path to something else, it doesn't like the new path either. Can't find a solution.

If i let it go locally, the errors disappear for subsiquent frames, but appear on the first frame of the sequence. Super weirdness.

[unknowsncript]

I am also having this issue. Max 2020 latest VRay Next. Appeared suddenly. I looked around, no missing image issue. The issue it is returning for me is that the file I am writing to cannot be found. If I change the path to something else, it doesn't like the new path either. Can't find a solution.

If i let it go locally, the errors disappear for subsiquent frames, but appear on the first frame of the sequence. Super weirdness.

try the latest nightly build, maybe it will help.

[kosso_olli]

I am also having this issue. Max 2020 latest VRay Next. Appeared suddenly. I looked around, no missing image issue. The issue it is returning for me is that the file I am writing to cannot be found. If I change the path to something else, it doesn't like the new path either. Can't find a solution.

If i let it go locally, the errors disappear for subsiquent frames, but appear on the first frame of the sequence. Super weirdness.

I get the exact same error on Backburner. The file I am writing can not be found. Which is strange, why should the file I am writing being loaded? The latest nightly doesn't help.