-
Bug
-
Resolution: Unresolved
-
None
-
1.21.60.21 Preview, 1.21.44 Hotfix
-
None
-
Confirmed
-
Multiple
-
1338819
Using the bone_orientation_trs molang query always fails to find the specified bone in the initial frames after entering a world, leading to an unavoidable content log error. The query works correctly and finds the bone as desired, but it produces a warning nonetheless.
How to reproduce
1. Download and open the attached world
2. Observe the content log error:
[Molang][error]-test:test1 | entity/test1.entity.json | t.trs = q.bone_orientation_trs('body'); return t.trs.t.y/50; | query.bone_orientation_trs couldn't find the specified bone in the current entity's queryable geometry.
Expected results
No error, since the entity does indeed have a body bone, and the query is working correctly.
Observed results
Despite the scale being set correctly, an error is produced.