I’ve been doing some investing regarding this very well-known issue with Enscape on Rhino as outlined on the forum below.
Enscape seems to be completely clueless about this issue, so I decided to look into issues on technical levels.
First, I suspected Object ID & Material ID, and as it turned out they are static and can’t be altered on worksession. After a bit of trying and error, I’ve noticed that Material Index do get renumbered everytime worksesion gets updated. So, could this be a case of loss of the materials on enscape?
So some questions here, does anyone know what Rhino or Enscape use Material Index for? And, would it be possible to force Rhino to not-renumber them?
I may well be all wrong about this. But it would be great if anyone could shine some light on this issue and hopefully help enscape to resolve this long outstanding issue…
Here are before and after screenshots showing the little code I sued and how Material Index are renumbered after worksession update.
Thanks very much in advance!