I have 2 scenes that are really large, that render fine in the live viewer. But when I use the picture viewer they take forever.
So instead of using the picture viewer at 2 minutes per frame, I have to go to each frame in the live viewer and save each frame out by itself at 5 seconds per frame. Its like its resending the data to my render nodes every single frame. I had a similar problem with modo when I used instances. Could this be the case here too?
C4D R19 and my Plugin is OctaneRender 4.00 (4000021). Cant really test updating at this point of the project because we don't have enough time.
Any ideas?!
Thanks!
Picture Viewer Taking Way Longer Than Live Viewer
Moderators: ChrisHekman, aoktar
Read FAQ under help/tutorials.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks. I couldn't find anything specific to my problem on there. But it at least sprung a light bulb to just select everything and put it on a null with an octane object tag. Now it doesn't update every frame. I had only movable update in the render settings before....
Win 10, Threadripper Pro, Dual 3090s
It sounds like you have subdivision and different tesellation factor for PV.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Weird? I will have to look into that topic more. In the scene out of 718 objects only 1 of them is a subdivision surface.. I guess I could try it without that object and see if thats the problem? Or does this run deeper than that?
There is a lot of objects from CAD in the scene. Could that be? But like I said, its fixed now that everything is in a null with an octane object tag applied.
Thanks
There is a lot of objects from CAD in the scene. Could that be? But like I said, its fixed now that everything is in a null with an octane object tag applied.
Thanks
Win 10, Threadripper Pro, Dual 3090s
Ok so it will be fixed without applying tag but use "All movable". It gives the same scene structure for Octane side.LFedit wrote:Weird? I will have to look into that topic more. In the scene out of 718 objects only 1 of them is a subdivision surface.. I guess I could try it without that object and see if thats the problem? Or does this run deeper than that?
There is a lot of objects from CAD in the scene. Could that be? But like I said, its fixed now that everything is in a null with an octane object tag applied.
Thanks
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw