Image I/O error

[Vizioen]

I'm getting this error now after rendering a +14K render and saving to .tga. Some of the render elements don't want to save. Some do. I don't really have time to troubleshoot but I had this error once in a blue moon, and I'm surprised it's still there. Might this be related to big resolutions?

[hermit.crab]

It might. Usually, the I/O error is related to memory. Does it appear if you render lower resolution images? Also, which output are you using - the 3ds Max native or V-Ray's? PS. This should be useful.

[Vizioen]

Well I'm used to rendering larger ones actually. 14K is not that big. I'm used to 20K as well. Rarely have problems. The scene wasn't more complex as the other ones and only a few render elements. But I didn't check my memory though as I had another scene open. Although with 128GB ram should have been more than enough. I'll keep an eye out next time. Thanks.

Screenshot says 25 GB used btw. I can hardly believe the rest of my system was using more.

[hermit.crab]

More questions: Do you have enough disk space in the location you're saving? Are you saving to a network? If yes, try saving locally. Are there any permissions set (i.e. Read only/access restrictions) in the output folder?

[Vizioen]

I'm saving locally. The disks have a few TB left, so that's not the problem either.

[hermit.crab]

I am not sure if this is the case, but I managed to reproduce the error by setting the output path to a non-existent one. Also, I read on various forums that non-Latin characters may also cause it.
I can confirm denying read/write restrictions also causes it.

[Vizioen]

Sorry to disappoint. Output paths are fine, because some of the render elements do get saved, around 25% of them were saved. Path only contained letters numbers, dots and forward slashes.

[Joelaff]

I have seen issues with path name lengths-- where some elements exceed a limit and other elements don't. Try a shorter filename and path name in general perhaps?

[Vizioen]

Thanks for all the tips. I'm very careful with path names and lengths. And everything is kept very short and well within the 256 character limit. I will update this thread if something else arises. Thanks guys.

[algato]

Hello Vizioen,
for me, the safest way at such high resolutions is always via pure vrimg, with disabled memory frame buffer.
After that you can convert the result to exr and extract anything you need.

That way i get ever poster siize work well done.

Kind regards
algato

[Vizioen]

Yeah I also start using vrimg more and more to save my images. Although I would really like a standalone VFB to be able to edit/export them to whatever I want. Now it's just a hassle opening 3dsMax.

[^Lele^]

You can produce tiled, bufferless EXRs without having to go throuhg the vrimg format.
Simply choose the EXR extension from the file save dialog of the raw file save.

[Vizioen]

Yes thank you Lele, I know, but I like the VFB for it's Lightmix, Tonemapping, easy cryptomatte masks, etc. The more abilities you guys add, the more powerful the VFB is becoming and the more it's used as a (preliminary) compositing tool (at least here).

[^Lele^]

Oh, i was replying to algato , only about the saving of tiled vrimg files to convert later.

[kosso_olli]

I have seen issues with path name lengths-- where some elements exceed a limit and other elements don't. Try a shorter filename and path name in general perhaps?

I'd put my bet on this as well.