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! π
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. π
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.
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.
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...
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.