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

gizmo is not responding #41

Open
DigitalMonkeyPa1 opened this issue Jun 17, 2018 · 6 comments
Open

gizmo is not responding #41

DigitalMonkeyPa1 opened this issue Jun 17, 2018 · 6 comments
Labels
bug Something isn't working Waiting for Godot Godot has a bug and should be fixed first

Comments

@DigitalMonkeyPa1
Copy link

the gizmo for HTerrain node is not responding, has to be edited manually in inspector.

@Zylann
Copy link
Owner

Zylann commented Jun 17, 2018

I can't fix this yet, it's a problem with Godot godotengine/godot#17499
Maybe a fix exists, but I'm not aware of it so let me know if you have one.

@Zylann Zylann added bug Something isn't working Waiting for Godot Godot has a bug and should be fixed first labels Jun 17, 2018
@DigitalMonkeyPa1
Copy link
Author

Can we use an area node with three collision shapes( cylinder or capsule or even box) each for one axis to receive input events?
It might sound crazy, I even doubt that does the area node gets scaled up/down (ie: gizmos maintains their size irrespective of the camera), if it is a child of the Gizmo node, maybe it does, in that case, Box shape causes no problem with scaling.

@Zylann
Copy link
Owner

Zylann commented Jun 23, 2018

That would be crazy indeed... it should not be that complicated to fix this. What must happen is, when the base plugin (Spatial) receives Gizmo input, it should not forward input to the specialized part (HTerrain).
If input works backwards however, perhaps I would have to call the base input function and run my code if it returns false? I'm not sure if script plugins have access to this.

@DigitalMonkeyPa1
Copy link
Author

Just try it once, if it feels like an overkill, remove it.
I personally use the inspector to make the terrain go back & forth, but this workflow feels complicated.

@Zylann
Copy link
Owner

Zylann commented Jun 23, 2018

I won't do this because I know already it's overkill and overcomplicated...

@DigitalMonkeyPa1
Copy link
Author

That's OK, hope the engine fix is provided soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for Godot Godot has a bug and should be fixed first
Projects
None yet
Development

No branches or pull requests

2 participants