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
Yes, I have observed atypical behavior from the new Faz, like your case.
Yes, very annoying. It happens to me too!
Thanks for the confirmation !
Now in 4.23, there's still no improvement ~ so that's why I have to keep using DS version 4.22.0.16 ~
The posts will be updated when there is a significant change to the integrated version of Iray.
I don't understand why the extra precision shown in the value matters. 100% is the same amount as 100.000000%. What doesn't work when the extra decimals are shown?
Where do I get the public build? Install manager doesn't install it and studio doesn't show it under Install panel.
If you haven't installed it before, then you need to "purchase" it.
https://www.daz3d.com/daz-studio-beta
Also, in DIM, make sure that the Public Build is selected in Settings - Advanced Settings - Downloads - scroll down till you get to Release Channel Tags.
It isn't a matter of things not working without the precision, it is that this particular Qt widget does that, and they have switched widgets as part of supporting localisation (see entries in the change log - though thi s still being worked on). It does show the precision that it can handle, though.
I interpreted people's complaints to be that the extra digits of precision were causing them a problem. My question was about what problem they were having because of the extra precision.
Downloaded and still doing the same. Everything was fine until the update. No changes to my pc. Looking at processes in task manager, studio is stuck at 1,554.6MB memory usage. It never changes no matter what. Still nothing showing in scene panel even though there are things in the scene and smart content and content library don't load. I'm at a loss.
Any chance to see a fix for the crashes when using Mesh Grabber 3 in DAZ Studio 4.23?
Since you guys at DAZ3D now own the code, I can't ask ManFriday to fix that...
They bought the whole thing from the PA, that's why they removed it from the store.
Also, it's DAZ Studio's issue here, since if I roll back to 4.21 Mesh Grabber 3 works correctly.
Mesh grabber 3 is still in the store.
I'm not saying there's nothing to fix on DS side, just that Daz doesn't own mesh grabber 3.
I described the issue many times in various threads.
Shall I describe the issue here too?
Ok.
Create a new scene and populate it really well. At least two fully clothed chars in a nice environment. Now choose a prop in the scene and change any part of it with Mesh Grabber, something simple like elongating a side or rotating a few polygons. Don't bake it into morph yet, leave it as it is. Save that scene.
Now load any other scene which is rich like the one you just created. Do nothing, just load it.
Lastly, with that scene loaded in DAZ Studio, go to File-> Load (or perform a double click in the file explorer) and reload the scene with the altered prop in it. DAZ Studio brutally crashes, giving errors on TBB.DLL.
After all this, run again DAZ Studio al load again the scene with the altered prop. Select it and now bake the changes to moprh using the Mesh Grabber's inner function. Save again the scene. From now on, the scene will load with no issues in any situation.
The crashes happens when you try to reload a scene containing a non-baked-to-morph change made with Meshe Grabber with another scene loaded. It stops happening if the changes are turned to regular morphs.
Thanks for the details. I'll see if I can reproduce that scenario. I almost never save a morph from my Mesh Grabber changes, but maybe I never did things in exactly this order.
Thanks for having elaborated the issue again ! Unfortunaltely, I still couldn't reproduce the issue with DS 4.23. This time, I did it as per what you described twice, with and without Mesh Grabber tool activated before loading the 1st scene file, there was still no crash.
Again, as for tbb.dll (Intel Threading Building Block Library), it's in the application folder of Daz Studio, in DS 4.21, 4.22 and 4.23, the DLL version is all the same (2018.0.0.0). However, some plugins like Fluido, Gescon... also have this tbb.dll file in plugin folder but they're newer versions. I'm not sure in your crash dump analysis, which tbb.dll was relevant, from DS per se or from the these plugins...
Though theoretically, other DLL files from a plugin is called only after that plugin is activated, I still suggest you totally remove / disable other plugins that have tbb.dll files, then test it again ~~
Or, furthermore, make DS 4.23 have the very same application environment / conditions as DS 4.21, e.g. same plugins config. same settings in Preferences, yada yada ~ before testing.
No, I cannot reproduce the problem either.
I made a scene with two HD G9 characters, dForce clothes, strand-based dForce hair, a props environment, an HDRI in render settings, several photometric lights in the scene and a ghost light. This maxed out my 10 GB 3080. I saved that scene wthout using Mesh Grabber. Then I used mesh grabber to move the bottom of the curtains on both sides. I saved the scene with a new name. I loaded the first scene that did not use Mesh Grabber. Then I reloaded the scene that did use Mesh Grabber. Everything worked fine. I rendered the scene that used Mesh Grabber. At no time did I create any morphs from Mesh Grabber modifications. I see no problem. I am using DS 4.23.0.4 Public Build.
In my system is a 100% sure thing. But perhaps depends on the fact all my scenes are animations and not stills...
I'll double check which TBB file is responsible of the crash.
Even if the Mac version is fixed, I don't believe that you'll be able to use the Filatoon shader as it's a Filament shader which isn't "scheduled" to work on Macs until DAZ Studio 5 or whatever it might be called when finally released (e.g. "DAZ Studio Pro 2026", perhaps? Maybe "DAZ Studio 2027"?).
Issue with 4.23:
* Decals will stop the iRay-in-viewport renderer from progressing past the 'smooth shaded' phase. Renders work fine.
(I was also experiencing difficulty with the (shape and) pose sets in which they would magically reset my figure scale back to 100%, but I found that by locking it, things remain sane, so I'm good there.)
I don't have any of those problems with 4.23.0.4. The problems you have may be due to specific product errors, rather than Daz Studio 4.23. You'd better list the decal, shape and pose products you are using that cause problems.
I loaded G9 Dev and scaled it to 50%. I tinted him blue in the surfaces pane to avoid any skin nudity. I selected G9 and applied a decal (Create>New>Iray Decal Node). I set the viewport to Iray Preview. The decal node showed up instantly as white. I applied a fish fabric shader to the decal. It appeared instantly in the Iray Preview viewport. I scaled the decal up, to cover multiple body parts, to make it more obvious that it was a decal. I dialed in the Base Masculine shape. The scale of G9 did not change. I posed G9 with one of the anime pose presets. The G9 scale did not change.
AAAAAAAAUUUUUUUUUUGH
MY FILES (SAVED FILES AND LAYOUTS) KEEP CRASHING 4.23.1 why why why why - auuuuuuugh I have a deadline
What do you mean saved files and layouts? What are you trying to do? What does the log say?
He's probably saying that, after updating DAZ Studio, all his scenes and work doesn't load anymore.
It happened to me too, many times. Luckily for me, I just needed a rollback to a working release of DAZ Studio and the scenes loaded correctly, try that.
If you reinstall just DAZ Studio you shouldn't lose anything, but make a backup of all your work in a separate drive, just for safety.
If you have updated to the latst nVidia studio driver then try rolling back to a previous one.
My 'saved' models i.e earthquake w/ characters and vehicles - it loads - partially loads - no error - just closes the program out when it crashes.
(Edited by mod to remove post from the quote)
Correct - my 'scenes' with almost any envionments crashes once the model comes in before the texture maps load.
Does it give an error message? It's a snall window with a green bug on it. Click on it to get more info and see what it says, especially in the lower part where the involved files are listed.