Hi ga, I'm flattening the living day-lights out of this now, but it's still not crashing...
------ The number of dimensions to a path hasn't got anything to do with 2D or 3D in the conventional sense. Essentially, you get an extra dimension whenever a component generates lists. This behaviour is likely to change soon as I'm working on better path-logic and more components to deal with paths. I don't see why it should be faster than custom lofting. It's VB.NET calling the same functions in both cases. -- David Rutten [email protected] Robert McNeel & Associates On Mar 23, 6:50 pm, ga <[email protected]> wrote: > David, > I've managed to replicate the error. And this is where my lack of > understanding about the specifics of paths comes in to play. I assume > that if I have one path of 200 base curves and one path of 200 offset > curves, that my objective for having them in paths is to have 200 2D > paths that each contain CurveBase(i), CurveOffset(i) so I used the > series components to try to get the path viewer component to say > something like : > > Structure (Paths = 200) > path {0;0} (N = 2)... > > But by default the definition created that with 3D paths, saying : > > Structure (Paths = 200) > path {0;0;0} (N = 2) > > Intuitively this seems like it has an extra dimension in the path, so > i began using the flatten toggle on the series component to get back > to 2D paths. This is where the error occurs. Is my intuition > incorrect? Can you explain how the paths work correctly as a 3D path? > Shouldn't this definition run much quicker than the same one that I > have done using VB.NET components to achieve local lofts? > > Thanks. > > Best, > ga > > On Mar 23, 11:19 am, David Rutten <[email protected]> wrote: > > > Hi ga, > > > thanks for posting. I haven't been able to get it to crash yet. I've > > been modifying values for about 10 minutes now, switching to different > > preview modes, changing graphs etc. etc. It's slow, but stable. > > I'll keep trying some more. > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates > > > On Mar 23, 3:57 pm, ga <[email protected]> wrote: > > > > David, > > > > Here is the link to the ghx file > > > :http://grasshopper3d.googlegroups.com/web/20090322_localLoft.ghx?hl=e... > > > It will work with any rhino file. > > > > Thanks! > > > > On Mar 23, 6:37 am, David Rutten <[email protected]> wrote: > > > > > Hi ga, > > > > > the error call stack is specially unhelpful (everything seem sot have > > > > happened in a remote file, which is clearly not the case since > > > > EH_Canvas.Regen() is a local function) in this case, I wonder if > > > > that's somehow a result of the error itself... One thing I do know is > > > > that "out of memory" errors only rarely mean you are truly out of > > > > memory. It seems to be a de facto error message when Microsoft doesn't > > > > know what went wrong exactly. > > > > > We used to get a steady stream of Display related crashes which were > > > > untraceable (most likely because they crashed a little while AFTER the > > > > problem occured), which is why I added this fail safe RSOD. Could you > > > > send me the ghx and the 3dm files? > > > > > -- > > > > David Rutten > > > > [email protected] > > > > Robert McNeel & Associates > > > > > On Mar 23, 5:26 am, ga <[email protected]> wrote: > > > > > > Hello All, > > > > > We've been trying to implement the new path and data handling > > > > > features of the most recent release and came across some interesting > > > > > errors. We managed to get a field of cells lofting locally but not too > > > > > soon after that we got the following errors and the GH RSOD > > > > > [Grasshopper Red Screen of Death]. The definition is built new with > > > > > 0.6.0006 components and the matrix of cells is only 20x10 so it seems > > > > > like it shouldn't run out of memory so easily. Has anyone else gotten > > > > > anything like this? > > > > > > Working Definition [For a minute] : > > > > > >http://grasshopper3d.googlegroups.com/web/20090323_LocalLoft01.jpg?hl... > > > > > > Error Screens : > > > > > >http://grasshopper3d.googlegroups.com/web/20090322_GHerror02.png?hl=e... > > > > > >http://grasshopper3d.googlegroups.com/web/20090322_GHerror01.png?hl=e...
