Skip to content

Conversation

itspvty
Copy link
Contributor

@itspvty itspvty commented Jun 18, 2025

When an object is created, it is now focused to the middle of the robot assembly as opposed to just its base. In other words, the automatic centering that occurs on focus now takes into account the Y axis.

Old:
image

New:
image

@itspvty itspvty requested review from a team as code owners June 18, 2025 21:54
@Dhruv-0-Arora Dhruv-0-Arora added ui/ux Relating to user interface, or in general, user experience gameplay Relating to the playability of Synthesis and removed ui/ux Relating to user interface, or in general, user experience labels Jun 18, 2025
Copy link
Collaborator

@Dhruv-0-Arora Dhruv-0-Arora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you merge dev?

@Dhruv-0-Arora Dhruv-0-Arora self-requested a review June 18, 2025 23:45
Copy link
Collaborator

@Dhruv-0-Arora Dhruv-0-Arora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The only potential problem with this implementation is that since you are pivoting from a physics based approach, which is more precise, to a mesh based approach. With a weirdly exported robot it might cause some issues but I can't seem to find any with our current implementation.

Another note is that when you start trying to topple the robot, the camera will start shaking due to the bounding box implementation rather than the jolt physics based implementation. It doesn't seem to be too big of a problem though. Additionally, the camera moves if you begin to move the mechanisms/arms which could be unwanted yet again doesn't seem to be too big of an issue.

@BrandonPacewic @PepperLola thoughts?

@Dhruv-0-Arora Dhruv-0-Arora self-requested a review June 18, 2025 23:54
Copy link
Collaborator

@Dhruv-0-Arora Dhruv-0-Arora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed; alternatively we could calculate the bounding box when the assembly is spawned and keep it constant but I personally think this looks better.

Copy link
Member

@BrandonPacewic BrandonPacewic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The only potential problem with this implementation is that since you are pivoting from a physics based approach, which is more precise, to a mesh based approach. With a weirdly exported robot it might cause some issues but I can't seem to find any with our current implementation.

Another note is that when you start trying to topple the robot, the camera will start shaking due to the bounding box implementation rather than the jolt physics based implementation. It doesn't seem to be too big of a problem though. Additionally, the camera moves if you begin to move the mechanisms/arms which could be unwanted yet again doesn't seem to be too big of an issue.

@BrandonPacewic @PepperLola thoughts?

Maybe, but this is such a small change (with such an obvious benefit) that we should just make it and revisit later if we really feel like it could be significantly better than this.

Good work, nice easy change 🛰️

@BrandonPacewic BrandonPacewic merged commit 1737745 into Autodesk:dev Jun 19, 2025
14 of 15 checks passed
@BrandonPacewic BrandonPacewic mentioned this pull request Jun 19, 2025
@itspvty itspvty deleted the aries/1897/camera-center branch June 24, 2025 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gameplay Relating to the playability of Synthesis
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants