feat(host): the Steam Deck's gyro reaches Motion controls when Steam starts the game #1181
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!1181
Loading…
Reference in a new issue
No description provided.
Delete branch "zeldaootr/Longshot:deck-gyro"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
On a Steam Deck started from Steam, Motion controls finds no gyro: Steam hides the Deck's built-in controls from the game and gives it a stand-in pad with no sensors, so players fake gyro aiming with a Steam Input "Gyro to Mouse" layout. This PR lets the game read the Deck's own gyro beside Steam Input's pad, and turns the Deck's motion sensors on when Steam left them off. In Game Mode on a Steam Deck OLED, started from the Steam shortcut with no gyro binding in the game's Steam Input layout, the Motion controls row reads "On (gyro found)" and aiming follows the Deck, before, during and after opening Steam's overlay (zeldaootr: "everything worked great"; Testing). That run was this PR's Deck code built on an earlier
main(Measurements' Baseline says what differs), not this head's own build.What it changes, in three parts:
SDL_GAMECONTROLLER_IGNORE_DEVICESlists Valve's pads; main already takes Valve's out (for the Steam Controller's gyro, MagicBeanDev/Hookshot#2495) but kept the Deck's (0x28de/0x1205) in. This PR takes the Deck's out too (HOS_DECK_GYRO=0keeps it in), sizes the new list from Steam's instead of a fixed buffer, and logs a warning, with the reason, whenever Valve's pads have to stay in the list. Beside Steam Input's pad the Deck's controls give their motion only: buttons and sticks keep coming through Steam Input as the player's layout maps them.HOS_DECK_IMU=0writes nothing. In Game Mode it turned the sensors on at the start and again each time Steam turned them off (Testing).What went wrong on the way, and the fix it led to. Headless stands on the Deck, with a one-entry list (
0x28de/0x1205) set by hand as Steam's, passed. Then the first real start from the Steam shortcut in Game Mode did nothing: one controller, Steam's stand-in pad, and no line about Valve's controllers. The cause:pads_startcopied Steam's list into a fixed 4096-byte buffer, and Steam's real list on the Deck is 11,102 characters, 793 entries;steam_pads_without_valverefused it (-1) andpads_starttreated that as nothing to do, without a word. The same buffer is on main (char kept[4096]inpads_start,host/pad_sdl.cline 118): main's own Steam Controller path. Fed that list, main'ssteam_pads_without_valvereturns -1 into 4096 bytes (42 Valve entries and 10,513 characters into a buffer that fits), so on main, under a list this long, a Steam Controller stays ignored too and Motion controls finds no gyro on it, with nothing in the log. This PR fixes that path as well; it is not run with a Steam Controller here (Still to test), and the list was read on a Deck, not on a PC's Steam. The second Game Mode start then showed the sensors left off without a gyro binding (50 re-arm lines, no aiming), which part 3 answers.Read first:
pads_startinhost/pad_sdl.c(the list sized from Steam's, the warning, the before/after line);steam_pads_without_valve,steam_pads_countandsteam_pads_is_deckinhost/steam_pads.h.deck_imu_pollinhost/pad_sdl.c, called frommotion_poll: only for the Deck's built-in controls (vendor 0x28de, product 0x1205) while they are motion only beside Steam Input's pad and the pad Motion controls reads; it opens the pad's own HID device by the path SDL opened it by, sends the 65-byte feature report00 87 03 30 18 00(SET_SETTINGS, IMU_MODE = 0x0018), and closes it.motion_poll's frozen-gyroscope rule leaves that pad alone (!deck_imu).host/hos_sdl.c: the pad's product id,SDL_GetHint,SDL_hid_send_feature_report.killrows forHOS_DECK_GYROandHOS_DECK_IMUingpu/vk/switches.def; docs:docs/dev/reference/input.md,docs/user/graphics-and-controls.md(Motion).tests/test_steam_pads.py(runspads_startcut from the source with a list shaped like Steam's: 11,102 characters, 793 entries, the Deck's twice, a trailing comma),tests/test_deck_imu.py, andtests/test_gyro_rearm.py's fixture.Related: #1796 stops the frozen-gyro rule firing on a gyroscope that is merely at rest, which this PR exposes on a Deck (Risks). The two are independent: this PR's Deck path keeps its own two-sensor test and only tells main's rule to skip the Deck's pad, and either merges without the other. Whichever merges second has a one-line textual conflict on the rule's test line in
motion_poll; the resolution is both conditions,if (read && !deck_imu && !memcmp(g, last_g, sizeof g) && !memcmp(a, last_a, sizeof a)), withtests/test_gyro_rearm.py's fixture keeping both itsaanddeck_imu = 0(the Game Mode builds carry exactly that resolution). #699 (a "Custom" gyro aim style) also editshost/pad_sdl.c; #1171 is another topic.Thanks to omgitsgela, whose report of the frozen-gyro rule firing on a Steam Deck LCD, 102 times in ten minutes (#1477, their comment of 2026-11-19 06:34), showed that a Deck's gyroscope reads exactly the same at rest: the IMU step's "both sensors frozen" test comes from it. First asked for in the team's Discord thread "STEAM DECK GYRO SUPPORT".
See #1477
Testing
Tested: by zeldaootr on a Steam Deck OLED (SteamOS 3.9.5, Linux 7.2.7-valve2, RADV VANGOGH Mesa 26.2.0-devel (git-5c65d4fc31), SteamOS's SDL 3,
libSDL3.so.0.4.12), Motion controls On. Every Deck build below is this PR's code at the time on main9ea65c7bf, not this head's own build; the Game Mode builds also carry #1796's two commits. The last one, v3.0.0-54-gcf94a4fec, has this head's Deck code:pads_start,deck_imu_polland both new tests are byte for byte this head's (Measurements, Baseline).with a gyroscopebeside Steam Input's pad,motion only,motion controls from "Steam Deck Controller"; then once each, at the start,the Steam Deck's motion sensors read nothing ...: turning them onand... were off ...: turned on; 0stopped changingre-arm lines (the build without the IMU step: 50), 0 warnings. Later, Steam turned the sensors off again and the game turned them back on: 4[debug] ... turned on again (N times now)lines in the 31-minute session (about 12, 12, 18 and 27 minutes in, each right after athe game read no controller for 2.2 s(or 3.3 s) line, as when the game loses its input to Steam's overlay) and 1 in the short start; never a steady stream. The log does not record the overlay itself, so which recovery followed which overlay close is not known: that aiming came back after the overlay rests on zeldaootr's play. Thehid:lines are in Measurements.SDL_*andSteam*variable Steam set for the shortcut, v3.0.0-54-gcf94a4fec and the build before it): the controller's hidraw device (28de:1205) opens read-write as the game's user. Four arms (the build without the IMU step; this build; this build with Steam's overlay library preloaded as Steam does; this build withHOS_DECK_IMU=0) all logged the two ignore-list lines, both controllers,motion only, its buttons come through Steam Input's padandmotion controls from "Steam Deck Controller", 0 re-arm lines and no write (started over ssh the IMU is already on). A forced arm, where a script first wrote IMU mode 0 to the controller: the game loggedthe Steam Deck's motion sensors read nothing ...: turning them on, once a second until they move, then... were off ...: turned on, and the next motion sample was already moving; the script set the mode back afterwards.taken out of Steam's ignore list (44 of its entries),now 10485 characters, 749 entries (the Steam Deck's 0)); "Steam Deck Controller" openedwith a gyroscopebeside Steam Input's pad,motion only,motion controls from "Steam Deck Controller",hid: 1 controller through SDL; the Motion controls row read "On (gyro found)". In the game the sticks, buttons, trackpads and the Steam and Quick Access buttons worked as usual; the back grips are unbound in that layout and were not judged. With no gyro binding, tilting did nothing: 50its gyroscope and accelerometer stopped changing: motion sensors turned off and on againlines (both sensors identical: no IMU data at all), until zeldaootr bound the gyro "As Mouse" in Steam Input; after that there were none, aiming followed the Deck, and a mouse cursor appeared (that binding's own effect). That start is why part 3 exists.connected (SDL), Steam Input's). Cause: the 4096-byte buffer against Steam's real list (Summary). Reproduced without the Deck:pads_startcut from that commit's source and fed Steam's list gave SDL nothing and logged nothing; the fixed one gave SDL 10,485 characters with no0x28deentry left.0x28de/0x1205, 600 s standing in Kokiri Forest, the Deck at rest): with this PR's first two commits (5306ca05d) SDL opened "Steam Deck Controller" with a gyroscope beside "Steam Virtual Gamepad" and Motion controls read it throughout (1346 motion lines); withHOS_DECK_GYRO=0only the virtual gamepad opened and nothing was read, as on main. Measurements.tests/test_deck_imu.pyfails at its test commit698f9b885(FAIL:126 writes >= 8 && writes <= 10and 7 more) and passes at the head. v3.0.0-54-gcf94a4fec started on this PC (Linux, llvmpipe) with every one of Steam's variables from the Deck, to the intro and out with exit 0, logging the same two list lines.Game-free, on Linux x86-64, in the PC's job queue:
3131b399don main08994a9ee),run_all.py --changed forge/main(55 checks that read the 10 changed files): 47 passed, 8 failed (test_crash_dialog,test_dev_ab,test_frame_overlap,test_hud_layout_row,test_linux_pressure,test_present_queue_default,test_vk_occlusion_queries,test_walk_key), all 8 also failing on main068fb8ebebelow.test_steam_pads,test_deck_imu,test_gyro_rearm,test_switch_tableandtest_settings_tablepass.python3 -I -B tests/run_all.py(not--strict) at 6ed99ae48 (these eight commits on main068fb8ebe; the rebase onto08994a9eechanged none of them,git range-diff=) and on main068fb8ebe, back to back on this PC: here 782 passed, 72 failed, 17 skipped; main 780 passed, 73 failed, 17 skipped. Every check that fails here fails on main too; main's failures are this PC's environment (tools, modules, timing).tests/test_steam_pads.pyfails atb98aec7ff(6 failures, among thempads_start: Steam's real-sized list (11102 characters) reaches SDL without Valve's entriesandHOS_DECK_GYRO=0: the Deck's entries stay, Valve's others come out, which is main's own behaviour), fails at651759394(steam_pads_countnot there yet), passes at the head. On main08994a9eewith this head's tests:test_steam_padsandtest_deck_imufail.host/pad_sdl.candhost/hos_sdl.ccompiled (-c, the build's host flags,-Wall) with gcc and clang for Linux and llvm-mingw 20261104 for Windows, at this head and on main08994a9ee: the same warnings on both (one from a generated header; one more inhos_sdl.cfromhost/fullscreen_monitor.h), none from this change.a104182b4(head8704dbc1a; the lines above name the head before it,3131b399don08994a9ee). Onlyhost/hos_sdl.candhost/hos_sdl.hconflicted: main now hashos_sdl_pad_productitself (for the Steam Controller), so this PR no longer adds it and uses main's.git range-diff:pads_start,deck_imu_poll,host/steam_pads.hand both new tests are unchanged, the rest differs inhos_sdland in docs context. The Deck's motion-only pad still stops before main's new vibration and haptics code:pads_pollreachescontinuefor it before the pad is counted and beforevib_choose. At8704dbc1aand on maina104182b4, the 49 checks that read the changed host files and the switch table: 42 passed and 7 failed here, 41 and 7 on main, the same 7 on both (test_crash_dialog,test_dev_ab,test_frame_overlap,test_linux_pressure,test_present_queue_default,test_renhdrum,test_vk_occlusion_queries), the one more here beingtest_deck_imu. Both files compile for Linux (gcc, clang) and Windows (llvm-mingw) with the same warnings as main. Not run in the game again after the rebase.The 72 checks that fail both here (6ed99ae48) and on main
068fb8ebetest_appimage_player_build,test_bug_report_defaults,test_capture_readback_visibility,test_capture_read_once,test_crash_dialog,test_crt_options,test_damage_debug_menu,test_dav1d_av1,test_dev_ab,test_dev_packs,test_discover,test_display_startup_failure,test_dlss_feature_size,test_draw_stream_visibility,test_failed_compile_keeps_objects,test_frame_overlap,test_fsr3fi_hud_layer,test_fsr_image_retirement,test_fsr_uniform_ownership,test_guest_imported,test_high_fps_fixes,test_host_guest_writes,test_hud_layout_row,test_insn_fixed_convert,test_libc_hooks,test_lift_cache,test_lift_lookups,test_linux_preflight,test_linux_pressure,test_linux_tools,test_linux_update,test_log_open_failure,test_make_game_cache,test_make_game_ngx,test_mise_build,test_missing_nup,test_mods_list,test_mods_size_table,test_native_zstd,test_ngx_sdk,test_nonuniform_image_arrays,test_nup_codec,test_nup_read_name,test_nup_stand_in,test_nup_verify,test_parallel_init_order,test_pending_guest_import,test_pipeline_play_cache,test_prepare_cache_save,test_prepare_stall,test_present_queue_default,test_present_source_crop,test_present_thread,test_profiling_mode,test_prompt_guide_lines,test_prompt_hand_guides,test_prompt_picture_tint,test_prompt_speed,test_psychov35_fsr3_fg,test_readback_timeout_source,test_replay_write_order,test_slow_frames,test_song_note_cue,test_staging_burst,test_texel_buffer_ownership,test_thinlto_tls,test_upscaler_rows,test_vbytes(times out at 600 s),test_vcore_escape,test_vk_occlusion_queries,test_walk,test_walk_key. Main also failstest_pipeline_cache_save.Still to test:
main, no gyro binding: one start, load a save and aim, open and close the Steam overlay once, expecting the samehid:lines as the v3.0.0-54-gcf94a4fec start in Measurements (turning them on,turned on, 0stopped changinglines, no[warn] hid:line) and aiming as there (by hand: zeldaootr)hid:lines (by hand: someone with a Deck LCD)hid: Valve's controllers (the Steam Deck's too) taken out of Steam's ignore list (N of its entries)and theSDL's controller ignore listline in the log, and the gyro aiming (by hand: someone with a Steam Controller)Measurements
Verdict: it works on a Steam Deck OLED in Game Mode: with no gyro binding in Steam Input, the game turned the Deck's motion sensors on at the start (one
turned online) and after each of the 4 times Steam turned them off in a 31-minute session, 0 re-arm lines against 50 in the build without the IMU step, and aiming followed the Deck by zeldaootr's play. The list fix before it opened the Deck's controls with a gyroscope where the earlier build opened only Steam's stand-in pad. No frame time measured: an input change, which reads two sensors per poll and, only while they are frozen, writes 65 bytes at most once a second (it turned the sensors on 5 times in the 31-minute session).Baseline: not main, and not this head's own build. Every column is a build on main
9ea65c7bfwith #1796's two commits: 7e1a68a43 is this PR's earlier head 5306ca05d, whose list code is main's 4096-byte buffer with the Deck's entry also taken out, so under Steam's real list it left the list as main does; bb0242662 adds the list fix (this branch's commits 3 to 6); cf94a4fec adds the IMU step (this branch's commits 7 and 8,698f9b885and3131b399d, cherry-picked). Why cf94a4fec's results hold for this head:git range-diff 9ea65c7bf..cf94a4fec 08994a9ee..3131b399dand a diff of the files showpads_start,deck_imu_poll,tests/test_deck_imu.pyandtests/test_steam_pads.pyidentical, andhost/steam_pads.hdiffering in one comment only. What differs: (1)host/hos_sdl.c:9ea65c7bfpredates main's HID calls (added for the DualSense's haptics, #405), so the build carries its own copy ofhos_sdl_pad_path,hos_sdl_hid_openandhos_sdl_hid_closewhere this head uses main's, which are the same but forhos_sdl_hid_openalso asking forSDL_hid_write(every SDL3 has it); (2) the frozen-gyro rule's line inmotion_pollhas #1796's accelerometer condition in the build and main's gyro-only one here, and the Deck's motion-only pad skips that rule either way (!deck_imu); (3) the rest ofmainsince9ea65c7bf, among it the new vibration code, which a motion-only pad never reaches (pads_pollmoves on before it); (4)docs/dev/reference/input.mdis not in the build. Main itself was not started from the shortcut;HOS_DECK_GYRO=0gives main's list (the stands below).Setup: Steam Deck OLED, SteamOS 3.9.5 (Linux 7.2.7-valve2), RADV VANGOGH Mesa 26.2.0-devel (git-5c65d4fc31), SDL 3 (
libSDL3.so.0.4.12), 16 GB; Game Mode, started from zeldaootr's Steam shortcut, Steam Input on, Steam's overlay preloaded; Motion controls On. What each start's log says was opened and read, its IMU andstopped changinglines and warnings, its length from the log's 5-secondvi:lines (andvk: status:lines, one per 600 frames); Motion controls' row and the aiming by hand. One start or session each: counts, not timings.SDL_GAMECONTROLLER_IGNORE_DEVICES)taken out ... (44 of its entries);now 10485 characters, 749 entries (the Steam Deck's 0)with a gyroscope,motion onlymotion controls fromread nothing ...: turning them on/were off ...: turned on[debug] ... turned on againstopped changingre-arm lines[warn]linesvi:lines × 5 s; frames)(Two more starts of cf94a4fec on the Deck that day were headless, without Steam's variables: no stand-in pad, so the Deck's controls play directly, the IMU step does not apply, 0 IMU lines and 0 re-arm lines.)
Headless stands, 2026-11-19 (Steam Deck OLED as above, Game Mode running, the game started over ssh,
HOS_HEADLESS=1, the list set by hand; Kokiri Forest, Link standing, 600 s each after the save loaded, the Deck at rest on AC, back to back). Reproduce:SDL_GAMECONTROLLER_IGNORE_DEVICES=0x28de/0x1205 SDL_GAMECONTROLLER_ALLOW_STEAM_VIRTUAL_GAMEPAD=1 HOS_MOTION_DEBUG=1 HOS_HEADLESS=1 RX_VK_PRECOMPILE=0(plusHOS_DECK_GYRO=0), load a save, leave the Deck still, readlongshot_log.txt. Main itself ran this way on 2026-11-16 (a main9c9d69edruntime): the virtual gamepad only, no motion, as theHOS_DECK_GYRO=0column.motion controls fromThe switches:
HOS_DECK_GYRO=0is main's behaviour. After quitting is not yet checked (Still to test)HOS_DECK_IMU=0does) 50 re-arm lines and no aiming. Measured on a Steam Deck OLED only: a Deck LCD is Still to testRisks
tests/test_deck_imu.py. On the Deck OLED those bytes turned the IMU on, and Steam turning it off again (4 times in 31 minutes) was answered each time, never a steady back and forth. A Deck LCD's controller is not yet run. Nothing is put back at exit; Steam sets it again when its overlay closes or its layout changes. While it is on, the IMU draws power as it does with a gyro binding.HOS_DECK_IMU=0turns this part off.HOS_DECK_GYRO=0keeps the Deck's controls in Steam's list, as on main.HOS_DECK_IMU=0it has main's rule again. Started outside Steam (no stand-in pad, omgitsgela's case) the Deck's pad keeps main's rule: that is #1796's to fix.longshot_options.ini, the caches and the renderer's interface are untouched. Two new log lines under Steam, two more on a Deck whose sensors Steam left off, and a warning when Valve's pads stay in the list. A revert is enough to undo it.Checklist
Ready for review
main; the title is a Conventional Commit. [head8704dbc1aon maina104182b4]9ea65c7bfwith PR 1796, not this head's own build; what differs is in Measurements' Baseline. The head's own build on currentmainis Still to test]mise run testpasses (any failure that also fails onmainis named). [the wholerun_all.pyat 6ed99ae48 on main068fb8ebe, the same commits, against main068fb8ebe; the changed-file checks at this head]main, or Measurements says why there is nothing to measure. [what the log shows per build and start in Game Mode, against the earlier builds that the Baseline line names (main's list code in 7e1a68a43, no IMU step in bb0242662); no frame time, and Measurements says why]third_party/untouched; nothing GPL-incompatible.When it applies
mainand passes here. [the 4096-byte buffer, on main too:tests/test_steam_pads.pyfails atb98aec7fffor it and on main, passes here;tests/test_deck_imu.pyfails on main and passes here]gpu/vk/switches.def. [HOS_DECK_GYROandHOS_DECK_IMUboth on, chosen by the Game Mode starts on the Steam Deck OLED (Measurements, the switches); both rows are in; a Deck LCD is Still to test]tests/that reads changed source is updated, not weakened. [tests/test_gyro_rearm.py's fixture getsdeck_imu = 0;tests/test_steam_pads.pyextended]host/pad_sdl.candhost/hos_sdl.ccompiled for both at this head; the HID path is SDL's own, passed through]Assisted-by:/Co-Authored-By:trailers.Ready to merge
main, measured again or a comment says why the numbers still hold. [Forgejo runs no CI yet; the head8704dbc1ais pushed, on maina104182b4; the Game Mode numbers are from cf94a4fec on main9ea65c7bf, the same Deck code (Measurements, Baseline), not yet run again on currentmain]Tested in game: Steam Deck OLED, SteamOS 3.9.5, headless over ssh with Steam's controller variables set by hand: with the change SDL3 opens Steam Deck Controller with a gyroscope and Motion controls reads it; main and HOS_DECK_GYRO=0 open only Steam's virtual gamepad. Not yet run from the Steam shortcut in Game Mode.
Possibly related, for context:
Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).
**Not testable by hand:**line saying why and what stands in for it. Then tick it.31dc503fd32ccf1040c5Rebased onto main
a433db328; the change gained akillrow forHOS_DECK_GYROingpu/vk/switches.def, which main'stests/test_switch_table.pynow asks for, and the test commit is unchanged. Three ten-minute headless stands on a Steam Deck OLED (built at 5306ca05d on main9ea65c7bf) are now in Measurements anddocs/tested/: with this PR the Deck's gyro is found and read beside Steam's virtual gamepad, and withHOS_DECK_GYRO=0only the virtual gamepad opens and there is no motion. The same stands show the frozen-gyro rule turning a resting Deck's sensors off and on 5 times in 600 s with this PR alone, and 0 times with #1796, so this PR should merge after that one. Still open, and the reason it stays WIP: the by-hand run in Game Mode from the Steam shortcut (aiming, buttons, trackpads, back grips, Steam and Quick Access buttons, after quitting and in Desktop Mode), by zeldaootr.2ccf1040c53131b399daTwo Game Mode starts from the Steam shortcut on a Steam Deck OLED. The first did nothing (only Steam's stand-in pad opened, with nothing in the log):
pads_startcopied Steam's real ignore list, 11,102 characters and 793 entries, into a fixed 4096-byte buffer and gave up without a word; main's Steam Controller path has the same buffer, so this fixes it too. With the list sized from Steam's and a warning whenever Valve's pads must stay in it, the second start opened the Deck's controls with a gyroscope beside Steam Input's pad and Motion controls read "On (gyro found)"; tilting did nothing until a gyro binding in Steam Input (50 frozen-sensor lines before it), because Steam leaves the Deck's IMU off without one, and with "As Mouse" bound aiming followed the Deck. The last two commits add the step that turns the IMU on when both sensors read nothing (deck_imu_poll,HOS_DECK_IMU,tests/test_deck_imu.py); it is test-first and smoke-run only, not yet run in Game Mode. Thedocs(tested)commit is dropped, since main removed the tested-configurations catalogue (the other eight commits unchanged,git range-diff=), and the description follows the new template. It stays WIP until the IMU step has run on the Deck.The IMU step ran in Game Mode: zeldaootr started v3.0.0-54-gcf94a4fec (this head's Deck code on main
9ea65c7bfwith #1796, not this head's own build; Measurements' Baseline says what differs) from the Steam shortcut on a Steam Deck OLED with no gyro binding in Steam Input, and aiming followed the Deck before, during and after opening the overlay ("everything worked great"). In a 31-minute session and a 70 s start the log has the two IMU lines once each at the start, 4 and 1 laterturned on againrecoveries, 0 re-arm lines (50 in the build without the step) and no warning; a headless forced-off check on the Deck also turned the sensors back on. Testing, Measurements, Risks and the three Ready-for-review / When-it-applies boxes are updated to match. Still open: this head built on currentmainin Game Mode, the trackpads and Steam buttons after quitting and in Desktop Mode, a gyro binding together with this, a Steam Deck LCD, a Steam Controller, and Windows.WIP: feat(host): the Steam Deck's gyro reaches Motion controls when Steam starts the gameto feat(host): the Steam Deck's gyro reaches Motion controls when Steam starts the game3131b399da8704dbc1aeRebased onto main
a104182b4(head8704dbc1a). Onlyhost/hos_sdl.candhost/hos_sdl.hconflicted: main now hashos_sdl_pad_productitself, so this PR uses main's and no longer adds it.pads_start,deck_imu_poll,host/steam_pads.hand the two new tests are unchanged (git range-diff). The Deck's motion-only pad still stops before main's new vibration and haptics code. The checks that read the changed files give the same failures here and on main; both files compile for Linux and Windows. Not run in the game again after the rebase.Rebased onto main
87c0d7b4d(head97bd6fb59), which now has #1796. The two touch the same lines: the frozen-gyro rule here now has both conditions, main's "and the accelerometer is frozen too" and this PR's "not the Deck's own controls". That is the combination the Game Mode test build ran (this PR's code with 1796's two commits). The three gyro checks pass at this head. Not run in the game again after the rebase.8704dbc1ae97bd6fb594Rebased onto main
6e1521a70(head56201f8a6). Main now marks the Deck's own controls so their trackpad mouse doesn't also fire mouse bindings; its new checks and helper are kept beside this PR's.pads_startanddeck_imu_pollare unchanged, and the Deck's motion-only pad still leaves the per-pad loop before it is counted and before any button, Sprint or vibration handling. The three gyro checks pass at this head; not run in the game again after the rebase.97bd6fb59456201f8a66View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.