Author Topic: After rendering is done a image i/o error appears and doesn't save renders  (Read 2855 times)

2024-06-01, 20:27:42

Paul_Phoenix_999

  • Active Users
  • **
  • Posts: 8
    • View Profile
Hello,

so in our team we use bath render plugin to render multiple renders overnight, and what ends up happening is let's say we put 4 files in rendering, when the first one ends it shows the image i/o error, it not only doesn't save  that render but also stops other files from staring rendering, so in whole night only 1 render is completed and other 3 renders are still pending

we tested it with Vray and it never had an issue with that, i was wondering if its a bug or we're doing something wrong

what we have done so far is, put path in common tab then updating render elements and checking it in asset tracing to see if both path are same and the folder exists, we have checked it many times and it's correct yet this error is unavoidable

we render usually in 6k x 4k resoultion in TIF format, on every machine theres 48-96 gb of ram available so we extremely rarely face any low on ram issue

Any hint or any workaround would be extremely helpful

Thank You

2024-06-03, 12:19:47
Reply #1

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 796
    • View Profile
Which batch render plugin you are using?

What version of 3ds Max and Corona you are using?

Are you saving the files locally or on network drive?
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2024-06-03, 12:51:40
Reply #2

pokoy

  • Active Users
  • **
  • Posts: 1982
    • View Profile
Maybe totally unrelated but I recently had a similar problem where exr files would throw an I/O error and not save.
Turns out it was an Umlaut in the path name and the solution was to remove any non-english characters in the path or filename.

2024-06-03, 13:04:34
Reply #3

Byteman3D

  • Active Users
  • **
  • Posts: 106
    • View Profile
It might be related to a couple of reason, having the same heading, can't write the file for some reason.

I've had the issue once with PNG files, apparently due to "some corruption" in the PNG I/O plugin.
It might happen simply because the program can't access any of the folders it has to access at the time of saving. Not only the output files but sender elements or God knows, whatever configuration file that has to be read or written and can't succeed.
The frame of such errors can be so wide that you can experience things you can never imagine. (Even the folder name length exceeding 256 characters cause problems or some Unicode character that doesn't represent a valid equivalent for the OS.)

3DS Max Batch system is also not so intuitive. I enter parhs, file names but at the end of the day, find some XXCamera _View 01 like naming scheme which I could never figure out how I have achieved that.

This is very probably Max issue, and in the Vray instant, you probably didn't have the same thing causing the problem.

2024-06-03, 15:44:48
Reply #4

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13625
  • Marcin
    • View Profile
There is this:
The message “Error Creating File Output”: caused by 3ds Max bug that adds non-existing paths to render elements.
Solution: go through your render elements and delete all non-existing output paths, or fix render element paths in the asset tracker (Shift+T).

But it would be great to know that your actual error message says. A screenshot would be great.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2024-06-03, 18:50:45
Reply #5

Paul_Phoenix_999

  • Active Users
  • **
  • Posts: 8
    • View Profile
Which batch render plugin you are using?

What version of 3ds Max and Corona you are using?

Are you saving the files locally or on network drive?

I don't know the batch render version but it's not it's fault, because earlier we used to open 4 3ds max and start rendering in all of them at once, and we would still get this error

3ds max version 2022 and corona version 9

files are currently on network drive but I don't remember if we had same issue in local saves

2024-06-03, 18:53:00
Reply #6

Paul_Phoenix_999

  • Active Users
  • **
  • Posts: 8
    • View Profile
Maybe totally unrelated but I recently had a similar problem where exr files would throw an I/O error and not save.
Turns out it was an Umlaut in the path name and the solution was to remove any non-english characters in the path or filename.

I see, but unfortunately we have only english characters in our file names

2024-06-03, 18:58:59
Reply #7

Paul_Phoenix_999

  • Active Users
  • **
  • Posts: 8
    • View Profile
It might be related to a couple of reason, having the same heading, can't write the file for some reason.

I've had the issue once with PNG files, apparently due to "some corruption" in the PNG I/O plugin.
It might happen simply because the program can't access any of the folders it has to access at the time of saving. Not only the output files but sender elements or God knows, whatever configuration file that has to be read or written and can't succeed.
The frame of such errors can be so wide that you can experience things you can never imagine. (Even the folder name length exceeding 256 characters cause problems or some Unicode character that doesn't represent a valid equivalent for the OS.)

3DS Max Batch system is also not so intuitive. I enter parhs, file names but at the end of the day, find some XXCamera _View 01 like naming scheme which I could never figure out how I have achieved that.

This is very probably Max issue, and in the Vray instant, you probably didn't have the same thing causing the problem.

having the same heading, can you elaborate on that

and for format we usually use 2 formats, Jpeg and TIFF and we experience this error on both formats, and out path names are also within 256 characters, in cases where it exceeded we were notified before the render begin ig

as for batch plugin, yes it might be the issue as well but in another firm uses network rendering and they never ever had this issue appear,

and it being a max issue, absolutely possible but I have little to no hope of getting it fixed from their forums since most of my coworkers have to go to other sites to find solution to things that were asked on autodesk forums

2024-06-03, 19:02:06
Reply #8

Paul_Phoenix_999

  • Active Users
  • **
  • Posts: 8
    • View Profile
There is this:
The message “Error Creating File Output”: caused by 3ds Max bug that adds non-existing paths to render elements.
Solution: go through your render elements and delete all non-existing output paths, or fix render element paths in the asset tracker (Shift+T).

But it would be great to know that your actual error message says. A screenshot would be great.

Thanks maru but we have tried doing that as well, when I'm setting up file to render high resolution what I do is put render path and file name in common tab and then refresh render elements by loading up a preset and choosing only render elements, then I check it with asset tracking to see if all the path that we entered are correct

and the actual screenshot, I'll have to ask but I'll try to get it posted here if possible