- Thu Sep 18, 2008 1:18 pm
#280610
Probably, your mapping widget is on channel 1 in Rhino's texture-mapping window, but your textures are on channel 0 in the plugin - 1.7 is more picky about having those numbers match, but I'm loosening it back up in the next plugin. There's a reason for the new behavior: if you assign two mapping widgets to the same object, and set up a different texture for each one in your material (i.e. using channel 1 and 2), you can switch between the mappings by clicking on each texture in the plugin. You may be aware that there is no way to do that in Rhino besides for actually changing some parameter in the desired mapping.
Ah, I see your second post now - yes, I definitely recommend using Maxwell materials if you want things to look as good as they can. If you use Rhino's material window, you are just getting code-generated materials, and though I try to make them look nice, there's no way I can compete with a custom-created material. It also explains the mapping issue...your Rhino-assigned texture will be using channel 0, but the mapping widget will be on channel 1 - this will not be an issue when the plugin is less picky about matching mapping channels.
Next Limit Team