- Queries to entity position, rotation, and joint poses all appear to be 1-frame late. Given the main use case for Molang for me is to drive procedural animation values, it's a shame I can't query the current entity location. When querying joints, it needs to form a dependency tree, as a joint may query another joint, and there can be cycles, however generally having responsive values and explicitly dealing with cyclical dependencies would be better than always getting 1-frame late data.
- Arrays might be a nice addition, that can be used by variables and store arbitrary data, floats or structures, not just resources. And to be able to read and write them. The main use case, I'd recommend is imagine wanting to capture a position as it moves through space in JS, pass that along to an entity via a property, and then be able to reconstruct it on the client-side and render animation with it every frame. For example imagine implementing a snake that slithers through the world, and not just whips it's entire body around when it turns, but the body has to follow wherever the head navigates.
- Adding functions to molang would help a LOT
- It would also be great if there were better native vector types and operators between native vector types. I'd like to be able to have quats, vectors, TRS transforms, and be able to inverse, and multiply them together, rotate vectors or transform positions, dot and cross product, etc.
0 Comments
Please sign in to leave a comment.
Post a new comment: