- Jun 30, 2022
- 72
- 728
- Jun 3, 2020
- 487
- 1,043
- Mar 2, 2024
- 12
- 17
Jumping on a serve is considered poor form, Bella. I'm available any time for a lesson.
- Nov 23, 2019
- 485
- 7,386
- Nov 23, 2019
- 485
- 7,386
For those who might not know. The V-ram usage Daz used to calculate, or still does if you're still using 4.16 like me, is not what is actually being used.
The green reading is via the Task Manager (CTRL Shift ESC)
The green reading is via the Task Manager (CTRL Shift ESC)
- Nov 23, 2019
- 485
- 7,386
- May 19, 2017
- 274
- 2,045
- Feb 17, 2020
- 1,615
- 4,569
That's right. I read that those readings from the application are not to be trusted. It's better to use external readings like the task manager's or the commonly recommended
You must be registered to see the links
's.
- May 14, 2019
- 120
- 2,885
- Jun 30, 2022
- 72
- 728
- Nov 23, 2019
- 485
- 7,386
A few reasons, well one reason, that calculation at the start was removed in newer versions, now I know how misleading they are, I can disregard this reason.
The second reason is ghost lights were "fixed" they don't work in 4.20 like they used to, I had a lot of scenes with ghost lights that were now messed up, some I made some "bought", the changes they introduced and the volumetric fog I think it was, just wasn't a good enough reason for me to upgrade.
I know there is a work around for ghost lights, but I don't like adding light values in the millions, in past experiences I've found it adds more initial noise and seems to take longer to render, as well as that the ghost lights weren't quite invisible.
Recent testing shows that the fix works better than it originally did, even renders a bit quicker.
The third reason in 4.20 a lot of textures that couldn't be found or wouldn't load or work, some for hair, some HDRI's, every time DAZ updates the version they always seem to introduce issues and incompatibilities. This is still an issue, and relying on updates from the vendor isn't a thing if you get the assets from the same place we do.
NOW, the biggest and most recent issue is V-ram use, which I only just tested. That pool party scene, used 10.8 GB in 4.16, I can't even get it to render in 4.22, it black screened at 10.8 and it holds onto the used V-ram after closing the render window, not allowing for consecutive attempts, in 4.16 that drops back down to 2-3 GB, allowing me to render again and again, without having to shut down and restart DAZ after every render. It's been 10 mins since I closed the render window and 4.22 is still using 10.5 GB V-ram.
All in all 4.16 is stable and does the job. I do have 4.22 installed if I ever want to work with G9, which is very rare, but I prefer 4.16.
Last edited:
- May 14, 2019
- 120
- 2,885
I see.
I remember I had to scrap a scene, because it kept blacking out when I tried to render it, even when I restart my PC. It maybe because it was a pretty huge environment and I tried to use 2 models but back then I never really had that problem. At worse it'll take a really long time to render.
Maybe I'll do some experiments with the 4.16 version of DAZ.
- Aug 30, 2022
- 261
- 3,214
Usually when this happens to me the OOT Hair is at fault. Worth checking if that's the case with you as well.
- Nov 23, 2019
- 485
- 7,386
OK, OOT was definitely the culprit in mine, it even clears the V-ram cache when I close the render window, allowing for multiple renders, and the ram usage is about the same.
One glaring problem however, can ya tell? Also the water, Daz couldn't find the .dsf file.
This is why I stick with 4.16
- Jun 26, 2022
- 233
- 398
There are other things too generaly Lighting works 'diffrent' and with that reflections. Sad because so many 'old' but good enviorments have now no lighting when the maker did the effort to light it out propably and yes i know i can make the old lights work again but it tedius.Newer Versions have some ups but it depends what you need and OOT hair are always something to suspect thats why i don't use them for my own charcters aldo the look good but you need to change or delete the problematic file/texture Night Hacker and m4dsk1llz talked how to do it on this Thread https://f95zone.to/threads/college-kings-fanart-and-assets-thread.169203/
- Apr 12, 2017
- 626
- 1,094
Daz has always had a problem with gobbling vram. I don't recall it being something new post-4.16. There are a few things which will always cause it and are best to avoid if you can.
1. Turning on the Iray preview mode will grab and hold a block of vram (which your real/full render can not use)
2. Rendering to a window and keeping that window open.
3. A failed render (yes, it's a bit ridiculous that even if Daz self-terminates a render because the system doesn't have enough vram rather than an actual crash, the vram it started grabbing in the attempt will be unavailable until Daz is shut down and restarted)
You don't have permission to view the spoiler content.
Log in or register now.
In any version of Daz, if it's using a bunch of vram before you start a render, the only sure way to clear the usage is to reboot Daz.
Last edited:
- Nov 23, 2019
- 485
- 7,386
I checked the thread out, good stuff, I'm still not sure of any benefit from updating to 4.22, if rendering was significantly faster, or assets less expensive on the ram, or add soft breast physics (lol) I might start using 4.22 or 4.23 now is it? I'd put up with errors and fix what can be fixed. Certain new hair models for G9 don't work in 4.16 but I'm good with that. As it stands I'll stick to 4.16
- Nov 23, 2019
- 485
- 7,386
The issue I had with Vram post 4.16 and why I thought it was using more, was to do with the oot hair. Without that fixed, it held onto the 10.5 GB even after closing the render window. After fixing the hair and closing the render window, it dropped back down to between 0.3 GB and 3.5 GB, so now it behaves like 4.16.
I never said DAZ lied about Vram use, I said it's misleading especially if someone's unaware, which I think it is misleading. You can almost double what that render window states. I'm certain the log reflects what the render window says. I remember looking that up when I had my 1080 8GB card and it wouldn't render a 6GB scene.
- Apr 12, 2017
- 626
- 1,094
My response wasn't to disagree with you. I was just trying to add some information.
But yes, all stats only tell the truth, and they all lie. Unfortunately numbers have no meaning until someone interprets them. And as soon as anyone interprets, all bets are off. It's much the same as when games on here got released and people constantly complained that games weren't nearly as complete as the version number claimed them to be (they simply had no clue that version numbers are not "percentage complete").