Previously rendered scene now will not render; crashes computer
RenderPretender
Posts: 1,041
Hi -
Yesterday, I rendered a particular scene, both in the Aux Viewport and regular render, without issue. Today, I decided to apply Zevos' Bend Control to the character and rerender. Without fail, the scene began crashing the computer when attempting to render in either the Aux preview AND regular render, even at very small resolution. I then removed the Zevo changes because they were the only alteration to the scene (but did not save the file) and tried again. Crash.
I'm hoping that someone can suggest a reason why a particular scene that has been trouble-free in the past now will not render even though there have been no material changes to it at all. Pulling my hair out on this one as it could kill a commissioned series.
Thanks.
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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
A few things to try:
- Open a new scene and merge the old scene in and see if the issue persists.
- Try resaving the scene with a new file name and retry.
- Reset render settings to default and retry.
- Select the Genesis figure and reload Genesis and select "Apply this character to the currently selected Figure(s) and retry.
Thank you... I'll try these suggestions and update... may not be til tomorrow as I need a drink! But I hear you suggesting that the file may somehow have been corrupted, and I was thinking the same thing.
Thank you again in the interim.
Well, unfortunately, none of that worked. And now I'm having the same issue with another file/scene that was previously fine. I might try to reinstall 4.11 in a wild stab because this makes no sense at all. DAZ has apparently decided that it will or will not preview or render at random.
Sorry to hear that, just a thought did you update your Nvidia drivers after installing 4.11?
https://www.nvidia.com/download/index.aspx
I am having the same issue with 4.11. Strangely, 4.11 Public Beta is much more stable for me although it is supposed to be the same version as the general release.
Is the issue related to prior saved scenes only or to all scenes including new ones?
I' rendering on CPU, and always have been. So perhaps this isn't applicable?
I hate to say it, but I take some solace in your pain. :( Come to think of it, this may have started after I updated to 4.11. Can one roll back to a more stable version easily?
Not unless you kep the 4.10 installer
Well, what finally broke the logjam with this scene and got it past the initial calculations was that there were at least ten point lights in the scene I'm using that were buried in a group, in addition to the lighting rig I'm using. Once I shut those point lights off, the render finished successfully. I had just happened to notice that my gear only supports eight lights, so this was dumb luck.
I upgraded to 4.11 through DIM. Is there a way to use a 4.10 installer through DIM?
I just did a test, re-rendering an unchanged scene that successfully rendered this morning, but this afternoon, crashed a freshly rebooted system. I have to suspect that these issues I and at least one other person am having is due to an instability in 4.11. There is simply no other logical explanation.
That's not quite how the lights limit works. It's only for the OpenGL render engine, which is what drives the Viewport unless it's in Iray preview mode. (Actually, the practical limit is seven lights, since the default camera Headlight counts as one, if it's active.) As soon as you start a render, whether 3Delight or Iray, all active lights — including mesh lights — will contribute to lighting the scene no matter how many there are.
In any case, that same scene is now refusing to render and locks the computer. Time for me to do some serious evaluation as to whether I will continue in this hobby. The return is no longer commensurate with the expense and frustration.
Relating to the subject, I am rendering a 20-panel series. Now I find that the last panel freezes the computer. All of the panels are identical in terms of content, lighting, etc.. What would cause one of a series of identical content panels not to render? My work is stalled until I resolve this. It's beyond frustrating.
Thank you.
Are you reusing the previous scene to make the next panel? I have run into an issue where I was doing that (setting up a scene, then just using Save As to make the next one in line and carrying on from there). It wound up with the scen only opening about 1 in 5 attempts. What I wound up doing is deleting the environment, ligthing props and zeroing out the poses on all of the characters in order to start from scratch. What I've started doing now is when I'm working with a full cast that will be around for more than 4 or 5 images, I make a scene with just the cast members in it. Then once i've finished the shots with limited pose differences, I can just create a new scene file and merge the cast file in so that the next scene is starting with a clean slate.
Yes, but I've been working ths way for years without issue. But I'm also using OOT Alice Hair that, when removed, allows the render to proceed. I have tried using a DAZ optimizing product to replace the hair textures with lower-rez ones, but as yet, no luck.
download HWInfo > https://www.hwinfo.com/
keep the window open and ontop while you render and see if you are running out of RAM, if you do, use lower quality render settings, unless you have virtual memory disabled, then enable it
Thank you. I think it's partly to do with RAM, but I just replaced the hair textures again with those from the Resource Saver product, and it rendered. I'm going to try the next scene soon and see what happens without rebooting first. Might try that tool too.