Re: [openvrml-develop] Rotation values do not correspond to the actual values in the VRML file

[Braden M. <br...@en...>]

On Fri, 2006-11-10 at 10:52 +0000, blue rpk wrote:
> Thanks for your reply.
> 
> Some examples of the values that are read in and expected values are as
> follows.
> 
> In VRML file -  0.979336  Rotation field value  0.96029615
> In VRML file - -0.143005  Rotation field value -0.19626954
> In VRML file - -0.143005  Rotation field value -0.19826628
> 
>   As you can see, the same value is read in as a different value in
> openVRML. It is most probably something that I am doing or haven't
> understood properly. I am attaching the VRML file that I am reading.
>   Any help and comments appreciated.

If I add this Script node to the end of your file:

        Script {
          field SFNode t USE VCube01
          url [
            "javascript: function initialize() { print(t.rotation); }"
          ]
        }

I get this console output using 0.16.1:

        0.979336 -0.143005 -0.143005 -1.592

That tells me that the values have made it into the runtime okay. If you
see the same output with 0.15.10, I'd guess the problem is introduced by
however you're retrieving the values.

(Note that the rotation axis value for VCube02 is not normalized;
OpenVRML *will* change the axis values here because it will normalize
the vector. Note that rotation axis values that are not normalized are
technically nonconforming; that's why OpenVRML emits a warning about
them.)

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>