-
-
Notifications
You must be signed in to change notification settings - Fork 20k
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
input_event triggered only once in a subviewport setup for 3D #79271
Comments
You included all relevant info, so that will not be necessary. In your project, please change This change was a necessary bugfix and got introduced in #57894. #79235 is about key-events and not about mouse-events, so I wouldn't consider it related.
|
In that case if you want to propagate the mouse-event to both SubViewports, please have a look at #79128. (Use
No, because only a single |
Very interesting this is exactly it, thank you very much ! |
Thanks for the feedback. Closing this issue accordingly. I will create a separate bugreport for the single-event, since the main issue here is resolved. |
Godot version
4.1 stable
System information
Godot v4.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 31.0.15.3179) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)
Issue description
Hi, this is my first bug report, please feel free to inquire any missing information.
I observed a regression in my game when updating to Godot 4.1 from Godot 4.0.3 stable.
With this hierarchy, hovering the mouse on the Area3D Collision Shape will only trigger the input_event function once.
![image](https://private-user-images.githubusercontent.com/80595355/252271385-35b80c36-5c5a-44b8-b4c9-fcd1b0e6f88f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ4NzE4ODQsIm5iZiI6MTcyNDg3MTU4NCwicGF0aCI6Ii84MDU5NTM1NS8yNTIyNzEzODUtMzViODBjMzYtNWM1YS00NGI4LWI0YzktZmNkMWIwZTZmODhmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI4VDE4NTk0NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0MjVkZGU1MzY5YjA5YjJmYzk5MjkxOTU3MTE5MmQzZjA0ZWZhODUwM2NiMWMyZjE0OTYxZGJhYWIxZmQ2M2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.UGlmZstUYaPU-fA8YzXZ16uV8i42c3rSqgKLZK5Aaf8)
Details as follow :
Current behavior :
Running the project and hovering your mouse on the Area3D will print exactly once the following :
Expected behavior : (last stable version of Godot)
The print should be triggered at every input, motion or button from the mouse.
Now correct me if I'm wrong, but I suppose this is a bug.
Additionnal behavior tested :
When Area3D is moved from the Editor while the scene runs, it resets, and allows for exactly one new print.
I found another ticket having issues with Input event #79235, but I am unsure if this is related.
Steps to reproduce
Create a SubViewportContainer, extend the size to full. Toggle Stretch. Select mouse_filter to ignore.
Create a child SubViewport. Toggle Object Picking.
Create a small 3D setup :
print("event")
under the _on_input_event() function.Run the scene, and hover the mouse back and forth over the Area3D.
Minimal reproduction project
Godot InputKey Bug.zip
The text was updated successfully, but these errors were encountered: