DeeJanuzandClaude Opus 5.5 c699e13104 Screens: find the controllers' laser tip during VR games too ...

GetComponentStateForDevicePath with no input source handle fails for
every render model component while a VR game runs (checked 2026-10-03
with a game up: all 21 components of frame_controller_right). TipOffset
then fell back to the controller's pose, which aims 40 degrees above the
Frame controller's laser. In games, pointing at a screen's middle missed
it and pointing below it hit, so the new aim-to-laser only worked from
the bottom; the controls' reveal and pin/roll aim were off the same way.
GetComponentState still answers then, with the same tip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-03 21:33:49 -06:00

..

controller-click-stability.md

Click stability: 32 logical pixels by default, not 8

2026-10-03 21:17:49 -06:00

design.md

Screens: find the controllers' laser tip during VR games too

2026-10-03 21:33:49 -06:00

floating-windows.md

Bring the docs up to date with the code

2026-10-01 14:47:53 -06:00

gaze-controllers.md

Bring the docs up to date with the code

2026-10-01 14:47:53 -06:00

hazards.md

Bring the docs up to date with the code

2026-10-01 14:47:53 -06:00

profiles.md

ft-floatd: profiles keep and relaunch Flatpak apps whose window names another app id

2026-10-02 19:40:45 -06:00

reference.md

Screens: in games, pointing a controller at a panel turns its laser on

2026-10-03 21:27:49 -06:00