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
The emrged things now appear in the 4.22.0.x entries, the ones left in the 4.22.1.x entries are still "future" builds, which we won't see until the 4.22.0.x version has a final release and we move on to prep for (probably) 4.23.0.1
Can confirm 4.22.0.10 is still using the older Iray 2022.1.7, build 363600.4887 release. If you check the DS log file it reports:
Which is a match for the build number for 2022.1.7 (the 5.5 version number is referring to the "Iray as a plugin" version tracking iirc.) For some reason either Daz or the Iray developers affected a source code change earlier this year that confusingly drops the YEAR.MAJOR_VERSION.MINOR_VERSION syntax from the reported Iray version number in the log file. Don't know why.
The reproting change would most likely be down to nVidia, Daz is just passing on the information it gets as far as I know.
The command for calling that version string still appears to be part of the Iray API, meaning that the choice to no longer include it in the log file (to save on log lines?) would've been a Daz developer decision, not an Iray developer one. Prior releases used to print it like eg.:
What does this mean:
>2023-12-12 17:40:57.316 [WARNING] :: \src\sdksource\general\dzcontentmgr.cpp(1851): Nested directory encountered while adding a content folder: G:/DAZStudio/Genesis-81 : G:/DAZStudio/Genesis-8
I have two CMS directories, one for explicit 8.1 content, calls ".../Genesis-81" and the other for G8 content ".../Genesis-8". This would seem to be a problem, "WARNING", what are the rules? Is it no-leading-prefix (so I have to rename ".../Genesis-8" as ".../Genesis-80"?)
Some more warnings:
The first one sounds pretty serious.
I'm getting these warnings at startup; I haven't got round to loading a real scene and, so far as I can see, DS hasn't started loading my own configuration. When it does I see more ("script error line90") which is presumably because layout.dsx is corrupted but I can see no way of fixing it. It would be good to have a beta without the startup warnings then, maybe, we have a chance to actually see what problems currently exist in 4.21+
Is G:/DAZStudio/ also a content directory? Having one content directory inside anothe ("nested") means that DS may start the relative path in the wrong place, which will cause issues on reloading on another system. E.g. you may en up with "/genesis-8/runtime/Textuers/somefolder/somefile.jpg" in the presets you save, rather than the universal "/runtime/Textuers/somefolder/somefile.jpg"
Since 4.22.0.10 everytime I try to save a generated Face Transfer Daz crash and shuts completely down. Anyone having the same issue? It does happen with both Face Transfer 1 & 2. But FT1 works fine on 4.16.
Is that not the 2023 SDK? (It is a macro, rather than a command, by the way.) You can tell where an Iray-related message in the log comes from by the format - if it says Iray before the severity, in square brackets (WARNING, ERROR, INFO, etc.), then it is an Iray message passed through by DS; if the severity comes first followed by "Iray" then it is a DS-generated mesage that is about Iray.
I have the same problem with 4.22.0.10,
so I reverted back to 4.22.0.7,
where Face Transfer 2 still works on my computer.
It has apparently been fixed.
Same problem here.
Fixed (in a forthcoming update) according to the post above yours.
Oki, everything is awesome then ;)
Has the crashing issue been fixed? If so, what version should we be looking for?
I am told that if you keep an eye on the Change Log you should see an entry appear relating to this.
Thanks. I'm watching...
I can't find the forum message again
, but that sample script link Richard posted, restores the Open Recent submenu perfectly. I ran the script and saved a Workspace, and the Open Recent submenu is back and seems to stay.
4.22.0.12, which should be live now.
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/actions/action_menu_submenu/start (Richard posted a link to, he didn't post the sample itself of course)
Thank you for reposting the link. I understood that you were the link poster, not the script author. But I never would have discovered it without you bringing it to our attention.
OK, I "hid" the Ryan Hair by OOT and that stopped the crash of DS 4.22.0.10 Public BETA. Is that going to be fixed in a future version of DAZ Studio or is that something that requires fixes & updates to all of OOT's hair products, so maybe that doen't get down lacking catalogue back sales; in which case a disclaimer should be put on the products' sales page or they should be removed from sale?
Many of the hairs have been updated, and it is a shared file that is tghe issue. Unfortuantely that does mean if you have an older copy in another content directory, earlier in the read order, or if you installed an updated product most recently, or if you use Connect and DS decides to load a product that hasn't been updated, then you may get the bad version.
I've been having a strange display problem since Tuesday, with 4.22.0.10 and now 4.22,0.12. Whenever DS beta goes into a Not Responding state, the DS window remains full size, but all the DS information is squished into the left side and the right side is blank. It doesn't seem to matter what I am doing at the time; it happens whenever DS becomes non-responsive. As soon as DS responds again, the display returns to correctly using the full screen area. I am attaching some screenshot examples.
I had a Windows update about the same time I installed DS 4.22.0.10 on Tuesday, so both changed at about the same time. I also updated the NVIDIA graphics driver to version 546.01 Studio Driver, on the incorrect belief that the change log said a newer driver version was necessary, because a newer Iray version had been merged to 4.22.0.10. The change log was later clarified to indicate that a newer Iray was NOT merged into 4.22.0.10, so the driver update I did was not necessary.
So, now I don't know if the issue was caused by the newer DS Beta, Windows update, or the newer graphics driver, or some other unrelated change that I don't even know happened. Has anyone else seen something like this happen? I could go back to an earlier driver, and see it the problem goes away, but I think I'll wait a bit and see if anyone else has seen the same thing.
EDIT: This was resolved by updating the NVIDIA graphics driver to version 546.33.
I deinstalled the Ryan hair, deleted the local cache of the Ryan hair installer, redownloaded and reinstalled it but the same problem. I have other OOT hairs but not a huge collection of them.
What is/are the shared files that need to get updated? I always install via DIM but for whatever reason sometimes DAZ Studio insists on creating that DAZ Connect content directory and sending some updates/contents for some packages that get duplicated in that connect directory. Are you saying that's the problem? How can I stop that? Delete the entire connect content directory in the File Manager? Or in the DAZ Connect pane?
Select the hair, switch to the Surfaces pane, and look for the Transmitted Color channel. If there is a map in that channel, remove it.
Stop logging in to Daz Studio, the option to log in, is there to enable using Daz Connect for updating/installing products.
DS Preferences -> Startup options, uncheck everything.
The official method of getting rid of Daz Connect highjacked installations, is to uninstall them in Smart Content.
If you have allowed Daz Connect to make updates/installations, those will get priority over DIM-installed items, even in cases when Cinnect installations do noe work.
Had this same issue a few weeks ago. Chalked it, right or wrong, to Nvidias new SysMem. Was using same beta as always (and still am). Only nvidia driver changed. Installed newer Nvdia driver and issue left the building.
Someone had a big issue with windows files being lost ( see tech forum). They never asnwered if they had a newer nvidia driver. Had similar windows corruption but mickey mouse compared to them. Caused again with DS and cpu computation intensive. Am still eyeing Nvidisa new Sysmem.
I've not encountrered such an issue... I think it most likely results from the Nvidia Drivers. 546.01 version for my cards is an NFB version, so versions of 537.58 - 537.70 should be stable.
OK, thanks!