How's it going.
Both IPR and rendering a frame through the buffer are working normally.
I am having issues with Batch rendering with Octane for Maya.
When I try a normal batch render from the Render-Batch Render option, It says:
Result: Rendering with OctaneRender®... //
but then nothing ever happens.
Next I closed out of Maya and right clicked on my scene, then hit render. This time I got more info, but this time it just does this forever.
[Check out Attachment]
I am also using GPU-Z to and my GPU load never goes above 0% using both methods.
Thanks!
Matt
Batch Rendering Issues
Moderator: JimStar
Update on my situation, now IPR and normal frame buffer render stopped working.
I have tried:
unloading and reloading the plugin
rebooting
reinstalling both standalone and the Maya plugin
making a clean scene and importing the old scene
So far nothing has worked.
When I hit IPR render it renders to 18 samples and stops every time even though I have max samples set to 5 thousand.
When I hit normal frame buffer it just freezes Maya.
I have tried:
unloading and reloading the plugin
rebooting
reinstalling both standalone and the Maya plugin
making a clean scene and importing the old scene
So far nothing has worked.
When I hit IPR render it renders to 18 samples and stops every time even though I have max samples set to 5 thousand.
When I hit normal frame buffer it just freezes Maya.
Windows 10| Octane for Maya 2017 | NVIDIA Quadro M6000 | 64GB | i7 - 5820K
- k.a.schubert
- Posts: 137
- Joined: Mon Feb 22, 2016 2:52 am
Hi mrviviano,
I busy with the v3 alpha release this week,
but after that batch rendering is on my plate.
Sorry for the inconvenience,
Kai
I busy with the v3 alpha release this week,
but after that batch rendering is on my plate.
Sorry for the inconvenience,
Kai
i am running into the same issue. any fix for that besides opening the maya window?
where is the bug hiding?
thats really terrible.
hopefully v3 will be solid very soon.
so many issues, bugs and workarounds.withe the maya plugin.
where is the bug hiding?
thats really terrible.
hopefully v3 will be solid very soon.
so many issues, bugs and workarounds.withe the maya plugin.
I hate to say that but octane for Maya is everything except production ready.
these are some issues that I am facing in last month:
Batch render from Maya just saves .exr files with 12 MB size but all blank (file names are frame.0001.passes.exr)
Batch render from command line works but it doesn't save Beauty pass just other passes.
Can not support UDIM for textures
Can't expand environment variables in paths
Can't show textures on viewport
After changing a texture the old texure remains on cache memory and I should change the file name
Can't handle Maya utilities
and the worst is Otoy's low resources for answering our questions.
and they are far away from building a new production ready version yet.
these are some issues that I am facing in last month:
Batch render from Maya just saves .exr files with 12 MB size but all blank (file names are frame.0001.passes.exr)
Batch render from command line works but it doesn't save Beauty pass just other passes.
Can not support UDIM for textures
Can't expand environment variables in paths
Can't show textures on viewport
After changing a texture the old texure remains on cache memory and I should change the file name
Can't handle Maya utilities
and the worst is Otoy's low resources for answering our questions.
and they are far away from building a new production ready version yet.
Maya 2016 SP6, Windows 10 x64, 4 x GTX 980 Ti
- cyrillweiss
- Posts: 91
- Joined: Wed Jun 02, 2010 2:52 pm
Hi mrviviano
I had this situation as well once and narrowed it down to a missing or big UV map (not normalized) of an object.
To make a simple check:
1. Select all objects
2. open UV texture editor
3. select "normalize" in the "polygon" menu
4. save scene to a new file
5. batch render
If this works, you need to find the object with the UV map, octane gets stuck with and correct it.
Hope this helps
cheers
cyr
I had this situation as well once and narrowed it down to a missing or big UV map (not normalized) of an object.
To make a simple check:
1. Select all objects
2. open UV texture editor
3. select "normalize" in the "polygon" menu
4. save scene to a new file
5. batch render
If this works, you need to find the object with the UV map, octane gets stuck with and correct it.
Hope this helps
cheers
cyr
HW01:WIN10x64/X79/i7-3930K/64gb/GPU:1xTitan X, GTX 1080ti, SW:Maya2018/2019, Cinema 4D R20
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
- k.a.schubert
- Posts: 137
- Joined: Mon Feb 22, 2016 2:52 am
@cyrillweiss
Thanks for sharing your experience!
Thanks for sharing your experience!
This has been happening for me as well. I've noticed my batch consistently stops after rendering for about 15 min or about 10 or 12 frames.
Also, it won't render anything if it has to re-write over an existing file. I get the same results if I launch via explorer (right click over file) or the Maya Plug-in. I've never ran a batch from the Standalone.
I'm running the latest version of the Octane Plug-in. I really could use some help with this!
Also, it won't render anything if it has to re-write over an existing file. I get the same results if I launch via explorer (right click over file) or the Maya Plug-in. I've never ran a batch from the Standalone.
I'm running the latest version of the Octane Plug-in. I really could use some help with this!
Ryan Darling
http://www.RyanDarling3D.com
http://www.Darling3D.com
System Spec's:
Windows 10 64x | i7 - 5820K 3.30Ghz| 2x 970 | 64GB Ram
http://www.RyanDarling3D.com
http://www.Darling3D.com
System Spec's:
Windows 10 64x | i7 - 5820K 3.30Ghz| 2x 970 | 64GB Ram
Just to be sure, are you using the 2.25_7.30 version of the plugin ?RyDarling wrote: I'm running the latest version of the Octane Plug-in. I really could use some help with this!
Hard to help without more information or a minimal maya example scene containing the problem.
But I can try to guess:
- Batch render failing is often caused by GPU heat problem, did you try to monitor your GPU during batch render ?
- Motion blur for deformable mesh can take a very very long time to export for some frames, sometimes even never succeed.
In this case the batch render seems to be stuck.
- Do you use network rendering ?
Pascal ANDRE