Hidden geometry in SketchUp shows up in Enscape rendering.
Open the file in SketchUp. Start Enscape and click a scene in either Enscape window or in SketchUp. Hidden geometry shows up in the render.
A bug?
/ Kaplan
Hidden geometry in SketchUp shows up in Enscape rendering.
Open the file in SketchUp. Start Enscape and click a scene in either Enscape window or in SketchUp. Hidden geometry shows up in the render.
A bug?
/ Kaplan
Hi @Kaplan , could you perhaps also upload the project to wetransfer.com for example, and share the link here again? It seems the file upload did not work properly in this case. I’d love to check out the scene of course for any issues.
Hi @Demian_Gutberlet . Sorry about that. Link should work now ![]()
Thanks a lot. I’m able to reproduce this behavior accordingly, but it also seems that you’ve only hidden the geometry of the scene, not the “object” in and of itself which this part you shared consists of - In this case, please try to use Right-Click → “Hide” once more in the “View hidden geometry” scene and then create a new scene with those adjustments through either SketchUp or Enscape itself, which should do the trick. Let me know if anything is unclear!
You are most welcome. ![]()
I’m aware that Enscape seems to hide both geometry (specific faces and edges) and objects (groups and components) as expected, but in this specific file something goes wrong. I suspect it has to do with the fact that my file originates from before SketchUp 2020 when the “hidden objects” feature was introduced, thus the geometry is hidden in an old-fashioned way.
Nevertheless, regardless of the hiding-method, hidden geometry/objects in SketchUp should not be visible in the render, right?
Thanks for the quick reply @Kaplan . ![]()
I do agree - There may be a small issue present that hinders the hidden geometry to be still displayed in Enscape, although as you say it thankfully seems to only persist with files/geometry from an older release of SketchUp. I’ll forward this as a bug to our Developers just to make sure they are aware of it, thanks again for the report!
Last but not least I also hope that this behavior will of course not influence your workflow in a negative way too much.
Sounds great.
No, not at all - now that I’m aware of the issue ![]()
I’m new with Enscape, so I’m testing the different features by using old SketchUp models, and trying to replicate renders made with other applications