-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Buttons D-PAd Down and Right Does Not Work well GODOT 3.5 #63972
Comments
@JesusRoberto64 Can you reproduce this in any of the 3.5 betas and RCs to determine when the regression started? |
I tested in Beta 1 and it does not have that button issue, I tried in Beta 2 and the problem appeared. I hope it helps. Thanks for the attention. |
I'm unable to reproduce either of the issues described. @JesusRoberto64 please provide an MRP that reproduces the issues. The attached MRP works fine with a PS3 controller's DPad. It tests both the For the record, the commits between beta1 and beta2 are:62fa80a Cleanup internal GUI state, if event is accepted in _input. As far as I can see the only change made to joypad input is: The only changes made to action input is: Neither of these are related to the issues described. |
Hi, Thanks for the response. https://www.ele-gate.com/producto/control-joystick-juegos-pc-laptop-gamepad-usb/ https://www.amazon.com/Controller-Gamepad-Joystick-Gamestick-Raspberry/dp/B09ZTSV7QK?th=1 Both are from different manufacturer and company, the only thing in common is that they are retro style 2.0 usb port. I tested in the project you provide and I have the same result. (Generic game pads don´t work). Again Thanks for the attention. |
@JesusRoberto64 Does this only happen with actions? Or, does it also happen when querying the button directly with Also, please provide the GUIDs for your joypads? The long number displayed at the top of the Joypads Demo. i.e. the output of |
@madmiraal Yes, the problem still happens in the Joypad Demo: Here are de GUIDS for my joypads: -Retro Controller -NEXT SNES Controller |
@JesusRoberto64 I think I've found the source of the bug. Please confirm whether or no #64211 fixes the issue. |
I compiled the #64211 , and the problem persists. Sorry if I take too much to answer. |
@JesusRoberto64 Thanks for the feedback. What is the output of
Also, with these controllers, is it only ever |
<style type="text/css"></style>
The values that returns are only 1 or 0. I hope this can help. |
Okay, I think I've now found the source of the bug. @JesusRoberto64 Please confirm that #64532 (the 3.x version of #64531) now fixes the issue. |
Yes, issue the was fixed. Now the joy-pads works normally :) |
Great! Thanks for testing. |
the button A on my nintendo switch pro controller simply don't work here. |
Godot version
3.5
System information
Windows 10 OpenGL ES 3.0 Renderer: GeForce GT 710/PCIe/SSE2
Issue description
When I press the D-Pad Button(down and Right) from some controllers, the Input.is_action_pressed keep calling the action, even when I release the button, thought. That make the UI navigating using focus buttons don't work properly. And also my game pad(generic game pad) its not longer usable on my game.
I tried with a PS3 controllers and it works fine when I press (down-Left pad). But I notice something strange, the action ui_focus_next and ui_focus_prev, does not work in Button-Control node, this happens in any game pad. If I put a print to see if there is a call for the Input.is_action_pressed, it its called but not detected by the Control-Button Node.
I haven't any issues of this kind in previous Godot versions 3.4.4 and below.
Steps to reproduce
1.-In Project Setting - Input map put any action using Device-0 Button 15(D-Pad-Right) and/or Device-0 Button 13(D-Pad-Down)
2.- Put a script to the detect Input event EXAMPLE :
func _process(delta):
if Input.is_action_pressed("ui_right"):
print("right UI ", randi()%100)
pass
3.- And then see that the action is keep calling till the end of time, with the buttons unpressed or released.
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: