[gtalarico]

I remember thinking that the SU material editor would not affect a material if it was a MXM mode material...

I am working on a model that has two similar materials, but one is more shiny. When the textures are copied to SU, they look exactly the same;
so I changed the hue of one of the textures (in SU) so that I could more easily tell them apart. But then at render time, one of them looked purple!!!

I checked that the MXM link was ok but making both materials 100% black, and the mxm link was ok.


Is this by design or a bug?
(I personally would prefer it the SU material editor would not affect MXM mode materials... for SU embeded materials it's ok...)

[JDHill]

I think I see what's happening there -- it is because you have pack & go enabled. Since pack & go makes all the paths in the MXS file relative, Maxwell ends up using the SU-modified texture in the pack & go folder, rather than the one actually referenced by the MXM. I will have to think about how to handle that.

[gtalarico]

You are spot on...
I was noticing that I had the "changed" texture in the texture folder....

[gtalarico]

PS: This keeps happening even with "Pack and Go" turned off (and textures folder cleared)

[JDHill]

I can reproduce that in Fire, but not otherwise. Meaning, specifically:

1. Disable Pack & Go.
2. Assign an MXM Mode material.
3. Copy texture to SketchUp material.
4. Change texture color via SU.
5. Render in Fire: colored texture is used.
6. Render or Export to Studio: original texture is used.

Please confirm that this is what you are seeing there.

[gtalarico]

JD:
Was this ever resolved?

(Sorry I disappeared! I think I finished that renderings and forgot about it!)

[JDHill]

The specific steps I list above are still the case.

[gtalarico]

Steps above work as deacribed, but only if pack and go is disabled.

But since I use PAG it to render to network, I still finding myself having to reset texture colors in SU before rendering.

Not a big deal though.