<div dir="auto">What code is generating the BVH? Who is responsible for the numbers? Should they be included in the conversation? Doug knows more about BVH than I do. I have not ever tried to write BVH generating code.</div><div dir="auto"><br></div><div dir="auto">Re: Blender</div><div dir="auto"><br></div><div dir="auto">We can’t run around patching all the Blender (BVH) exporters to suit you, Joe, let’s focus on what we have done. I don’t want to burden Katy with changing all her numbers to meters, but that might be possible. Hopefully, some small tweaks to the model in Blender could do it, but Blender is tabled for now, and we’re working on animations out of other tools, I think. If there are issues with the X3DV exporter, Blender work can be reopened, but I’m targeting the beginning of the year for more work on Blender. I am satisfied we have the X3DV exporter working for our animation needs.</div><div dir="auto"><br></div><div dir="auto">I understand that we should not have Xposition, Yposition, Zposition in the HAnimMotion code, or have PositionInterpolators in Blender exports for HAnim. The question is, what if someone does specify translations during animation?</div><div dir="auto"><br></div><div dir="auto">There was some discussion of bringing HAnimMotion (with values) back, but I think Doug will want to focus more on his currently proprietary nodes.</div><div dir="auto"><br></div><div dir="auto">I realize that some people may want to specify segments instead of joints for bones, but they haven’t given me any data yet. It’s likely we’ll have a bones are segments vs bones are joints in the import/export GUI unless there’s update in recent Blender. Using segments requires “guessing” joints, perhaps, I am not sure about this. We might have to specify the LOA in Blender to get the right joint. I have not tried comparing joint/segment pairs between LOAs. Instead, I tried to compute the joint between two segments. Meanwhile, if segment names are used for bones, no segments or sites will appear, only joints in X3D, so it will be pretty obvious joint names should be used. Both Doug and Joe recommended going with joints for bones, so I backed down. I got joint names from Katy as well. Where is the segments as bones data? Find need and fill it.</div><div dir="auto"><br></div><div dir="auto">The orientation interpolator keys and keyValues are complete in the Blender X3DV exporter, the code is checked in. An addition might be to remove more key frames (neighbor duplicates are already removed), but that should be studied.</div><div dir="auto"><br></div><div dir="auto">Again, I am not doing any BVH exporter coding for Blender, I am exporting using off-the-shelf Blender with X3DV exporter, which doesn’t include BVH “encoding.” I am using the OTS BVH exporter.</div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 1, 2023 at 10:09 PM Joe D Williams <<a href="mailto:joedwil@earthlink.net">joedwil@earthlink.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div style="font-family:arial,sans-serif;font-size:12pt;color:rgb(0,0,0)"><p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">> JOINT sacroiliac<br> {<br> OFFSET 0.000000 97.241234 0.000000</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Yes, these numbers look silly </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Is the thing maybe 194 tall? </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Probly not. Maybe 1.94? </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">So guess that the units of this are in cm? and just move the . on x y z and see.</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">> JOINT vl5<br> {<br> OFFSET 0.133384 107.967499 -0.574449<br> CHANNELS 6 Xposition Yposition Zposition Xrotation Yrotation Zrotation<br> JOINT vl3<br> {</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">For this encoding, use the OFFSET for the before animation default pose joint center</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">then forget (don't bother trying to use) the </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Xposition Yposition Zposition data and</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">then use the </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Xrotation Yrotation Zrotation data list (euler angles) to develop orientation interpolator keyvalues. </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Also, you may encounter these files using name of a bone (HAnim Segment) instead. Just be sure the 'bone' data is applied the the parent Joint when you create the skeleton. </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Thanks,</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif">Joe</p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p>
<p style="margin:0.1rem 0px;line-height:1;font-family:arial,sans-serif"> </p></div></blockquote></div></div>