Material overrides do not persist upon new version load

Trying to test the link and update workflow as aluded to in this article

n Envision, importing a file doesn’t embed it directly into your scene - instead, it links the file. The content of the linked file remains connected to the original source file. Linked files can exist in multiple versions, and you can easily switch between them through Envision’s user interface while preserving any overrides or adjustments you’ve made. This linking mechanism allows for a flexible, non-destructive workflow.

  1. Model in Rhino 8
  2. Assign Enscape materials and apply texture mapping.
  3. Start Enscape, export vrscene (exports .vrscene file and .data folder, the .vrscene file is autonamed with the scene name and timestamp e.g. Enscape_2025-09-18-17-51-59_Enscape named view 1.vrscene)
  4. In Envision File → Import… and import vrscene.
  5. In Envision apply new materials to imported scene elements… so far so good.
  6. In Rhino, add scene elements, move objects and re-export .vrscene.
  7. In Envision, select imported scene object, select version and replace from new .vrscene file.

THIS IS WHERE I’M CONFUSED: The scene materials are completely reset as if it’s a new import. All elements previously turned off are on again. Should these overrides persist? If not then what overrides and adjustments should persist?




​​​

Hello, this is unfortunately a known issue on our side (reference: EC-1865), related to the current process of unique asset export. We will provide an update here once any new information becomes available.
For reporting additional issues, please create a thread in the following section of our forum:
Chaos Envision Issues

Thank you,

Thank you George,
Is the reference EC-1865 something I can look up or is that a Chaos internal reference only?

Hello, yes sorry this is for internal use only ;).