Astro Bot DLSS setup: correct Streamline files and recorded launch checks
ItsOOGWAY · PC guides & recorded tests
Astro Bot DLSS setup: correct Streamline files and recorded launch checks
Set up Astro Bot on Windows with the KytyPS5 DLSS build. This step-by-step PC guide shows the Windows download, adding your own extracted game, installing the correct NVIDIA Streamline x64 files, choosing the Astro Bot settings and checking the console before testing gameplay.
The key checkpoint: Use the x64 Streamline runtime in a streamline folder beside kyty_emulator.exe. Check console activation and distinguish generated display frames from rendered frames.
Before you start
- Recorded experimental build: astrobot-dlss-int21-20.
- Game recording: PPSA21567 version 01.019.000; allow space for extracted data.
- The corrected 2x DLSS-G session retains game TAA; later Streamline errors remain part of the evidence.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Choose the build and add your game
Astro Bot is running on this PC, including Sky Garden, combat and a bot rescue. But getting the game to open and getting the DLSS setup right were two different things. I downloaded the wrong package during my first attempt. In this guide, I'll show the corrected route, the settings I tested, and how to check whether frame generation is actually doing anything. Start with the Kyty PS5 fork linked in the resources section. Open its Releases page and choose the Astro Bot build with DLSS and FSR support.
The release used here is the experimental int twenty-one, build twenty. Download its Windows sixty-four-bit package and extract the complete archive into a separate folder. This is a prebuilt Windows release, so you don't need to compile the emulator from source for this walkthrough. You also need your own compatible Astro Bot game files, already extracted and ready for the launcher. My recording uses game version one point zero nineteen, with the title ID ending in two one five six seven.
Keep your game and emulator in separate folders. The game entry shown here is about one hundred and forty-nine gigabytes, so allow space for the unpacked files as well as any archives you keep. The compressed download size is not the installation size.
Walkthrough 02
Understand the per-game graphics choices
Open kyty launcher from the extracted emulator folder. If you have used another build before, you might already see games in the list. If Astro Bot is missing, open Settings and add the directory containing your extracted game to Game folders. Save, return to the library and let it refresh. Check that the Astro Bot entry points to the actual game folder. A separate backport folder is not the game entry I launch here. Before changing performance settings, right-click Astro Bot and open its own game configuration.
This matters because the per-game choices can differ from the global defaults. I use this window throughout the recording, so follow the Astro Bot configuration rather than changing settings for every game in your library. We'll save the choices and relaunch after making a meaningful change. The first thing to separate is upscaling from frame generation. Upscaling reconstructs the image from a chosen render resolution. Frame generation adds intermediate displayed frames. In the corrected take, I select two-times DLSS frame generation, while Upscaling still says the game's own T A A.
So this particular demonstration is not proof that DLSS super resolution is enabled too. Read both fields instead of assuming one switch enables everything.
Walkthrough 03
Correct the Streamline architecture and folder
For the NVIDIA frame-generation route, check the supported hardware and Windows requirements in the release notes before continuing. Two-times DLSS frame generation is the relevant option for my RTX forty-seventy Super. Windows hardware-accelerated G P U scheduling needs to be enabled, and changing it requires a restart. The release also says to turn off NVIDIA Smooth Motion for the emulator, so two different frame-generation systems aren't competing with each other. Now we reach the download that caused my first mistake.
Open the linked NVIDIA Streamline two point fourteen point one release. Choose the normal Streamline S D K ZIP for Windows x sixty-four. Don't pick the A Arch sixty-four or Arm sixty-four E C packages. I used the wrong architecture in the earlier recording, so I'm replacing that attempt with the corrected download shown here. A matching version number alone isn't enough; the architecture needs to match too. Go back to the extracted Kyty folder, the one containing kyty emulator dot exe.
Create a folder named streamline directly beside that executable. Open the downloaded S D K archive, go into bin, then x sixty-four, and copy the runtime files themselves into streamline. Don't leave them inside another bin or x sixty-four folder under it. The emulator needs to find those files at the location shown on screen. Use the normal runtime files from bin slash x sixty-four, rather than the development subfolder. Check the finished folder before launching again: the emulator executable is outside streamline, and the copied DLL files are inside it.
This is the corrected file placement from my later take. You don't need to repeat the game extraction just because the separate Streamline package was wrong.
Walkthrough 04
Save and inspect the launch messages
Return to Astro Bot's game configuration. In the corrected launch, the screen resolution is nineteen-twenty by ten-eighty, the render resolution is also nineteen-twenty by ten-eighty, frame generation is two-times DLSS G, and upscaling remains the game's T A A. Smooth frame pacing is checked. I'll keep this settings screen readable so you can distinguish the options instead of copying a quick flash of the menu. You'll also see me try different frame limits and V blank values across the recordings.
Those are tests, rather than several steps you must all repeat. A value of one hundred and twenty in a settings box is not a measurement of the gameplay. Start from the release's recommended configuration for your display, then make one change at a time. If a change makes the game run at the wrong speed, restore the previous setting before testing anything else. Save the configuration, launch Astro Bot and give the first startup time to finish.
The splash image, startup logos and travel sequence all appear in this session. I'll shorten those waits, then return to normal speed when there is something to control. A busy console during loading isn't, by itself, a reason to keep closing and reopening the game. Watch for progress and an actual error before deciding what to change.
Walkthrough 05
Check Sky Garden and later errors
The console gives us a better check than the menu alone. In the corrected launch, it verifies NVIDIA-signed files from the streamline folder. Later, there is a frame-generation status line reporting two frames shown per rendered frame. That's useful evidence that the path is being used. For your own run, check the activation messages described in the release notes, rather than treating a selected dropdown as the final confirmation. There is also an important difference between the two frame-rate readings.
The emulator's counter reports the game's rendered rate, while NVIDIA's overlay can include generated frames. Those numbers answer different questions. Frame generation can improve the displayed motion without doubling the speed at which the game simulates input. When comparing results, keep the same scene and settings, and say which counter you are reading. Here is the result from the corrected session. Astro moves around the crash site, jumps onto the rocks and continues into the galaxy map.
We then enter Sky Garden, move through the opening area, fight enemies and rescue a bot. I'll leave a stretch at the recording's original speed, with the game sound, so you can judge the movement and transitions instead of only seeing a loading screen or a high number in a menu.
Walkthrough 06
Compare results with useful logs
This run also shows why I wouldn't stop checking after the first smooth scene. Later console output contains repeated Streamline errors even though the game is still visible. I also return to settings and try another launch. That doesn't erase the working gameplay, but it means this recording isn't a complete stability test. If your own run starts producing errors, keep the message and compare it with the last setting you changed. For a useful report, include the exact fork and build, your game version, graphics card and driver, the frame-generation and upscaling choices, and the console messages around the problem.
Note whether it happens during loading, entering a level or a bot rescue. That gives another tester something specific to reproduce. Changing several options together and only reporting that it feels worse makes the cause much harder to find. The route to follow is now clear: use the correct Windows build, point the launcher at your own extracted game, install the matching x sixty-four Streamline files in the right folder, save the Astro Bot settings and check the launch messages.
The main avoidable mistake here was the wrong Streamline download. Keep the working setup together, and compare later changes against it instead of starting over every time.
If your result differs
| Situation | Next useful check |
|---|---|
| Your result differs from the recording | Compare the exact recorded version, folder checkpoint and error before changing another setting. |
| The application closes or reports an error | Keep the current log and note the stage, game version and last changed setting. |
| A progress or FPS number looks promising | Check the matching scene and what that counter measures; the recording does not establish complete-game compatibility. |
Comments
Post a Comment