Texture Cache build up during Enscape Launch

Rendering
1

Hi all,

Firstly want to say I have raised this issue directly with Enscape with no resolution since September so wanted to ask here as well to see if anyone has any ideas.

Using Rhino7 in certain models (possibly where worksharing is being used) when launching Enscape the folder C:\users%username%\AppData\Local\Temp\McNeel\Rhinoceros\V7\Texture$Cache$ slowly builds with black and white tiff files. Once complete the Enscape window shows the model. The issue here is two things; For example in the model I just tested (which admittedly is large) this cache grew to 105GB so Enscape takes a long time to load whilst this happens but also if the user has limited disk space the machine grinds to a halt.

I don’t know if this is an Enscape or Rhino issue but there are combinations of Rhino and Enscape where this behaviour doesn’t happen. Those are, Rhino 7 with Enscape <3.5 & Rhino 8 with Enscape 4 (preview). So any version of Enscape 3.5 has the issue in Rhino 7 but I can’t replicate it in Rhino 8 however only the Enscape 4 preview loads in Rhino 8 so I can’t fully test.

We have found one workaround in Rhino which is the main reason to post here, if the material type is changed to Enscape on all materials then this doesn’t happen.

Sorry if this is not clear, anyone got any ideas?

Thanks

2

If you’re using procedural textures on Rhino materials then it may very well be that for each surface the material is applied to the textures get back. If you have many surfaces you’ll end up with a lot of baked textures.

So check if you’re using rhino procedural textures - basically anything not one of bitmap texture, simple bitmap texture and high definition range texture.

Changing to Enscape materials probably means that no conversion needs to be done.

edit: if you have lots of copies of the same object consider making block instances out of them, that will bring down the amount of baked textures.

3

Thanks for this, I’ll have a look in to it and come back.

4

For the benefit of anyone experiencing the same thing, I have just received an update from Enscape support, this is a known issue resolved in Enscape 4 in Rhino 8 only. Can confirm I have tested Enscape 4 (preview) in an evaluation copy of Rhino 8 and the issue does not occur.