HNY all!
after what feels like forever I’ve finally managed to entice some of our Rhino wranglers away from their beloved Vray to play with Enscape. Good news!
Bad (?) news - their enthusiam for assets (ootb and custom) has led to considerable geometry bloat, stalling both Rhino & Enscape on (fairly) decent machines.
Disclaimer, I’m not all that au fait with Rhino, so I’m shooting a little in the dark here - but…with Revit we’ve got around the mesh geometry weight/mess of the enscape assets by using the GUID asset parameter in simple volumetric proxies - and I’m digging around an asset block here in Rhino right now to see if we might do the same… but I can’t see where Enscape might be fetching the proxy value (that I’d hope to point our GH peeps at so they can rip them out) - perhaps Enscape-for-Rhino thinks/works different?
Either way, has nay one any ideas / solutions for approaching the same?
Thanks!
aha I think I got it (Object Information, not Block Properties)
TBC
nope spoke too soon, those Block ID: values are internally Rhino based, but exploding one of the asset blocks and reaching to the mesh does give us/me:
UserData ID: & Plug-in: fields that look promising… but I’ve (presently) no idea how to get at those…?!
*EDIT
…yeah so (as I probably should’ve expected) this is a bit more involved in Rhino than it is in Revit… I’m certainly not conversant in C# and API to tackle this looks to be leading me down:
https://developer.rhino3d.com/api/rhinoscript/user_data_methods/user_data_methods.htm
so I’ll have to park this curiosity for now.
boo.
Sorry for bringing this old topic up. I have thousands of trees in a Rhino file that I am trying to display as pointcloud object rather than mesh. @Clemens_Musterle could you please share with us some insights on how to turn Enscape asset into proxy display geometries? Thanks.
Hey @joeykey ,
not sure I can follow 100% of what you’re trying to do.
But in general the Custom Asset Editor allows you to define an arbitrary placeholder model in the UI:
You can import a arbitrarily reduced version of your mesh to avoid slow downs in the CAD’s viewport, but get the full quality in Enscape.
Point cloud rendering on the other hand is not a supported feature in Enscape at the moment.
Hi Clemens, hope you have been well and thank you for your response! Let me clarify what I and OP are trying to do here.
First you see this Enscape asset is taking 232 faces. Imagine you have a forest of this that would very quickly bog down the viewport.
Apparently you cannot hide or do anything to the mesh that live inside the Enscape asset as the mesh uses some “ID” to communicate with Enscape. My question is - what is that ID? and how could I bind Enscape asset to some lightweight proxy mesh with less faces to not bog down viewport? Appreciate if you could shed some light on this topic.
A workaround here for folks that run into this problem:
You can delete the mesh faces of Enscape mesh and leave even just 1 face and Enscape can still recognize the asset. Here a reduction from 232 faces to 15 faces.
Hey joey,
thank you for the in-depth explanation and sorry for the delayed reply.
As I’m not an expert on the CAD (and specifically Rhino) domain, I had to check back with other developers on your question.
Long story short: What you’re already doing is probably the best workaround for the time-being (and it’s not recommended to manually manipulate the IDs).
That being said, we’ll discuss potential future options to allow replacing a proxy geometry.
