bagginsbill opened this issue on Apr 23, 2008 · 2832 posts
bagginsbill posted Tue, 13 January 2009 at 7:25 PM
Is that how it applied? Some of it worked and some didn't? Or did you go manually fix some?
When you run VSS on a figure first time, it studies how the image maps in the existing materials are wired up. For Image_Map nodes that are not explicitly named, It tried to guess what they are for from how they are used. For example, if an image map is plugged into DIffuse_Color or Alternate_Diffuse on the root node or plugged into some other node that eventually plugs into the root node Diffuse_Color or Alternate_Diffuse, then it will assume that is a Color Map. It will then rename that Image_Map node to be Color Map. That image will be used where the template says the Color Map is supposed to go.
So this boils down to what the pre-VSS shader looks like, and/or what image maps have names if any.
Once it has run, the shader is now replaced with the VSS template shader. So the next time you synchronize, it will already know (from the previous run) how it mapped the images.
If it made a mistake, you can go into each material zone that is broken, and correct the files associated with the Color Map, Bump Map, etc. After that it should work correctly.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)