Unary AtPosition() strategy #358
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xyao-nv
approved these changes
Jan 27, 2026
alexmillane
approved these changes
Jan 28, 2026
Collaborator
alexmillane
left a comment
alexmillane
left a comment
There was a problem hiding this comment.
Looks great! Thanks for adding that!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Introduce the
AtPositionrelation, a unary constraint that pins objects to specific world coordinates. When composing object placement constraints, the existing On relation controls z-positioning (placing on a surface) and constrains x/y to stay within the parent's bounds. However, there was no way to specify an exact x/y position on that surface.AtPositioncan be used along arbitary axes. If not specified as z in the example above, its just omitted in the loss calculation.