Stream setup and troubleshooting

Host Poco Loco in its web game window or a supported desktop build, then capture that window in your broadcast software. The host device renders and runs the race. Viewers join from supported stream chat and do not need to run the race renderer themselves.

Prepare the host device

Use an internet-connected desktop or laptop with a browser/device capable of WebGL 2. The supported desktop app uses the same Poco Loco service and signs in through your system browser. Start with the download page for the currently available builds; do not assume an unsupported operating system has a download.

A phone can be used for provider chat and supported viewer surfaces. That does not establish phone hosting or track-authoring capability. For your first stream, use a host device with a keyboard and pointer, test its renderer, and verify the broadcast capture before going live.

Capture the game in OBS

Open Poco Loco and add Window Capture in OBS for the game window. In the desktop app, the operating system keeps one window titled Poco Loco across Arena/Grid/Race/Finish, so the source does not need to switch targets between these screens. In the web version, capture the browser window containing the game.

Resize the game window and fit the source to your scene. Preview Grid, a moving race, and Finish, checking both picture and the audio routing you selected in OBS. A URL added as an OBS Browser Source is not a substitute for an authenticated game window that actually runs your session. Check fullscreen separately before using it live.

Complete provider sign-in

Use Login with Twitch or Login with Kick for the channel you intend to host. Desktop authentication opens your system browser; finish the flow and return to the app. Check that the intended provider/channel is connected and enabled for the session.

If a login or callback fails, retry from the game's sign-in entry and read the visible error. Do not paste tokens into chat or share a credential-bearing callback link. Linking both providers does not merge their interaction capabilities: Twitch Companion/Bits and Kick chat actions have separate contracts.

Recover a blank canvas or WebGL failure

WebGL not supported means the browser could not create the WebGL 2 context used to draw the track and vehicles. Keep your browser and graphics drivers current, check hardware acceleration, and try another supported browser or the supported desktop app on the same capable device. Device policy or graphics limitations may still prevent rendering.

Close unnecessary graphics-heavy tabs or applications and retry the game. If a context is lost or an asset fails to load, use the visible recovery/retry and preserve any visible error for support. A readable guide page proves the documentation loads, not that your device can render a race.

Find missing participants

Keep Grid open and verify that viewers send commands in the enabled channel. Twitch Grid shows !vamos and !race; Kick accepts join, race, or vamos. Viewers need an identified provider account, and capacity is 125 racers.

Joining closes when the race starts. No action can add a late entrant to that running race. A local test/fill control can demonstrate cars, but it does not verify a live provider connection. Use a real viewer join in the intended channel as your setup check.

Check unavailable actions and saved results

Boost needs a running race and your entered racer. Free allowances can be exhausted, and paid Twitch actions can be pending or unavailable. Check the controls guide before troubleshooting an expected disabled state as a connection problem.

Wait for the results submission to complete at the finish. If Result submission failed appears, the visible race finish is not proof of a saved server result. Use the retry offered by the game. A cancelled session and a Builder test are different from a completed hosted race.

Ask for help with useful evidence

Use Support for an unresolved setup, provider, payment, or rendering issue. Include the game surface, web/desktop, your operating system/browser, what you tried, the public/session link if appropriate, and the exact visible error. A screenshot of the error or OBS preview can help explain a capture problem.

Do not send passwords, tokens, private draft data belonging to someone else, or payment credentials. The expected setup result is a captured game window, a real viewer on Grid, a moving race, and saved results shown at Finish.