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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
yeah it is. it worked just fine up until like 2 days ago when this issue REALLY started to kick in so did all the graphics card updates and so on as usual, but it didn't help any
...hmm not sure then.
Changing a pose should not affect the rendering at all
Meanwhile, I've been running a few more tests trying to troubleshoot the issue I posted about but with no success. I even tried running it in the 4.12 beta using the dForce Helper (which for some reason does not appear in the Window Menu/Panes selection in 4.15) to focus just on one component at a time and it still crashed at the same point.. I also converted the the top, pants, and shoes with the RSSY G8 to G3 Clothing Converter to see if that would help, but ended up with the same result.
Each time before running a simulation, I made sure to first click on the dForce Simulation settings for the clothing in teh content tab so I'm following all the necessary steps
The pose I'm using is not at all extreme (see attached screen shot) yet it seems to consistently occur when the character's hand passes behind her (at about the 49% mark during the initial "Simulating from base pose" routine) Just before that moment her hand collides with her hip but then moves for about another two frame steps before the sim freezes after which the display driver crashes. Never had this happen running dForce before even during those long 19 min hair sims I was recently dealing with..
I'm using the recommended Nvidia driver for 4.15 so that shouldn't be the cause. I even tried the latest driver available and it still occurred so I am out of ideas.
ETA:
Apparently this outfit is no longer in the store nor been moved to another so I cannot tell if it has any hierarchical presets that might be causing the issue.
We talking explosions? or just failure to complete? Explosions are a pain but can be fixed easy enough by altering a keyframe in simulate to timeline IIR. but if it is just refusing to complete... that's a whole other barrel of monkeys.
Hierarchcial poses could not have any bearing.
If the hand passes through the figure, trapping the cloth, then a failure to simulate is almost certain - but now quickly will depend on the outfit and on the Simulation settings, it may take a couple of steps for the energy build up in the springs to reach an irreconcilable point.
...failure to complete that results in a crash of the video driver
The product is dForce clothing. Unfortunately for some reason it is no longer in the store. so I link to a promo page.
...so why did it just not stop, explode, or crash the programme itself rather than the video driver? That is what makes no sense.
I can't answer that in detail, but it may be that it sent impossibly values to the OpenCL system and those caused a crash (which would suggest a bug in the driver's error handling, as well perhaps as a fault in the way DS generates the values to be sent over).
...well, I'm using the recommended driver for 4.15 (451.48) so there shouldn't be a fault in that as others have ran the sim on this product successfully.
I'll modify the pose to keep the hand from passing through the body and see if that works.
Uploaded and installed version 4.15.30.0 on my Mac (Big Sur) and when it runs I get a message about haveing "recertify" content.
It's been a while since I've used Studio and not sure what its talking about. Help?
...finally got around to altering the pose today so the arms stayed in front and the sim finished. So yes, it was the hand passing through the character's mesh that caused the crash.
However after it finished it looked terrible, not even like it appeared before running the sim. The leggings of the slacks seemed to collide with each other during the process instead of moving apart. Before attempting another sim I noticed something odd in the crotch area and as i zoomed in there were multiple tears in the mesh even though I had converted the clothing with the RSSY G8 - G3 conversion script which should have prevented that.
When you log in from within DS the first time it stores a "key file" on your system, which is used afterwards by Connect to decode the files it gets from the downloads server when installing content from DS. This "key" is computed based on characteristics of your system, and if a major one like the OS changes then you must generate a new version by logging in from DS again.
Hi , I just updated my studio from the previous version to the newest ( 4.15.0.30 ) , now Daz opens way slower then before y is thas happening ? is there some sort of bug / glitch ? never had a problem starting before it opened/started right away.
Never mind it was my computer needed an update . :)
I just installed the 4.15.0.30 upgrade and everything works fine... except I can no longer render in IRAY. Regardless of what camera I use, (create new camera or even using the Default camera), every render is solid black with nothing else in the frame. Would any one have any idea as to what is wrong? I am using an HP Pavilion Gaming Laptop,15.6", Intel 8th i5+8300H, with NVIDIA GTX 1050Ti and 8GB of RAM. I've installed the latest NVIDA driver: 496.49 Thank you.
Check these 4 things:
1. Check the Scene Tab to see if there is a Skydome If so delete it from the scene and instead, add the Skydome image into the "Environment Map" under Render Settings - Environment tab
2. If you are not using a Sydome, the go to the Render Settings - Environment tab, and check if the default HDRI image is loaded into the Environment Map box. Also check your Environment Intensity (1 = Default), Environment Mode (Dome and Scene = Default) and Dome Mode (Infinite Sphere = Default)
3. In the Render Settings -Tone Mapping tab, try to brighten the scene by lowering the Exposure Value (13 = Default), or Increasing the Film ISO (100 = Default), or Decreasing the Shutter Speed (128 = Default), or Lowering the F-Stop (8 = Default), or increasing the Gamma (2.2 = Default)
4. Check to make sure the Daz Studio update did not disable your GPU. In the Render Settings tab, then Advanced tab at top and next to "Engine:" select NVIDIA Iray from the drop-down menu. Then, below in the Hardware sub-tab, you will see a list of available devices. Put a checkmark in the box next to your GPU (ex. CUDA 0 - GeForce...)
Let us know if any of those 4 solutions work for you.
Well, here we go again. How will Daz Studio work with the latest Apple upgrade to Monterrey? I still haven't had any success trying to get DazCentral to work on Mac with Big Sur. It loads, then immediately hangs and becomes unresponsive. Ony remedy is to "Force Quit". So, I just use Daz Studio and DIM when necessary. Very frustrating especially after being notitfied that DazCentral "Now works on Macs!"
Big Sur broke, though apparently not irreprably, the version of the Qt application framework that Daz was using - as fart as I am aware Monterrey is a much less dramatic change, and I believe we have had at least one report on the forums that DIM and DS are working.
No, sorry to say that none helped as all settings were already as you suggested. I am able to get Studio to do one rendering per opening, then I must close it, open it again to get one more rendering.
OK then... Where can I report a bug. I can not locate any page on the DAZ site to do this.
Open a support ticket for Technical Support please https://www.daz3d.com/help
Thanks, I've got a ticket in.
..not here.
Not crashing for me either.
Could you attach a log of the crash to your next post so others can have a look?
Okay, this happened... Wasn't my whole computer this time.
https://1drv.ms/u/s!AhpXMWQ8tVpLgQKsyYQSxDIcNITh?e=G0fgII
Can't attach it here for some reason. It gets stuck on "Uploading..."
A whole lot, it can't even render with 3Delight. Went back to 4.12.0.86 immediately.
I've updated the CPU to i7 12700k and now cannot login in DIm (it's immediately shutting down after clicking on the Login button). Also, Daz studio shut down after I try to open previously saved scenes. Yesterday everything works smoothly, so it seems that's the problem with new intel processors compatibility
Which versions are you using? Daz studio 4.15.0.22 and Install Manager 1.4.0.80 fixed an issue with OpenSSL that affected recent (tenth geenration plus, I think) Intel CPUs:
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_15_0_30#4_15_0_22
http://docs.daz3d.com/doku.php/public/software/install_manager/change_log_1_4_0_80#1_4_0_80
3Delight has not been chnaged, what issues are you having when you try to use it?
Brutal crashes when I try to render, both in Spot Render and regular render modes. It happens pretty randomly yet very often, somehow related on how much stressed the CPU is. For example, if I try to render while using my web brower, it fails.
Also now it gives me a colossal amount of error messages that I never seen before on some shaders, totally different than the usual "Displacement bound 0%". The final render seems to be fine (when it works) but not knowing what's going on on my renders leaves me pretty uncomfortable.
On 4.12.0.86 everything works fine and smooth. I can even play small games while rendering in there.
What are the new error messages you are getting?