How to get 3DCoat to be a good CPU sharing app ?
Posted 06 May 2012 - 03:24 PM
When I'm doing a render ... my PC becomes unusable for simple other things like
wed-surfing. Can I change some settings to make it better at sharing ?
Posted 08 May 2012 - 03:04 AM
The interruptable behavior of 3DCoat during render on my machine is horrible.
3DCoat does not give back enough CPU cyles and does not poll often enough ...
is not threaded such that ... USER CANCEL can be made to a render.
It is very very hard to do on my machine.
Posted 08 May 2012 - 04:42 PM
Posted 08 May 2012 - 05:17 PM
I agree with digman, you need to head over to the Mantis page and put in an official request there if there isn't one already (do a search first). There are also a number of areas where 3DC could use warnings. You know, prior to beginning an operation that may bring ones PC to it's knees, begging for mercy lol. I've encountered such a warning on a few occasions, but more often than not there isn't one at all and interrupting was next to impossible just as you've stated. I've actually had to hard reset my PC more than once, causing me to lose work in other apps open at the time (hence why I now pre-open task manager... when I remember to heh). An animated icon might also be useful so we can tell whether 3DC is still working or has frozen (like when it seems stuck at X%).
4.5.12A x64 DX CUDA || Windows 7 SP1 x64 || Nvidia GTX670 v353.30 || Intel 3770K @ 4.5 GHz || 16 GB DDR3-1600 || SpaceMouse Pro v10.2.6 r1934 || Intuos4 v6.3.13
Posted 08 May 2012 - 05:53 PM
But this brings up what is for me ... a related issue. The renders are not very "TUNABLE". For example ... if I pick
60 rays per frame ... if I'm doing a turn-table ... 60 rays for frame 1 is maybe much much brighter than 60 rays for frame 2.
Some aspect of brightness is wild at low rays per frame. This makes ray per frame USELESS when it comes to taming down
turn-table render times.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users