hmm.... I thought you could lock any entity... but looking at the API - it'd appear only groups and instances can be locked...

Chris thanks for the feedback, and I have thought about doing the copy and duplication of the terrain manually. One more question, is there any way to perform the "Make Texture Unique" automatically. Once I get the duplicate terrain (on a seperatre layer), I want to dice up the terrain into smaller faces so I can add an opaque coloring to the individual faces. Basically, I need to make all faces in the terrain have their own materials/textures in order to paint or color them individually (while they still retain their own terrain image/graphic). Thanks a ton, Jim Higgins

@martinrinehart said: TIG, as always, was right. If you transform!() the translation is relative to the current location. I was right, too. If you move!() the translation is to the specified point (or to origin + vec, if you specify a vector, which comes out to the same thing). The doc, which says the two are the same, is dead wrong. (Or the doc is right and the code is wrong. We'll never know.) A relief to know that neither of us was going mad I'd never use move! anyway - unless in an animation...

thanks. I know that plugins. but I meant to include any plugins. even *. rbs only using the keyboard shortcuts to create the toolbar

hum, ok, thx. When i search on this API i don't find...-_-' you are my angel thx

Thanks, both -- They both look really interesting...will check them out.

Never mind. I figured out. I put the files in the wrong folder. lol thank you.

I believe crate.rb, at Ruby Library Depot can provide a way. But it does not work from single line mesh as you show. Lines2tubes will approach this with a 4 side specification, but the cross section may be rotated in the final result to resemble a "diamond".

http://forums.sketchucation.com/viewtopic.php?f=323&t=14975

Yea - I'm not dealing with points. As remus pointed out to me, it was four numbers. I just wanted a method that'd convert a plane defined as four numbers into [ point3d, vector3d ] - as the Geom module says planes can be in either format.

@chrisglasier said: Thanks TIG. That is a human type thing that I think I can control; I was wondering if there were any technical if and buts. You can always turn a group into a component and if you explode a component back into a group...

I fear not... Section Planes are very badly provided for in the API - it's a miracle my SectionCutFace tool works - you do have to have manually selected the cut-plane first in that ! I have tried before but there are no work arounds I can see...

I think animation in SU, however it is achieved, is susceptible to skipping if the model is large, or vast amounts of data are being animated. Try it in a DC. DC's animate objects and you can put them on a timer. The more complex the object being animated is, the bumpier the live animation is. But if it could be exported to a video, then it wouldn't matter so much.

@tig said: @thomthom said: TIG, I think it's a native SU warning, not a ruby script warning. So I'm not sure if that can be suppressed at all... Well, in that case it can't be suppressed... it's there for a reason If the warning is sent to the console via STDERR, you may be able to suppress it by changing the setting for $VERBOSE. See this post in the Optimization thread. http://forums.sketchucation.com/viewtopic.php?f=180&t=25305#p217508 If it's a viewtip or a messagbox in a .rbs, well ...

DoubleCut makes me huddle up in a corner and cry.... My wish for SU in the future is for it to be developed further as a platform. Sorting out the bugs in the existing API and filling in the gaps.

@adamb said: FWIW This is essentially how LightUp works under the hood. I've had for some time realtime painting tools working in LightUp but I've never had time to productize them. Adam Maybe a MakeUp plugin.

thanks Jim. just before your response I solved it in another way, using the axes of the target direction and creating a transformation array. wish I had asked this question 3 days ago

i must have missed this topic, sorry saiscience83 To hide objects in there pre-active stage, you just delete that material. Let's say for example you want buildings that are going to be constructed hidden before the construction starts. Then you just have to delete the material 'Construction_pre' from the materials library.

Components/groups end up skewed if you got them nested a couple of times inside non.uniformly scaled parents.