[FifteenPen]

What and why

Drag x Drive (040041601D83A000, v196608, SDK 20.5.6, Nintendo EPD's engine, NVN2) plays on the Mac with a pair of Joy-Con 2s over Bluetooth LE, at the game's own 30 fps. This adds its profile (the survey's game.tsv with its name and two NVN keys, the shader tables, a prewarm list recorded in play), its note, its row in the games table and its line in README's Switch 2 list.

It depends on two other pull requests:

• NVN: account for four-byte direct indexed draws using control memory #1609 (four-byte draw tickets, issue NVN2: oversized model scratch recordings exhaust BFRES resource heaps (Wonder Switch 2 Edition) #1580): without them the game crashes 5 s after boot, as it initializes a buffer in no memory pool ([RED] BufferInitialize: pool has no storage (pool 0x0 … size 0x170), then CRASH sig=11 addr=0x4 pc=h_nvnMemoryPoolGetFlags+0). The same host with DM_NVN_DRAW_CTL=0 crashes there; with nvn_draw_ctl on it plays. The profile sets nvn_draw_ctl on, which main ignores until NVN: account for four-byte direct indexed draws using control memory #1609 is in.
• nn::hid::EnableUnintendedHomeButtonInputProtection is answered by the host and logged: Drag x Drive no longer crashes at sdk+0x63ce10 as player 1's Joy-Con 2 joins #1921 (nn::hid::EnableUnintendedHomeButtonInputProtection): the game calls it as the Joy-Con 2s join. Its commit is this branch's first, so the note's link to its reference entry resolves; it drops out on a rebase once nn::hid::EnableUnintendedHomeButtonInputProtection is answered by the host and logged: Drag x Drive no longer crashes at sdk+0x63ce10 as player 1's Joy-Con 2 joins #1921 is merged.

#1943 (the controller applet on the big host stack) fixes a crash seen once in play; the note lists it under Open.

render_cond on is set as in every session played; it was not measured without it.

Checked

• Tests, on this branch (main cfbdd93 + nn::hid::EnableUnintendedHomeButtonInputProtection is answered by the host and logged: Drag x Drive no longer crashes at sdk+0x63ce10 as player 1's Joy-Con 2 joins #1921's commit + this one):
  • python3 -m unittest dm/tools/tests/test_docs.py dm/tools/tests/test_game_profile.py dm/tools/tests/test_env_switches.py, python3 dm/tools/docs_symptoms.py --check.
  • Every dm/tools/tests file that reads the profiles or the games table (27 modules, 540 tests, with the CI's pinned packages): pass.
• Games run: Drag x Drive (040041601D83A000, v196608), from its NUP by scripts/build_ipa_from_nsp.py --platform mac-app, M4 Pro, docked, a pair of Joy-Con 2s (the launcher's Switch 2 controllers setting):
  • main e82888e + nn::hid::EnableUnintendedHomeButtonInputProtection is answered by the host and logged: Drag x Drive no longer crashes at sdk+0x63ce10 as player 1's Joy-Con 2 joins #1921 + NVN: account for four-byte direct indexed draws using control memory #1609: boot, the title and about 6 minutes of play in a session, 30 fps (frame time p50 33.33 ms in nearly every 300-frame window), GPU p50 7–11 ms, no red line;
  • the same app on main + nn::hid::EnableUnintendedHomeButtonInputProtection is answered by the host and logged: Drag x Drive no longer crashes at sdk+0x63ce10 as player 1's Joy-Con 2 joins #1921 without NVN: account for four-byte direct indexed draws using control memory #1609: the boot crash above;
  • an earlier tree (main db206a4 with the Joy-Con 2 work since landed on main, host/input: keyboard, mouse and trackpad on the iPad, Mac mouse camera #1490 and NVN: account for four-byte direct indexed draws using control memory #1609): 27 minutes of play.
• The prewarm list is the host's per-device list of the sessions played (1,591 shaders, 651 render, 64 task / mesh and 5 compute pipelines).
• Devices and OS: Apple M4 Pro (20-core GPU, 24 GB), macOS 27.2.
• Not checked: iOS, online play, render_cond off. The display version of v196608 was not read (the build row has ?).

Docs

• The finding is in its game note or its docs/reference/<subsystem>.md entry, and python3 dm/tools/docs_symptoms.py was run (the symptom index)
• A chain tool changed: not applicable
• No game files, keys or data extracted from a game in the change or the attachments

[FifteenPen]

This is ready to go. Game fully works.