New since u59-windows-20261002-int3: lower VRAM use, on in the bundled u59-preset.json. The shader recompiler emulates LDS in vertex and pixel shaders with a 32 KiB array per shader invocation, and the NVIDIA driver reserves memory for that array for every thread the GPU can keep resident (about 3.9 GiB on an RTX 3090) until the game exits. KYTY_FUNCTION_ARRAY_SHRINK shrinks these arrays to the elements a shader can reach before the driver sees it; KYTY_VRAM_GC_BUDGET collects textures and buffers against the VRAM budget while the game runs instead of thresholds fixed at startup. Measured on one PC (RTX 3090, Ryzen 9 7950X3D, 120 Hz vblank), Astro Bot Sky Garden start view, six alternating runs each: dedicated VRAM 9.4 GB with int3 and 6.3 GB with a local build of this source, peak since start 12.4 GB and 7.5 GB; 33.6 fps with int3 and 33.0 fps with the local build (within the spread between runs). Smaller cards were imitated by another process that holds 12 GiB or 16 GiB of the card's 24 GiB from boot: Astro Bot now reaches the Sky Garden and runs at 32-33 fps there, where int3's preset got stuck in the galaxy map. Tested on NVIDIA only; setting either flag to 0 in u59-preset.json turns it off. Release builds now compile from the source path the PGO profile was recorded at (C:\kyty-src); earlier GitHub builds missed the profile for every function in an anonymous namespace (2,499 of the 17,426 functions in int3's profile). This did not change the frame rate measurably. kyty_emulator is built with a new PGO profile recorded in Astro Bot with this source. Open launcher.exe directly; the existing shared Kyty.ini supplies game paths and display settings. The first launch can compile shaders again. See U59-README.md.