Studio stalls / infinite loop when going from iray render back to texture.
I got a somewhat complex scene, no question. Studio renders fine (viewport and render set to photorealistic), but when I want to go back to the more simple Texture Shading viewport is in an infinite loading / calculating loop. While the render view took around 1min to show up with quite a good quality going back is impossible (waited around 15min, Studio screen got a whitish taint on it, Win10 says "isn't responding".
So I started a real render (into window) just in HD and after 45min the render engine did around 1/3 of the work, fine. Then I canceled the render and wanted to save the partly rendered image (like I did before 10s of times). And again, Studio stalls or better freezes, "no response from program" and 45min of rendering time to the bin. And I fear - if this persists - the work of one week to the bin!
Additional the "interactive" mode both set in Draw Settings and Render Settings make Studio crash as soon as the scene is a little more than just one figure in it - every time. Of course I can send the crashlogs, but there are around 20 at the moment.
My machine is 6 core, nvidia 2080S, 32GB RAM. And that shouldn't be a real problem as the photorealistic render works most of the times. Workload when freezing is 100%GPU, 1/12 Threads at 100%, the others near idle, VideoRAM at 96% full. Win10 doesn't freeze, just Studio.
Studio is a real nice program, *but* with these uncertainties - you never know if your work will still be able to get loaded and then rendered in the end - makes working with it frustrating.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
If this is something that has suddenly started and having no problems previously, it smells of W10 updates that have made changes to the system.
Check the version of GPU drivers.
Well, I hope it's that simple. nVidia shipped out new drivers 456.71 yesterday - I install them now. My usual habit is to install new GPU drivers almost as soon as they are released, so I can't tell if it's some previous driver update that causes the problems. As I play around with Studio for just over a month now I can't really tell if it was stabile before, as with growing skills I put more into my scenes.
But I fear it's not the drivers.
Thank you! I installed new drivers (the other were around 2 weeks old) and it seems to work fine. Still I am suspicious that it was "just the drivers"
(as I am usually very sensible with driver updates). But even canceling the render lets me return to the viewport.
Remember, you are not the only one meddling with your computer... W10 has been built with the idea that MS knows better, even when they don't.
Windows Update has a reputation for replacing actual current NVidia drivers with lower spec generic drivers. The most annoying thing is that it doesn't happen every time, only when you forget to check after Update Tuesday.
yes, I should have known better. Thanks for the reminder. Day is saved and man... this was frustrating!
Hmm.. I thought that at least if you're using Win 10 pro, there are things that you can specifically select to exclude from updates, such as drivers for dedicated graphics cards? Sometimes I wonder if its worth getting the enterprise version and avoid the driver update headaches completely.
Is that possible? I thought the Enterprise Edition only allowed delaying updates (hopefully until all the bugs inflicted on everyone else are worked out), not stopping them completely.
Enterprise edition allows you to configure updates as you will with group policies. My workplace has Enterprise, and they tend to do updates every two months, more or less -- they flatly refuse to do monthly updates, since they can't test them with all of the major applications in that amount of time while doing everything else they need to do. Pro -- the step down from Enterprise/Education -- allows you to delay monthly updates for up to 35 days, and the twice-yearly major updates can be delayed up to a year. Or could before this upcoming edition; Microsoft reportedly removed that option because people were delaying the semi-annual updates so long that a given installation would fall out of support. (There's a registry hack to get around that ... but it IS a registry hack, which a lot of people aren't comfortable doing.) Microsoft is also reportedly forcing some people who are on 1903 (or 19H1, as it will now be called) or earlier versions of W10 to update to the most recent 20H2 (2009 that was), but it's happening so randomly that nobody is quite sure what the trigger is.
All that said, there are a couple of ways to block driver updates.
https://www.minitool.com/news/disable-automatic-driver-updates-win-10-009.html
https://www.howtogeek.com/302595/how-to-stop-windows-10-from-automatically-updating-hardware-drivers/
Note: This is as blunt a tool as Windows 10 has; it will stop ALL driver updates, so it's then on you to update as needed from the manufacturer as needed.