Union Suit Issue
Anyone else having a problem with the union suit. It loads but none of the hierarchical materials load.
This is what I see in the log Begin asset load (merge): /People/Genesis 9/Clothing/Lyrra Madril/UnionSuit/Materials/US Red Knit.duf
2023-12-21 15:24:00.369 [INFO] :: Determining missing assets...
2023-12-21 15:24:00.568 [WARNING] :: Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found.
2023-12-21 15:24:00.568 [INFO] :: Error loading asset: C:/Users/Public/Documents/My DAZ 3D Library/People/Genesis 9/Clothing/Lyrra Madril/UnionSuit/Materials/US Red Knit.duf
2023-12-21 15:24:00.568 [INFO] :: Operation failed
I've manually installed it and used Install manager. Have the same problem with both.
Comments
I ran into this problem also but it was with a Face Transfer character and I wasn't sure if there was a weird hierarchy issue that I didn't know about yet. It was expedient just to update the surfaces manually. But I'm watching this thread for an answer.
Did you select the G9 character when applying the hierarchial materials?
I tried both the character and the suit. At first I thought it might be because the character was a preload and not named Genesis 9, but then I tried it on a base G9 and had the same issue.
Parent it to Genesis 8 Male and try again, that is what I see inside the Duf.
That's the problem right there. It's supposed to be for Genesis 9.
Really quick test and it works fine. Are you using G9?
Just got a chance to check, and they work fine for me, too.
And you tried applying the hierarchial material presets?
Downloaded the installation file again, opened "US Red Knit.duf" in Notepad, searched for "Parent" and I find "Genesis 8 Male"
Just quickly checked, the H.Mat Presets also work fine for me. Though the vendor used the Preset files from the old product of G8M version, the presets still work on G9 because G8 commonly uses the name of "geometry" as id as well as urI in it geometry definition file (dsf). Then H.Mat presets derive from this definition.
Starting from G9, geometry id and urI was identically defined as Genesis9/Genesis9-1. So in general, H.Mat presets from G8 work on G9 but they don't work inversely...
Finally got back home.
Loaded a G9 character and fitted the Union Suit on it.
Selected the character and applied US Red Knit preset... "Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found"
Selected the suit and applied US Red Knit preset... "Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found"
Loaded a G8M to the scene and changed the parent of the Union Suit to G8M (Suit still fitted to G9)
Selected the G8M character and applied US Red Knit preset... All is fine, the material was applied to the suit.
Using DS 4.15.0.2
For me the Genesis 9 presets work, as long as the suit is selected. The readme isn't showimg any updates but I don't think it appeared with one.
Last year we got the unionsuit for G8M. Maybe the user is applying those hierarchical materials to the G9 unionsuit by mistake.
That makes sense. I'm also using 4.21.
That 2022 suit was one of my favorite PA gifts. It was much appreciated and so was your render of it.
I get this error if I try to update the materials when the suit is on a stock G9 figure. If I put a G8 male in the scene and put the suit on him, I am able to update the materials. Is it easy to update the files so they reference G9 instead? (FWIW, I am using 4.21.)
Materials don't work for me.
When you are getting the errors are you using smart content? I had no issue with G9 and the G9 materials but I don't really use smart content.
For me, I load the character, load the clothing item with the character selected, then load the material pose. Error with G9 selected, error when clothing is seletcted. Latest version of Studio. Windows system. Same process I have used for years beyond count.
I'm still wondering about those that do not get the error, as the Duf file refers to G8M
Which version of DS do you use, the whole version number?
4.22.0.15 Pro Edition (64-bit)
Latest Genesis 9 has the definition of Alias to support Genesis 8. In fact all G8 H.Mat Presets should work on G9. I don't have the older versions of G9 Starter Essentials but pls check "Genesis9.dsf" in your data folder, and make sure you have the latest G9 update installed.
Without the line shown in the screenshot, there'll be an error when applying H.Mat presets ~~
Thank you @crosswind. I was having the issue of material presets not working...checked my G9 base & did not have this line. Updated starter essentials & all works well now.
I don't have that line. How do I update the starter essentials. I recall updating them a couple of weeks ago, so I am not sure why I don't have the latest version.
My version of the starter essentials is: "file_version" : "0.6.1.0", and it was updated via DIM on 16 December 2023. Looking at G9 change log this issue was fixed (lines added about aliases) on 2022-12-07 "Added G8 aliases so HMATs can work on G9"
I have manually re-installed over writing all files and still no "aliases" in the file.
You're welcome ! Merry Christmas !
Yes and the package you've installed seems correct as the latest G9 starter package is dated Dec 16, 2023 ... Besides, that file_version (DSON file ver.) usually means nothing to users as very less people modify it intentionally... but it should be "0.6.0.0" in the current "Genesis 9.dsf".
More likely you ever installed the very initial version of starter essentials via Daz Connect I presume.. This version is loaded first...
Pls check it carefully. If so, uninstall it in Smart Content or break the link of Connect folder in Content Directory Manager for a test.
Merry Christmas !
I uninstalled G9 starter essentials and re-installed. No change. I bought G9 as a pre order and downloaded the starter essentials as soon as G9 was available. I use DIM to download and install. http://docs.daz3d.com/doku.php/public/read_me/index/86958/start also has the same date. Your date is earlier, I am not sure why it is a pre-release date.
I don't know the reason for the time being. But you need to check if there's any copy of old version in other library...Meanwhile, extract the dsf file from the latest IM package... if it is still not the correct one, better submit a ticket.