vfb core error render region to raw image file, error writing tile to exr

[digitarch]

"vfb core error render region to raw image file, error writing tile to exr"

happens in some scenes
when spawning big still images from around 8000x4000
max framebuffer disabled, small output size
not getting resolution from max famebuffer
render to memory framebuffer disabled
region render in both framebuffers disabled
when saving the vrayrawimagefile directly to exr
the exr is created, file size seems ok, but file is corrupt

no error when rendering small resolution images
any idea?
matthias

[digitarch]

oops, it works when render to vray memory framebuffer is disabled. is there (sometimes) an magic maximum size for showing the framebuffer?

[vlado]

Is this on a 32-bit machine?

Best regards,
Vlado

[digitarch]

4 quadcores spawning, all of them are xp64sp2, some with only 4gb.
it works when:
not saving to vrimg or
not spawing or
render to memory framebuffer disabled or
resolution smaller than 2500x1000 (with this scene...)

[digitarch]

hmm, tried some other scenes, all creating the
"vfb core error render region to raw image file, error writing tile to exr"
error and an corrupt exr-file when spawning stills with bigger resolutions.
works when not spawning or rendering small images ....

[digitarch]

i add the exact error code, maybe it helps:
[VFBCore::SetRegion]Error creating raw image file [ExrFile::WTRegion] Error writing tile to .exr file

[digitarch]

hmmm, yesterday i had a completely new scene, rendered fine with spawners and saving the vrayrawimagefile to exr.
then i had the error just once after upping the resolution, the second try and all following worked then. might it be possible its some network timeout problem creating/accessing the exr?
Matthias

[digitarch]

it´s still me, i need working exr please, any help out there?

very interesting: when enabling render region i don´t get the error!
When NOT render region my .exr are still corrrupt when rendering bigger sizes
when setting the render region to the whole image i also get the error.

[digitarch]

Hey Vlado, any idea?
When saving to vrimg and converting manually via vrimg2exr.exe everything is fine. When saving directly to .exr i get corrupt files.

[vlado]

Are you saving to a network location? If yes, you can try a local file and see if it helps. Other than that, I'm not sure what the problem might be - it seems to be with the OpenEXR library itself; we will have to examine the code to see where things might go wrong.

Best regards,
Vlado

[digitarch]

Vlado,
indeed it works when saving to an local drive!!!! As everything else works concerning networking (bitmap paths, unc, access rights, ...) i dont have a clue what might help.
Matthias

[digitarch]

rechecked the situation with different scenes: saving the exr while spawning to an local drive workes everytime. Using an network location works depending on the image size - this gives me the impression it might be some accessing timeout problem as small exr images work out fine, big ones are created corrupt.

[Jacob Hutson]

i have the same problem too saving exrs to UNC name
same with local paths but i only use UNC anyway.

i hadnt tried locally.
the whole UNC vs drive mapping is messy and inconsistant in the vrimage and GI maps dialog boxes.
hopefully theyll get it sorted for v2 or before (nudge nudge)

[vlado]

the whole UNC vs drive mapping is messy and inconsistant in the vrimage and GI maps dialog boxes.

Which part of it is inconsistent?

Best regards,
Vlado