- This topic has 15 replies, 9 voices, and was last updated 6 years, 4 months ago by
.
-
Posts
-
I spent 2 day. 2 days setting up a scene. Made sure everything was setup for IRay, double checked the materials, set the lighting, and then put in to render...
It froze and when it came back, my PC needed to restart to even re-open Daz. Okay. Go load up the scene (save, save, and save just to be sure) adjust the render to a smaller shot, turn down some of the settings. Render.
It does it again.
One more try. It renders... a completely black screen with a dot of neon red-yellow.
Got annoyed. Started working on a smaller scene all 3Delight materials. Set it up to a simple 1:1 shot. Hit render, it does the 3Delight countdown. Render window pops up... and then Daz closes.
I'm just about done with this program.Would need to know more about the rig you are using and how complex the scene is. DS can be a bit twitchy at times, but I have to go out of my way to make it crash, but I do have a decent system.
Yes, I've had the thing crash on me multiple times. My recent issue is very minor compared to yours, but I often have to restart the damn program to allow for my gpu cards to be utilized again. Basically needs to flush out any memory it has. It's got some issues that's for sure.
Let me know if I/we can help. Often times it's a good idea to try and see if it happens on a different machine or not.Or better yet, try to render the smallest things possible you could. Smallest and simplest. When I first tried my hands with Daz, I only had 5 year old laptop with me. Tried to work with it multiple times, but soon learned that it can't handle much. Not to mention, I wouldn't also be able to see the results fine enough.
That thing got me discouraged enough to buy a new rig after a couple of months. I never experienced crashes even on the laptop for the couple days I tried to use daz. (It didn't have any gpu either, so I was stuck with vpu rendering, considering a 5 year old laptop without a gpu, it didn't fair much well)
Nonetheless, if it's crashing on a simpler scene too, it could very well be the graphics driver or one for your processor (cpu). Either of them could make a difference, try updating your graphics drivers perhaps. Also, if you have dual gpu setup (dedicated nvidia + integrated intel/amd), it could very well be the settings.
Don't do as much as I want or at the size that I want. Making do with a Dell Inspiron 560. Has Intel Celeron 450 processor, 2.20GHz and 6 GB installed Ram.It's frustrating at the very least. My daughter got it in 2010 and gave it to me to use when my e machine died. Daz crashes on a not so regular basis, but is aggravating when it does.
Hope your situation gets better.
Thanks. I uninstalled the program. It kept telling me to update my drivers but they were up to date. Then I had to restart my system because it stayed on a blank screen for about 20 minutes. I'm done, which sucks, but that's all for me now. Guess I'll just lurk.
I bought a Titan RTX card just to play with Daz3d. With 24 gigs of memory, the Titan can render very large scenes with out a hiccup.
I hardly ever render on Daz. (Much less if the scene is complicated ...). Iray shows well if there is a powerful graphics card, which can double the cost of normal equipment. My advice is to use other softwares like Cinema 4D with the Arnold render engine. There are many render engines, such as Octane, Redshift, etc ..., but the standard now in cinema is Arnold. If it is a fixed shot, like a photo, you export everything in Obj format, never in Fbx, since it loses detail in the geometry. (Apart from the fact that the exporter of Daz with Fbx is weak and terrible ..). You should always think of textures, which Daz (well, content creators ..) think are great for a render to impact people. This is all false. The ideal of an image producer is a fast working fluid and that NEVER occurs in Daz Studio. Iray is, sorry, a scam and a fiasco.
Of course, forget the Alembic plugin for Daz. The format is not the current one. It is the HDF5, not the current Ogawa and it uses Maya, Blender, etc.
I have to agree with LivingPixels.
For me, when rendering, DAZ eats up 6 GB of memory (half of what my system has) and 80% of my 4 cores. And I'm rendering with my GTX cards. If it doesn't use my graphics cards due to memory maxing out, it uses my CPU and it makes my machine crawl.
I like the quality of the results, but this program will eat up any resources (CPU, memory, graphics cards) it can get its hands on.And don't forget the 'helping hand' that Windows 10 [if you use it] gives your renders.
That was sarcasm, by the way.
Good old Win 10 will, if you use Nvidia cards especially, reserve up to 10 - 15% of your vRam [even your shiny new RTX]
Many threads exist out there regarding this - yet no one knows why, or attempts to resolve it.
Nvidia at fault? Windows at fault? Each blames [or just ignores] each other - apparently has been an issue for years.If you have an older system, that you have 'upgraded' to Win 10, and you are using Nvidia, you might just have a rendering paperweight.. 🙁
hi there,
i've used daz studio for a long time now, and had those problems in the beginning, as i learned more how to use it, i came to realize that daz studio has indeed some troubles when it gets busy in a scene.
It's important to know your system and what it can handle.
In the past i had a issue with a render, that was pretty simple in essence, a character sitting on a haybale, yet, that required 6+ GB of video memory to render (and i only have 4GB), so, my screen itself went completely dark.Now, it's important that you make use of this: https://zonegfx.com/scene-optimizer/
When you experience trouble with rendering a specific scene, i can think of a few things.
There are props etc in your scene that perhaps have too high textures (while DAZ can handle 8K, 8K textures are a overkill), maybe some of them have a too high SubD level (and do not take the viewport & render SubD levels as the same, they are not)I good way, which i learned is to analyze this stuff very carefully, as artists by default can use textures as low as 2k, or have sometimes a prop set to extreme high levels which isn't actually needed.
Furthermore, turning off all glossy and specular effects helps too on characters (but do not remove the specular map), and removing the bump maps on anything that isn't closeby is also a amazing idea.
these are just all steps i've learned to take to prevent such scenario's from happening.
Hope it does help you.
Mello
If anyone is interested in a nice test scene, to find out how well [or badly] their current system is performing, the link below is useful.
the scene is made up of basic elements that should already be on your DS installation. Just load it up and render away...There are some tips on the Deviant site, and comments from a number of members.
I found it interesting to load and compare render performance on a few of my systems [some I gave up on, one highly pleased].Sickleyield: Benchmark Test Scene [DeviantArt]
https://www.deviantart.com/sickleyield/art/Iray-Scene-For-Time-Benchmarks-519528033
Has anyone tried this benchmark test yet???
Any interesting results?
Sickleyield: Benchmark Test Scene [DeviantArt]
https://www.deviantart.com/sickleyield/art/Iray-Scene-For-Time-Benchmarks-519528033
- You must be logged in to reply to this topic.
