TT to the rescue again. Many thanks. I tried it the first way as well but found the send_action call didn't work either. Your second method works like a champ. You're a star.

One additional problem with raytest: if you have a group/component open and you want to get a list of visible verties/3d points, then raytest won't be any good if there is geometry outside that scope between the camera and the vertices. Even if Hide Rest of Model is enabled. Alternative to that is to manually iterate all faces and intersect eye-point. Horrendously slow!

I don't care - I'm not supporting it. IE updates with the system unless they block it. If they do - then their loss. That pesky thing needs to die.

thank u，i have got it...

There is nothing built in that specifically tests this. But you could make it using ray_test. I'm not sure how fast it is especially over larger models. But if you had to, you could. Someone else might even have made something similar already, Chris

You could also look at model.raytest The point could be one that you used for your vertical edge and the vector is [0,0,-1] It will return any array raytest[0] is the intersection point and raytest[1][-1] is the face or edge it hits... http://code.google.com/apis/sketchup/docs/ourdoc/model.html#raytest

@thomthom said: what flags did you use when you obtained the PolygonMesh? Face.mesh http://code.google.com/intl/nb/apis/sketchup/docs/ourdoc/face.html#mesh @unknownuser said: Add these numbers together to combine flags. A value of 5 will include all flags, for example. This is wrong. 7 is the value if you want to include them all. It's a bitwise combination of the optional values. Thanks for that. Indeed, I was using 5 instread of 7 as the mesh flag. Thanks again

@chris fullmer said: because you are finding the bounding box for the first entitiy in the list of entities. What you want is to find the bounding box of the first entitiy in the selection set I would bet. model = Sketchup.active_model sel = model.selection first_entity = sel[0] try that i got it ，thank u ~

whaat you could make a component (dynamic if you light) call it camera_light and then use the align camera light ruby.

That 'that' is manually rotating about a point and then scaling in a certain axis often gives quite different results from scaling in a certain axis then rotating about the same point That is that !

facepalm! model.rendering_options.add_observer(self) - duh!

The syntax checking is a big plus. I've also just setup subversion control on it. Great to easily revert to previous version if I have messed up code. Commit once I know it is good. I also really like looking at differences between two versions. I can have both side by side, or on the active version, there is a notation of where I have made changes, and clicking the icon brings up a popup with the old code. I can then revert just that piece back vs. the entire file. The global searching is also nice. I'm working on someone else s code on a complex project, and it is great to quickly see where else specific code is being used.

Got one already: http://www.smustard.com/script/TextLabelOverride Todd

@chris fullmer said: AND 3rd aprty renderers do not appreciate the 16th element of the matrix being anything other than 1 also. So they often freak out when they come across these face-me's that have been incorrectly scaled. Previous version of VfSU didn't like that type of transformation. The new one seem to deal with it properly. @chris fullmer said: Yeah, this was a fun bug to track down Obcurity - thy name is SketchUp!

@wind-borne said: Initially, I will be looking at Lux for estimates of losses due to shading as program does face calculation if I understand the static reading. LightUp Insolation rendering gives 3 readings: A spot Kwh/m^2/day for the exact position from which you're taking the reading. (Static) A Face reading of Kwh/day (ie scaled by the area of the face). This is useful if you model panels with a single face. (Tracked) A Face reading of Kwh/day assuming the face tracks the sun (and is therefore more efficient). Adam

What I'm trying to say is this: If you add Q*(Face Normal) to each of your points you get a new face. If you align your texture to this new face but assign it to the old face it should be distorted. PS: sorry for my bad English... I'm not a native speaker.

@unknownuser said: I like the work put into the menu system Chris, I presume you're using that in a plugin you've created? (Or is SketchUp not capable of doing that?) Thanks. Both cgScenes and nsetSketchupAPI work as plugins and have been downloaded 130+ times. Here are copies of the download links. cgScenes R 1.051.zip nsetSketchupAPI 1.00 Nov15 1350.zip Here is how I introduced the API one: @chrisglasier said: I hope some people find the nset version of Alex's cheat sheet useful but really the main purpose was to demonstrate an alternative method of working that energerises names with computer code. Linked together in sets they provide machine-like support. Specific data is simply clicked into focus rather than the reader having to look through pages. . We thought that others might join in by adapting devices like Jim's web console [image: Rzjn_API012.png] and creating new ones using the same "name-based OS" that links everything together (the main menu is the model). But it seems web dialogs are not considered a serious solution, which is a great shame. I believe ignoring the real potential of the Net is very short-sighted. So I decided to concentrate on expanding cgScenes as I know there are SU people who would like to use hierarchies of scenes (views of their models) to facilitate design, present to clients/customers, submit to authorities, support purchasing, direct site work, explain timing and methods with diagrams and model animation, and handover useful and reusable automated information for ongoing activities.

"Adjust" is a Tool within the 2Dtools toolset - accessed from the Draw>2Dtools menu or the 2Dtools toolbar...

@jim said: Yeah, that's pretty much all there is to it. Make sure to read all the values; you can't skip them even if you don't use them. Because of variable chunk length? @jim said: I made a mistake when I said the values did not match - it works out no problem. You managed to recreate an SU camera? What's the lens value? AOV? FOV?

Use an inputpoint to get all the SketchUp inference points. This is a bare-bones code snippet that will make a tool, use an inputpoint and then draw that inputpoint to the screen. ` class SUC_IP_POINT def activate @ip1 = Sketchup::InputPoint.new end def onMouseMove(flags, x, y, view) @ip1 = view.inputpoint x,y view.invalidate end def draw(view) @ip1.draw view end end Sketchup.active_model.select_tool(SUC_IP_POINT.new)` So check that out, see if it helps. Chris