Everything you can change while you play is in Longshot’s in-game menu: graphics, sound, gameplay and controls. Pick a
starting point below, then look up any single setting in the list.
Open the menu
Input
Open or close the menu
Move around it
Keyboard
F1, Insert or Esc
Q and E (or Tab and Shift+Tab) switch tabs, the arrow keys choose and change, Enter changes too, Esc goes back
Controller
Home, or Select and Start together (or click the touchpad on a DualShock 4 or DualSense)
LB and RB (or the triggers) switch tabs, the D-pad chooses and changes, A changes and opens a page, B goes back
Mouse
Click a tab or a row’s name, click the left or right half of a value to lower or raise it, drag a slider, turn the wheel to scroll, right-click to go back
F1 always opens the menu. Controls → Menu shortcut can take Esc or Insert off the
list; without Esc, it only lets the mouse go. A and B are the buttons your Layout preset puts the Switch’s
A and B on. Beside the rows, the help says what the row does and what the chosen value does.
UI-only example from main f1f2dc5b (nightly 680) on Linux. The Custom values shown are illustrative, not recommended defaults.
Your choices are saved as you go, in longshot_options.ini: in %APPDATA%\Longshot when the launcher starts the game
on Windows, so every version shares them, otherwise in the game folder (where the files go).
A setting marked After a restart applies the next time the game starts: when you close the menu it asks whether to
restart, with a list of what the restart applies (the settings changed, and the mods switched on the Mods tab).
Later keeps the change for next time (and is not asked again until you change one of those settings, or a mod); Restart now starts the game again, and you lose any progress
since your last save.
A row for something your PC can’t use is not shown: NVIDIA Reflex and AMD Anti-Lag 2 without a GPU and driver that have
them, the DLSS rows where DLSS doesn’t run, the HDR rows while HDR is off.
Good starting points
A first start uses the Auto (this PC) quality preset. It picks settings from your graphics card and its video memory,
then adjusts the render resolution during the first minute of play. If you change nothing, that is what you get. The
Output resolution starts at the game’s own 2560x1440, or at your screen’s size where that is smaller (a Steam Deck’s
1280x800, a 1080p monitor), in your screen’s shape: a 2560x1080 ultrawide starts at 2560x1080 and a 2256x1504 laptop at
2256x1504, pixel for pixel. 2048x1152, marked “(reduced)”, is the game’s own smaller picture, lighter on the GPU.
On supported Windows Vulkan setups, switching from 1280x720 to 1024x576 at 16:9 can preview the new Output resolution
in play. Set V-Sync to On, enable Threaded rendering (its change takes effect at the next launch), and set
Upscaler to Game’s own. Turn off HDR,
frame generation, and NVIDIA Reflex. If 1024x576 is missing from the list, type it in Custom output size.
Choose Yes within ten seconds to keep the change. No, Back, or letting the countdown finish restores the
previous resolution. Other mode changes apply after a restart.
Your PC
Quality preset
Upscaler and render resolution
Frame rate cap
Frame generation
Steam Deck, handheld, integrated GPU or a 4 to 6 GB card
Auto (this PC) picks Minimum (4GB); Low (6GB) on a 6 GB card
Game’s own, as the preset sets it, or AMD FSR 3.1 at Performance
60
Off
Most PCs (8 GB card)
Auto (this PC)
What Auto chooses: NVIDIA DLSS on an RTX card, AMD FSR 4 on an AMD RDNA 4 card (RX 9000) where the build has it, otherwise the game’s own
60
Off
A fast PC with a high-refresh monitor
High (12GB) or Ultra (16GB+)
DLSS or FSR 4 at Quality, or Native (DLAA or FSR 4 Native AA) for the sharpest picture
60
2x or Auto, up to your monitor’s refresh rate
Keep the frame rate cap at 60. Caps from 90 to 240 and Uncapped are experimental: some bosses and cutscenes
still count frames and can misbehave. For smoother motion, use frame generation instead.
Frame generation adds frames between the game’s own. Motion is smoother, but the game itself doesn’t run any
faster and input delay goes up a little. Auto matches your display’s refresh rate. NVIDIA Reflex and AMD
Anti-Lag 2 cut the added delay.
DLSS and DLAA look softer than the game’s own upscaler: set Sharpness to around 80% with them.
Ultrawide and 4:3: leave Aspect ratio on your monitor’s shape (the default). The 3D fills the screen while the
HUD keeps its 16:9 size with its corners at the screen’s edges (or in the middle, with HUD layout); movies stay in
the middle.
HDR: turn on HDR (Expanded or Native), then set HDR peak brightness to your monitor’s.
Every setting
Each row of the menu, in the menu’s order, with its choices and its default. Labels on a setting say when it applies:
after a restart, only on some GPUs or builds, only while HDR is on, or set for you by a quality preset.
91 settings.
No settings match. Try another term or clear the filters.
The picture's shape: your monitor's own (the default: wider on an ultrawide, narrower on 4:3 or 16:10), the game's 16:9, or another your screen has. The Output resolution lists that shape's sizes.
Choices and requirements
The shapes your screen’s resolutions have, narrowest first (5:4, 4:3, 16:10, 16:9, 21:9, 32:9, …), your monitor’s own marked “(monitor’s)” (after a restart)
The game's whole frame, HUD included, before it is scaled to the window. Docked only. On supported Windows setups, 1024x576 can be previewed from 1280x720. Other changes apply after a restart.
Choices and requirements
The Aspect ratio’s sizes: your screen’s resolutions and the common ones (1440p, 4K, 5K at 16:9; 1920x1200, 2560x1600 at 16:10; 3440x1440 at 21:9; …), and 2048x1152 (the game’s own reduced size, 80% of its 2560x1440, marked “(reduced)”) at 16:9; your screen’s own size is marked “(native)” (most changes apply after a restart)
Default 2560x1440, the game’s own picture, or your screen’s size where it is smaller (a Steam Deck’s 1280x800, a 1080p monitor), at its own shape (a 2560x1080 ultrawide starts at 2560x1080, a 2256x1504 laptop at 2256x1504); Auto (this PC) leaves it as it is
An Output resolution of your own, typed as width x height: your monitor's size, such as 3440x1440, 2560x1080 or 2560x1600. Each side is rounded down to a multiple of 8; a size the Output resolution offers is chosen there. Empty: none. Docked only.
Choices A size of your own, typed as <width>x<height> (most changes apply after a restart)
Game’s own, NVIDIA DLSS (only in builds with NVIDIA’s DLSS SDK, on NVIDIA RTX GPUs), AMD FSR 3.1 (every build, on GPUs it runs on), AMD FSR 4 (only in builds with FSR 4, on GPUs AMD’s files cover), Off (no upscaling), Intel XeSS (Windows, with Intel’s libxess.dll beside the game). NVIDIA DLAA, AMD FSR 4 Native AA and Intel XeSS Native AA are DLSS’s, FSR 4’s and XeSS’s Native, chosen on the Render resolution row
Default Game’s own; Auto (this PC) chooses DLSS or FSR 4 where they run, never XeSS
Which of NVIDIA's DLSS networks draws the picture.
Choices and requirements
Transformer (K) (CNN (E) in its place on cards with less than 7 GB of video memory), Transformer 2 (M), Transformer 2 (L), NVIDIA default, CNN (E), CNN (F) (shown where DLSS runs; used by DLSS and DLAA)
Where NVIDIA DLAA smooths the picture: after the game's bloom and tone map, or before them. Changes at once.
Choices and requirements
Off, On: where NVIDIA DLAA smooths the picture, after the game’s bloom and tone map or before them (shown with NVIDIA DLSS; changeable with Render resolution Native (DLAA) only; changes at once; RX_VK_DLSS_PRE_BLOOM over it for one run)
The share of the output the 3D is drawn at; the Upscaler fills in the rest.
Choices and requirements
Auto (the game’s own dynamic resolution), 100%, 75%, 67%, 50% (each with its size). With DLSS or FSR 4: Auto, Native (DLAA or FSR 4 Native AA: the 3D at full size), 92%, 83%, 75%, Quality (67%), Balanced (58%), Performance (50%), Ultra Performance (33%). With Intel XeSS the same stops, named by the XeSS mode each runs under: Native (XeSS Native AA), Ultra Quality Plus (92%, 83%), 75%, Ultra Quality (67%), Balanced (58%, 50%), Ultra Performance (33%). With FSR 3.1: Auto, 100% (its native AA), then the same as DLSS from 92%. With Off: Auto, 100%, 75%, 67%, 50%, 33%
Makes frames between the game's own, for smoother motion, at a little input delay. Fast motion or camera cuts can show artifacts. With NVIDIA DLSS Frame Generation it goes up to what NVIDIA's runtime makes on this GPU: 6x on an RTX 50, 2x on an RTX 40.
Choices and requirements
Off, Auto (it shows who makes its frames: FSR 3.1 FG or Built-in FG), 2x to 8x; with DLSS FG up to what NVIDIA’s runtime makes on the GPU (6x on an RTX 50, 2x on an RTX 40)
Who makes the frames at 2x and up. NVIDIA DLSS Frame Generation needs a temporal Upscaler (DLSS, DLAA or FSR) for the scene's depth and motion. Changes at once.
Choices and requirements
Shown while Frame generation is on. DLSS FG (NVIDIA DLSS Frame Generation: RTX 40 and newer, with a temporal Upscaler), FSR 3.1 FG (AMD FSR 3.1’s frame interpolation, from the scene’s depth and motion: any GPU), Built-in FG. DLSS FG is offered only where it runs; elsewhere the row has FSR 3.1 FG and Built-in FG, and its line at FSR 3.1 FG says why not DLSS FG (the log has NVIDIA’s answer). At DLSS FG, FSR 3.1 makes the frames DLSS FG does not (Frame generation’s Auto). At DLSS FG, the game’s own menus, movies and loading screens show only the game’s own frames (they have no Upscaler picture to make frames from): the row’s line and the FPS counter say DLSS FG paused. With an Upscaler that is not temporal, the built-in one makes the frames and the line says why. RX_VK_DLSS_FG=1 fixes the row at DLSS FG for a run. Changes at once
Default DLSS FG where it runs, else FSR 3.1 FG (an options file’s Auto from before is this default)
Limits frames rendered by the game. Generated frames are additional. Changes at once. Past 60 is experimental: the game keeps real time, but some cutscenes and bosses can misbehave (Gohma, the intro's narration). 60 is the safe choice. Uncapped: as fast as the PC can, still at real time; with V-Sync on, the display's refresh rate is the limit. 30 FPS always uses real-time game speed, even when Game speed is Per frame.
Choices 30, 60 (the console’s), 90, 120, 144, 165, 240, Uncapped (changes at once)
Choose the screen used by Fullscreen, F11 and Alt+Enter. Auto uses the window's current monitor.
Choices and requirements
Auto (current monitor), or a named connected screen. While windowed, chooses the next fullscreen destination; while fullscreen, moves the game. An unavailable choice is retained with a temporary fallback.
Filters the finished picture, including the game's HUD, after window effects. Longshot's menu and overlays stay clean. Changes at once; quality presets leave it alone.
Virtual CRT raster, not Render resolution. Capped at half the destination height (at least one line); width follows its aspect. Non-integer scaling can cause moire.
Choices 240, 480, 720 virtual lines (shown with a CRT filter on; changes at once; capped at half the destination height)
With the Aspect ratio at the monitor's shape: the pause, item and map menus, and what shows beside them. Loading screens and pre-rendered movies, which draw no world either, get the same sides. Changes at once.
Choices Full width; Centred, blurred sides; Centred, black bars (with the Aspect ratio at the monitor’s shape)
HDR10 out on an HDR display (Windows: Use HDR on in the display settings). Expanded: the game's SDR picture, its white at the paper white and its highlights up to the peak. Native: the game's own HDR, told the display's peak and paper white.
The HDR picture's contrast around mid grey, as the RenoDX HDR mods grade it: above 100% deeper shadows and brighter highlights, which ease into the peak brightness; below it flatter. With Native the game's own HDR picture is graded too, under the peak brightness the game is told.
Choices 50% to 200% around mid grey, in steps of 5 (while HDR is on)
With Native, how the game's scene meets the peak brightness. Vanilla: the game's own curve. PsychoV35: RenoDX's tone mapper, the same mid grey with highlights that roll off into the peak and keep their colour.
Choices and requirements
Vanilla (the game’s curve), PsychoV35 (RenoDX’s; with HDR set to Native). Compatible DLSS/DLAA, FSR 4/native AA and shared-chain FSR 3.1 upscaling run automatically; RX_VK_PSYCHOV35_DLSS=0 disables that compatibility route. Off and the spatial/FXAA TAAU replacement support PsychoV35 directly. FSR 3.1 FG remains separately opt-in and 2x only; legacy own-input FSR upscaling remains unsupported
Keeps textures sharp on surfaces seen at a slant, such as the ground ahead: higher is sharper in the distance, for a little GPU time. Game's is the console's own (1x or 2x).
The size of the sun's shadow maps: higher keeps the shadows of thin things near you, such as chains, fences and leaves, smooth instead of stair-stepped, for more video memory and a little GPU time. Highest also makes them shimmer less while the camera moves. Applies at once.
Choices and requirements
Auto (for the card’s memory), Game’s (1600), High (2200), Highest (3072): the sun’s shadow maps, applies at once; Highest also keeps the nearest shadows from shimmering as much
Adjust capture for Longshot only; system volume is unchanged. Use the microphone test to see live levels while adjusting gain. Changes apply to new samples.
Choices Software input level, 0–400%; applies to new samples without changing system volume
Start or stop microphone capture. No playback or audio files. You can adjust Microphone gain while testing. Leaving Audio, closing the menu or selecting Off stops the test; the game can still use the mic.
Choices Start/stop capture; live levels appear in the help box for Test microphone and Microphone gain
How large the FPS counter is drawn. Auto grows with the window, as the menu does; Small, Medium and Large keep one size whatever the window, the size Auto has in a 720p, 1080p and 1440p window.
Which lines the FPS counter's Dev level shows, and whether the version and hardware show at every level.
Choices and requirements
Opens the FPS counter details page: Version and hardware at every level (Off, On; Off), then a line each of the Dev level (VRAM, Textures, Draws, Dispatches, Render passes, Draws skipped, Texture uploads, Pipelines built, GPU slot waits, Queue submits, Write-backs) and the footer’s CPU and GPU lines and its render lines: the resolution the 3D is drawn at and what upscales it (Off, On; On each)
How much of the world you see: 100% is the original view. Higher is wider, lower is closer. Changes apply at once during gameplay. Cutscenes keep their own view.
Choices 50% to 150%, in steps of 5; applies immediately during gameplay
Starts a launch with the most recent saved game: presses A on the title screen, its file list and its Yes as soon as the game waits on each. Does nothing until the game has a save.
Auto (the game’s language), or English, Português (Brasil), Español (Latinoamérica), Español (España), Français, Deutsch, Italiano, Nederlands, Polski, Русский, 日本語, 한국어, 简体中文, 繁體中文
Skips the new-game opening (the story movie and the opening wake-up scene) and leaves later cutscenes, the first dungeon meeting, and the title screen alone.
Choices Off, On (skips the new-game opening: the story movie and the opening wake-up scene; later cutscenes and the title screen stay)
Saves what an issue needs in a new folder, bug-reports in the game folder: report.txt with the issue form's answers (this version, where you are, your graphics card and driver, CPU, RAM and system, the options and switches you changed), the logs of this run and the last one, and a picture of the game. Your user name and home folder are taken out of them. No saves or game files go in, and nothing is sent.
Choices Saves a report into a new folder in bug-reports
Stops the camera gradually turning toward the direction you move, useful with native mouse look. Off keeps the game's standard behavior. Manual camera controls and recentering still work.
How far the camera turns for a mouse movement, with either Mouse camera: at 1.00 native look turns 0.1 degree a count. The - and = keys change it in game too.
How fast the right stick turns the camera, in percent of the game's own speed; the camera keys too, and the mouse with Mouse camera As the stick. The game's own camera speed setting still applies.
How far a stick moves from center in any direction before the game sees it. Lower for a precise stick, higher for one that drifts. The game's own dead zone still follows.
How the controller vibrates. Auto plays the best it can: a DualSense its voice coils, a Switch controller and an Xbox controller RenHDrum's HD rumble, a Steam Controller (2026) its grips, every other controller its motors. Basic plays the motors on every controller. Off stops it.
A DualSense also taps its speaker and kicks back on L2 and R2 while you hold them, from the game's vibration, with deeper heavy hits. Off: its fine haptics alone, as before.
The button icons the game shows, in its texts and menus: those of this controller, for the buttons your controls put each action on.
Choices and requirements
Auto, Original console, Xbox, PlayStation 4, PlayStation 5, Steam Deck, Keyboard (on the Controls page; changes at once where the game allows it, else after a restart)
Motion controls: aiming with the controller's gyroscope, its sensitivity and its inverts.
Choices and requirements
Opens the Motion page: Motion controls (Off, On; On), Motion sensitivity X (10% to 600%) and Y (10% to 300%, in steps of 10; 100%), Invert motion X and Y (Off, On; Off), Motion deadzone (Low, Standard, High; Standard)
How the Walk key makes Link walk with the movement keys: while it is held, or from one press to the next. It is Caps Lock unless the Controls page changes it.
With Sprint On, by default hold Shift, or click and hold the left stick, while moving: Link runs without rolling, talking or picking things up, and moves as before once you let go. The Controls page's Sprint Toggle cell changes this to a press to start and stop. Turning Sprint on changes your controls: Shift moves from B to Sprint (B goes to V) and the left stick's press from LS to Sprint. Turning it off puts them back. Controls you rebound yourself are left alone; the Controls page's Sprint line rebinds it.
Choices and requirements
Off, On (by default, Link runs while you move and hold Shift or the left stick pressed in, without rolling; the Controls page’s Toggle cell changes this to a press; turning Sprint on moves Shift and the left stick’s press to Sprint)
Which keys open and close this menu. F1 always does; F1 only leaves Insert free for an overlay. With Esc, Esc opens it too, as a PC game's pause menu (open, Esc still goes back a page or closes it).
Which of the controller's buttons opens and closes this menu, so that no keyboard is needed: Home, or one of the back buttons of a pad that has them (GL and GR on a the supported console Pro Controller). None leaves all of them to the game.
Choices None, Home, Back left (GL), Back right (GR)
Which of your NFC tags to use: the files of your NFC folder, by their names. The Longshot Launcher's NFC page adds and removes them; dumps of your own figures (.bin, or a Flipper Zero's .nfc).
Choices The tag files of your NFC folder, by their names
Reads a tag you own with a the supported console Pro Controller's reader (over USB) and saves it in your NFC folder, so it can be tapped from this tab from then on. The tag itself is not changed.
Choices Reads a tag you own with a the supported console Pro Controller (USB) and saves it in your NFC folder
Default —
For a live preview while adjusting Custom HUD placement, use the compact menu. Right Shift switches to it by default.
The Debug tab is for testing. Its Debug tools (or HOS_OOT_CHEATS=1 in longshot_env.txt) add flight, a free
camera, teleport, the inventory and the other tools below the row. Its Developer rows are workarounds to try when a
helper asks you to.
About some settings
Colour vision correction: in Graphics → Accessibility, choose Off, Protan (red-green),
Deutan (red-green) or Tritan (blue-yellow). The setting takes effect immediately and is remembered.
It shifts colour differences while preserving brightness. The three modes are fixed presets and their
usefulness varies by player and scene.
Quality preset sets Render resolution, Window scaling filter, Sharpness, Frame pacing, Game speed, Profile and
Shadow resolution for a card with that much memory. It leaves the Upscaler and Frame generation as you chose them:
with DLSS, FSR 3.1 or FSR 4, the preset’s resolution becomes their nearest mode. Changing most other rows yourself
sets it to Custom.
Auto (this PC) chooses for the PC it runs on: the memory tier from the card’s video memory (Minimum on an
integrated GPU, a Steam Deck or a card without mesh shaders), DLSS on an NVIDIA RTX card or FSR 4 on an AMD RDNA 4 card (RX 9000)
where the build has them. In the first minute of play it lowers the Render resolution a step while frames are missed
with the GPU busy, or raises it while the cap holds with the GPU under half busy: at most two steps. It chooses again
when the card or the screen changes; longshot_log.txt’s Auto (this PC) lines say what it chose and why.
The scaling rows, in the picture’s order: Output resolution is the size of the whole frame, HUD included. The
Upscaler fills it from the 3D, whose share is the Render resolution. Off is no upscaler at all, not even
the game’s own: the fastest choice, with jagged edges. The Window scaling filter then scales the frame to your
window, and Sharpness sharpens it. For the sharpest picture, set the Output resolution to your screen’s size: the
filter row then shows “Not needed (window = output)”. NVIDIA DLSS, AMD FSR 4 and Intel XeSS need files of their
makers’ (optional upscalers); AMD FSR 3.1 is in every build.
Aspect ratio lists the shapes of your screen’s resolutions, your monitor’s own marked “(monitor’s)”, and Output
resolution that shape’s sizes, your screen’s own marked “(native)”. A size larger than your screen is drawn at that
size and scaled down. For a size the menu doesn’t offer, type it in Custom output size (<width>x<height>, each
side a multiple of 8, from 640x360 up to 5120x2880’s pixels, between 5:4 and 48:9); the menu says why it refuses one.
For three 16:9 monitors, use 5760x1080 or 7680x1440 with a window that spans all three.
Frame generation by chooses who makes the extra frames: DLSS FG (NVIDIA DLSS Frame Generation, RTX 40 and
newer, the default where it runs: up to 6x on an RTX 50, 2x on an RTX 40), FSR 3.1 FG (AMD’s, on any GPU, the
default elsewhere) or Built-in FG. Frame pacing (Debug tab) shows those frames at an even interval: less
stutter, up to a frame of delay. Present queue (Debug tab) can make them more even with V-Sync Off on some cards,
but lost the GPU on others: if the game then crashes before you reach the menu, put RX_VK_PRESENT_QUEUE=0 in
longshot_env.txt, turn the row off and remove the line.
Game frame rate cap limits the frames the game renders: with a cap of 60 and Frame generation at 2x, the output
reaches 120 FPS. A cap above 60 is experimental: the game keeps real time, but some cutscenes and bosses count frames
and can misbehave. Uncapped renders as fast as the PC can; with V-Sync on, the display’s refresh still holds it.
V-Sync: Auto is mailbox where the driver has it (no tearing, no wait), else On, or Off on Windows. On waits for
each refresh; Off shows each frame at once and can tear.
HDR: Expanded expands the game’s SDR picture; Native is the game’s own HDR, with the HDR tone mapper row.
On Windows, if the game stays SDR, the HDR row’s help says why (HDR stays SDR).
CRT filter adds scanlines and a phosphor mask to the finished SDR picture, HUD included; CRT lines is its
virtual line count. Native HDR leaves it out.
Anisotropic filtering keeps the ground sharp at a slant; 16x costs little on most cards, and Game’s is the
console’s own. Shadow resolution sets the sun’s shadow maps: Auto picks by the card’s memory (the game’s 1600 up
to 6 GB, High at 8 GB, Highest from 12 GB). On Highest the nearest shadows shimmer less while the camera turns or
Link walks: the map near Link stays put in the world instead of following the view. The steady fit is a little coarser
than the game’s own fit standing still, so below Highest the game’s fit is kept (developer switches).
GPU device matters on a PC with more than one graphics card: Auto prefers a dedicated one. The card you choose is
remembered as that card, not its place in the list.
Threaded rendering: On draws the picture on threads of its own (a render thread and a recorder thread) while the
game goes on to its next frame, for a higher frame rate on a processor with cores to spare; it can still show
flashes. Auto counts the processor’s cores for the game: both threads with 6 or more, the render thread alone with 4
or 5, Off with fewer. It applies after a restart.
Robust buffers drops a read past a buffer’s end instead of stopping the GPU: Auto is on, on every card.
ASTC as RGBA8 is the AMD texture workaround.
Intel shader compiles (Intel graphics on Windows): One at a time is the safe choice; Side by side builds faster
on many cores but can crash in Intel’s driver. Auto is side by side on the Arc B-series with driver 101.9154 or newer.
FPS counter has five levels: FPS; Frame time (with the 1% low, green at the cap’s rate, amber under it,
red under two thirds of it); Graph (the last 4 seconds, red marks over frames that took twice the cap’s time);
Breakdown (where each frame’s time went: the game, the renderer, the waits); Dev (the renderer’s own numbers,
for bug reports). Its footer shows the version, CPU, GPU and driver, then the resolution the 3D was drawn at and what
upscaled and anti-aliased it, as the last frame drew them. FPS counter details turns the Dev level’s lines on or off
and can show the footer at every level.
Game speed: Per frame slows the game whenever it is below 60 fps; Real time keeps normal speed down to 15 fps.
Field of view changes the gameplay camera’s angle: 100% is the game’s. Cutscenes, the HUD and movies keep theirs.
Skip title screen loads your most recent save at the start, once you have saved once. It presses A for you on the
title screen, its file list and its Yes, each as soon as the game waits there, and on nothing else; the game itself
loads the save. With no save yet the title screen stays, so a new game can start.
Game language writes language.txt in the game folder, read at the next start. Menu language is this
menu’s: its translations are machine-made, and corrections are welcome.
Bug report saves what a report needs in a new folder (what is in it).
Speaker layout: Auto is 5.1 when the output device has 5.1 speakers, else stereo. Mono puts both channels in both
ears. Microphone is what the game hears when its own microphone option is on; Test microphone
shows its level.
Mouse camera: Native turns the camera with the mouse one to one, as in a PC game; As the stick uses the mouse in
the right stick’s place (- and = change the sensitivity in game); Off leaves the mouse out.
Disable camera centering stops the game turning the camera toward your movement.
Camera speed is how fast the right stick and the camera keys turn the camera, in percent of the game’s own.
Stick dead zone: how far a stick moves before it counts. Lower it for a precise stick, raise it for one that
drifts.
Vibration: Auto plays the best each controller can (a DualSense its voice coils, on a cable or over Bluetooth;
an Xbox One or Series controller all four motors; a Switch Pro Controller its HD rumble; a Steam Controller (2026) its
grips, still experimental; any other its two motors); Basic plays the two motors on every controller.
Test vibration says what plays the controller you used last. DualSense HD Haptics (on) adds the DualSense’s
speaker and its L2/R2 to that: soft taps from the speaker, and a kick in a trigger you hold when something hits.
Motion (a page on the Controls tab): the gyroscope aims where the game uses motion, with Switch Pro controllers,
pads in Switch mode, DualSense and DualShock 4. Set the pad down for a second if the aim creeps.
Walk mode and Walk speed: while the Walk key is held (Caps Lock unless you change it), the movement
keys tilt the stick only Walk speed of the way. With Toggle, one press walks and the next runs.
Sprint (Controls tab, off by default): Link runs the game’s own run, the one after a roll while A stays held,
without the roll. By default, hold Shift while you move, or on a controller hold the left stick pressed in; let go and
he moves as before. With Sprint On, its Toggle cell on the Controls page instead starts and stops it with a press.
He runs past people, signs and pots without talking, reading or picking up; tap A to roll or
act as usual. Sprint is disabled while the instrument is waiting for a note. Turning the row on moves Shift from B
to Sprint (B goes to V, when no control has V) and the left stick’s press from LS to Sprint; turning it off
puts them back. Controls you rebound yourself are left alone, and the Controls page’s Sprint line rebinds it.
Controls
Use a controller, or the keyboard and mouse. On the keyboard, WASD move
(hold Caps Lock to walk), the arrow keys (or IJKL) turn the
camera, and E is A (it selects New Game on the title screen).
Toggle HUD starts unbound. Assign a key or controller input on the Controls page to hide or show the gameplay HUD
during the current session. The dungeon’s small-key count follows the minimap’s placement and visibility. The full map
stays available with its own small-key count and the Boss Key icon when owned. While assigned, the shortcut takes priority
over any gameplay action on the same key or button.
Change a binding on the Controls tab’s Controls page: choose a row and a column (Gamepad or Keyboard), press
Enter (or the bottom face button), then the new button or key. Esc cancels, Delete
clears it, and Reset to defaults puts them all back. A gamepad button taken from another Switch button swaps with
it. The Toggle column makes a Switch button stay held from one press to the next, and Sprint run from one press to
the next instead of while held, when the Controls tab’s Sprint setting is On. The five note rows (the
instrument’s notes) are unset until you bind them to inputs of your own.
Mouse in the game’s menus (Windows): the title screen, the pause menu, the map and the save dialogs free the mouse.
Point at an entry and left-click to choose it (A), right-click to go back (B); the wheel turns the pause menu’s pages,
scrolls lists and zooms the map, and dragging pans the map.
Rumble: a Switch Pro Controller plays the game’s HD rumble as the console does (on Linux it needs Steam’s
udev rules, the steam-devices package on most distributions). A third-party pad in Switch mode that turns it into
weak rumble or none gets the plain motor rumble with HOS_HD_RUMBLE=0 in longshot_env.txt.
DualSense haptics: a DualSense on a USB cable plays the game’s own fine vibration on its voice coils, through
RenHDrum, which the Longshot Builder puts beside the game. Without it, the pad gets its motors. With DualSense HD
Haptics on (the default) its speaker taps and its triggers kick back too; turn it off for the voice coils alone.
The supported console’s Pro Controller over USB (Windows): the game reads it itself, with its motion sensor and
rumble. Choose its own Layout preset for its buttons and icons; its Home button opens this menu (Controller menu
button). Close Steam and any bridge program first: only one program can have the controller. Not over Bluetooth.
NFC tags: where the game asks for a figure’s tag, the menu’s NFC tab gives it one. The tags are dumps of tags you
own (.bin, or a Flipper Zero’s .nfc) in %LOCALAPPDATA%\Longshot\nfc on Windows or ~/.local/share/longshot/nfc on
Linux; the Longshot Launcher’s NFC page adds and removes them. Choose one in NFC tag and press Tap tag. A real
tag held on that Pro Controller over USB is read too, and Scan tag on controller saves one. No tag is ever
written.
Writing the controls in longshot_options.ini yourself
pad_a=0
key_a=69,13
toggle_a=0
pad_<button> is a gamepad input by position: 0 bottom face button, 1 right, 2 left, 3 top, 4 Select or Back, 5 Home,
6 Start, 7 and 8 the stick presses, 9 and 10 the shoulder buttons, 11 to 14 the D-pad (up, down, left, right), 15 and
16 the triggers, -1 none. key_<button> is one or two
Windows key codes in decimal (69 is
E, 13 Enter), 0 none; the mouse’s buttons are 1 (left), 2 (right), 4 (middle), 5 and 6 (side
buttons). The buttons are abxylrzlzrplusminuslsrsleftuprightdown; for
keys only, the left stick’s and the camera’s directions and walking: move_upmove_downmove_leftmove_rightcam_upcam_downcam_leftcam_rightwalk; and the five notes, which also take a pad_ line:
note_lnote_rnote_anote_ynote_x; and sprint, which takes both lines (none by default; the Sprint row
gives it Shift and the left stick’s press). A button the file leaves out keeps its default. toggle_<button>=1 turns
that button’s Toggle on (not for plus, minus, the stick directions, walk or the notes; toggle_sprint=1 for Sprint).
Change one thing at a time
When something looks or runs wrong, change a single setting and compare the same place in the game. To report a
performance problem, follow Report slow performance.