[WizardOfCodez]

What and why

This builds on #1304 and #1305, which fix the small docked picture. It should merge after them; it does not need their code to build. #1310 (the copy absorb) is not part of it, but the play test below ran with it.

• Resolution setting. With The graphics scale is tier 0 in both modes: Star Fox's docked 3D was 768x432, smaller than handheld #1304 and A Switch 2 display's largest layer is its largest buffer: Star Fox outputs 1920x1080 on a 4K screen, rendering 960x540 #1305, Star Fox renders its scene at its own scale of the target: 0.5 docked, so 1920x1080 on a 4K screen, then upscales with NDSR. A frame-step stub at main+0xb4498ac (build a7730d0f… only) replaces that scale with DM_RESOLUTION_SCALE when it is set. The launcher offers it as Resolution (Game's own / 75% / 100%), gated on the build's RESOLUTION_SCALE capability. With 0, every instruction the game runs is its own. patch_nso.py gives frame-step code ctx.area(offset): main's text is 189 MB, so a branch from the front patch area cannot reach the site.
• Avatar settings crash. nn::chat::GetVirtualCameraNativeWindowHandle returned 0. The game creates an NVN window from whatever handle it gets, so this crashed. The hook now returns an off-screen native window: the window initializes, acquires at once with its sync signalled, and presents nowhere. Reference entry: docs/reference/services.md (GameChat).
• Probes. DM_PROBE_FP=1 logs s0–s15. DM_PROBE_WATCH and DM_PROBE_POLL take as+<offset> (relative to the guest address space base), so an address found in one run works in the next.
• Game note. It records the picture's cause chain and the measurements, plus the Venom 2 out-of-memory that A GPU copy into a texture taken from its storage no longer uploads all of it again: Star Fox's 7-10 s stalls at scene changes #1310 removes.

Checked

• Tests:
  • make -C dm/host/tests GAME=0400E88025B1A000 run passes (t_pctl: 67 checks, including the virtual camera window).
  • make -C dm/gfx/tests GAME=0400E88025B1A000 check_t_nvn passes (238, including the off-screen window).
  • check_t_readback passes (173).
  • test_docs.py, test_patches.py, test_settings.py and test_launcher_settings.py pass.
  • clang-tidy and lint_python report nothing new in the changed files.
• Game run: Star Fox (0400E88025B1A000, v131072) on an M1 Pro (32 GB), macOS 27.0.1.
  • Docked on a 4K screen, a test build with The graphics scale is tier 0 in both modes: Star Fox's docked 3D was 768x432, smaller than handheld #1304, A Switch 2 display's largest layer is its largest buffer: Star Fox outputs 1920x1080 on a 4K screen, rendering 960x540 #1305, An sRGB texture in an image slot is loaded and stored raw, as on NVN: Star Fox's picture was encoded twice #1308 and A GPU copy into a texture taken from its storage no longer uploads all of it again: Star Fox's 7-10 s stalls at scene changes #1310 was played through the whole campaign to the end of Venom 2.
  • The player reported that everything worked. Opening the avatar settings in the game was not checked separately, only by the unit tests.
  • Frame rate at Game's own, 75% and 100%: 60 fps in flight, 30 in cinematics.
• Venom 2: without A GPU copy into a texture taken from its storage no longer uploads all of it again: Star Fox's 7-10 s stalls at scene changes #1310, the GPU ran out of memory at the load of the second part, after 69 minutes. The residency set held 23.8 GB of textures, against a working set of 25.5 GB.
  • With A GPU copy into a texture taken from its storage no longer uploads all of it again: Star Fox's 7-10 s stalls at scene changes #1310, the full re-uploads of the streamed BC7 arrays at scene changes go away: 20–26 per change, about 1.4 GB each, down to 0, on the same route through Venom 2's first part.
• regress.py check: not run. This Mac has no other games. The host changes reach only a game that asks GameChat for a virtual camera window, or that uses the new probe switches. The rewriter's ctx.area is used only by this profile's stub.

Docs

• The findings are in the game note and docs/reference/services.md, 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