Does Anyone Have This Problem?
melanie
Posts: 806
in The Commons
Recently, I think just since DAZ 4.10 came out, I've had a problem with rendering. It doesn't happen every time, and rebooting the computer doesn't always help, but occasionally when I render, it will render only the bottom half of the picture, but not the top half. Has anyone else had that problem? It never did that for me before 4.10 came out.
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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
4.10 seems to have a massive memory leak problem. The sympoms vary, but there are many people commenting about various similar rendering problems.
...which is why I'm sticking with 4.9 for now. been hearing of too many bugs.
Yeah still on 4.9 with no intentions to upgrade;) Just hope that DIM doesn't think I want the newest version and decides to help me out:(
Yeah, I've had that a couple or so times. Never gave it much thought, just saved and restarted DS. But now that I think about it, it's only happened with DS 4.10 (Beta).
Edit: Oops, I checked if I'd saved any and actually the top half was rendered but at what appears to be around 25% opacity, so probably nothing to do with your issue. My bad.
I wish they'd not concentrated on the newest shiney until they'd fixed the bugs in 4.9.
...so far 4.9 has been pretty stable compared to what I hear about 4.10. I may downoad the latest beta to do some tests, but for my main work I will stay with in 4.9.4. Also don' have a very robust GPU card to deal with dForce.
In a word NO !
Yeah I have a fairly strict policy of letting everyone else who enjoys it sort out any bugs with latest versions, and then 6 months later if all is well I'll try it. I think some people don't mind dealing with bugs as long as they have the latest, but I'm different. I hate bugs and annoyances.
+1 I would have stayed with 4.8 if I didn't have to reinstal due to a computer problem.
Ypu need to be careful about what you read as a bug - a lot of these issues seem fairly exotic and may not be DS bugs as such, or may be highly system dependent. It's obvious that a lot of people are using DS 4.10 without great issue. If you do have problems please make sure you report them to Daz - non-universal issues can't be addressed unless the people experiencing them report them, ideally with a scene that shows the issue attached to the report.
I had this problem even under 4.9, what you need to do (at least this works for me), reset all the render settings for default, then try a render, set it to low iterations 10 or so, let it complete, do not halt the render.
Then redo all your custom settings and render a good final image.
I have never been able to figure out what causes this, but it happens more when a render is canceled and another started, also it seems to happen when I increase the number of custom settings.
Frustrating, yes. I thought it was just me and a problem with custom settings.
I had this once a while ago, I can't remember if it was 4.9 or 4.10. It happened with one scene everytime I tried to render it, I think I just gave up and rebuilt the scene from scratch and it worked OK.
I have had 4.10 crashing during rendering a few times. I've had this before with large scenes but it seems to be happening with much simpler scenes in 4.10. The ones affected do contain dForce clothes but I assume that once the simulation has finished dForce shouldn't put any extra load on Studio.
On my side Franckly speaking...I think I have a very good hardware (IE7 32GB + 2 NVIDIA cards 980 and 1080 GTX) and I am a bit disapointed at renderings time not specially less time consuming then the days I only had the 980 GTX card. And worst when testing dforce first time
I had something like that "... kernel is not compiled for it do you want to to continue ?" Then it start to simulate. Slowly than I could expect 3 min for 1 piece. My card is up to date with last drivers. I have even check Simulate seeting I cannot use both cards, contrary to renders settings I can use my 2 cards.
So...don't know.
The kernels for dForce will update, I believe, when DS does, or when you switch OpenCL device (between GPUs or to/from CPU). I'm not sure if a driver update will trigger a rebuild or not. As long as nothing triggers a rebuild you should not have to wait for that process - if it does keep happening that sugests that something (perhaps security software or some kind of system-tuning tool) is removing the needed files.
I have to chime in here to agree. I have a VERY old system (8 yrs.) with integrated graphics, and so far, Daz Studio 4.10 not only does everything it's supposed to, but it has NOT crashed. Not even once. And I have TRIED to break it! LOL. I did have issues with previous versions, but not with this one AT ALL! (knock on wood).
Makes me wish my old Vista computer hadn't smoked the OS. Of course, the recovery disk didn't work.
It is now my Linux internet box.
I cancel and restart renders all the time and don't have issues (4.10.0.123). Haven't had any issues w/ 4.10 or 4.9 or 4.8 etc either.
Bear in mind that if you keep a render window open, that amount of memory will be held, in addition to the amount for Studio itself, until the render window is closed. In my current case, Studio was using 5.7GB. I closed an open render window and usage dropped to 2GB. I closed Studio and watched the memory be released over about 10 seconds. This while copying a 2 TB file in the background and having 4 tabs opened in Chrome.
I didn't know for sure if it was just me or if others had this problem too, before I reported it as a bug, which is why I threw it out here to see. I've had my renders do two things: render the top half as semi-transparent with the gray checkerboard showing through, or the top half is totally black. I didn't want to report a bug if it was just something only I was experiencing. I didn't want to report a bug if it turned out that wasn't the case.
This has now just happened to me twice in the last week or so. I think it may be my sorry excuse for a GPU, but it never happened until I installed 4.10 (which, incidentally, also crashes VERY frequently -- but may also be a symptom of my overworked GPU.) Before I file a bug report, I was just wondering if anyone else had experienced this weird "half-my-render-is-weird" thing and might offer a solution?