Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Mentioned earlier, 3090 and 4090 and a 3060 ( used to run the desktop ).
Sorry for the late reply.
I'm using Hollywood Blvd with darkside, midnight style ( if you mean Daz UI ).
I'm pretty sure these material anomalies we are seeing are caused by the DS6 Alpha's displacement handling (Adaptive Displacement?). If I set the SubD Displacement Level to 0, the artifacts go away in Garage Hideout.
Edit: Same thing for the Collective3D Backyard Driveway. The House object's Foundation surface uses Displacement SubD. If I set that to 0, the set renders fine.
Edit 2: Interestingly, the Collective3D Backyard Driveway Table object's Table Glass surface also has Displacement SubD, but it doesn't seem to cause visible artifacts that I have discovered.
Edit 3: Changing Displacement Adaptive Quality to a value higher than the default 0 (I tried values of 1, 10, 100.) had no impact on the artifacts; they were still there when SubD Displacement Level was greater than 0.
Since the character vendors (at least in this Daz store...) usually provide big size thumbnail images for character's Head and Body morph, as default, DS sets big Card in Shaping pane for all the morphs of non PHM/PBM morphs under Actor path.
You can uncheck Preferences > "Show Property Cards" in the context menu of Shaping pane ~~ to make morph properties as "horizontal morph sliders" ~~
Excellent sleuthing
I think you are correct.
It seems that any displacement in the scene will cause these artifacts.
Removing the setting displacement to zero and removing all displacement maps makes the artifacts go away.
I'll play around with other things and see if I can recreate the artifacts by adding displacement to things that don't have it.
OK, the screen shot does show the Daz crash reporter so please click the Save button in that and then attach the zip to a reply - issues (apparently) with DirectX are unusual.
Some issues with this were fixed a while back - if you are still experiencing the issue please (if you can) provide before/after versions of the UI configuration files and your logs (so that things like active plug-ins and start-up scripts can be seen).
Can you provide more specifics about what files from what folders need to be provided? I am still having the problem where Update and Merge menus deletes my Bookmarks menu completely and empties my Favorites and Scripts menus.
The UI files are in C:\Users\username\AppData\Roaming\DAZ 3D\your dStudio version\user layouts\
Richard asked for before and after UI files and also log files.
I think C:\Users\username\AppData\Roaming\DAZ 3D\your dStudio version\user layouts\ would only have my saved UI files (i.e. the "Before" files) and not the "After" files, unless I save new ones after running Update and Merge Menus. Is that what I am supposed to do (Save layout again after my menus are emptied and deleted)?
What log files are needed? Only the Help/Troubleshooting/View Log File files, or some other log files?
The saved ones would cover the before state, probably, but I was thinking of the actions, customeactions, layout, menus, and toolbars.dsx files from the root of the DS appdata foilder (which also has the log file).
I trimmed a few levels out of this long back and forth. This is about the failure of Update and Mege Menus.
OK, I understand what you are looking for now. I will work on gathering it up. I'll probably submit it all in a help request
Thank you.
I wrote up a request, attached the files and when I submitted it, the window just went blank, and there is no such request in My Activities. This website is nearly impossible to work with. Something is always going wrong. I give up for today.
Richard, when I received a reply from Customer Service for a report from 2024 that was being worked on then, I noted this phrase - "This ticket was unassigned during a transition in our ticketing systems."
Is there still an issue with the ticketing system that impacted what @barbult experienced yesterday and may have been contributing to other non-answered reports for others?
I am not aware of anything, and I don't think I have had a message like that on any of my tickets. But someone else did report issues with getting signed in to ZenDesk in another thread; I just logged in OK now, for what little that proves.
You could attach the files to a post, or put them on Google/One Drive and PM me a link if you don't want to shre them too widely (as long as I am not too wide) and I can send the link or files on.
I tried again today to submit a help request and this time it went through.The title should say "deletes" instead of "deleted", but I didn't notice the typo before submitting.
Request #478608
Update and Merge Menus empties and deleted menus in DS 2025 Alpha (DS 6)
RE: Update and Merge Menus problem in DS6
I sent you a PM with links to the files on Google Drive, in case Customer Support doesn't process my help request in time to be useful. Please pass them on, and/or investigate them yourself, if you are curious about the problem.
Thank you, I will have a poke but it will probably take more expert eyes than mine so I will also send them on.
If you haven't opened DIM, there was an update to 'Public Build Install Modules' available this morning.
This isn't an update to DS, it corrects an error in the code for the Alembic plug-in in the DIM "package" that can be used to install all at once
I created a scene in DS4.24.0.3 and opened it in DS6 Alpha 6.25.2025.22607 to render. It rendered fine and quickly, but when I closed the application, it took 3 minutes to clear the scene, and then I got a bunch of warnings in the log:
2025-08-24 05:19:03.421 [WARNING] :: QObject::disconnect: Unexpected nullptr parameter
2025-08-24 05:19:03.421 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryScenesCbx
2025-08-24 05:19:03.422 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryCharacterCbx
2025-08-24 05:19:03.423 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryPoseCbx
2025-08-24 05:19:03.425 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryFaceCbx
2025-08-24 05:19:03.426 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryHairCbx
2025-08-24 05:19:03.428 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryHandCbx
2025-08-24 05:19:03.429 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryPropCbx
2025-08-24 05:19:03.431 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryLightCbx
2025-08-24 05:19:03.432 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryCameraCbx
2025-08-24 05:19:03.434 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryMaterialsCbx
2025-08-24 05:19:03.435 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryScenesCbx
2025-08-24 05:19:03.437 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryCharacterCbx
2025-08-24 05:19:03.439 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryPoseCbx
2025-08-24 05:19:03.440 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryFaceCbx
2025-08-24 05:19:03.442 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryHairCbx
2025-08-24 05:19:03.443 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryHandCbx
2025-08-24 05:19:03.445 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryPropCbx
2025-08-24 05:19:03.447 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryLightCbx
2025-08-24 05:19:03.449 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryCameraCbx
2025-08-24 05:19:03.451 [WARNING] :: QObject::disconnect: wildcard call disconnects from destroyed signal of QCheckBox::ContentLibraryMaterialsCbx
And that same list of warnings was repeated 4 more times. Should I be worried, it is this expected?
I don't know, but it looks like something to do with releasing the resources used by a dialogue box or pane. Interstingly the names are the Poser format library containers
DIM overwrites the files. That's what it does. I simply move the files to a different directory and then place links to the files in the DIM directory. I'm pretty sure I have every single release of DAZ Studio plus all the products etc since I started doing this. It's not hard, but it's not in Tati's interest to do that; we have to do it ourselves. It's not hard.
Yes, that! Especially the disappearing manipulator and the broken Undo are absolutely infuriating. They seem to be linked, when the manipulator disappears, I know it's time to shut down the program and restart it, or the broken Undo will screw me over.
@Richard
Latest Alpha is again having slower viewport than the previous one.
Version 6.25.2025.23807 doesn't allow me to select key items in the timeline. I am trying to delete "bad" keys (i.e., values I inadvertently set), and cannot select them (left click on the unhighlighted key) to delete. When I first noticed this, I assumed that DS had messed something up internally, so I saved the scene, and restarted DS and reloaded the scene. I still could not select them. I tried a different scene, and I cannot select keys there, either.
The previous version (22607) works fine (in this respect).
I can confirm that the same is happening on the Mac version, dropping back to previous version.
Repeatable recreatable dform crashes on this weeks build. When moving the default tool with the field parented too it.
Do people really move the tool about without the field parented after first spawning it? I've always found it annoying that it isn't.