Flood of InvalidHandle errors for unbound optional actions in RC3
See original GitHub issueI’m using the 2.0 RC3 plugin to setup SteamVR Input actions in an overlay.
The console is flooded with GetDigitalActionData error ({fullPath}) InvalidHandle handle: {handle}
errors for every action that is not bound on the current controllers. Even when the action is marked as optional and not bound because there is no button that makes sense to bind it to.
I have verified that buttons I do have bindings for don’t show up in this error list, and that I can receive events from them.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8
Top Results From Across the Web
CS-GUIDE-smartBASICEXT-BL654 v29_3_3_0 .pdf
This user guide provides detailed information on BL654-specific smartBASIC extensions which provide a high-level managed.
Read more >Diff - 5b52c00^! - device/google/crosshatch-kernel
... fatal CORB/RIRB error more clearly 2690ec2a x86/apic: Soft disable APIC before ... but unbound socket 1f232107 nfc: fix potential illegal memory access ......
Read more >ChangeLog-6.4
Switch to propagating the error codes upstream. Fixes: ff65ffe46d28 ("mmc: Add Actions Semi Owl SoCs SD/MMC driver") Signed-off-by: Sergey Shtylyov ...
Read more >[PATCH 4.9 000/121] 4.9.238-rc1 review
Fixes: 6a21dfc0d0db ("RDMA/ucma: Limit possible option size") ... phy: Avoid NPD upon phy_detach() when driver is unbound Greg Kroah-Hartman ...
Read more >Change log : linux package : Debian
udp6: fix udp6_ehashfn() typo - ntb: idt: Fix error handling in ... interrupt on Intel hardware as well - USB: serial: option: add...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I believe this is fixed by a runtime update:
Thanks for the report and discussion everybody. This issue has been fixed in the recent SteamVR beta. We’re strongly encouraging developers to switch to the beta for development purposes.