Crash to desktop because of "Transfer missing assets"

[kosso_olli]

Hey guys,
there is consistent crashing when sending a job via Backburner to render farm. The error message is

[2022/Feb/18|17:06:46] error: Cannot send asset \\XXX\RENDER\PREVIEWS_TESTS\override_TEST\bioconta iner_18_override_TEST.exr Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]

The file in question is the rendered output itself, which of course can not be found at this location until the render is finished. Why should the rendered output sent with "Transfer missing assets" in the first place?

Regards

Oliver

[vladimir_krastev]

Hi are you using this output dialog (the 3ds max's one instead of the frame buffer's):

[^Lele^]

The file in question is the rendered output itself, which of course can not be found at this location until the render is finished. Why should the rendered output sent with "Transfer missing assets" in the first place?

As Vladimir pointed out, if you are using *any* of the standard max saver dialogs (so, also the split file save one.), what happens is that the file path isn't a string (i.e. some text) but an actual bitmap (don't ask...).

[kosso_olli]

Nope, we're not. We're using the output path of the frame buffer in the V-Ray settings. Actually, it was the first thing we checked.
If you enable the output path in the frame buffer settings, the path shows up in the asset tracker, though.

[kosso_olli]

Also, this scene renders totally fine with DR from the workstation itself. But sending this to Backburner does not work at all.

[^Lele^]

That's the one i called "split file save", it's a bitmap, not a string.
See if it works with non-max paths (i.e. raw file output).
It could well be permission issues, as the path looks unwriteable from BB, but not from the workstation.

[kosso_olli]

I'm not sure that's the problem. The output file is written just fine if "Transfer missing assets" is turned of.
V-Ray tries to transfer a file (the rendered output), which can not be there until the render is finished. The file simply does not exist at the start of the render. But because the render crashes because of the missing file, it will never be transferred. See the problem?
Also, why does V-Ray need to transfer the output file? It is not needed for the render itself.

[^Lele^]

Well, as mentioned, max needs a bitmap file written to set a file output.
So, before the render starts, the "asset" needs transferring, and fails.
Did you try the suggested method?
Did it start the render and fail at trying to write the raw output?

[kosso_olli]

Well, as mentioned, max needs a bitmap file written to set a file output.

At the start of the render?

I did not test the suggested method, because our whole workflow is built around the separate channel output. V-Ray raw output is not the right thing for us.
So, right now we are simply disabling the transfer missing assets feature. Which defeats it's whole purpose.

[^Lele^]

Yes, at the start of the render, as that's when the file output is generated.
For the raw file output (our file writer) is a simple string, we do not have anything to transfer, but for max it is a bitmap class object, and so this is a possible occurrence.
If the location isn't writeable, for whatever reason, an error is thrown up.
Using the raw output is to test the theory, and your infrastructure, not to suggest a different workflow.
Alas, do as you wish.

[kosso_olli]

Yes, at the start of the render, as that's when the file output is generated.

But the file is written at the end of the render, not at the start?

Anyway, here is the test with Vray Raw Image file. Same crash right after building the light cache:

[2022/Feb/22|15:32:52] error: Cannot send asset \XXX\RENDER\PREVIEWS_TESTS\override_TEST\biocontai ner_18_override_TEST.vrimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]

Settings for saving:




Edit: The vrimg gets saved though, it is here. But crashes still

[fixeighted]

Not wanting to complicate the issue but as a possible workaround in lieu of an actual fix, what happens if you pre-save something random as that same named file.
Then it'd at least have something to locate...possibly. It'd then get overwritten by the subsequent actual renders, I'd presume.
Unfortunately I can't test this approach. Bit of a mad problem tbh

[kosso_olli]

Bit of a mad problem tbh

It's driving us mad, yeah.

[^Lele^]

But the file is written at the end of the render, not at the start?

No.
When you manually set a file output path with a max saver, max creates a physical bitmap on disk, and if that is successful, you get to set the bitmap up and save the actual path.
When this path is passed over to network rendering, a slave initiating rendering will check that path for validity, thereby creating a temp bitmap on disk.

Anyway, here is the test with Vray Raw Image file. Same crash right after building the light cache:

[2022/Feb/22|15:32:52] error: Cannot send asset \XXX\RENDER\PREVIEWS_TESTS\override_TEST\biocontai ner_18_override_TEST.vrimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]

Settings for saving:




Edit: The vrimg gets saved though, it is here. But crashes still

Yes, as a side behaviour to the way max sets output bitmap paths, you are crashing still because the multi-channel file output hasn't been cleared, you just unticked the save box, and that is the file that is still crashing on you.
You will need to run this script lines to ensure it's cleared.

renderers.current.output_splitfilename = "" --clears the STRING for the filename
renderers.current.output_splitbitmap = undefined --clears the BITMAP to be saved

Interesting that the raw file writer has no issue, while the max one does.

We have tried and cannot replicate the issue on our side, nor have we any entry about these issues on record.
It's either a new problem with BB, or it's got to do with writing rights, or analogous lack of location access by some slave, on your side.

edit: to be perfectly clear: any dialog that looks like this, regardless of how it pops up (split file save, main output, saving from the VFB) is a max file saving one.


EDIT #2: Just so you don't think i'm trolling you with the max saving, here's code from Oblivion, back in 2013, on setting up split file output:

fn setSplitFileOut bmpPath=
(
cr.output_splitgbuffer=true
[I][B]-- create a temporary bitmap[/B][/I]
local tempBitmap = bitmap 1 1 filename:bmpPath hdr:true
save tempBitmap
[I][B]-- assign it[/B][/I]
cr.output_splitbitmap = tempBitmap --this is an EXR file
cr.output_splitFileName = bmpPath
[I][B]-- and delete the temp file[/B][/I]
close tempBitmap; deleteFile bmpPath
)

[kosso_olli]

Alright, here is the next test. I used your script to delete the older output entry with success:



So the render setup window now looks like this:



Crashing, still. Same message as before.

[2022/Feb/22|18:18:56] error: Cannot send asset \\XXX\RENDER\PREVIEWS_TESTS\override_TEST\Test_v01 .vrimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]
[2022/Feb/22|18:18:56] error: Cannot send asset \\XXX\RENDER\PREVIEWS_TESTS\override_TEST\Test_v01 .vrimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]


I'm running out of ideas.