Similar to this post , I’m having trouble with ShapeDiver not consistently displaying geometry I am uploading. However, I do subscribe to the Designer account, so it should work with Rhino 7.
Here and here and here and here are different examples with similar Grasshopper files that I’ve been messing with to get everything I need to appear.
I am expecting it to look like this when all the toggles are toggled on. - It should have color coded walls that change depending on the “Category” dropdown menu, Angle numbers on those walls, the floorplan and column, and the ‘Pad’.
Unfortunately I might need to give up on trying to get my company to shift to using ShapeDiver since things like this are being unreliable, and I’ve spent more time than I’m allotted trying to get it to work. Sorry! But my last effort can be this forum post!
Your account allows you to switch to Rhino 7 but you did not do it yet, all those models are uploaded to the Rhino 6 system. Please go to the “Backend” section of your account settings and pick the Rhino 7 system there. All models uploaded afterwards will be run on Rhino 7.
We will soon make it more obvious to do this step by sending a warning when uploading Rhino 7 models to the Rhino 6 system.
if its helpful, I made the “info” section of each one of these links say what isn’t showing up and if it was uploaded after the Rhino 7 backend setting changed.
This is likely what happens also on the servers. Can you describe what type of geometry you are internalizing there? Can you maybe also try to mesh all this geometry and internalize the meshes instead?
In the example created with the 1.13.1 version, I still get empty internalized geometry when I open the definition, and it seems that this problem is not linked to ShapeDiver. Could you save a gain the definition as .ghx and post it here? And could you tell me more about your process for internalizing this geometry? Is it done in the traditional way (select objects from the Rhino document and right-click > internalize) or do you use some external tools to do so?
Hey! Yeah sure let me put that together for ya, thanks so much for the attentive help ! <3
Yeah I was planning on having my coworkers use the Reference By Layer node from Elefront 4.2.2 (but I totally can update Elefront), so the geometry comes from that
I meant to save the definition as .ghx (instead of .gh) so we can easily check if something is wrong with it. But as you mentioned Elefront, we do not support this plugin, and it is likely that this way of internalizing geometry is creating problems on our servers. Please test by internalizing geometry the usual way and let me know if this solves the issue.
This is internalized without using Elefront. However, my new theory is that it’s taking issue since the Rhino geometry that I am manually internalizing, was previously edited by Elefront in a different Grasshopper file.
Ok that was definitely it, sorry for bothering y’all with such a small human error! Here it is, if I can finish it up in time, I’ll let you know what our client thinks of it!
