Current Materials data including settings are stored as assets.
This issue recommends using values PrimShapes for the materials metadata for faces. The PrimShape data is already organized by prim faces. This is how Materials were implemented in Halcyon. It has the advantage of not spamming the asset database with materials settings in cases where someone is changing materials settings on the fly in scripts. It essentially makes the scripting functions useful.
Also requires a touch in the OAR save/restore code to handle materials correctly since they are no longer loaded from assets. Materials coming from an older OAR would need to be converted when read in/written out.
Current Materials data including settings are stored as assets. This issue recommends using values PrimShapes for the materials metadata for faces. The PrimShape data is already organized by prim faces. This is how Materials were implemented in Halcyon. It has the advantage of not spamming the asset database with materials settings in cases where someone is changing materials settings on the fly in scripts. It essentially makes the scripting functions useful.
Also requires a touch in the OAR save/restore code to handle materials correctly since they are no longer loaded from assets. Materials coming from an older OAR would need to be converted when read in/written out.