k. I believe this is the n1 item on the list and it will be fixed until the public release coming shortly. Hang in there!
Check: https://github.com/mostaphaRoudsari/Butterfly/issues/43
In the meantime, please let us know of the values you had to change manually in controlDict and fvSolution. Was that due to wrong values set from BF or was it because they weren't updated through BF?
Kind regards,
Theodore.…
e sideline on that comparison. But my interest is within the thermal investigations in big indoor spaces/semi-outdoor spaces as I am studying temperature distributions in atria. So it was regarding those kind of comparisons.
I sure hope I have time within my project to test out BF and hopefully compare to Ansys. I'd btw be using the k-w SST solver in Ansys. Which solvers are available in BF for indoor studies?
- Lasse…
.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
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…