Nitro-Fueled PC controls and settings
Updated · Checked against GetLostIn v0.4, OCTR v0.5.4
GetLostIn v0.4 supports keyboard bindings and SDL gamepads. Mouse camera control is not supported in this build; use the arrow keys for the right stick or a controller. The tables below use the GetLostIn v0.4 Windows launcher and a fresh portable preset.
Default keyboard controls
Match the PS4 button symbol shown in the game to its keyboard input. These names describe the input sent to the game, so they work with the control scheme you select in the game.
| PS4 input | Keyboard | Gamepad |
|---|---|---|
| Left stick | W / A / S / D | Left stick |
| Right stick | Arrow keys | Right stick |
| Cross | Space | South face button, A / Cross |
| Circle | Left Shift | East face button, B / Circle |
| Square | E | West face button, X / Square |
| Triangle | Q | North face button, Y / Triangle |
| L1 / R1 | 1 / 3 | Left / right shoulder |
| L2 / R2 | R / F | Left / right trigger |
| L3 / R3 | Z / C | Left / right stick click |
| Options | Enter | Start / Options |
| Touchpad | Tab | Back / Select or touchpad click |
| Touchpad right | Backspace | Unbound by default |
| D-pad up / down / left / right | I / K / J / L | D-pad |
| Runtime menu | Insert | L3 + R3 |
| PS4 input | Keyboard |
|---|---|
| Left stick | W / A / S / D |
| Right stick | Arrow keys |
| Cross | Space |
| Circle | Left Shift |
| Square | E |
| Triangle | Q |
| L1 / R1 | 1 / 3 |
| L2 / R2 | R / F |
| L3 / R3 | Z / C |
| Options | Enter |
| Touchpad | Tab |
| Touchpad right | Backspace |
| D-pad up / down / left / right | I / K / J / L |
| Runtime menu | Insert |
| PS4 input | Gamepad |
|---|---|
| Left stick | Left stick |
| Right stick | Right stick |
| Cross | South face button, A / Cross |
| Circle | East face button, B / Circle |
| Square | West face button, X / Square |
| Triangle | North face button, Y / Triangle |
| L1 / R1 | Left / right shoulder |
| L2 / R2 | Left / right trigger |
| L3 / R3 | Left / right stick click |
| Options | Start / Options |
| Touchpad | Back / Select or touchpad click |
| Touchpad right | Unbound by default |
| D-pad up / down / left / right | D-pad |
| Runtime menu | L3 + R3 |
Use Controls → Keyboard to change these bindings. The runtime menu is separate from the game's own pause menu.
Rebind keys and controllers
Set your inputs before starting a new session.
- Close the game.
- Open the launcher's Controls tab.
- Select Keyboard and find the row for the input you want to change.
- To replace an existing custom binding, press Clear in that row first.
- Press Change, then press the new key. Use Escape to cancel capture.
- Check the displayed binding. Change replaces a default binding, but adds another key to an existing custom binding; an input holds up to four keys. Default restores that input's original binding.
- Return to Play and start the game.
Bindings are stored as key.<input>= entries in bbport.ini. For a gamepad, use the Controls tab's device list and live test, find the game-input row, press its Change button, then press the gamepad button.
Player 1 can stay on automatic selection, which follows the last gamepad used. Assign controllers explicitly to players 2–4 for split-screen. Stick dead-zone defaults are inner 5 and outer 127; increase the inner value if a stick drifts at rest.
Settings: display and rendering
Open Settings → Display. Start with the ordinary 16:9 output and change one setting at a time.
| Setting | Options | Default | What it does |
|---|---|---|---|
| SettingAspect / output | Options16:9: 720p, 1080p, 1440p, 4K; 21:9: 2560×1080, 3440×1440; 32:9: 5120×1440 | Default16:9 1920×1080 | What it doesSelects the output layout; ultrawide turns upscaling off and caps internal resolution at 1440p |
| SettingInternal resolution | Options480p, 720p, 1080p, 1440p, 1620p, 2160p | Default1080p | What it doesChanges the game's 3D rendering resolution; restart after changing it |
| SettingUpscaling | OptionsOff, FSR 1, FSR 3, FSR 4, DLSS | DefaultFSR 1 | What it doesEnlarges or reconstructs the image; temporal modes are experimental |
| SettingDLSS quality | OptionsAuto, DLAA, Quality, Balanced, Performance, Ultra Performance | DefaultAuto | What it doesAuto follows internal resolution; other modes use the selected DLSS output after restart |
| SettingDLSS output | Options1080p, 4K | Default1080p | What it doesSets the target for DLSS quality modes |
| SettingDLSS model | OptionsTransformer, CNN | DefaultTransformer | What it doesSelects the DLSS model; requires an RTX GPU |
| SettingFSR 3 sharpness | Options0–1 | Default0.30 | What it doesAdjusts sharpening |
| SettingGame MSAA (2x) | OptionsOn, off | DefaultOff | What it doesLeave off for the dotted-sky/light-shaft fix; restart after changing it |
| SettingFullscreen | OptionsOn, off | DefaultOff | What it doesChanges window mode |
| SettingFPS counter | OptionsOn, off | DefaultOff | What it doesDisplays the frame counter |
| SettingMonitor | OptionsAvailable monitors | DefaultPrimary | What it doesChooses the display |
| SettingPresentation | OptionsMailbox, Fifo, FifoRelaxed, Immediate | DefaultMailbox | What it doesSelects frame presentation; Fifo uses vertical synchronization |
| SettingFrame generation | OptionsOff, FSR 3 | DefaultOff | What it doesAdds interpolated display frames; game timing and the game FPS limit stay the same |
| SettingFrame-generation motion | OptionsFlow, game | DefaultFlow | What it doesChooses the motion information used for generated frames |
For FSR 4, the GPU needs the required INT8 operations. For visible trails or flicker with FSR 3/4 or DLSS, return to FSR 1 or Off. Frame generation uses 8-bit frames and works best on a 120 Hz or faster display.
Before choosing ultrawide on GetLostIn v0.4, reach the menu once at 16:9 and exit normally to save the shader cache. Preparation can need about 9 GB of space. In OCTR v0.5.4, its corrected ultrawide layouts run offline; online starts at 16:9.
Settings: frame rate and patches
The Settings tab's frame-rate controls and the Patches tab change different parts of the setup.
| Setting | Options | Default | What it does |
|---|---|---|---|
| SettingFPS limit | Options0, 30, 60, 72, 90, 120, 144, 240 | Default60 | What it doesCaps game frames; 0 removes the cap |
| SettingCompile shaders in background | OptionsOn, off | DefaultOff | What it doesExperimental: reduces some first-use stalls, with effects potentially appearing a frame later |
| Setting60 FPS patch | OptionsOn, off | DefaultOn in the portable preset | What it doesChanges the game patch; restart for patch changes |
| SettingNo motion blur patch | OptionsOn, off | DefaultOn in the portable preset | What it doesChanges the game's blur patch; restart for patch changes |
Start at the 60 FPS preset. If frame pacing is poor, keep the cap and display mode consistent before adding frame generation. A 240 option in the list is a limit you can choose, rather than a speed every computer will reach.
Other launcher tabs
Keep the tab names in mind when following an older tutorial.
| Tab | Use |
|---|---|
| TabPlay | UseSelect and prepare existing game files, then start |
| TabSettings | UseFrame rate, display, console/language and related options |
| TabControls | UseTest devices, assign players and change keyboard/gamepad bindings |
| TabAchievements | UseView trophy progress and dates |
| TabPatches | UseSelect available game patches |
| TabSaves | UseBack up or import your own saves |
| TabDLC | UseManage optional add-ons you already own |
| TabTools | UseRuntime tools and maintenance actions |
Game language is under Settings → Console. CUSA13795 offers English, Latin American Spanish, French and Brazilian Portuguese; CUSA14876 offers English, Spanish, French, German, Italian and Arabic.
OCTR's Windows launcher adds an Online tab for its community server and nickname. Use its v0.5.4 release instructions for those options.
When input does not respond
Open the Controls tab's live test first. If it does not show the device, check the controller selection before changing game bindings. If the test responds but player 2 does not, assign that controller to player 2 explicitly.
Use Insert or L3+R3 for the runtime menu. For an input problem that persists, record the runtime version, controller and assigned player, then follow Report a problem.