I know there has been a lot of discussion on Render freezes, but...

malcolmkarpeta_40f9af0b00

[I know there has been a lot of discussion on Render freezes, but] I have read them all and tried various things to no avail. My freezing is only happening on one particular character/scene that I created recently involving G8F Aisling. Past creations are fine, no issues. To my knowledge my strategy for posing, morphing etc has been the same, except on this G8F Aisling character I did venture into the Mesh Smoothing and Collision thingys.

Now, when I open said problem character/scene the progress bar at the bottom of the screen is active (Very slowly) I noticed that it is when this happens that I get the render freezing issue, or "Daz Studio is not responding. Maybe I'm not waiting long eough at the render stage before giving up and force quitting :(

I think it may be something to do with morphing/modifers/smoothers and wotnot so my question is this. Ahem!

What is the progress bar actually doing when I open one of these characters? Knowing this may help me identify my issue

Thank you

Malc

Richard Haseltine

At what point is this putative freezing happening?

malcolmkarpeta_40f9af0b00

Well, it happens as soon as I try to render, the dialogue box opens to say "Rendering" but no preview pane. I wait maybe a few minutes, as that is how long it usually takes, and then go to activity monitor, click Daz Studio and it immediately changes to "DZ not responding" so I close it. Perchance I am not waiting long enough? Maybe I ought to try rendering again and go and clean the oven while it's happening....?

malcolmkarpeta_40f9af0b00

Update Richard: I have just tried to render the problematic scene again but cunningly left the Activity Monitor window open. After about 2 minutes the dreaded "Daz Studio not responding" came up again. I didn't touch it. Honest.

Ah! Now after a couple of minutes the render preview window has opened up again (I render first in 400x300 to test) and the Activity Monitor shows DS working! Spooky.... (This is live news-as it's happening)

I think I may be just too impatient so now it's time to try a full render. I'm going in...

Richard Haseltine

Yes, Not responding means the application is busy in a way that is stopping it from checking the event loop, it doesn't necessarily mean it is hanging irrecoverably.

malcolmkarpeta_40f9af0b00

Wise words once again my friend, wise words. I left DS to it's own devices for a while and indeed it managed to sort out what the heck I was asking of it, not actually "Not responding". A tip for our other readers: Be patient. Now rendering seems to be back to normal.

Many thanks

Malc

RainbowArtist

It might be better if it said 'Busy computing' ( or processing or something like that ) instead of 'Not responding' unless it was actually stuck. Then Not responding'  would let the user know that there was an actual problem instead of just a delay.

Richard Haseltine

"Not repsonding" is a Windows label. Daz might be able to rewrite the code in such a way that it didn't go unresponsive while transferring (or they might not if it's waiting on a driver response), but I can well imagine that would have a serious impact on performance and might open the way to conflicts if a contradictory instruction was issued in mid transfer.

malcolmkarpeta_40f9af0b00

RainbowArtist and Richard Heseltine, sorry for the late acknowledgement but have been away for a while. Many thanks for the comments, I understand and agree with both.

Malc

nonesuch00

I have noticed that too with the newer DAZ Studio Public Betas; meaning DS 4.11+ & 4.12+, that rendering in iRay is seizing my computer I/O much more persistently than in the past despite that I have created a shortcut to start DAZ Studio with CPU affinity configured such that DAZ Studio only can use 4 or 8 available CPU threads (i.e. DS shortcut command line is started with "/c start "DAZ Studio" /affinity F" as arguments in it).

malcolmkarpeta_40f9af0b00

nonesuch00, if I understood all of that I would probably try it! :) However, currently my renders have tolerable durations and I leave DS to do it's own thing now when shutting down. Thanks for the input :)