Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transform Gizmos on Mirabuf Assemblies #1009

Merged
merged 34 commits into from
Jul 10, 2024
Merged

Conversation

Dhruv-0-Arora
Copy link
Collaborator

Description

This branch adds transform gizmos to the mirabuf assemblies as they spawn in. These transform gizmos currently are always on the Mirabuf assemblies as they spawn. The physics system is disabled when the user presses the transform gizmo (will implement so physics is disabled for only the one assembly and also it stays disable as long as the gizmo is attached).

JIRA Issue

@Dhruv-0-Arora Dhruv-0-Arora self-assigned this Jul 2, 2024
@Dhruv-0-Arora Dhruv-0-Arora requested a review from a team as a code owner July 2, 2024 00:57
@Dhruv-0-Arora Dhruv-0-Arora requested review from PepperLola and BrandonPacewic and removed request for a team July 2, 2024 00:57
@Dhruv-0-Arora Dhruv-0-Arora added physics Relating to either the underlying physics engine or the usage of it ui/ux Relating to user interface, or in general, user experience gameplay Relating to the playability of Synthesis labels Jul 2, 2024
@Dhruv-0-Arora
Copy link
Collaborator Author

Dhruv-0-Arora commented Jul 2, 2024

Right now it does not set Rotation or Scale. Only position

…same object and also implemented physics being disabled only for the one object

need to implement esc listener to escape the transform gizmo
…ng branch 'origin/dev' into dhruv/1733/mirabuf-gizmo

made a lot of changes with bugs and other issues
@Dhruv-0-Arora
Copy link
Collaborator Author

Completely ready for review

Copy link
Member

@HunterBarclay HunterBarclay left a comment

Choose a reason for hiding this comment

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

I added a quick change to your PR that also sets the bodies to be sensors when disabled, meaning they won't act on generated collision contacts.

When spawning in a field, we should restrict it to translation movement only. Not rotation. I also noticed that after finishing with the gizmo, if I try to move the camera by clicking near the center of the screen, it doesn't work, I have to click on the edge, and then it essentially snaps out of it and I can orbit the camera like normal.

@HunterBarclay HunterBarclay self-requested a review July 8, 2024 17:24
fission/src/mirabuf/MirabufSceneObject.ts Outdated Show resolved Hide resolved
fission/src/mirabuf/MirabufSceneObject.ts Outdated Show resolved Hide resolved
@HunterBarclay HunterBarclay self-requested a review July 8, 2024 23:02
Copy link
Member

@PepperLola PepperLola left a comment

Choose a reason for hiding this comment

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

Are the negative axis arrows supposed to be partially invisible? Also, I noticed the squares for moving along a plane disappear when the angle between them and the camera is too shallow. Not sure if there's much you can do about that though but I could be wrong.

@Dhruv-0-Arora Dhruv-0-Arora requested a review from a team as a code owner July 10, 2024 01:20
@Dhruv-0-Arora Dhruv-0-Arora requested review from a-crowell and LucaHaverty and removed request for a team July 10, 2024 01:20
@Dhruv-0-Arora
Copy link
Collaborator Author

Dhruv-0-Arora commented Jul 10, 2024

Are the negative axis arrows supposed to be partially invisible? Also, I noticed the squares for moving along a plane disappear when the angle between them and the camera is too shallow. Not sure if there's much you can do about that though but I could be wrong.

Well I can't really do much about either since it is the built in transform gizmo from three.js. The negative axis arrows being partially invisible is intentional on their end

Copy link
Member

@HunterBarclay HunterBarclay left a comment

Choose a reason for hiding this comment

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

I'm approving this for now because we want it in for the MVP and it's currently blocking two critical tasks. That being said I created a new Jira ticket for Sprint 4 to address a lot of the issues I have with Transform Gizmos.

fission/src/Window.d.ts Outdated Show resolved Hide resolved
@@ -27,6 +29,17 @@ class MirabufSceneObject extends SceneObject {
private _debugBodies: Map<string, RnDebugMeshes> | null
private _physicsLayerReserve: LayerReserve | undefined = undefined

private _transformGizmos: TransformGizmos | undefined = undefined
private _deleteGizmoOnEscape: boolean = true
Copy link
Member

Choose a reason for hiding this comment

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

I'll let this be for now, but the entirety of transform gizmos needs a major refactor to be more adaptable. It should honestly be worked into some kind of UI component. Jira ticket for refactoring

fission/src/ui/components/TransformGizmos.tsx Outdated Show resolved Hide resolved
@HunterBarclay HunterBarclay requested a review from PepperLola July 10, 2024 21:08
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.

Let's get this MVP done!

@HunterBarclay HunterBarclay merged commit 82338c7 into dev Jul 10, 2024
12 checks passed
@HunterBarclay HunterBarclay deleted the dhruv/1733/mirabuf-gizmo branch July 10, 2024 21:57
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 physics Relating to either the underlying physics engine or the usage of it ui/ux Relating to user interface, or in general, user experience
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants