I may be way off, but from what i gather from the screenshot, the v/50 expression is very relative to the size of the original surface. If you are creating a surfaces 1000 times bigger, or you are working in millimeters instead of meters, the volume number will be 1000^3 bigger and you'll have 1000000000 more subdivisions (i think). Try dividing the sub-surface bounding box volume to the complete surface's bounding box volume, so you've got something more relative to the surface you are working on.
On Nov 25, 11:47 am, David Rutten <[EMAIL PROTECTED]> wrote: > Hi Oompa, > > if you pick high subdivision values, your computer will get bogged > down trying to create (and mesh) thousands of surfaces. > Be sure that the expression doesn't generate big values. > > The "V" in the expression refers to a single variable; the name of the > parameter in this case. For this to work, you have to rename the > integer parameter from "Int" to "V". > > -- > David Rutten > Robert McNeel & Associates > > On Nov 25, 12:47 am, oompa_l <[EMAIL PROTECTED]> wrote: > > > David > > > I found this thread while searching for a way to learn about how to > > subdivide a surface adaptively - i think I have something in mind for > > which ppl dont typically use subdivision, or I just completely dont > > understand it - and on trying to recreate your file from the screen > > grab there are two problems. First, I'm not sure where the V/50 > > expression goes. Tried placing it in the int component but that made > > my computer pretty angry. Since then I've also tried it in the volume > > brep piece but also didnt work. I think I cleaned out the failed > > attempts. Now I keep getting an exception of type > > > 'System.OutofMemoryException' msg - what am i doing wrong? > > > thanks again > > g
