Scene Evaluation takes forever
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
- laihinchun
- Posts: 2
- Joined: Fri Jun 16, 2017 10:35 am
Seriously, I'm pretty much done with Octane and switching over to FStorm. Rendering a scene without getting stuck on "Scene Evaluation" is like a hit-or-miss
- paride4331
- Posts: 3808
- Joined: Fri Sep 18, 2015 7:19 am
Hi laihinchun,
Could you kindly explain in detail what kind of issues,
what about your hardware configuration and Octane 3dsMax plugin version are you using?
Possibly share your scene with the issue listed (even in PM)
Regards
Paride
Could you kindly explain in detail what kind of issues,
what about your hardware configuration and Octane 3dsMax plugin version are you using?
Possibly share your scene with the issue listed (even in PM)
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
paride4331 wrote:Hi laihinchun,
Could you kindly explain in detail what kind of issues,
what about your hardware configuration and Octane 3dsMax plugin version are you using?
Possibly share your scene with the issue listed (even in PM)
Regards
Paride
same here. if file uses 5-6 Gb of vram and has a lot of itoo forest trees and movable proxies like cars it does take 1 - 2 minute to open octane viewport and during rendering about 30-45 seconds to load before actual rendering each frame
- paride4331
- Posts: 3808
- Joined: Fri Sep 18, 2015 7:19 am
Hi coilbook,
Speaking on overview it is difficult to give answers.
5-6GB is not a little and what's inside the scene you have, geometries, instances, displacement, particles, volumes .. etc
How much your CPU is fast and how many cores, how much ram, hdd or m.2, how many lanes each GPU has, etc..
In short, to say is fast or not fast is to say is nice or ugly.
Paride
Speaking on overview it is difficult to give answers.
5-6GB is not a little and what's inside the scene you have, geometries, instances, displacement, particles, volumes .. etc
How much your CPU is fast and how many cores, how much ram, hdd or m.2, how many lanes each GPU has, etc..
In short, to say is fast or not fast is to say is nice or ugly.
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
Thank you. You are right 6 Gb is a lot. And some of our slaves have slow CPUs and RAM because I did not know octane uses that too.paride4331 wrote:Hi coilbook,
Speaking on overview it is difficult to give answers.
5-6GB is not a little and what's inside the scene you have, geometries, instances, displacement, particles, volumes .. etc
How much your CPU is fast and how many cores, how much ram, hdd or m.2, how many lanes each GPU has, etc..
In short, to say is fast or not fast is to say is nice or ugly.
Paride
- paride4331
- Posts: 3808
- Joined: Fri Sep 18, 2015 7:19 am
Hi coilbook,
We were talking about voxelization time, so no slaves.
Are you thinking issues you're referring depend on network render?
Regards
Paride
We were talking about voxelization time, so no slaves.
Are you thinking issues you're referring depend on network render?
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
seems like scene evaluation takes forever when we have fire and liquids in the scene. Even though scene can be 2-3gb it takes 5 minutes or more to open octane viewport.
and it is on master. Slaves take even longer
and still after rendering is over and then continuing working and clicking open octane viewport max crashes
and it is on master. Slaves take even longer
and still after rendering is over and then continuing working and clicking open octane viewport max crashes
- laihinchun
- Posts: 2
- Joined: Fri Jun 16, 2017 10:35 am
Mine was stuck at scene evaluation for over 30 mins and never refreshed ever since. My specs are i7 6800, 32GB RAM, gtx 1080 x2 and my scene is pretty complex, using approximately 6.2 gb vram + 1gb cpu.coilbook wrote:seems like scene evaluation takes forever when we have fire and liquids in the scene. Even though scene can be 2-3gb it takes 5 minutes or more to open octane viewport.
and it is on master. Slaves take even longer
and still after rendering is over and then continuing working and clicking open octane viewport max crashes
But well, as soon as I finish this project i'm gonna move on from Octane. So I'm not planning to fix this shit.
It's ridiculous and time wasting. The other night I could have started the render at 2am and left the office.
But instead, the viewport never got pass the scene evaluation stage. I ended up got lucky at around 9am to begin the render.
- mark0spasic
- Posts: 146
- Joined: Thu Mar 08, 2012 4:46 pm
Maybe you runout of system RAM in some scenes 32GB is not enough.laihinchun wrote:Mine was stuck at scene evaluation for over 30 mins and never refreshed ever since. My specs are i7 6800, 32GB RAM, gtx 1080 x2 and my scene is pretty complex, using approximately 6.2 gb vram + 1gb cpu.coilbook wrote:seems like scene evaluation takes forever when we have fire and liquids in the scene. Even though scene can be 2-3gb it takes 5 minutes or more to open octane viewport.
and it is on master. Slaves take even longer
and still after rendering is over and then continuing working and clicking open octane viewport max crashes
But well, as soon as I finish this project i'm gonna move on from Octane. So I'm not planning to fix this shit.
It's ridiculous and time wasting. The other night I could have started the render at 2am and left the office.
But instead, the viewport never got pass the scene evaluation stage. I ended up got lucky at around 9am to begin the render.
AMD FX 6300, 24 GB RAM, Gigabyte ga-990fxa-ud5, 2x MSI GTX 780 3GB
- paride4331
- Posts: 3808
- Joined: Fri Sep 18, 2015 7:19 am
Hi laihinchun,
mark0spasic is right, your issue probably depends on RAM, Octane Render eats a lot of RAM in the voxeling phase.
3dsMax eats a lot of RAM too, probably your OS works in paging and stacks and slacks.
Paride
mark0spasic is right, your issue probably depends on RAM, Octane Render eats a lot of RAM in the voxeling phase.
3dsMax eats a lot of RAM too, probably your OS works in paging and stacks and slacks.
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid