[osuire]

Hi Jeremy,

I sometimes need to re-attribute a material to a layer to make Rhino take into account changes that have been made to the layer.
I had the case with a material for which I had to update the paths to the maps.
In the "Rendered" viewport, I still had the pajama stripes on the object with the missing link.
Had to re-drag-and-drop the material with the updated links on the layer to see the proper preview.

In the same field, I noticed that the indication "has bad paths" does not update when the paths are good anew : it takes closing and re-opening the material to give the proper indication (Has bad paths = No).

Cheers,

--
Olivier

[JDHill]

I'm trying to duplicate this, but not quite getting there:

• 1. create a document
  2. drag a textured material onto a layer
  3. save the document
  4. close Rhino
  5. move the texture somewhere else
  6. open the document again
  7. the texture is missing
  8. browse to find it again
  9. objects on the layer now have the new texture

I do see that the 'Has Bad Paths' link is not updating after step 8 -- as you say, I need to select a different material, then this one again to reload it. However, the viewport seems to be updating fine without reassigning the material. I think there was a problem with materials being saved in one of the recent betas; could what you're seeing be related to that? Meaning, that the material really was not assigned to the layer until you re-assigned it?

[osuire]

Oh !
I forgot to tell you I'm using march 16th 64bit WIP...

[osuire]

Proof by image...


--
Olivier

[JDHill]

I'm not doubting you, Olivier, but I'm not seeing it here. What I would be interested in seeing is, if you Export to Studio, is the correct material assigned? If so, what happens, back in Rhino, if you use the Refresh Viewport Materials command in the plugin's Functions toolbar?

Lastly, is this only happening in V5 WIP?