DS unresponsive / display driver recovery when loading object. why?
sriesch
Posts: 4,243
I'm hoping somebody can provide insight as to why loading a particular object causes DS to become mostly unresponsive (if I have display optimization set to none) or causes the display driver to stop working then recover (if I have display optimization set to best), with the goal of either a workaround or a system upgrade to handle it if appropriate.
Random facts that may or may not pertain:
To trigger it, all I have to do is double-click to load the "EMRC Crag RockA50k.duf" object from the content library, (sometimes then frame it, other times that's not needed) then wait. with display optimization set to best I get the video driver recovery message. DS is unresponsive, most of the main screen windows are just blank white, the screen flashes every second or two and CPU is pegged at about 33% for DS, although I have no idea what it's doing. I can do other things without a problem in the background. I am able to exit DS, so it's still responding to some things.
I'm using DS4.8, render engine 3Delight (which works great for this product without conversion even though it is intended for Iray), Windows 7 64-bit, 16GB memory (not even close to being used up)
This looks like a really cool product, and I'd like to be able to use it at it's maximum resolution option.
The product in question is the most detailed crag rock out of the product "formations for rock collection". If I load the lower resolution "EMRC Crag RockA5k.duf" it works fine.

Comments
I have no clue, but I assume you've checked your video drivers are good and up-to-date, and you've re-installed the content that is giving problems?
I have this set & I can render the large crag rock but I use Iray & the latest Daz Studio 4.9.4.122 - I did check in 3DL & could render it there to - I have 32GB Memory & GTX 1080 with the most up to date drivers (385.41)
For Iray you need to make sure you have Instance Optimization set to Memory - If its on Speed then I can't render & my system locks up but that probably does not help you as you are using 3DL anyway.
sorry for the delay, PC maintenance.
I redownloaded the product (and the product it depends on them) and while the downloads hadn't changed, I reinstalled anyway. I also updated to the lastest Nvidia driver. (also Windows updates that are probably unrelated.) Now after loading, framing, and rotating, DS locks up for a number of seconds then just crashes (rather than the previous behavior.) Fault Module Name: nvoglv64.DLL
Time for a bug report as that is the 64 bit OpenGL drivers for your card.
If it only happens when you load this one item then it sounds like a compatibility issue between the OGL systems in DS and the 64 bit Nvidia drivers, one that only shows up when you use this item.
Reporting it won't solve it for me, I'm stuck at DS4.8 so I'll be unable to get a fix if it turns out to be a DS issue.
Ah well, perhaps if the bug is tied to or triggered/revealed by my card's specific drivers I'll be able to get it working with a different card. Won't be changing cards today, but I burn through them like candy so I'll doubtless have another in a few years.
DS 4.8 was known to have some issues with certain models so the fix is to update to latest version. I believe the actual problem was in Iray but the fix is still the same.
Do you recall what the iray issue was or how it came into play, or remember a keyword I can search for to find the discussion in the forums? I'm wondering if there was a workaround since I'm not rendering in Iray. For example the default materials are iray, but if I were to somehow find a way to convert them and save it with the converted 3DL materials, then load only the converted version that is no longer referencing iray could I sidestep the issue, (EDITED TO ADD that specific idea didn't work, but maybe similar ideas?) etc. Probably not but you never know.
Check this out, perhaps it can help you.
scroll down to my comment.
https://www.daz3d.com/forums/discussion/199941/gpu-renders-first-frame-only-for-iray-image-series-then-goes-cpu-only#latest
In my opinon it seems you just have a card that is too weak or too old to keep the scene. The error is opengl so it's the viewport, not the rendering. Proof of it is that you say keeping display optimization to none doesn't crash but it's sluggish. If you didn't yet, you may try to also set texture to performance in the preferences. Or update your video card.