all normals got pointed to the outside.
But I am still not out of the woods - even though the normals are OK now. I attached a 3DM file baked from my current GH layout. The part is made using 4 basic steps: (1) capping the outside surface which is made by joining 2 surfaces, each lofted from 11 polyline curves, (2) capping the inside surface made by lofting 11 circles, (3) whacking 5 units of height off the bottom of (2) by doing SDiff with a 5 unit high capped cylinder, and (4) using SDiff to subtract (3) from (1)
Step 3 is necessary to allow for a solid bottom thickness of 5 units. All the surfaces are NURBS, none have been converted to meshes.
I would have thought that there would be no problems printing this part because it is made from only solid surfaces. The 3DM file has no naked edges - which is what I expected. But my generated STL file is 23.19 MB in size and the 3D Builder program says it has errors. The 3DB program "fixes" the errors, but when it does so it closes the top of the part, so that function is useless. 3DB will also simplify the STL file and create a resulting file that is much smaller, but this also has problems that would result in a failed 3D print.
I totally realize that my problem may lie completely outside GH & Rhino and I don't mean to add clutter up this board with extraneous posts. It's just that I have not had issues like this until I tried the idea of joining 2 lofted surfaces that have reverse twists. I have made many parts before that included reverse twists - but not lofted surfaces. Here is just one example: http://www.thingiverse.com/thing:1606442…
Added by Birk Binnard at 3:22pm on September 14, 2016
s
(distance from Spine to Profile)
4) Create Circles at each floor
5) Rotate Each Floor by twisted amount
(according to height of floor)
6) Divide each floor by number of Flutes
7) Flip Matrix of Flute Points (version 0.7)
(if using v0.6 then search flip matrix on site for method)
(Rows to Columns)
8) Interpolate Curve through Flute Points
9) Mirror Flute Curves
10) Create display grid
11) Make a vector 2Pt from the floor centre
to the corresponding display point…
I extract the first two with a "Redim Preserve t(1)" command.
In the first case, the redim is correct, Line 7 = Line 2 and Line 8 = Line 3. It just kept the first two values like it is supposed to be.
But, for the second curve starting Line 9, some t values are messed up after the Redim. Line 16 = Line 17 despite Line 11 was different from Line 12. That's what is creating a problem later in the Split.
Weird.
…
se of the tool at one building per time and it is even not very efficient. For example in a situation like the image I attach I have four buildings facing the area on which I need to calculate the solar envelope that guarantees 2 hours of direct sunlight on all the surrounding facades. If I have to input the sun vectors that guarantee 2 hours insolation for the South facing facade (from 11 to 13) then the solar envelope is most likely not correct for the East and West facing facades and it totally null for the North facing facade. So the suggestion is to develop further Solar Envelope component and add to the _sunVectors input also another input for the required minimum hours on specific facades. Thank you!!
Francesco
…
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
ror "nighttime"
how could that be - must be in the weather file i assume - is there anyway to fix this ?
suncalc.net gives me the following
00:00—02:17 — night
02:17—03:43 — astronomical twilight03:43—04:39 — nautical twilight04:39—05:19 — civil twilight05:19—05:23 — sunrise05:23—21:11 — daylight21:11—21:15 — sunset21:15—21:55 — civil twilight21:55—22:51 — nautical twilight22:51—00:17 — astronomical twilight00:17—00:00 — night
plz help - thank you !!!
…
(18, 11, 0, 17), also put in the assembly component.
How can I know which value of the reaction forces correspond to which support?
In the manual is stated that when the reaction force component is used, than the values are displayed in ascending sequence of the corresponding nodes.So if I input the support nodes like thispoint with index 18point with index 11point with index 0point with index 17are the reaction forces displayed like this (per loadcase)?0 - reaction forces in point with index 01 - reaction forces in point with index 112 - reaction forces in point with index 183 - reaction forces in point with index 17
Thanks!
BestLara…
into new tree, so that branch {0} has points from branch {0} {1} {2} combined, branch {1} has points from {2} {3} {4}... as it shows in the atached image.
The main problem is that points need to overlap in the new tree.
Any suggestions?…
the use of digital technologies as architectural design tools. The workshop " Computer Aided Design: parametric design and digital fabrication " aims to do some introductory teaching in the use of some of these tools.
The workshop will focus on the use of computational models of parametric behavior for generating architectural forms. The generative capacity of these models it will be tested in the development of designs defined by repetitive non-standard components, based on the parametric control of its variations and series differentiations. This process will be developed by the use of a three-dimensional modeling software - Rhinoceros, associated with an application for visual programming - Grasshopper.
The last day of the workshop is dedicated to the use of digital manufacturing tools in architecture. Part of the work will take place at the facilities of the Institute of Design of Guimarães (IDEGUI) providing for the use of their laboratories and manufacturing CNC machines (computer numerically controlled).
At the end of the workshop, it is intended the students to understand that the use of digital technologies in architecture can overcome representational functions, and their integration in the design conception, analysis and construction enriches the methodology of project development.
Terms & Participants
The workshop will take place at the School of Architecture of the University of Minho (Campus Azurém, Guimarães) and the Institute of Design of Guimarães (Couros, Guimarães).
The workshop is pointed at students who attend the 3rd year and 4th year from MiArq, EAUM.
The maximum acceptance is 20 students and a minimum of 10 students.
Deadline for entries is April 11 and must be performed by eaum.pac@gmail.com.
Program summary :
Day 23 April 14 -20h
Introduction to 3D modeling in Rhinoceros. Regular geometries, ruled surfaces and NURBS surfaces.
Day 30 April 14 -20h
Parametric design in architecture. Introduction to methods of visual programming.
May 1, 9 -13h 14 -18h
Development of a design idea by the use visual programming processes in Grasshopper.
May 2, 9 -13h 14 -18h
Introduction to methods of digital fabrication. Manufacture physical models of the proposals made.
It is expected that this meeting will take place in the IDEGUI labs.
team:
Bruno Figueiredo ( Lecturer, EAUM )
Paulo Sousa ( PhD candidate , EAUM )
Nuno Cruz ( Invited Lecturer , EAUM )
Cláudia Alvares ( 5th year MiArq student , EAUM )
Javier Bono ( 4th year MiArq student, EAUM )
João Amaro ( 5th year MiArq student, EAUM )…