Maya batch not outputting any files

[jangwee]

Hey guys,

So I've run into a problem rendering animation scene in Maya batch.
I've queued up a bunch of renders in Backburner to output different LayerMask InfoPasses, but renders just go through render process and don't write any files.
GPU usage goes up as expected but nothing comes out after it's finished.

Same maya scenes render with same version of Octane plugin on home PC but on work PC it just fails to output any files.
Digging thru render logs i found these lines but not sure why it's failing?? (i've removed project folder path names for confidentiality reasons)

0:00 ...done creating meshes
0:00 Octane mesh data is set to render engine.
0:01 Octane: Scene export complete.
0:01 ...done
Octane: Refreshed image, 173 samples per pixel of 300
Octane: Refreshed image, 300 samples per pixel of 300
ERROR, Cannot open file E:/-----/LayerMask_Bag/LayerMask_Bag.0121.png; ensure that it exists and is of type "PNG"
ERROR, No more internal memory
Error: line 0: Failed to open output file: E:/-----/LayerMask_Bag/LayerMask_Bag.0121.png
Error: Octane: Error saving frame 121 ("png" image to "E:/-----/LayerMask_Bag/LayerMask_Bag.0121.png"): (kFailure): Unexpected Internal Failure

Octane: starting animation of frame 122...

At first I thought it might be something not translating correctly to Backburner so tried rendering in Maya batch from Maya GUI session. Made no difference.
I'm using Maya 2016 (SP4), Octane v 2.23.2, and OctaneForMaya plugin v2.23.2 (7.9).

Any ideas???
I'm stumped.

[abreukers]

hi jangwee, does your work pc have exactly the same hardware specs as your home pc? the work pc is saying 'No more internal memory'. that seems to be a vram thing.

[jangwee]

Yeh I though that too but the scene is only simple setup with no textures, and not even close to hitting VRAM limit when loaded to render.

Both PCs are running 2x Titans each.

Work PC is actually much newer and has more onboard RAM.
Home PC is older i7 930, 24GB RAM, 2x Titans
Work PC is i7 4790, 32GB RAM, 2x Titans.
Both on Win7 Pro.

After checking other things, the only other difference I can find apart from motherboard and obvious hardware difference is Home PC is on Maya 2016 (ServicePack2) where work PC is ServicePack4.
Unless something maybe broke in Maya batch process with latest maya update, I'm not sure what's going on here.

[JimStar]

According to the log the error happens inside Maya code. The plugin uses Maya API to save the image and the error you see in the log is reported by Maya, not by the plugin.
So, looks like something is different on the computer where it happens. It's hard to guess from here...
Be sure that the disk E:\ exists on this computer. Be sure the Maya batch process has the rights to write to this path. I see some strange named folder name in path - try to play with path... Try to watch the memory usage during rendering...

[jangwee]

Thanks Jim,

I've been trying again to isolate different things and seems to only fail to output files when I use the output filename to nested folders.
For instance, if I use the flags to output files with "<RenderLayer>" as folder and filename (eg. "SceneNumber/<RenderLayer>/<RenderLayer>.0001.png"),
it fails to output files when rendering.
If I only have flags for actual filename it works fine, (eg. "SceneNumber/<RenderLayer>.0001.png").
Does same this with explicitly named folders too. Will only output to one folder deep.

Never come across this kind of behaviour in all my years of using maya with different renderers. Very strange.
Does same thing on both my PCs.

This is a problem when outputting large amounts of files for animations across many scenes within project.
Makes for very messy render file outputs and folder structures.

[Wenneker]

Octane only outputting one folder deep is something that has been like this for quite some time.

viewtopic.php?f=28&t=40299&p=187481&hil ... er#p187481

[jangwee]

Thanks mate. I wish I'd seen that post before flipping out trying to figure out what was wrong.
Hope this gets fixed in future.
That's a pretty critical production pipeline feature