Troubleshooting – Chiaki-ng

Fix ‘Console Available But Session Fails to Start’ in Chiaki-ng

Admin — Thu, 15 Oct 2026 01:31:12 +0000

If your console appears in chiaki-ng but the session dies the moment you connect — or registration keeps failing — the cause is usually a stale PIN, a discovery problem, or outdated console firmware. Newer builds fixed several of these edge cases (including sessions failing while waiting for the login PIN), so updating to v1.10.0 is step zero. The checklist below covers the rest.

Step 0: Update Everything

Chiaki-ng → v1.10.0. Recent v1.9.x builds fixed real session-start bugs: consoles that became available right after clicking but never started a session, and sessions failing while waiting for the login PIN. If you are on an older build, update before changing anything else — downloads on GitHub.
Console firmware → latest. PS5: Settings → System → System Software Update. PS4: Settings → System Software Update. Firmware updates regularly fix Remote Play handshake issues.

Step 1: Fix Registration (PIN Problems)

Generate a fresh PIN on the console.
PS5: Settings → System → Remote Play → Link Device. PS4: Settings → Remote Play Connection Settings → Add Device. PINs expire quickly — enter it in chiaki-ng immediately.
Or skip the PIN entirely.
Since v1.9.4, chiaki-ng supports automatic pinless registration for locally discovered consoles. On your home network, just double-click the discovered console and register without a PIN.
Double-check your PSN Account ID.
It must be the Base64-encoded Account ID (fetch it via the in-app PlayStation login added in v1.6.0), not your username or email. A wrong ID fails registration silently.

Step 2: Fix Discovery (Console Visible, Session Dies)

Enter the console’s IP manually. In the registration dialog, type the console’s local IP address (find it in the console’s network settings) instead of relying on auto-discovery.
Same subnet, no VPN. Both devices must be on the same local network branch; disable VPNs on the streaming device and turn off router AP/client isolation.
Restart chiaki-ng after registering. Since v1.9.x, PSN-registered hosts appear immediately — but if a console was registered long ago on an old version, re-registering fresh clears stale entries.

Step 3: Remote (Away-from-Home) Session Failures

If sessions start at home but fail remotely, the issue is the internet path, not registration: complete the
Remote Play over the internet setup (PSN registration + NAT/port forwarding 9295–9297). Carrier-grade NAT on some mobile networks cannot be punched through by any settings.

Frequently Asked Questions

Why does chiaki-ng show my console as available but the session fails to start?

This exact bug was fixed in recent v1.9.x builds (consoles becoming available right after clicking, sessions dying while waiting for the login PIN). Update to v1.10.0 first. If it persists, update console firmware, then try manual IP entry in the registration dialog.

My 8-digit PIN is always rejected. What am I doing wrong?

PINs expire within minutes — generate a fresh one on the console and enter it immediately. Or skip PINs entirely: v1.9.4+ supports automatic pinless registration for locally discovered consoles on your home network.

Do I need the PSN Account ID or my PSN password to register?

The Account ID — a Base64-encoded token, not your password or username. Get it through the in-app PlayStation login (v1.6.0+) or the open-source lookup script. Entering your username instead of the Account ID is a common silent-failure cause.

Session works at home but not when I'm away. Is registration broken?

Registration is fine — the internet path is the problem. You need PSN-based registration plus a working NAT/port path (see our remote-over-internet guide). Some mobile carriers use carrier-grade NAT that no client setting can traverse.

Chiaki-ng.com is an independent, unofficial resource site. Chiaki-ng is free and open-source software (GNU AGPLv3) built by its community contributors. This site is not affiliated with, endorsed by, or connected to Sony Interactive Entertainment.

Fix Black Screen / No Video in Chiaki-ng

Admin — Thu, 15 Oct 2026 01:31:03 +0000

A black screen in chiaki-ng — audio playing but no picture, or nothing rendering at all — is almost always a renderer or GPU driver issue. Since v1.10.0 added an OpenGL backend alongside Vulkan, the fastest fix is usually a 30-second renderer switch in Settings → Video → Render. If that doesn’t work, the checklist below covers drivers, Vulkan support, and HDR edge cases.

Fix 1: Switch the Renderer (Works Most of the Time)

Open Settings → Video → Render in chiaki-ng.
Switch to the other backend — if you are on Vulkan, try OpenGL, and vice versa. The OpenGL renderer was added in v1.10.0 specifically to resolve rendering failures on configurations where Vulkan misbehaves.
Restart chiaki-ng and reconnect. Renderer changes sometimes need a fresh session to take full effect.

Fix 2: Update GPU Drivers & Verify Vulkan 1.2+

Chiaki-ng requires a GPU with Vulkan 1.2 or higher driver support. Black screens on older or misconfigured systems usually mean the driver can’t initialize the video pipeline:

Windows: update drivers from NVIDIA / AMD / Intel directly — not just Windows Update, which often lags months behind.
Linux: install your distro’s Vulkan packages (e.g. libvulkan1 plus the Mesa or proprietary driver Vulkan component) and libva for the AppImage build.
macOS: keep macOS updated; Apple ships the graphics stack with the OS.

Fix 3: HDR-Related Black Screens

If the black screen only happens with HDR enabled, try disabling HDR in chiaki-ng’s video settings first to isolate it.
On Windows with AMD graphics, v1.9.9+ enabled zero-copy HDR decoding via the Vulkan path — if HDR broke after an update, try the OpenGL renderer as a workaround and check for newer GPU drivers.
Mismatched display HDR settings (Windows HD Color on, but the game outputting SDR, or vice versa) can also produce a black frame — align them.

Fix 4: Resolution / Bitrate Combination

An extremely high resolution + bitrate on a weak GPU can fail to initialize the decoder, presenting as a black screen. Drop to 720p / 8 Mbps as a test — if video appears, raise settings back up gradually to find your GPU’s stable ceiling.

Frequently Asked Questions

Why is my chiaki-ng screen black but I can hear the game?

The video renderer failed while the audio path works fine. Switch renderers in Settings → Video → Render (Vulkan ↔ OpenGL, added in v1.10.0) — this resolves the large majority of black-screen cases.

Does chiaki-ng need a dedicated GPU?

No, but your GPU or integrated graphics must support Vulkan 1.2 or higher with current drivers. Very old integrated graphics that lack Vulkan support cannot initialize chiaki-ng’s video pipeline at all.

Black screen only when HDR is on — how do I fix it?

Disable HDR in chiaki-ng’s video settings to confirm HDR is the trigger. Then update your GPU drivers (AMD zero-copy HDR decoding changed in recent builds) and align Windows/macOS display HDR settings with the game output.

Chiaki-ng shows a black screen on Linux but works on Windows. Why?

Almost certainly a missing Vulkan driver component or libva on the Linux side. Install your distro’s Vulkan packages and libva (required for the AppImage), and make sure PipeWire is running.

Fix Controller Problems in Chiaki-ng (DualSense Haptics, Mapping)

Admin — Thu, 15 Oct 2026 01:30:56 +0000

Most chiaki-ng controller problems are Bluetooth quirks or mapping settings, not broken hardware. The classic symptom — a DualSense that connects but loses haptics and rumble — usually means it paired while low on battery, or PipeWire isn’t running on Linux. Work through the fixes below by symptom; chiaki-ng’s controller mapping database (greatly expanded in v1.9.x) covers far more gamepads than the official client.

DualSense Loses Haptics / Rumble

Charge the controller first. A known issue: connecting a DualSense while it is low on battery can silently drop haptic feedback. Charge it, then reconnect.
Prefer USB over Bluetooth for full features. Bluetooth mode works, but wired USB gives the most reliable haptics and adaptive triggers.
Linux: PipeWire must be running. DualSense haptic data travels through the PipeWire audio pipeline — without it, rumble is bypassed entirely (same requirement as game audio).
Tune intensity manually. Newer builds let you adjust true haptic intensity and adaptive trigger strength in the controller mapping panel, scaled to your console’s own settings.

Adaptive Triggers Feel Wrong or Delayed

v1.9.x builds fixed the Bluetooth-mode adaptive trigger delay and improved trigger accuracy against the console’s settings. If triggers feel off: update to v1.10.0, then re-check the trigger thresholds in the mapping panel — chiaki-ng can now fetch trigger parameters from the console profile automatically.

Third-Party Gamepad Won’t Map Correctly

Open the controller mapping panel in chiaki-ng and remap manually — the built-in database covers many more controllers than Sony’s official app, including Xbox, Switch Pro, and 8BitDo-style layouts.
For Nintendo-layout controllers, try the positional layout option (maps by button position instead of labels).
On Steam Deck desktop mode: holding the Options button toggles the Deck’s own controller mode, which can conflict with chiaki-ng’s input — make sure you are in the mode you intend.
Check for double-input: if both Steam Input and chiaki-ng try to handle the same controller, buttons may fire twice. Disable Steam Input for the chiaki-ng shortcut.

Motion Controls / Gyro Not Working

Gyro support needs a controller that actually has a gyroscope (DualSense, DualShock 4, Switch Pro) and a mapping that assigns it. v1.9.x improved motion controller reset detection — if gyro drifts or freezes, update to v1.10.0 and re-run the mapping wizard.

Related: troubleshooting hub ·
fix audio crackling (PipeWire affects haptics too) ·
upstream releases on GitHub

Shopping for a controller? See our best controllers for chiaki-ng & PS Remote Play — DualSense vs Xbox vs 8BitDo compared.

Frequently Asked Questions

Why did my DualSense lose vibration in chiaki-ng?

The two usual causes: it connected while low on battery (charge and reconnect), or PipeWire isn’t running on Linux (haptics travel through the PipeWire pipeline). On Windows/macOS, try USB instead of Bluetooth for the most reliable haptics.

Does chiaki-ng support adaptive triggers?

Yes — chiaki-ng supports DualSense adaptive triggers and haptic feedback, with intensity scaling matched to your console’s settings. Bluetooth-mode trigger delay was fixed in the v1.9.x builds, so update to v1.10.0 if triggers feel laggy.

Can I use an Xbox controller with chiaki-ng?

Yes. Chiaki-ng’s controller mapping database supports Xbox controllers and many third-party gamepads, with full button remapping. You won’t get DualSense-specific features (adaptive triggers, true haptics) on non-Sony hardware, but standard rumble and gyro (where the hardware has it) work.

Why are my buttons double-pressing in chiaki-ng on Steam Deck?

Steam Input is probably also handling the controller. Right-click the chiaki-ng shortcut in Steam → Controller settings → disable Steam Input for that shortcut, so only chiaki-ng processes the input.

How do I remap buttons in chiaki-ng?

Open the controller mapping panel in chiaki-ng’s settings, select your controller, and assign each function manually. For Nintendo-layout controllers, the positional layout option maps by physical button position instead of labels.

Fix Lag & Input Delay in Chiaki-ng Remote Play

Admin — Thu, 15 Oct 2026 01:30:48 +0000

Lag in chiaki-ng is almost always your network, not the app. Remote Play streams raw video frames over UDP, so every millisecond of network delay becomes input delay you can feel. The fixes that matter most are physical: wire your PS5 to the router, get the streaming device off crowded 2.4GHz Wi-Fi, and then tune bitrate and renderer settings to match what your network can actually sustain.

Fix 1: Wire Your PS5/PS4 to the Router (Biggest Single Win)

A console on Wi-Fi halves your available airtime and adds jitter in both directions. A Cat5e or better Ethernet cable from console to router removes the largest source of latency and packet loss in the whole chain. If the router is in another room, this one change is worth more than every setting tweak below combined.

Fix 2: Get the Streaming Device on Clean Wi-Fi

Use a dedicated 5GHz or Wi-Fi 6 (802.11ax) band for the device running chiaki-ng — never 2.4GHz if you can avoid it.
In your router’s wireless settings, switch to a less crowded channel (Wi-Fi analyzer apps on your phone show which channels neighbors use).
Keep the streaming device reasonably close to the router; every wall between them costs latency.
Turn off bandwidth hogs during play: 4K video streaming, large downloads, cloud backups on the same network.

Fix 3: Lower the Bitrate to What Your Network Sustains

Chiaki-ng’s bitrate slider moves in 1 Mbps increments and defaults to 15,000 Kbps (matching Sony’s official app). If your network cannot sustain the current bitrate, frames queue up and you feel it as input lag and stuttering.

Open Settings → Video and note your current resolution and bitrate.
Drop the bitrate in 2–3 Mbps steps and play for a minute after each change. Stop when motion stays smooth.
Or drop the resolution first (e.g. 1080p → 720p): lower resolutions need far less bitrate for the same smoothness, and on a phone or Deck screen the difference is small.

Fix 4: Switch the Renderer (Vulkan ↔ OpenGL)

Since v1.10.0, chiaki-ng ships an OpenGL renderer backend alongside Vulkan. On some GPUs and drivers, one path delivers frames noticeably faster than the other:

Go to Settings → Video → Render and try the alternative renderer.
Enable VSync there if you see tearing; disable it if you suspect it adds latency on your setup — test both.
Spatial upscaler presets (also under Video → Render) can sharpen a lower-resolution stream; try them on versus off and keep whichever feels more responsive.
Make sure your GPU drivers are current — chiaki-ng needs Vulkan 1.2+ support, and outdated drivers are a classic cause of frame pacing problems.

Fix 5: Let the Adaptive Queue Do Its Job

v1.10.0 introduced adaptive queue depth management and congestion control that smooths frame delivery automatically. If you upgraded from an old version and carried settings over, reset video settings to defaults once so the new queueing logic starts from a clean baseline.

Playing away from home? Different rules apply — see
Remote Play over the internet. Also related:
troubleshooting hub ·
fix audio crackling ·
fix black screen

Hardware still the bottleneck? The biggest latency wins are hardware, not settings — see our router & network gear picks for PS Remote Play.

Frequently Asked Questions

What is the best bitrate setting for chiaki-ng?

The default 15,000 Kbps matches Sony’s official app and suits most home networks. If you feel input lag or see stuttering, lower it in 1–3 Mbps steps until motion is smooth — a stable lower bitrate always feels better than an unstable higher one.

Should I use Vulkan or OpenGL in chiaki-ng?

Try both: go to Settings → Video → Render. Since v1.10.0 both backends are available, and on some GPUs/drivers one delivers frames with noticeably less latency than the other. There is no universally faster option.

Why is remote play laggy even though my internet is fast?

Remote Play quality depends on your local network and latency, not your internet download speed. A 1000 Mbps plan means nothing if your PS5 is on congested 2.4GHz Wi-Fi two rooms from the router. Wire the console, clean up the Wi-Fi, then tune settings.

Does lowering resolution reduce input lag?

Yes, indirectly: lower resolutions need less bitrate, so frames spend less time in network queues. If your network is the bottleneck, dropping 1080p → 720p often removes more perceived lag than any other single setting.

My stream was smooth and suddenly stutters every few seconds. What happened?

Periodic stutter is usually another device or app saturating the network (cloud backup, 4K streaming, large download) or the router switching Wi-Fi channels. Check what else is active on your network before changing chiaki-ng settings.

Fix Audio Crackling & Stuttering in Chiaki-ng

Admin — Thu, 15 Oct 2026 01:30:40 +0000

Audio crackling or stuttering in chiaki-ng is usually a network or buffer problem, not a broken app. The three common causes are Wi-Fi interference, an audio buffer set too small for your connection, and — on Linux — a missing or misconfigured PipeWire setup. Work through the fixes below in order; most people solve it in under five minutes.

Cause 1: Wi-Fi Interference (Most Common)

Remote Play audio rides on the same UDP stream as video. When packets arrive late or out of order, you hear it as popping and crackling first.

Switch the streaming device to a 5GHz Wi-Fi band (or Wi-Fi 6) — 2.4GHz bands in apartment buildings are congested.
Better: connect the device running chiaki-ng via Ethernet, and always wire your PS5/PS4 to the router with a cable.
In your router settings, try a less crowded Wi-Fi channel (1, 6, or 11 on 2.4GHz; any clean channel on 5GHz).

Cause 2: Audio Buffer Too Small

Chiaki-ng lets you tune the audio buffer directly. A buffer that is too small for a jittery connection produces exactly the crackling you hear.

Open Settings → Audio in chiaki-ng.
Raise the audio size buffer slider — it adjusts in 10ms increments. Increase it in a few steps and test after each change.
Trade-off to know: a larger buffer smooths out crackling but adds a small amount of audio latency. Find the lowest setting that stays clean.

Cause 3: Linux Audio Stack (PipeWire)

On Linux, chiaki-ng’s audio path — and DualSense haptics — depend on PipeWire. If your distribution still runs plain PulseAudio, audio can stutter or cut out.

Install and enable PipeWire on your distribution (most modern distros ship it by default now). The Flatpak and AppImage builds both expect it.
Emergency fallback: if you cannot switch to PipeWire, launch the Flatpak with
flatpak run –env=SDL_AUDIODRIVER=pulse io.github.streetpea.Chiaki4deck

This routes audio through PulseAudio — but be aware DualSense haptic feedback will stop working in this mode.

v1.10.0 reworked the audio path (plus microphone and haptics) for better packet recovery. If you are on an older build, update first — your crackling may already be fixed upstream.

Frequently Asked Questions

Why does chiaki-ng audio crackle but video looks fine?

Audio is more sensitive to packet jitter than video. Your connection is dropping or delaying audio packets while video frames still arrive on time. Fix the network first (5GHz/Ethernet), then raise the audio buffer slider in Settings → Audio in 10ms steps.

What is the best audio buffer setting in chiaki-ng?

There is no universal best value — it depends on your network jitter. Start from the default and raise it in 10ms increments until the crackling stops, then stop. Going higher than necessary only adds audio latency.

Does the Flatpak PulseAudio fallback break anything else?

Yes: running with –env=SDL_AUDIODRIVER=pulse disables DualSense haptic feedback entirely. Use it only as a temporary workaround on systems where PipeWire cannot be installed.

My microphone doesn't work in chiaki-ng on Linux. Is it related?

Often yes — both go through the same audio stack. The v1.10.0 release reworked microphone capture alongside the audio and haptics paths, so update first, then confirm PipeWire is running and the correct input device is selected in Settings → Audio.

Audio was fine yesterday and crackles today. What changed?

Check for a router reboot that moved you to a crowded Wi-Fi channel, a console firmware update, or another device saturating your network (large downloads, 4K streaming). Re-run the Wi-Fi checks above before changing chiaki-ng settings.