So it seems like doing the new approach is best for Dropping Objects to other Geo, but using the Voxel method works alot faster when dropping verts to…
Well doing what you said local dir = [0,0,-1] –o.objectTransform.row3*-1 local thePos = [o.center.x, o.center.y, (nodeLocalBoundingBox o)[1].z]…
Yeah, that’s kinda what I thought Denis. But then the concern was if i pushed too far past the object, causing it to not detect the surface properly. …
Hmm… yeah I was just thinking that too. I guess I could try that. So that would be less memory intensive/faster than attaching geo? I would assume …
Yep, like lo said, if I convert the Terrain Geo to Editable_Mesh, it works just fine.
Here’s my sceneI’m testing with. Try using this code below, to Drop the Floating Rocks to the surface. Some will drop down, but others won’t. I know…
Ahh… hmm, damn. I might have to stick with my attach method then… :(. At least for the automated option. Basically, any object in the scene besides…
I don;t skin anything most of the time, but I think this script is still quite awesome. As for doing the offset, that seems like the fastest/easiest …
Nevermind…
Wow, that blew my mind
Nice. I just found another error, by trying to use it too fast I guess there isn’t error checking if the selected list count == 0? I tried placing…
Very interesting. I found a bug though right away … When I was placing an object, and I moved the mouse in/out of the surface I was placing on, the…
I didn’t try / look at the code, but may its because of System Units, and the object being a different size in different max instances?