Game: the System page's controller lines don't follow the controller or its mapping (PS5: the d-pad's line ends on the left stick) #1211
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1211
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
main @
615b2498(built from source)Channel
Built from source
What kind of problem
Display (button prompts)
What happened
On the pause menu's System page, the controller picture's leader lines (from each label to the button it names) don't follow the controller. A line can end on the wrong part of the picture.
The PlayStation 5 face is the clearest case: the d-pad's label line ends on the left stick. On the DualSense the d-pad sits top left and the left stick lower in. The lines still follow the Pro Controller's layout, where the left stick is above the d-pad.
Why:
nx2/prompt_assets.pybuilds the lines from fixed rows taken from the game's Pro Controller page (GUIDE_LINES: ZL, −, left stick, +, A, right stick). Each row is routed to a part of the face's picture (nx2/prompt_faces.pyparts). The rows, their order, and which label is on which side are the Pro Controller's. A face whose controls sit in another order, or a binding moved to another pad input, gets lines that cross or end on another part.What a fix must do
The page must show the true mapping of the controller in use:
Proposed approach: a line from any label to any pad input, routed per face (not fixed rows from the Pro Controller):
host/prompts.calready writes the line of the bound input).Where in the game
Pause menu → System, the controller picture.
How often
Always, with the PlayStation 5 face (and any face whose layout differs from the Pro Controller's).
Graphics card and driver version
AMD Radeon 680M, Mesa RADV
CPU, RAM and operating system
Linux (CachyOS 7.3.4)
Changes from the defaults
Button prompts = PlayStation 5
longshot_log.txt
Not needed: the lines are made at the build (
nx2/prompt_assets.py), not at run time.Screenshots or video
To be added in a comment below.
Possibly related, for context:
Screenshots. Build: main @
615b2498plus the open prompt fixes #1125, #1126 and #1184, none of which touch this page. Linux, Radeon 680M, 1280x720, English, default bindings. The game started on the PlayStation 5 face; each other face was then set live from the menu, with the page left open.With PS5 from the start (the picture and the lines both PS5's):
After a live change (the most visible case of "the d-pad matched to the left stick"). The labels and lines change to the new face's, but the controller picture stays the PS5 one the game started with. Each line is routed to the new face's parts, drawn over the PS5 picture:
So the fix covers two things:
Still to check: other languages (label width), other resolutions and ultrawide, and a rebound control (Controls page) on this page.
Full screenshots per face:
We might need a hidden button map layer on the texture itself to do that