i spoke about a case, when a face-origin pyramid is partially inside and partially outside of the calculated shape but maybe since complicated things tend to be trivial once you get the 'clue' after adding all the pyramids together you will get the correct result, forgive me for being sceptic... comparing your and the original 'slicing' method could prove your point

TBD thanks for your encouragement, will share for sure, it's fairly easy with the bounding box proposal from above - will get to it tomorrow, hope that method works stay tuned

TIG thanks, thought i'd try..

Here are my findings in relation to attributes assigned to the SKM file: SU will not save an attribute containing an array or hash SU will save multiple keys within single attribute dictionary .. but will load only first! In attached sample there are three keys saved: <n0:AttributeDictionary count="3" name="su2kt"> <n0:Attribute key="kt_lib_path" type="10">TEST1</n0:Attribute> <n0:Attribute key="kt_map" type="10">KT MAP</n0:Attribute> <n0:Attribute key="kt_mat" type="10">KT MAT</n0:Attribute> but only first kt_lib_path will be loaded I am afraid only a fix from Google would help. Tomasz http://www.sketchucation.com/forums/scf/sas/Ruby/Silver.zip

I usually have camera scenes, and then scenes that save something else, different section cuts for instance. Different phases on diff. layers, or whatever... so in one cam. I can show 3 diff. phases, 3 diff. section cuts, then move to the next view, and do it all again...very powerful w/ clients and bosses.

hank You, I'll give it a try

Also there's this http://www.smustard.com/script/ChamferAlongPath The old SU forum needed to move in order to gain access to the greater Google resources to better support the growing user community http://groups.google.com/group/sketchup-Pro-Groups.

You probably already know, but just in case: if you turn the opacity to 70 or higher, it will then receive shadows. Or at least that was the rule when they first introduced transparency in SketchUp. Haven't tried it since \ Juat checked. That measure has to do with casting shadows, not receiving them. sorry about that.

It's a bug. I reported it to Google for you. Todd

Yes, it's possible. It sounds like you may have opened the dialog as a modal dialog.

I actually found this implied in an example in the length class API. If you use a float, the math comes out like you would expect. The Length class is where this changes (as Al suspected). Notice that the 0.001" value that I got while testing is not mentioned as a limiting factor. @unknownuser said: < The < method is used to see if one length is less than another length. Syntax status = length1 < length2 Arguments length1 - a length value length2 - a length value Return Value status - true if length1 is < length2; false if length1 is not < length2 Comments For example, if l1 = 1.0.inch and l2 = 1.000001.inch then l1 == l2 so l1 < l2 should return false.

That's the best way to do it for now Chris. Todd

Ah yes, that also often happens.

Hey g2ktcf, we're looking into this problem on our side. Thanks for reporting it! Cheers, CraigD

Heck, I can NEVER pass up Lupe's! Next week is fine by me. Let me know when as my week is open (for now )

I would think this needs to be a material. I have actually done this the hard way in several different solid modeling programs. It works but it slows things WAY DOWN. The same goes for threads on screws... Chris

you need win32ole.so for that example. ... but you still need another file to access process identification (win32ole or win32api)

better than that, i will post the files. [image: http://www.sketchucation.com/forums/scf/sas/Ruby/BOARD01.JPG] [image: http://www.sketchucation.com/forums/scf/sas/Ruby/WOO003.JPG] [image: http://www.sketchucation.com/forums/scf/sas/Ruby/ratty_wood.jpg] [image: http://www.sketchucation.com/forums/scf/sas/Ruby/garden_wood_slats_color.jpeg]

Wouldn't that work only for realtime play? I'm looking for a way to step through an animation frame by frame. (not scenes/pages) I want to be able to access certain frames to fix possible errors.

SU gives you weird horizontal camera angles if you resize the SU window to an elongated horizontal rectangle. The SU camera angles are calculated vertically, so they are not directly equivalent to 35 mm cameras, where the angle is determined diagonally across the image. So on a normal screen, the horizontal camera angle is bigger than the value you type into the VCB box. Anssi