Hi Quirin, 1. I don't understand it either. I need to examine this file in much greater detail, but I'm afraid my brain just died. I need a few hours of calmly sitting on a chair somewhere. I'll let you know when I find out the problem. I can tell you one big difference between 0.6 and <= 0.5; if you reference a Rhino object which no longer exists, then this blank reference was removed from the parameter. Now, there's a null in its place. It might go some way to explain why you have a set of propagating nulls. I don't think this is desired behaviour so I'll probably have to stop this from happening.
2. Which components are you using that cause you to use much more memory with non-flat data? In my experience so far non-flat data usually results in /fewer/ output values. -- David Rutten [email protected] Robert McNeel & Associates On Mar 20, 3:34 pm, quirin <[email protected]> wrote: > hi david > > maybe you could have a look at the attached files: > > http://grasshopper3d.googlegroups.com/web/grid_structure_0103.ghx?hl=... > > http://grasshopper3d.googlegroups.com/web/point%20grid%20projection.3... > > 1. > i don't really get why i produce these null objects and still have > the full path information after dispatching a list. > i would imagine by dispatching a list to dispatch the path information > as well. > i actually tried several ways to produce the same effect with > simpler setups but non of them returned null objects. > funny though cause it produces the desired result. > > 2. > while working with a higher amount of geometry and i don't remember to > flatten input values before attaching them to the input nodes, my > system runs out of memory. > probably for some nodes flattening should be set as default to avoid > memory overflow > for heavy calculations. not sure if this really makes sense, but it's > really > annoying to restart the computer all the time.
