Daz crashing when translating ( Moving ) objects
davegv
Posts: 164
I am having a ongoing problem with daz crashing when I am translation a object ( More often a character, both G3 and G8 )
I can use the translation tool gizmo ( The xyz tool that shows up on screen ) or the sliders to translate.. and I seem to get way too many crashes.
Nothing is noted in the error log - I have a Threadripper 2950x, 32 GB ram, RTX2080ti. I use a number of other 3d programs ( Max, Maya, ZBrush, and never encounter a similiar problem )
I have Daz3d rel 4.11.0.383 and also the rel 12 beta and the problem exist in both. I have latest NVidia Drivers. The screen is in texture view mode ( Not iRay preview ) These are NOT "heavy" Scenes.
Any help or suggestions would be most appreciated
Added : What does the "Click here to toggle whether this property overrides any controllers" mean? It is located to the left of the Lock symbol on the translate slider ( Only the y translate has this...
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
I'm not sure on the crashing, and I'm not certain on the other question - I think it may be the chain icon, which cotnrols whether any remote control links are applied (one property can be set to influence others, that's called ERC, I suspect that at least one of the shapes on the figure you are using has links to the y control to make sure the feet stay on the floor when it is applied; clicking the chain icon, turning it into a broken chain, would stop the correction from being aplied.
Thanks Richard for the reply. I cleaned up some morph errors appearing in the log file - So when i load the scene the log shows Zero conflicting morphs, ect. This didn't help the perodic crashing when moving a figure. I am stumped, but, it is very frustrating trying to work like this. Recently when I clicked the chain icon you referred to above it instantly crashed . ( Thanks for the explanation just the same ) on top of that problem I am testing my new RTX2080Ti ( 3 days In ) I read the impression's others have with the speed increase from Rel 11 to Rel 12 but a typical sample scene I used for comparision gave me this : Release 12: 51minutes, 36sec VS Release 11: 1 hour 13min - So I am not that impressed with the speed increase in IRay, BUT, it is as advertised a 15-25% increase - I'll take that.. I was just wishing for more....and that same scene was also within 10 minutes of what my previous GTX1080 performed. But I have discovered that the VRay Next4.o release is BLAZING fast within 3DS Max ( a render that took 26 minutes on my previous GTX1080 is finished in just 12 minutes on the RTX2080Ti. ) So, I am very, very happy with that. The VRay interactive viewport in Realtime will render and not even blip while constantly updating the progressive render while spinning the entire scene in the viewport . Quite impressive. Anyway, not to get off subject to far. If you or anyone have any idea why this Translating is causing a crash I'd sure like to know. I used Rel10 Daz3d and even Rel11 forever without this sort of conflicts. Puzzeling for sure.
Which benchmark is that? The times seem too long for the SickleYield scene, if the GPU is actually being used.
No, Not the Benchmark scene used in the forum discussion / or the SickleYield scene. The scene used was one I choose of my own as a typical scene/render that i would do. Typical of my workload. Still no luck on the crashing problem troubleshooting. A completly empty scene with just Genesis 8 female I can freely move her along the xy axis useing the move tool on screen quickly with no problem, but while testing this i quickly rotated her then went back to a xy move and as soon as i attempted the move - Crash, out like a light. I have tried every driver from 430.86 up till current ( Mostly the studio drivers, because I use a number of other 3D programs they support as well ) The empty scene told me it is likely not due to a large scene or another item in the scene. And I have narrowed it to the G8 Characters, Genesis 3 seems to not cause the problem. Quite a puzzle, and not a easy one to troubleshoot. Other than the problem described I am totally impressed with my new RTX2080TI (EVGA) Impressive performance with my 3D apps. No game testing, as I have a separate game system (EVGA GTX1070TI)
Still trouble shooting this problem when I move a character in the viewport sometimes I will get a random crash. Experiment: A completly empty scene with just Genesis 8 female I can freely move her along the xy axis using the move tool on screen quickly with no problem, but while testing this i quickly rotated her then went back to a xy move and as soon as i attempted the move - Crash, out like a light. I cannot duplicate the crash with a Gen3 male or female character? I did go into Draw settings and change the Manipulation draw style to: switch to wire bounding box. While translating the character (moving) the character reverts to a wire mesh bounding box. I Ran several test cycles and have not caused a crash yet....
Edit: It crashed with this test as well..... Back to square 1
A question I have for you Daz Guru's: What are the best performance settings in the NVidia Control panel for Daz3d - In particular for viewport performance and of course IRay as well.
The only two settings I have changed specific to Daz3D are:
1) ensure that the RTX2080ti is selected under Cuda - GPU
2) Open GL renderingGPU = RTX2080Ti
Thanks for reading and I sure could use some suggestions...
I have I believe solved this problem.
Again, the Genesis figures do not load with every morph they have, they are just references to the actual morph data.
OP, how did you fix this, I am having the same issue, Mac OS