But when I change a parameter, it disappears again…
I attached my grasshopper file (I tried with a simplified version but their was not the issue, maybe the issue is the complexity of the file?) test 1 étagères.gh (5.3 MB)
Your model is complex but it’s well structured and it will work fine, you just need to take extra care when working with data trees in ShapeDiver. I had a quick look on your definition and you flatten and simplify trees a lot. This might not be a problem on your computer but it causes unpredictable behavior on the platform for a number of components including XFromGeo. Make sure that geometry and corresponding transformations are on correct tree branches and don’t get mixed up after flattening or simplifying. This video tutorial explains the topic in more detail.
Thanks for the response.
This does not seems to be the issue as the model appears when I click on the camera button. Therefore the grasshopper file works, the issue seems to be in shapedriver apparently… Do you know if this issue could be reseolved?
Thank you for your reply. I checked the data tree and I am pretty sure of its structure. Here is a video capture of my issue.
The initial configurations is the most complex possible. I can see it when I click on the camera button. However, when I change the parameters for a simpler configuration, I cannot see the model anymore, even if I click on the camera button. Therefore, I am pretty sure that the issue does not come from the Grasshopper file, as I am able to see the most complex configuration. Could you please try to check if the issue may come from shape driver?
Thank you for your revision!
The reason why I kept the null elements is that if a branch is empty the XForm parameter, the corresponding Geo branch will appear in its default state. I would like that it does not appear at all. In rhino having null elements resolves the issue, do you know how I could do for shapedriver?
You just need to check which branch is empty and remove the mesh from the same branch before entering it into the C# component. Alternatively, you could also use the Clean Tree component to do a parallel clean up