Wow, those are some seriously long transition times. If you're working with a large site model, I'd suggest something along the lines of 10-20m/s for motion speed. Of course, it all depends on whether you want fly-by, drive-by, or walk-by speed, and the physical size of the site/campus. As it is, you can use the multiplier. Select all scenes, use 1/5 as your multiplier, then click the "Apply to Selected TT", then click "Save Changes". That will speed things up considerably. The Transition Time is a time in seconds that it takes to transition from one scene to the following scene. Your TT of 80 seconds for scene 1 is a LONG TIME. That's why I suggested using 1/5 for your multiplier - it will yield a 16 second TT (and other selected scenes will also be reduced by 80%). Hope that helps...

Hi, The simplest way: arc= model.entities.add_arc([x+@dist, y+@dist, z], vecx, vecz, @d/2, 0, pi/2, @s) line1 = model.entities.add_line([x+@dist, y+@dist, z],[x+@dist, y+@dist+@d/2, z]) line2 = =model.entities.add_line([x+@dist, y+@dist, z],[x+@dist+@d/2, y+@dist, z]) face = model.entities.add_face[arc,line1,line2] face.pushpull @thick Regards,

Got it working! Thanks for the help. Read more here: http://www.sketchucation.com/scf/viewtopic.php?f=9&t=1986

In my office I have Free SU 6. I can check - unless someone will be faster than me. At home I cannot install Free SU6 for I have Pro and they don't run parallel with each other.

Thanks.

thanks todd for taking a look on it.

Here's a 'universal solution'... Paste this into a file: (c) TIG 2007, ANY without warranty... BUT you can use it freely... however, it'd be nice NOT to claim it as your own OR at least just to mention me when you do reuse it... To use it: Put it in the Plugins folder... as 'GetShortcuts.txt', and the you can manually load it, when required [load"GetShortcuts.txt"] in the Ruby Console... require 'sketchup' Choose where you want the list to go PICK ONE # ... #filepath=ENV["TEMP"]+"/Shortcuts.txt" ### list's in, =YOUR Temp... #filepath=ENV["TMP"]+"/Shortcuts.txt" ### =YOUR Tmp... filepath="C:/Temp/Shortcuts.txt" ### =SystemTemp (PC) file=File.new(filepath,"w") Sketchup.get_shortcuts.sort!.each{|s|file.puts s} file.close

Oops. Command = 1048576 Alt = 524288 Control = 262144 The Command key, also known as the "apple" key, shown as a ⌘ in the Doc, is the Mac equivalent to the PC's CONTROL key. The control key on a Mac isn't used that often. The ALT key is also named the Option key. Todd

@cphillips said: @jim said: Is there a plugin to select only geometry that can be seen on the screen? Edit: Including the backfaces. Maybe select visible is a bad description. How about select all within the field of view? Cant you just use select and drag across the whole window? That does the same thing. Yes, but wanted to do it using Ruby.

Thanks! I'll try that.

yes i thought so - was thinking to organise my plugins menu but went up in a ballon... (and thanks for your great plugins)

An observer script could be written to "link" objects to accomplish this.

you're awesome... that trouble script is the foshizzle

I believe so. I believe it can be opened with a standard editor. If I can get a sample file of data points, I will post it here. I'll have to wait until person who creates specific KMLs returns from vacation in 2 weeks.

The problem is compounded by angles generally being measured counter-clockwise, while azimuth angles are measured clockwise. I think it would come down to determining the quadrant of the vector (by checking X and Y for +/- value), then adding the previous right-angle azimuth vector to the angle_between of it and the specified vector if vector.x>0 if vector.y>0 az = [0,1,0].angle_between(vector).radians else az = [1,0,0].angle_between(vector).radians+Math;;PI/2 end else if vector.y<0 az = [0,-1,0].angle_between(vector).radians+Math;;PI else az = [-1,0,0].angle_between(vector).radians+(3*Math;;PI/2) end The above example doesn't take into account cases where x or y equal zero, so you'll have to add that. It shouldn't be too difficult, though.

It's possible to use vectors to represent axes. The face.normal should be the Z axis, the X axis should be the intersection of a flat (XY) plane with the face plane, and the Y axis can be determined by the cross product of the X and Z axes. There's also a quicker way to do this after finding the Z axis (the face.normal): axes = face.normal.axes xAxis,yAxis,zAxis = axes However you do it, once you have the axis vectors, you can then either: test the X and Y axes against the points of the face to determine which are minimal and maximal, or use an axes transform to convert the vertex positions of the face to the world XYZ coordinates and then determine the minimal and maximal XY values.

Hi TIG Your extrude along a path is my bread and butter script for plan development. The core of a copy plan system and tut that I am in process on as we speak. An align_face script would be appreciated by all I am sure and thanks for the get-back. Dave

Thanks, Rick, but that's not really what I am looking for. I'm not trying to test whether the user is editing their photomatch (i.e. adjusting vanishing points, origin, etc.). I just want to know if the user has selected a photomatch scene tab and has not changed the camera view (photo background is still in view). The active tool could be anything (select, linetool, pushpull, etc, I don't care). In other words, I just want to test if the photomatch background is still in view. There doesn't seem to be anything in the RenderingOptions, Page, or Camera classes to help me here.

OK, here's the workflow to create unfolded sheetmetal parts - create first end of a transition create second end of transition use skin.rb to join the ends delete end faces and tweak surfaces as necessary use JF_unfold.rb to create a flat pattern align flat pattern to xy, xz or yz planes perspective off, select appropriate view, export DXF for profile cutting. Will play around with the Align feature later.

The thing with "between" definitively is an error from the filter_extension extension, it is located in the file filter/geom_selection.rb in line 4. Because the programmers used the evaluation technique, the error is hard to track. So I crawled all the "requires" and decoded them. From the filter_extension.rb you can see who has made the script - F. Rodriguez and Didier Bur. Also have a look on this old (cached) thread For the housebuilder thing look here. azuby