.OpenNURBS.OnCurve' can not be converted to 'Table 1 dimension (s) RMA.OpenNURBS.OnBrep'. (Line 83)
Message d'origine:
Après essai:VB Scipt:rhUtil.RhinoSweep1(x, y)X OncurveY OncurveError: Une valeur de type 'RMA.OpenNURBS.OnCurve' ne peut pas être convertie en 'RMA.Rhino.MArgsRhinoSweep1'. (line 83)Error: Une valeur de type 'RMA.OpenNURBS.OnCurve' ne peut pas être convertie en 'Tableau à 1 dimension(s) de RMA.OpenNURBS.OnBrep'. (line 83)…
Added by Rémy Maurcot at 2:25pm on December 16, 2010
A low-resolution work. Real time motion capture display made with an 11x8 (88) pixels iPad matrix using Grasshopper + Firefly + Pure Data + TouchOSC for iPad.
a working solution with replacing this line of code with:
Dim charList As New List(Of Char)(charArr)
Is this because of a version incompatibility (I'm using Rhino 4.0, and GH 0.8.0062)? Just curious.
Regards,
JJ…
f the mesh was self-intersecting everywhere. So instead I used Millipede (isosurface) to get the same undulations, but ignore the complex 'folds', you can see the difference in cross section thickness. I then tessellated it with the inverse pattern of the outer surface.
To make it a single 3d printable mesh, i just deleted a single face on inner and outer skin, then lofted the naked edges. (creating a tiny hole through the model). Therefore creating a single mesh that folds in on itself, not sure if there is a better way of defining the space between two meshes as the solid area...
Full GH (Kangaroo - Meshmachine - Weaverbird - Millipede)
Special thanks to Laurent Delrieu for his interesting offset mesh method that i based my approach on.
http://www.grasshopper3d.com/forum/topics/offset-mesh-problems-with-3d-mesh-with-weaverbird…
Added by Nick Tyrer at 5:25am on December 10, 2015
ases where you have angled shades and the component is doing trigonometry to figure out how close the blinds could be to the glass without touching. I just re-wrote the code so that, now you cannot have the blinds closer to the glass than half of the blind slat depth, which seems to be the limit of what E+ will tolerate.
Also, E+ does not like it when you input blinds that are perfectly at 90 degrees so I changed the component to automatically write out shades at 89 degrees when you connect up 90.
Using the Shade geometry as context worked perfectly for me and I am not sure what was wrong in your situation.
See your working file attached.
-Chris…