[x3d-public] Units for BVH vs HAnimMotion.values

[GPU Group]

I have the same question and posted it on h-anim. Might help to have some
options and analysis of the options.
1. Units statement
Analysis: that would apply to all rotations in the file, including other
scenery Transform rotations which is awkward for most workflows
2. Motion.values in radians by default
Analysis: will break some scene example data such as HAnim Annex D
Motion.values which is in degrees
- would need to update Annex D
3. Motion.values in radians by default, and browsers can support degrees
with a field
Motion {
SFString [] angleUnits 'RADIANS' ['RADIANS', 'DEGREES']
//or
SFBool [] angleUnitsDegrees FALSE
}
Analysis: would still break the Annex D example which doesn't show any
Motion field for angle units, and would need to update the specification
for Motion to include an additional field.
4. export in degrees, and put an export option on the export option panel
for Motion data in [degrees, radians] so browsers will still work either
way until a more permanent solution such as 2 or 3.
Q. how many web3d browsers have implemented HAnimMotion and angle units did
you use for Motion.values ?
-Doug

On Fri, Oct 13, 2023 at 12:44 PM John Carlson <yottzumm at gmail.com> wrote:

> Apparently BVH uses degrees for rotations.  Units for HAnimMotion should
> use radians unless otherwise specified in a UNIT statement, AFAIK.
>
> Comments?
>
> Thanks!
>
> John
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231013/723116a6/attachment.html>