What happened when you tried it? There isn't a specific plugin to do this particular task.

@jim said: Could not this be done more directly using an actual PolygonMesh instead of using cpoints? I mean, you could generate a flat mesh of some density, then iterate the points and adjust each points's Z coordinate (using .set_point) to the "ground" using raycast? You certainly could - the drape_cpoints then triangulate method was written some while ago in response to a request [it does allow you to adjust some of the cpoints before making the mesh so in some respects it's perhaps easier that trying to move a mesh's vertices later on?]... BUT a method like you suggested that auto-drapes a flat [grouped] mesh over some 3d solid forms below using a raytest and a 'vertex-move' method would be quite doable [so over to you...]

You can't format how a dimension is displayed, other than by setting it in your Model Info > Units settings - so if your precision is 0 there is no decimal reporting but a ~ will be added to the front of the number if it's no a whole number of meters. The other way is to edit the dimension's text and type in what you want to see - but then it looses its ability to update whenever its connected geometry changes - because it will always show that edited text. Incidentally, you can change a dimension's text AND keep the standardly formated 'numerical' part which will update, by using this syntax <>xxx - where the '<>' represents the dimension's standard output and the 'xxx' represents some text, like ' Site Dimension'; this additional text can come before the '<>', or after it, or on both sides...

@bjornkn said: Assigning a shortcut to "Make unique" would take you 10 secs, and 0.1sec every time you use it after a Move/copy. yeah... thanks.

That's certainly the closest to what I'm looking for. What would improve it are 1) control over the amount of jitter (I was able to control it some by editing the .rb file but that's not the best option) and 2) each vertex should be aware of what it's neighbors are doing (so instead of each point having a totally random value it has a random value in relation to the vertices next to it so you can create waves at various frequencies - that would be better for bends in metal coping) -Brodie

OK i will git it a try.And thank's to you tig for all your amazing script.

I am almost regretting doing this... I wish the SU team would add way to load an "external" plugin library. I really want to have my plugins in my Dropbox so I have them all sync in all computers that I use for sketchuping. Most plugins seem to work, but I have noticed a few that don't. Every time I open Sketchup I get all these errors! PS: I still haven't replaced the "find_support_file". Error Loading File I:/_Library/SketchUp/_Plugins/Artisan/artisan_load.rb (eval):3641:in join': can't convert nil into StringError Loading File I:/_Library/SketchUp/_Plugins/artisan_loader.rb (eval):3641:in join': can't convert nil into StringError Loading File I:/_Library/SketchUp/_Plugins/c-midpoint.rb I:/_Library/SketchUp/_Plugins/c-midpoint.rb:196: syntax error, unexpected kEND, expecting $endError Loading File I:/_Library/SketchUp/_Plugins/camera-cameraslidecontrols.rb no such file to load -- smustard-app-observer.rbError Loading File I:/_Library/SketchUp/_Plugins/CameraKeyMaker/camera_key_maker.rb no such file to load -- bezier.rbError Loading File I:/_Library/SketchUp/_Plugins/cameraKeyMaker.rb no such file to load -- bezier.rbError Loading File I:/_Library/SketchUp/_Plugins/q-parking.rb I:/_Library/SketchUp/_Plugins/q-parking.rb:137: syntax error, unexpected tCONSTANT, expecting '{' BEGIN CHANGES BY organizerEdit.rb ^ I:/_Library/SketchUp/_Plugins/q-parking.rb:149: syntax error, unexpected tCONSTANT, expecting '{' END CHANGES BY organizerEdit.rb ^Error Loading File I:/_Library/SketchUp/_Plugins/zzz-SU_Podium_Browser_loader.rb (eval):361:in `small_icon=': can't convert nil into String

is it possible to hide the other layer excepte the one that hade the scene name? so you will have every layer in separate scene.

thanks for everythings. i'll try

I guess someone already has the solution: PageHide v.1.100 by Rick Wilson

@dave r said: With. Without: delete the geometry, materials, layers, etc., in the model whose scenes you want to use. Save as... with a new name so you don't loose the original model. Open the other model. Select all, Copy. go to the Scenes file. Edit>Paste in Place. hi dave, thanks for the tip.. never thought that trick before.. regards,

Thanks! fixed it...

that's cool. Thanks, Tig.

Here is a work around for this process that might work. create a scene tab for each composition layer and a corresponding style for each. once the styles are created this should be a pretty quick process for each view. go into model info and turn off scene transitions under animation export a animation but set it to export jpegs. you can set the jpegs to whatever size you need hit go. I have exported multiple scenes like this and its worked well. I think all you would have to do would be to incorporate the styles of the composite layers that you need and you should be away to the races

Thanks, guys, found em. Beats me why they don't show up in Spotlight, though. Jim

I believe the little one with the green dot is a SET Centerpoint tool. Don't quote me. . .but If you undock the tool bars, won't you see the name of the plugin?

@didier bur said: Hi, Ye,s I think this one could be of some help: http://rhin.crai.archi.fr/rld/plugin_details.php?id=219 yes! thank you Didier...

@unknownuser said: Hi guys, does anyone know of a plugin that would allow me to do this on a closed loop? (ie a circle?) For a repetition along a circle you have the regular tool Rotation + Copy (Key Shift)

I got an email today about an update, is there possibility to get a changelog? I'm still interested in the instances/components in FBX and the ability to not triangulate the mesh. Thanks.

The 'midpoint' script code is easily recast so that the new guide-point is not placed half way. What proportion would you want it to be for a 'golden-section' - probably gs=point1.distance(point2)/1.6180339887 will be more than accurate enough for the offset of the picked point1 towards point2... thus pointc=point1.offset(point1.vector_to(point2), gs); then use entities.add_cpoint(pointc)