Astro Bot
Astro Bot has an open bring-up thread. A third-party index says gameplay with freezes, with Windows and Linux reports.
Unofficial notes. No game files, BIOS, firmware, keys, ROMs, or mirrored builds. Download each project only from its official GitHub repository.
anyps5games. Sources collected 2026-10-15; latest dated source row 2026-10-12.

- Product codes
- PPSA21567, PPSA21564
- Projects
- KytyPS5, SharpEmu, prosper, AnyPS5
- Rows
- 7
| Game | Project | ID | Status | Platform | Updated | Source |
|---|---|---|---|---|---|---|
| Astro Bot | KytyPS5 | PPSA21567 | In gamein-game | Linux | 2026-10-02KytyPS5-2026-10-01-4479808-Linux-x86_64 | Open |
| Astro Bot | KytyPS5 | PPSA21567 | Nothingdoesnt-boot | macOS | 2026-10-09Official build KytyPS5-2026-10-09-7b9997b (v0.3.0 macOS release) | Open |
| Astro Bot | KytyPS5 | PPSA21567 | In gamein-game | Windows | 2026-10-05Official [KytyPS5-2026-10-05-dc3cd2d](https://github.com/KytyPS5/KytyPS5/releases/tag/KytyPS5-2026-10-05-dc3cd2d), compared with the BryKytyPS5 fork, build BryKytyPS5-2026-10-04-a9e1ae5. cc @BryanKAdams: issues are disabled on your fork, so I'm posting here. Your Astro Bot measurements are from AMD hardware; these are from Intel + NVIDIA. | Open |
| ASTRO BOT | SharpEmu | PPSA21564 | In gameingame | Windows | 2026-10-06a17aaca(main) | Open |
| Astro Bot | prosper | PPSA21564 | In progressin-progress | Linux* | 2026-10-12 | Open |
| Astro Bot | AnyPS5 | PPSA21564 | In gamecommunity | Windows | — | Open |
| Astro Bot | AnyPS5 | PPSA21564 | In gamecommunity | Linux | — | Open |
What the reports establish
7 result rows from 4 projects are preserved here. 0 rows only describe a discussion, an absent entry, or a different console; those are not extra tests. Sources were collected on 2026-10-15.
Dated result rows range from 2026-10-02 to 2026-10-12. These are the dates printed in the copied reports, not a new test or a new publication date for this website.
The 7 project/platform scopes do not all have the same status. Compare the individual project, OS, date, and build below. A difference between projects or machines is not proof of a regression in one emulator.
1 source links are shared by multiple rows. Those rows are not independent confirmations.
Report details and provenance
KytyPS5 · Linux
- Original status
- in-game
- Reported date
- 2026-10-02
- Build / version
- KytyPS5-2026-10-01-4479808-Linux-x86_64
- Game version
- Not supplied in the source table
- Reported hardware
- Intel Core i3 12100f / Nvidia RTX 3080 FE / 32gb micron DDR4 RAM
- Platform scope
- Named on the individual report
the game reaches main menu and gameplay , sound is slow , graphical artifacts shaders broken
Reported reproduction steps
1.Open kytyps5
KytyPS5 · macOS
- Original status
- doesnt-boot
- Reported date
- 2026-10-09
- Build / version
- Official build KytyPS5-2026-10-09-7b9997b (v0.3.0 macOS release)
- Game version
- Not supplied in the source table
- Reported hardware
- Apple M4 Pro (14 cores, arm64) / Apple M4 Pro (Metal 4.0 / MoltenVK 1.4.2) / 48 GB Unified Memory
- Platform scope
- Named on the individual report
On macOS (Apple Silicon via MoltenVK), attempting to launch ASTRO BOT ( ) fails immediately during Vulkan device suitability checking before guest execution can begin.
Reported reproduction steps
1. On macOS Apple Silicon, launch `kyty_emulator`:
KytyPS5 · Windows
- Original status
- in-game
- Reported date
- 2026-10-05
- Build / version
- Official [KytyPS5-2026-10-05-dc3cd2d](https://github.com/KytyPS5/KytyPS5/releases/tag/KytyPS5-2026-10-05-dc3cd2d), compared with the BryKytyPS5 fork, build BryKytyPS5-2026-10-04-a9e1ae5. cc @BryanKAdams: issues are disabled on your fork, so I'm posting here. Your Astro Bot measurements are from AMD hardware; these are from Intel + NVIDIA.
- Game version
- Not supplied in the source table
- Reported hardware
- Intel Core i9-12900KF (8P + 8E, no SSE4a) / NVIDIA GeForce RTX 5080, driver 617.14 / 64 GB DDR5-4800 / 16 GB
- Platform scope
- Named on the individual report
No observation excerpt was preserved for this row.
Reported reproduction steps
1. Windows with an Intel CPU (no SSE4a); run with `--amd-cpu --redzone`, 3840x2160 fullscreen, non-RT patch.
SharpEmu · Windows
- Original status
- ingame
- Reported date
- 2026-10-06
- Build / version
- a17aaca(main)
- Game version
- 1.018
- Reported hardware
- 5800X3D/4070S
- Platform scope
- Named on the individual report
Reach in gameplay, performance heavy.
prosper · Linux
- Original status
- in-progress
- Reported date
- 2026-10-12
- Build / version
- Not supplied in the copied fields; check the original report
- Game version
- Not supplied in the source table
- Reported hardware
- Not supplied in the source table
- Platform scope
- The source file describes this OS; it is not a per-title OS test
Opening sequence and title screen
AnyPS5 · Windows
- Original status
- community
- Reported date
- Not supplied in this row
- Build / version
- Not supplied in the copied fields; check the original report
- Game version
- Not supplied in the source table
- Reported hardware
- Not supplied in the source table
- Platform scope
- Named on the individual report
No observation excerpt was preserved for this row.
AnyPS5 · Linux
- Original status
- community
- Reported date
- Not supplied in this row
- Build / version
- Not supplied in the copied fields; check the original report
- Game version
- Not supplied in the source table
- Reported hardware
- Not supplied in the source table
- Platform scope
- Named on the individual report
No observation excerpt was preserved for this row.
What is still missing
3 result rows have no identifiable build in the copied fields or excerpt. Hardware and game versions are shown only where the source table supplies them; a value mentioned by one reporter belongs to that setup only. This site did not rerun these sessions. For reproduction, open the original report and match the emulator commit, game title ID/version, CPU/GPU, driver and OS before comparing outcomes.
In game means a cited report got past menus into gameplay on a named setup. It is not a promise for your GPU, and it is not the official Playable mark.
Freezes mean the index is not claiming a stable session. Discussion 357 is the upstream thread to read. This page does not turn that thread into a Playable row.