Game: button prompts ignore the PlayStation 4/5 choice and stay on the connected pad's face #413
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#413
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Longshot version
v3.0.0-rc.3 (source cb01b5a3)
Channel
Release candidate
What kind of problem
Controls
What happened
Set Insert - Gameplay - button prompts (按键提示) to PlayStation 5 and restarted: the in-game action prompt still draws the Nintendo A face. Set it to PlayStation 4 and restarted again: same. So both PlayStation faces behave the same way and a restart does not help.
The controls screen itself does follow the setting: with PlayStation selected, the 输入1 column reads ○ button, × button, △ button, □ button. It is only the prompts drawn in game that do not.
What I expected: the chosen face is what the HUD draws, whichever pad is plugged in.
What the two runs say: the prompts resolve through auto both times, never through the chosen face.
Meanwhile longshot_options.ini holds button_prompts=1 while the menu showed PlayStation 5, so the choice does reach the config. It looks like the runtime re-derives the face from auto (the detected pad) instead of using the chosen one: with the Switch Pro connected, auto yields the Switch face, which is the A in the screenshot.
Repro: set 按键提示 to PlayStation 5 or 4, restart, look at any action prompt.
Where in the game
Anywhere: the action prompt at the bottom right, e.g. the door prompt that reads A 打开
How often
Every time
Graphics card and driver version
RTX 4090 (24138 MB), NVIDIA 621.24
CPU, RAM and operating system
Ryzen 7 7800X3D, 48 GB, Windows 10 Pro 22H2 build 19045.7807
Changes from the defaults
按键布局: Nintendo (default). 按键提示: tried PlayStation 5, then PlayStation 4. Pad: Nintendo Switch Pro Controller (SDL). Output 5120x2160, DLSS frame generation 2x, V-Sync off, motion controls on, keyboard bindings customised. No overlay, no ReShade, no shader-cache tool, no frame-generation injector.
longshot_log.txt
Full longshot_log.txt and longshot_log.1.txt to follow (the upload box did not take the file); these are the copied lines.
longshot_log.txt (no pad, prompts set to PlayStation 5), line 2 and 63 and 113:
[hos host] longshot v3.0.0-rc.3 (source cb01b5a3)
[hos sead::MainThread] prompts: auto: controller "(none)": keyboard
[hos ARes Loading 0] prompts: keyboard icons, 16 buttons on these keys
longshot_log.1.txt (Switch Pro connected), line 45, 48, 125:
[hos host] hid: controller "Nintendo Switch Pro Controller" connected (SDL), with a gyroscope; guid=0500b7e67e0500000920000000006803
[hos sead::MainThread] prompts: auto: controller "Nintendo Switch Pro Controller": switch
[hos ARes Loading 0] prompts: switch icons, 16 buttons on these pad's controls
longshot_options.ini: layout_preset=0, button_prompts=1
Screenshots or video
Two to follow in a comment: the controls screen with 按键提示 = PlayStation 4 and ○ / × / △ / □ in the 输入1 column, and the in-game prompt still reading A 打开. Full logs to follow as files.
Before you send it
From #897 (closed as a duplicate of this one):
The same PlayStation 5 selection is ignored in v3.0.0-rc.4 after updating from rc3, with Japanese language and Nintendo layout preset. The menu reflects the selection (Japanese controls page uses 〇/× names), but in-game prompts show Switch glyphs, including the ocarina hint. This shows the issue persists in rc4; logs/GPU details were unavailable.
Could not reproduce on Linux (main at
7ff5256e, 2026-11-14). I tested with #897's setup: Japanese, Nintendo layout preset, PlayStation 5.That build has #321 (the prompts made in
cache/prompts/) and #358 (each face drawn in a process of its own), but not #314 (packaged builds keep unchanged prompts).Setup:
language.txtset tojalongshot_options.ini:button_prompts=4(PlayStation 5),layout_preset=0(Nintendo)HOS_HEADLESS=1 RX_VK_PRECOMPILE=0) for 3 minutes, loading a save in the Deku TreeResult: the PlayStation 5 face is used. The HUD's item buttons read R1 and R2, not the Switch's R and ZR:
The first line is the one to compare. With a face chosen,
host/prompts.cchoose_facelogsprompts: ps5 iconsstraight away. Theprompts: auto: controller "…"lines in this issue's logs mean the start read nobutton_prompts=of 1 to 6 fromlongshot_options.ini, so it used Auto. Thebutton_prompts=1quoted above would also have chosen a face (the Switch's), not Auto. So the file read at the start didn't hold the choice the menu showed. Either the game read anotherlongshot_options.ini, or the file changed after the start.Also checked, in the game's files:
Font2/Font*.bfarc) draws the button icons fromExternal, the font Longshot patches.UI/Layout2Archive/Common.*for every language.Still open:
cache/prompts/write uses ANSI file calls (a long or non-ASCII folder path);The next step is the real
v3.0.0-rc.4build on Windows, with a face chosen in the menu, then a restart. Look at the firstprompts:line oflogs/longshot_log.txt(a face orauto) and at thebutton_prompts=line of thelongshot_options.inibeside the game at that moment.From clawstheone on Discord:
A Steam Deck player reports that setting Button Prompts to Steam Deck has no effect on NPC dialogue prompts even after restarting. They clarify this is a failure of the existing selection setting, not merely a request for additional prompt styles.
From pikuś on Discord:
On Windows 11 with RTX 4070 Ti, NVIDIA driver 621.01, and Longshot Nightly 323 (
6fb13fe5), Xbox prompts were manually selected but Switch prompts remain after restart. The attached log's only prompt-related line isprompts: no %USERPROFILE%\Games\Longshot\nightly-187-9e6f231d\prompts/External.bfotf: the game's own icons, indicating the customized prompt asset is missing for that install.From keios3476 on Discord:
A user reports the same symptom as the existing issue: the game initially showed the selected prompts correctly, but they now see Switch prompts despite selecting Xbox and restarting. They ask for troubleshooting. No version, system details, or log were provided. Another Discord participant notes commit
1764fed2as a possible cause for changes in Nightly 320+, but it is an FPS-counter overhaul and that connection is unconfirmed.Still not reproduced on current main, now on Windows (Wine) too and with the ocarina hint. Follow-up to my comment above.
What I checked:
用户设置) andbutton_prompts=4(PlayStation 5). The first line isprompts: ps5 icons, and the PS5 face shows in game. The ANSI file calls I named as a lead above load the prompts correctly there.The newer reports point elsewhere. pikuś's log (Nightly 323, Windows) has one prompt line:
prompts: no …\nightly-187-9e6f231d\prompts/External.bfotf: the game's own icons. In that install the game found apromptsfolder with noExternal.bfotfin it. Without that file it draws the Switch's icons whatever Button prompts says, so the menu choice can't take effect there. The build only writes a complete prompts folder (nx2/prompt_assets.pyrefuses an incomplete one), so the file went missing after the build.To find out how, please send, from a player who sees this:
<game folder>\prompts\(names and sizes);A rebuild from the launcher should bring the file back. The same check applies to the Steam Deck report: its first
prompts:line will say whether the font was found.Related fixes (open, not the cause of this issue):