- Mar 18, 2019
- 237
- 3,856
I decided to make one of those Twitter challenge things...
View attachment 1388491 View attachment 1388492 View attachment 1388494 View attachment 1388495 View attachment 1388497
Hey, fun stuff!Is Anyone else going to get in on this?
XenoFash 's original post
My take on it.
come on people don't let this initiative run out of breath with just one attempt at it (sorry Captain Bipto but yours doesn't really count does it?)![]()
Not on a session that's not crashing. Daz has a serious memory leak problem. I only have 64GB so I could only match yours but people were crashing with 128GB on Daz forum and I bet those people can top yours. There is also a guy on deviantart who was testing the limit of RTX3090 and found out that Daz always crashes after his RTX3090 went above 20GB VRAM and far below its 24GB and it was because he ran out of DRAM in his 64GB rig.
What is the asset used for the model.
The problem is that DAZ get problems when you have CPU and GPU enabled for render and the amount of data exceeds the amount of VRAM and DAZ tries to switch to CPU render only. I switched my preferences to GPU only render and now when it exceeds the amount of VRAM it does not crash when switching to CPU render. The difference between GPU+CPU or only GPU render is not that massive for me. DAZ now only crashes when it exceeds the normal RAM too. And another problem is that DAZ is not good with cleaning up. Rendering and then deleting a scene and loading a new scene and render can crash and doesn't happen if you restart DAZ after rendering and then start with a new scene. There is even a render queue tool that does that because they know the problem.Not on a session that's not crashing. Daz has a serious memory leak problem. I only have 64GB so I could only match yours but people were crashing with 128GB on Daz forum and I bet those people can top yours. There is also a guy on deviantart who was testing the limit of RTX3090 and found out that Daz always crashes after his RTX3090 went above 20GB VRAM and far below its 24GB and it was because he ran out of DRAM in his 64GB rig.
Even if you are in GPU only mode the amount DRAM is still needed to be 2-3x your VRAM for Daz not to crash or slows to a crawl if it taps virtual memory. Daz needs to decompress ALL the textures into DRAM before CPU can send the scene to GPU. Geometry memory supposedly works differently. Geometry uses more VRAM but saves DRAM and speeds up rendering if not pair with unnecessary normals. There is a guy on Daz forum who did tests and that Daz HD characters in SubD4 renders at least 50% faster than its non-HD counterpart at SubD2 because Daz HD characters don't use normals. HD does use more VRAM.The problem is that DAZ get problems when you have CPU and GPU enabled for render and the amount of data exceeds the amount of VRAM and DAZ tries to switch to CPU render only. I switched my preferences to GPU only render and now when it exceeds the amount of VRAM it does not crash when switching to CPU render. The difference between GPU+CPU or only GPU render is not that massive for me. DAZ now only crashes when it exceeds the normal RAM too. And another problem is that DAZ is not good with cleaning up. Rendering and then deleting a scene and loading a new scene and render can crash and doesn't happen if you restart DAZ after rendering and then start with a new scene. There is even a render queue tool that does that because they know the problem.
Yeah for sur you wanna follow her tail... trail !I wouldn't validate that suit either, but that's the magic of fan art to do what's not valid. And the girl "Kate" sends you a big kiss for the sweet compliment
![]()
Superbe !
you don't name these beautiful creatures?
I didn't either thoughyou don't name these beautiful creatures?