This is just the basic Poser values, I don’t have a running copy of Poser, I’ve got a copy of 10, but it won’t run under my current Linux/Wine environment. I added a multiply node and RGB color because I seem to remember Poser color interacted with the texture something like this.
I’m not loading anything in particular. Just poking around my various runtimes and choosing things at random. I took a long look at the Poser node tree stuff today (various Jesse materials) and I think, long term, loading those might be doable.
For now, I think its best to stay with the old-school materials:
The keywords with hashes are the ones I’m actually using in the material setup right now. (I just committed a patch to turn on tMax.)
Blender doesn’t have a per-material KaColor that I can see.
I was thinking about averaging KsColor to set specular? Principled BDSF doesn’t have a KsColor per se?
TextureColor - should I be using this instead of KdColor when multiplying textures? Check Posette since that generation uses this method?
bumpStrength - I guess I should capture it and plug its value into the bump node
ksIgnoreTexture ?
reflectThruLights and reflectThruKd?
ReflectionColor?
ReflectionStrength?
I’m very interested in thoughts about leveraging the Poser values to create good materials, whether with the node setup I have or another one. I’m trying to make the tool modular enough that we can plug in entirely different node setups without too much work as well. LIBMaterial.py takes the parser output and returns a Blender material that the importers use.