READY TO EXPLORE
ASTRONEER
A solar system of possibilities.
Your next expedition starts here.
KytyPS5 · Vulkan · HTML5 viewer
01 / EXPEDITION
ORBIT / LIBRARY
Local connectionLOCAL
MAKE ROOM FOR PLAY
Your library.
One place for your worlds. Ready when you are.
/mnt/unas_plex/PS5Fixed libraryAll games 0
FROM ARCHIVE TO ADVENTURE
Game extraction
Prepare PKGs and RAR sets from your fixed library. Jobs run one at a time and continue when you close the browser.
Checking local space…Original files stay on the NAS · Prepared games use local storage
Extraction log
The library stays on your NAS. Prepared runtimes, saves and profiles stay on this machine.
YOUR LIVE SESSION
Now playing.
Choose a game from your library to begin.
At your fingertips
Keyboard → controllerW A S DMove
T F G HCamera
JCross / confirm
LCircle / back
I / KTriangle / square
EnterOptions
Q / EL1 / R1
Z / CL2 / R2
↑ ↓ ← →D-pad
Shift / CtrlL3 / R3
SESSION PROFILE
Command line session
Settings appear when a game starts.
Explore game profiles ↗Viewer size controls the stream canvas. The game may render internally at a higher resolution.
FIND YOUR SWEET SPOT
Game profiles.
Keep the settings that work. Give experiments their own space.
Profile settings
UntestedRecord a test observation
Run this custom profile first, then record the milestone you reached.
MEASURE. COMPARE. REFINE.
Benchmarks.
A clearer picture of how your session runs.
Record a session · Goal 1080p60
ReadyEvery game targets 1920 × 1080 at 60 FPS: 16.67 ms per game frame. Launch a game, settle into a repeatable scene, then record. Each run saves the game version, active profile and build.
Know what you're measuring.
Emulator CPU and RAM belong to the game process. Host CPU and CPU pressure reveal competing work. GPU, VRAM and power include other applications.
Standard recordings collect host telemetry and leave gameplay performance unverified. Native frame measurements and approximate overlay snapshots are labeled separately in run history. A 60 FPS stream or client bandwidth test does not establish 60 FPS gameplay.
GPU activity
GPU 0 · last 90 samples100%50%0%
Run history
| Scene / profile | State | Game timing | CPU avg | Host CPU | GPU avg | Peak RAM | Samples | Export |
|---|
For meaningful comparisons, repeat the same scene, duration and cache conditions. CPU 100% = one core. Exports include raw samples.
INPUT, VERIFIED ON THE HOST
Controller lab.
See what Linux receives from the browser or Mac client.
ISOLATED TEST SESSION
Test input goes to a separate Linux receiver. Your game keeps running independently.
Make every input visible.
Start a test session, then connect here or from the Mac client.
HOST EVENTS
0
CONNECTED VIEWERS
0
LAST HOST RECEIPT
—
KEYS HELD
0
Expected controller state
DEFAULT KYTY MAPPINGDerived from keys received by the Linux test window. This is not a readback from the game. Stick values are digital; mouse movement is shown separately.
Raw host input
WaitingKeys
NoneUnmappedNoneMouse position0, 0Mouse delta0, 0Mouse buttonsNoneWheel total0, 0No clients connected.
Connect the Mac client
Client handoff ↗Use the same RFB transport as the game viewer, with the test stream endpoint. Read the shared telemetry from any device to verify delivery.
Test video + input
The copied stream URL includes the current connection token. The handoff explains startup, press/release events, polling, and mapping checks. Audio integration guide ↗
Received event trace
Recorded by the Linux receiver, including short taps. Export retains the latest 1,000 events. Clearing this view leaves the server trace intact.
| Seq | Host time | Event | Received data |
|---|---|---|---|
| Waiting for host input. | |||
EVERY MILESTONE COUNTS
Achievements.
Your games’ trophies, read directly from their local files.
Choose an extracted game.
Export JSON ↗BEHIND THE SCENES
Your system.
Local files. Local compute. A little visibility into both.
Current session log
LAST 24 KBNo session log loaded.