-
Notifications
You must be signed in to change notification settings - Fork 53
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
Conversation
Made the functions only run once by putting them in the event listener
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
Completely ready for review |
There was a problem hiding this 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.
…gizmo' into dhruv/1733/mirabuf-gizmo
Added deattaching transform gizmos from mesh
enables physics for all nodes also removed redudant enabling physics for root node
There was a problem hiding this 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.
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 |
There was a problem hiding this 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.
@@ -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 |
There was a problem hiding this comment.
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
There was a problem hiding this 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!
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