HI @ all.

i have an issue when loading a model created in Poser into DAZ, as the original in Poser is using the U_SCale and V_Scale property. DAZ Doesnt seam to be able to interprete these and applies the texture at 100%, which looks messy.

Any idea how that Parameter is beeing set in DAZ?

Also, another issue is, that DAZ doesnt seam to be able tio interprete "spaced" names for textures, so, in Poser named Materials called Walls 1, Walls 2 etc would not be correctly loaded by DAZ as it all calls them Walls. Any idea how this can be corrected?

Getting a little frustrated about this as the products i produced in Poser dont seam to be fully useable in DAZ.... thanks for your input,. Much appriciated.

D|S 2.3 doesn't use node-based textures, so any P5+ procedural materials won't work properly.

D|S can handle textures with spaces in the names -- does the texturemap line in the .pz2 have quotes around the entire filepath and name?

Hi mishamcm

thanks for the answer. It loads the texture, yes i used "quotes" around the pathes, so its loading the file, but the material part of the pp2 (or cr2 whatever) would use ie a line like

material Bath Walls

shown as Bath in DAZ. So if i had another material call Bath Sink it would be overwritten and DAZ Applies the material from the Walls to the Sink. Using Quotes there like

material "Bath Walls"

didnt make any difference. I have just a little given up i must say and accept that DAZ Is very limited when it comes to Poser files i assume....

using image names like that can have detrimental effects in Poser, as well.  It has this glitch where, if the texture name is a two-part name without a joiner (such as an underscore or hyphen), Poser looks for the first part of the name, and will go from there.  I would recommend, honestly, for all texture creators to make unique names for their textures, as even if I load your Bath Wall figure, your folder in my runtime might not be at the top.  The first folder in my runtime (Starting with the main runtime) with the texture Bath Wall.jpg will be pulled, and it most likely will not be yours.
This goes for .obj's as well.  Poser, especially for those of us running multiple runtimes, is not picky when it comes to loading things.  It will pick the first one it finds that it thinks fits the bill, whether you do or not.