creed2003 opened this issue on Sep 21, 2014 · 5 posts
creed2003 posted Sun, 21 September 2014 at 7:26 PM
Just bought Vue 2014 Complete and today I noticed its maxing out my CPU to 100% when rendering. Never noticed this with other versions of Vue and my other PC. Of course with my old PC I never bothered to check or look. The program crashed on me so I brought up Task Manager to check my system statistics and that's when I noticed it. Should I be concerned or is it no big deal?
Misangelic posted Sun, 21 September 2014 at 7:38 PM
It's perfectly normal.
In my experience all rendering programmes will max out your CPU when rendering. Some like Reality/Luxrender offer the option of setting how many CPU cores to use, but most will just use all the cores/threads.
If you didn't already know, the maximum number of cores/threads you can use in Vue Complete is 8.
You will probably find you can still do other low level things on your computer while Vue is rendering, such as listening to music, watching a movie or using a browser, etc. But something like playing a CPU intensive video game is a no-go
The exhiliration of obscenity, the obscenity of obviousness, the obviousness of power, the power of simulation... ravishing Hyperrealism... mind blowing!
creed2003 posted Sun, 21 September 2014 at 8:13 PM
Thank You!
czarnyrobert posted Wed, 24 September 2014 at 1:45 AM
Hi Jim,
Once I had Vue 6 Infinite crashing during rendering and it was cused by CPU overheating. (Strangely other versions of Vue rendered the same scene without crash on same computer, also no other software crashed). After I cleaned up CPU radiator, Vue 6 rendering crashes stopped.
However rendering crash can be caused by something in the scene. Then it Vue will crash at the same moment every time you render it. CPU overheating crashes happened at random.
You should check if your CPU has good cooling, check CPU temperature when rendering (there are dedicated software for that - probably you should get some with your motherboard)
You can try to assign les CPU cores to Vue - you can do it with Windows Task Manager (example from Windows XP 64):
Another reason for crashes can be memmory modules running at too high speed. You shouldn't use any acceleration to your system when rendering in Vue, and check if memory modules have been certified for your motherboard and that they run at nominal speed. You can also try to slow down your system and chek if it helps.
Anyway, Vue is very crashing software, so crashes happens quite often, even if your computer is perfectly OK.
Best 3D vegetation from Green Gene
creed2003 posted Wed, 24 September 2014 at 7:03 PM
Quote - Hi Jim,
Once I had Vue 6 Infinite crashing during rendering and it was cused by CPU overheating. (Strangely other versions of Vue rendered the same scene without crash on same computer, also no other software crashed). After I cleaned up CPU radiator, Vue 6 rendering crashes stopped.
However rendering crash can be caused by something in the scene. Then it Vue will crash at the same moment every time you render it. CPU overheating crashes happened at random.
You should check if your CPU has good cooling, check CPU temperature when rendering (there are dedicated software for that - probably you should get some with your motherboard)
You can try to assign les CPU cores to Vue - you can do it with Windows Task Manager (example from Windows XP 64):
Another reason for crashes can be memmory modules running at too high speed. You shouldn't use any acceleration to your system when rendering in Vue, and check if memory modules have been certified for your motherboard and that they run at nominal speed. You can also try to slow down your system and chek if it helps.
Anyway, Vue is very crashing software, so crashes happens quite often, even if your computer is perfectly OK.
Best 3D vegetation from Green Gene
Thanks for the tips! This is a brand new laptop, about 5 days old, so I'm confident it's not the computer. What's funny is Plant Factory also crashes but I can run other programs like Daz and Terregen rendering large scenes with no problem.