Where lies the bug?

thomthom

Tom,

Sorry to pop up in this. I may have missed something.
Do you wish to rotate and scale individual cubes (which is what I guess), or the whole selection?

Whole selection. In regards to the RotaScale plugin: http://forums.sketchucation.com/viewtopic.php?f=180&t=19199
The plugin works, in SU at least - but the problem is that VfSU doesn't read the transformation of the groups/components properly. So the transformation data needs to be converted into the same as it would if you'd use native SU tools.

scottlininger

Thom,

Can you filter the weirdness down to a few lines of Ruby and post? Sounds like SketchUp is using one unused cell of the transform matrix to store some scale information. I have no idea why, but there's probably a legacy reason for it.

Pout

we had a similar thingie with rotation an object in AutoCAD and then exporting it to VRML.
I see if i can get a descent answer from a developer

thomthom

In this screenshot the two cubes are of the same definition. The large one is roated 45 degrees and scaled x2.0 manually.
.transformation.to_a returns this for the manually rotated and scaled box:
[1.4142135623731, -1.4142135623731, 0.0, 0.0, 1.4142135623731, 1.4142135623731, 0.0, 0.0, 0.0, 0.0, 2, 0.0, -16.3076205658699, 55.6776993060274, 0.0, 1.0]

If I then RotaScale the small box to fit the large one .transformation returns this:
[0.707106781186548, -0.707106781186548, 0.0, 0.0, 0.707106781186548, 0.707106781186548, -0.0, 0.0, 0.0, 0.0, 1.0, 0.0, -8.15381028293495, 27.8388496530137, 0.0, 0.5]

Every value of the RotaScaled component is half of the manually scaled and rotated component.

In Sketchup everything looks fine. But when I render RotaScaled groups/component with V-Ray they don't match.

What it looks like is that the scaling transformation I make is stored scaled down in the matrix and that this is indicated in the last (15th) array value. I've reported this to ASGVis.

Question is, is this suppose to be like this?