Repository navigation
Releases
Astro Bot DLSS frame generation (astrobot-dlss-int21-23y, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_ASTRO_UPSCALE=0 |
Astro Bot: DLSS/FSR upscale only to the game's 2432x1368 TAA output, as before 23q |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR ...
Astro Bot DLSS frame generation (astrobot-dlss-int21-23w, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_ASTRO_UPSCALE=0 |
Astro Bot: DLSS/FSR upscale only to the game's 2432x1368 TAA output, as before 23q |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR ...
Astro Bot DLSS frame generation (astrobot-dlss-int21-23v, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_ASTRO_UPSCALE=0 |
Astro Bot: DLSS/FSR upscale only to the game's 2432x1368 TAA output, as before 23q |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR ...
Astro Bot DLSS frame generation (astrobot-dlss-int21-23r, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_ASTRO_UPSCALE=0 |
Astro Bot: DLSS/FSR upscale only to the game's 2432x1368 TAA output, as before 23q |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR ...
Astro Bot DLSS frame generation (astrobot-dlss-int21-23q, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_ASTRO_UPSCALE=0 |
Astro Bot: DLSS/FSR upscale only to the game's 2432x1368 TAA output, as before 23q |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR ...
Astro Bot/Playroom DLSS/FSR frame gen + upscaling – built-in Decouple, real Playroom upscaling, more game versions (astrobot-dlss-int21-23o, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR upscaling (experimental)
Astro Bot draws its 3D image at a render resolution and its own TAA pass upscales tha...
Astro Bot/Playroom DLSS/FSR frame gen + upscaling – built-in Decouple, real Playroom upscaling, more game versions (astrobot-dlss-int21-23M, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564 / PPSA21567 / PPSA21568) and
Astro's Playroom (PPSA01325):
New in this release -
- Built-in Decouple
Decouple is now built into the emulator for Astro Bot (any version and region) and Astro's Playroom. It finds the game's timing code itself, so you don't need the patch file or a button combo. It uses the v3 smoothing and the 1/20 s delta-time cap. The patch file's Decouple and the mods that need it (frame-limiter sleep, precise frame caps, delta-time caps) are skipped while it's on, so use the launcher's Frame rate limit instead. Playroom is smoother too, and no longer runs at double speed above Vblank 60. The console shows Decouple: built-in one on. "KYTY_ASTRO_DECOUPLE": "0", goes back to the patch file.
- No more slow motion at level starts
The "[Fix] Bot rescue" mod is now skipped. Its hooks fire when you enter and leave a level, not on rescues, so it was switching Decouple off mid-stage. Rescues work fine without it.
- Real DLSS/FSR upscaling in Astro's Playroom
Before, DLSS/FSR only anti-aliased Playroom at the render resolution. Now they upscale the scene to the full output size, with the game's own effects (bloom, particles) kept on top. 540p works too, upscaled 3x and stretched the rest of the way. The HUD is drawn at the render resolution for now: sharp at 1080p and above, a little soft at 720p.
- More Astro Bot versions supported
The built-in render resolution and the "too many objects" crash fix now work on:
- 01.007.000, the disc / unpatched version (thanks to moooohung, PR #3)
- other versions, found by what the code does and only patched when there's exactly one match
- the Asian edition (PPSA21568), alongside US and EU
If you're on anything other than 01.018, please post your console's fixed render resolution ... and command buffers x2 ... lines (or the not applied / not found line).
- Gyro
The gyro is centred from the start: the resting offset is saved per controller. There's also a new re-centre key (F9 by default, set in the launcher).
- Fixes from moooohung (PR #2)
Korean and Japanese text no longer shows as ?, and FSR frame generation now works without FSR upscaling.
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
- Jitter bug squashed in Astro's playroom - thanks to TomiSharked for flagging
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot and Astro's Playroom keep their
speed with Decouple built in: no patch file or button combination needed, any version and
region. The console shows Decouple: built-in one on. If it says not applied instead, a
"Decouple gameplay timers from render FPS" mod in the patch file is used as before; please report
that line with your game version. The community "[Fix] Bot rescue" mod is skipped: it slowed the
game down (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO.
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G rea...
Astro Bot/Playroom DLSS/FSR frame generation and upscaling (astrobot-dlss-int21-20, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564) and
Astro's Playroom (PPSA01325):
New in this release -
- Continuous gyro calibration
What it does: whenever the controller has been still for half a second (barely rotating, with gravity steady), the emulator learns the gyro’s resting offset and removes it from every reading. That covers both the rotation speed the game reads and the orientation the emulator works out from it, so aim and tilt should stop creeping sideways.
When it adjusts: the first estimate is ready after about a second of stillness. After that it adjusts slowly, so it follows the sensor warming up but doesn’t eat intentional slow movements. Each controller learns its own offset.
What you’ll see: the console prints Gyro calibration: resting offset x, y, z degrees/s removed ... once it has learned the offset, so you’ll see your controller’s actual drift figure. "KYTY_GYRO_CALIBRATION": "0", turns it off.
This fixes the gyro drifting out of sync in Astro Bot
2.Minor Housekeeping
Re-ordered some elements of the launcher.
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot needs a "Decouple gameplay timers
from render FPS" patch to keep its speed. The community "[Fix] Bot rescue" mod that goes with it
could leave Decouple switched off for a whole level (Pumpkin Peril played in slow motion until the
level was left); this build replaces that mod with a built-in version that switches Decouple back
on by itself (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO. Astro's Playroom: keep the Vblank frequency at 60
(see below).
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher c...
Astro Bot/Playroom DLSS/FSR frame generation and upscaling (astrobot-dlss-int21-19, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564) and
Astro's Playroom (PPSA01325):
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency 60, with frame generation on top (2x: 120 fps on screen) at a matching
Frame rate limit. Lower the render resolution if your PC cannot hold 60 in the busiest
levels: evenly timed frames feel far smoother than a rate that keeps dipping.
Below 60 (40 or 45 gives beautifully even frames) Astro Bot needs a "Decouple gameplay timers
from render FPS" patch to keep its speed. The community "[Fix] Bot rescue" mod that goes with it
could leave Decouple switched off for a whole level (Pumpkin Peril played in slow motion until the
level was left); this build replaces that mod with a built-in version that switches Decouple back
on by itself (see Known issues). If you still see slow motion below 60, go back to 60 and please
report the level.
Without a variable-refresh display keep FIFO. Astro's Playroom: keep the Vblank frequency at 60
(see below).
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested working on Windows in both Astro Bot and Playroom.
On Linux and macOS (new in this build, untested by us) FSR frame generation is built into the
emulator from AMD's FidelityFX SDK 1.1.4 sources, so the same launcher choice (or
"KYTY_FRAMEGEN": "1", with "KYTY_FRAMEGEN_BACKEND": "fsr", in u59-preset.json) works on any
Vulkan GPU, no extra file needed. AMD's frame generation swapchain is Windows only, so there the
emulator shows the frames itself, on its vblank ticks: the generated frame at the tick a new game
frame arrives, the game's frame at the next tick. So set Vblank frequency to twice the game's
frame rate (e.g. 120 for 60 fps, with a display that shows 120 Hz); if the game reaches the
vblank rate itself, no frame is generated. The console shows Frame generation: AMD FSR 3.1 frame generation asked for (2x, built in), FSR 3.1 ready (..., built in), FSR on and
FSR 2x on (...; built in, shown at the vblank ticks). It needs SDR output (not HDR). Please report
whether it works, with those lines.
DLSS and FSR upscaling (experimental)
Astro Bot draws its 3D image at a render resolution and its own TAA pass upscales that to the
output resolution. With **DL...
Astro Bot DLSS/FSR frame generation and upscaling(astrobot-dlss-int21-18, experimental)
KytyPS5 (Jetsku U59) with DLSS and FSR for Astro Bot and Astro's Playroom
An experimental, unofficial test build of Jetsku/KytyPS5
that adds frame generation and modern upscaling to ASTRO BOT (PPSA21564) and
Astro's Playroom (PPSA01325):
What's new in build 18
Silky-smooth frame times on G-Sync / FreeSync displays
Set Present mode: Immediate with Smooth frame pacing ticked. A late frame is now shown the
moment it's ready instead of being doubled, so frame times stay remarkably even. In a busy
Astro Bot level (Sky Garden) the visible hitches dropped from 97 a minute to 7, and the slowest
1% of frames went from 33 ms to 23 ms.
Then pick a Vblank frequency your PC holds even in the busiest levels: a steady lower rate feels far
smoother than a higher one that keeps dipping. Tester's setup (RTX 5080), smooth all the way
through: Vblank 40, Frame generation 2x, Frame rate limit 80, Immediate, Smooth frame pacing,
G-Sync on.
Fixed: slow motion with frame generation
With Smooth frame pacing on, frames that took a little too long to present (most often with
DLSS-G 3x) cost the game vblanks, so Astro Bot could drop into slow motion until the next load.
The game now gets every vblank on time, at 2x, 3x and 4x.
Also since build 17
- 960x540 and 1280x720 render resolutions for both Astro Bot and Astro's Playroom (launcher:
Render resolution, no patch needed) - Playroom no longer runs too fast with Immediate + Smooth frame pacing
- FSR 3.1 frame generation on Linux and macOS (new, untested on real hardware)
Without a variable-refresh display, keep Present mode on FIFO. Astro's Playroom: keep Vblank at 60.
Full notes, setup and known issues below.
| What it does | GPU | Platforms | |
|---|---|---|---|
| NVIDIA DLSS frame generation (DLSS-G) | 2x, 3x, 4x generated frames, with Reflex | RTX 40 / 50 (3x/4x: RTX 50) | Windows |
| AMD FSR 3.1 frame generation | 2x generated frames | any GPU (AMD, Intel, RTX 20/30, ...) | Windows, Linux, macOS |
| NVIDIA DLSS upscaling (super resolution) | replaces the game's TAA | any RTX | Windows |
| AMD FSR 3.1 upscaling | replaces the game's TAA | any Vulkan GPU | Windows, Linux, macOS |
| Built-in render resolution | 540p / 720p / 1080p / 1368p / 1872p / 2160p, no patch file needed | any | all |
Everything else is Jetsku's U59 int21 release (24 October 2026).
All of this only switches on where it finds Astro Bot's or Playroom's inputs (depth, motion vectors
and camera); in other games it stays off. With the streamline folder present Streamline still sits
between the emulator and the driver, so if another game misbehaves with this build, set
KYTY_FRAMEGEN=0 or remove the folder.
Requirements
- Windows 10/11 with hardware-accelerated GPU scheduling on (Settings > System > Display >
Graphics > Advanced graphics settings; restart after changing it), for frame generation. - DLSS-G and DLSS upscaling: an NVIDIA RTX card (RTX 40 or 50 for frame generation) with a
recent driver (tested: RTX 5080, 617.42), and NVIDIA's Streamline v2.14.1 runtime files (not
included, see below). - FSR upscaling and FSR frame generation: any GPU. Nothing to download: AMD's
amd_fidelityfx_vk.dll(FidelityFX SDK v1.1.4, MIT licence) is included next to the emulator. - Linux / macOS: see below (FSR upscaling, FSR frame generation and the render resolution).
Setup
-
Download this release's zip and unzip it into a new folder.
-
For DLSS only: download NVIDIA Streamline v2.14.1:
https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.1 - pick
streamline-sdk-v2.14.1.zip(not the aarch64/arm64ec ones). -
For DLSS only: in the unzipped emulator folder, next to
kyty_emulator.exe, make a folder
named exactlystreamlineand copy into it the files from the Streamline zip'sbin\x64folder
(the files themselves; thedevelopmentsubfolder is not needed).KytyPS5-AstroBot-DLSSG\ ├── kyty_emulator.exe ├── kyty_launcher.exe ├── amd_fidelityfx_vk.dll ├── ... └── streamline\ ├── sl.interposer.dll ├── sl.common.dll ├── sl.dlss_g.dll ├── sl.dlss.dll ├── sl.reflex.dll ├── sl.pcl.dll ├── nvngx_dlssg.dll ├── nvngx_dlss.dll └── ... -
Turn NVIDIA Smooth Motion off for kyty_emulator.exe in the NVIDIA App (it clashes with
frame generation). -
Pick your settings in the launcher (below) and start the game as usual.
Settings
In the launcher, a game's Graphics & display settings have:
- Frame generation: Off, 2x, 3x, 4x (NVIDIA DLSS-G; 3x and 4x need an RTX 50 card), or
2x (AMD FSR 3.1, any GPU). - Upscaling: the game's own TAA, NVIDIA DLSS or AMD FSR 3.1.
- Render resolution: the game's 3D resolution, for both Astro Bot and Playroom (lower is faster).
- Relaxed shader maths: simpler shader maths, see below.
- Smooth frame pacing (
KYTY_PRESENT_ABS_VBLANK): after a slow frame a vblank is skipped
instead of the next frames being shown back to back. Only the display skips it: the game still
counts the vblank, so its speed stays right. - Frame rate limit (
KYTY_FRAMEGEN_FPS_CAP): with DLSS-G, NVIDIA Reflex holds the rendered
frames to that rate so generated frames are evenly spaced; pick one your PC holds, e.g. 40 or 60
with Vblank frequency 120.
They take precedence over u59-preset.json.
Recommended on a G-Sync / FreeSync display: the smoothest way to play
With these settings the frame times are remarkably even: no judder and no hitching, just a
steady, fluid picture. In the tester's words, "ultra smooth because of the perfect frame times".
- Present mode: Immediate, with Smooth frame pacing ticked. A frame that misses its vblank
is shown the moment it is ready, instead of a whole vblank later, and the variable refresh shows
it evenly. Measured in a busy Astro Bot level (Sky Garden) against FIFO: the visible hitches
(doubled 33 ms frames) dropped from 97 a minute to 7, and the slowest 1% of frames went from
33 ms to 23 ms. - Vblank frequency: one your PC holds even in the busiest levels. A lower rate that never dips
feels far smoother than a higher one that keeps missing it: every frame then takes exactly the
same time. Astro Bot keeps its normal speed below 60. - Frame generation on top, at a matching Frame rate limit.
The tester's setup (RTX 5080), smooth all the way through: Vblank frequency 40, Frame generation
2x, Frame rate limit 80, Present mode Immediate, Smooth frame pacing on, G-Sync on.
Without a variable-refresh display keep FIFO. Astro's Playroom: keep the Vblank frequency at 60
(see below).
This build is made like Jetsku's U59 releases (profile-guided optimisation trained on Astro Bot,
the emulator's diagnostics compiled out) and ships Jetsku's tuned u59-preset.json next to
the launcher. While that file is there, the launcher ignores KYTY_... environment variables
and uses the file instead: add settings to it, one "NAME": "value", line each, for example
"KYTY_FRAMEGEN": "2", or "KYTY_VRAM_BUDGET_MB": "12000",.
| Variable | Effect |
|---|---|
KYTY_FRAMEGEN=0 |
Frame generation off |
KYTY_FRAMEGEN=1 |
2x (default) |
KYTY_FRAMEGEN=2 / 3 |
3x / 4x multi frame generation (DLSS-G, RTX 50 only) |
KYTY_FRAMEGEN_BACKEND=fsr |
AMD FSR 3.1 frame generation instead of DLSS-G (launcher: 2x AMD FSR 3.1) |
KYTY_DLSS=1 |
DLSS upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR=1 |
FSR 3.1 upscaling in place of the game's TAA (launcher: Upscaling) |
KYTY_FSR_SHARPNESS=0.5 |
FSR upscaling's sharpening, 0 to 1 (default off) |
KYTY_ASTRO_RENDER_RES=1080 |
Render resolution: 540, 720, 1080, 1368, 1872 or 2160, both games (launcher: Render resolution) |
KYTY_FRAMEGEN_FPS_CAP=40 |
With DLSS-G: Reflex limits the rendered frames to 40 fps (launcher: Frame rate limit) |
KYTY_FLOAT_PROFILE=relaxed |
Simpler shader maths (launcher: Relaxed shader maths) |
KYTY_STREAMLINE_DIR=<folder> |
Use Streamline files from another folder |
KYTY_VRAM_BUDGET_MB=12000 |
Leave video memory for DLSS-G (helps on 16 GB cards at 4K) |
KYTY_PORTABLE=0 |
Use the shared Kyty.ini instead of this build's own (see below) |
NVIDIA DLSS frame generation (DLSS-G)
The emulator's console window shows, in order:
Frame generation: Streamline loaded from ...\streamline (1 generated frame(s) per frame)
Frame generation: Streamline offers DLSS-G with this GPU, driver and Windows
Frame generation: Vulkan is loaded from sl.interposer.dll (Streamline's interposer, as needed)
Frame generation: DLSS-G ready (1 generated frame(s) per frame); it turns on in the game's 3D view
Frame generation: the game's inputs found (motion and depth 3840x2160, ...)
Frame generation: DLSS-G on
Use the NVIDIA overlay (Alt+R) to see the frame rate on screen: it counts the generated
frames. The emulator's own counter shows the game's real frame rate, which frame generation does
not change.
AMD FSR 3.1 frame generation (experimental)
Frame generation: 2x (AMD FSR 3.1, any GPU) generates frames with AMD's FSR 3.1 instead of
DLSS-G, on any GPU, from the same depth, motion vectors and camera. No Streamline files are
needed. Use it with FSR upscaling or the game's own TAA (not with DLSS upscaling). The console
shows Frame generation: FSR swapchain ..., FSR 3.1 ready ..., then FSR on and
FSR 2x on (render ..., display ...) in the 3D view; it switches off during videos and menus and
back on in the 3D view. "KYTY_FRAMEGEN_DEBUG": "1", draws FSR's tear and reset lines, "2" its
debug view. Tested wor...