Skate 3 browser controls: every key and input

Keyboard to Xbox 360 pad

This is the complete keyboard map, read from the Skate 3 browser port's own key table. The left column is what the game receives — the Skate 3 browser port builds a virtual Xbox 360 pad each frame and hands that to the engine, so the game never sees a keyboard at all. That is also why the mapping is worth learning as a controller layout rather than as a list of shortcuts.

Gamepads, and why they feel better

A pad is a genuine upgrade here, for one specific reason: the right stick becomes an analogue FlickIt stick. A flick gesture needs a direction and a release, not just a direction, so a real stick reproduces the console input exactly, whereas the arrow keys quantise it to four directions. Everything still works on keys — it is simply less forgiving on diagonal flicks.

The engine behind the port supports Xbox and XInput pads, PlayStation pads, Switch pads and generic HID controllers, with XInput kept as a fallback on Windows. What the browser recognises as a gamepad is what the port receives.

If a pad does nothing, the cause is usually the browser rather than the pad. Press a button once the game screen is up so the browser opens its gamepad connection. There is one deliberate quirk worth knowing: a button that was already held down before a screen appeared does not count as your press, so if the menu will not accept input, let go and press again.

Trackpad Mode

The Skate 3 browser port has a second analogue stick you may not know about. Under the pause menu, PLAYER, sits Trackpad Mode, which turns mouse or trackpad movement into the right stick. It is the closest a keyboard session gets to stick feel.

How it works in practice:

1. Click once on the game area to lock the pointer, so long strokes never run into the edge of the screen.
2. Move the mouse or trackpad down, then quickly back up. That single stroke reads as the pull-back-and-flick the FlickIt gestures expect.
3. Stop moving and the virtual stick springs back to centre, so the next gesture starts from neutral.

There are four sensitivity steps, from off to quite fast. If ollies are not registering, the usual cause is a stroke that is too slow for the spring-back, not a broken setting — try a shorter, sharper flick, or move up a sensitivity step.

Touch controls

On a touch screen the Skate 3 browser port draws an on-screen controller, and it feeds exactly the same virtual pad the keyboard uses, so nothing about the game changes. The left stick steers and crouches; the right pad is the FlickIt stick and springs back when you lift your finger, which is what makes the down-then-up gesture work with a thumb.

One practical note: a flick needs room for both halves of the gesture. Starting a pull right at the edge of the right stick area leaves nowhere to snap back to, so keep strokes centred in the ring. Phones also benefit from landscape orientation, which moves the browser chrome out of the way.

Keys nobody documents

The Skate 3 browser port ships a few bindings that never appear in its control help:

• F8 — a debug camera.
• T — drop your skater at the debug camera's position. Useful for getting to a spot without skating there.
• F1 / F2 — yes and no in a multiplayer kick vote. The port claims these two keys from the browser specifically so the browser's own F1 help does not steal them mid-session.
• Enter — confirm, the same as Space in menus.

When keys seem dead

The most common "the controls are broken" report has nothing to do with the mapping. Until the game canvas has focus, your keystrokes go to the page and scroll it instead. Click once inside the game area and the keys start reaching the skater.

The Skate 3 browser port also clears every held key when the window loses focus, which is why alt-tabbing away and back can leave you apparently stuck mid-gesture: nothing is held any more, so release everything and start the trick again.