elpo, you may be able to use a boolean gate that stops the surfaces from folding if the test for intersection becomes positive. That may not explain it that well, but if you have a gate with the A output to allow for further 3D rotation (fold) and the B output to stop the folding of the plane at its max angle of rotation. Check this guys tutorial out its the first place I've seen these gates being used in a definition file that makes sense to me.
http://www.archinect.com/forum/threads.php?id=87371_0_42_0_C158 Good luck. perhaps post the file and some of us can take a look at it. - Case On Apr 2, 11:19 am, taz <[email protected]> wrote: > Elpo, > > If you have sliders controlling surface geometry and you wish to test > for a surface intersection event to cause the slider to be disabled > (thus removing the slider from its data stream) this would be a > recursive operation which can't be done with regular components. > > You may want to post your file and and get a second opinion, but a > custom scripted node may be your only option. > > -taz > > On Apr 1, 8:42 pm, elpo <[email protected]> wrote: > > > hi, > > I have made a definition based on folding surfaces. Each surface can > > operate individually with its own slider. But as certain surfaces fold > > into each other simulaniously they continue folding through each > > other. Not come to a stop at the intersection point where ever that > > may be. I have tried using a dispatch switch which was talked about in > > topic related to "on/off switch" but have had no suscess. I will try > > upload my definition for anyone to look at. On my definition Srf_A > > shouldn't be able to intersect with Srf_B and vice versa. this > > intersection point changes with diferent slider values for slider A > > and B. This value is also changed when surfaces 1 and 2 and folded > > together. > > Thanks
