For some reason that scene doesn't come in with bump or normal maps, neither through 3Dchange nor CC3.
They are present in DAZ, but not exist in the .fbm folder and not embedded.

However, here are a few renders after fixing a few things manually, hope you like them :)

---

Oh, for a moment I thought it was the Desert Motel station -- my Python routines brought in all the textures properly.



If you have a link to the Daz model I'd be happy to see what's going on with the textures (just where it is on the Daz product page would be fine).

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

Thanks for taking the time Mike.
Here's the link: https://www.daz3d.com/fg-gas-station

---

Ah, yes, Mr. Fugazi.  Well, he's a difficult developer.

If you examine the textures used in his models (but let's just take this particular one) what he does is split up the objects from the scene into separate folders.  For example, the Soda Machine 2 doesn't exist in a general folder (like most Das Devs do), but in the Fugazi1968/FG Gas Station/Soda Machine 2 folder.  What we would like would be to have that Soda Machine 2 folder just be in the general FG Gas Station one because it's the base folder for the object and thus the only place we're looking for stuff.

My Python routines don't consolidate those folders -- would be a difficult proposition to do anyway but wouldn't do a ton more good as located each individual prop/piece still might not work (see some of my other videos to note).  And since the CC3 import through Transformer uses my Python logic, it operates the same way (so you can't get them through there either).

For fun I'm going to play around with this a bit this morning and see if there's any way all of those folders could be automagically smashed together in my routine to make this work (and, if so, I'll see if the CC3 dev can do the same thing for Transformer).  I'll let you know any (or no) progress.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

Hmm, now that I look a little further I see there are very few bump/normal maps anyway -- there are a couple (plasterwall, for example) but because it's improperly named (by the Dev) my routine couldn't find it anyway.

There ARE a lot of roughness/metallic maps, though -- did my routine not find them?  Or did you not run it?  I'll have to see if my own routines in iClone can do it first.  I can handle a LOT of things but bad naming by the Dev is not one of them (and never could be -- just WAY too many variables to try and account for).  Let me give it a try and we'll see what happens.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

Yeah, my Pythons stuff doesn't work much better.

There are some Daz devs just better to stay away from - unless you just like doing a LOT of work.  In this case you can spend a few hours and get most of the textures back in (although, as I said, FG seldom provides bump/normals -- there are only a handful in there for the hundreds of objects).  As always, I say if there is any Daz item you want me to check out please ask here first and I'll let you know how much work it might be and/or how it will look in iClone.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

Thanks again Mike.
No the roughness/metallic maps didn't come in either.
I only tried it with 3DXchange and CC3, but not your blender script.

---

No, I was using my iClone python script -- does a much better job than the Blender one but not in this case.

His stuff is just... weird.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

Well, it seems some of these developers care little or nothing about file naming conventions.
For example, why would one call the diffuse map '1.jpg' and the bump map '2.jpg'?
Or, some files have underscores to prevent spaces, and others do not.
That's a complete mess. And what adds to it, is obviously an export problem of DAZ itself.
So i found several threads via google, where people having issues with bump and other maps not being included in the FBX export.

Since CC3 transformer has the ability to detect files based on a variety of patterns, i wonder if it would be better to fix those texture names already on the DAZ side?
https://manual.reallusion.com/Character_Creator_3/ENU/3/Content/Character_Creator_3/3/09_Transformer/Advanced_Conversion.htm#Naming_Regulation

---

You're suggesting that Daz devs do this?  Or people do this IN Daz?

It would be just as much work doing it in Daz before export (maybe a lot more).  Oh, I guess there is some scripting inside of Daz, but I'm not going into THAT black hole.  Particularly when MOST Daz devs are just fine (there really are a minority who don't play nice with others).  But if someone wants to give it a shot (at a Daz script) I wouldn't mind advising them.  From afar.  Like "there's a good boy" <g>.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley