Serious geometry corruption in Enscape for Rhino – keeps happening across files

Hi everyone,

I’m running into a recurring and frankly unacceptable issue where clean Rhino geometry turns into mangled surfaces the moment I open the model in Enscape.

  • Left side of the screenshots: Rhino 7 model – watertight polysurfaces, no naked edges, no bad objects.

  • Right side of the screenshots: The exact same file in Enscape 4.0 – faces disappear, edges tear open, and entire slabs invert into black “voids.”

I’ve attached three views that show the problem at both close-up and overall scale.

What I’ve tried

Attempt Result
Explode the offending polysurfaces, then re-join No change
Update graphics drivers / Enscape version No change.
Mesh settings in Rhino (Jagged & faster, Smooth & slower, custom) No change.
Export selected to a fresh Rhino file Still broken once Enscape starts.

Why this is a problem

It happens on multiple machines (RTX 3080 Ti desktop + RTX A4500 laptop) and on several different projects, so it’s not a one-off file corruption.

Exploding every architectural element just to make Enscape behave is not a viable workflow for large commercial projects.

Clients see these artifacts in live reviews – not exactly confidence-inspiring.

Ask

Has anyone found a reliable fix that doesn’t require exploding polysurfaces?

Devs: can you confirm this is on your radar and provide an ETA for a fix?

Any diagnostic logs or sample files I can send to speed things up – let me know.

Thanks in advance – this issue is blocking deadlines and needs urgent attention.

Oscar



If you run, Selbadobjects , does that select the object? Is it a open poly surface or closed?

It´s a closed polysurface, no naked edges. It´s also not a bad object

Hi @oscarm and thanks a lot for this report.

One of our Rhino specialists would gladly check this out in detail. For that it would be ideal if you could forward this behavior via our Help Center/Support button as detailed here and we’ll be able to assist you further from there. It suffices if you simply include a link to this thread in the submission form for reference as well.

Please also feel free to let me know once you’ve submitted this via said Help Center/Support Button so that I can keep an eye on the case right away.

Thank you very much in advance!

Thank you Demian, I´ve submitted a ticket

We have been experiencing this on several different pc’s and 3D models at the office… If we remapped the texture of an object it sometimes “cleaned” it self. But not every time. Don’t know how to fix it though… Our work-around was using a different renderengine…

Hi @SOS , allow me to hereby share with you what has helped the previous user @oscarm with resolving this particular problem:

So in general you can of course start trying this one a single machine first and by making sure the latest GPU drivers and version of Enscape is installed, if that helps you can continue updating both on other machines where this issue persists. In case you’re unsuccessful from the get-go we also reccomend the general clean re-install of Enscape and ideally the graphics card drivers too as detailed above.

Otherwise please kindly forward this behavior through a support report incl. log files as well so that our support team can identify why this still persists.

Thank you in advance for your cooperation!