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

Open
opened 2026-11-16 19:07:10 +00:00 by gab9281 · 3 comments
Member

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.py builds 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.py parts). 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:

  1. Any controller: every face (Switch, Xbox, PS4, PS5, Steam Deck), and a generic SDL pad that falls back to one of them.
  2. Any mapping: a control rebound to another pad input (Controls page, Input 1 / Input 2) gets its line to that input's part.
  3. Any language: the labels' text width changes per language; a line starts at its label's bar whatever the text.
  4. Any resolution: the page is drawn at every output size (720p to 4K, ultrawide) without the lines drifting off their parts.

Proposed approach: a line from any label to any pad input, routed per face (not fixed rows from the Pro Controller):

  • Groups with one shared frame and individual inputs inside: the d-pad (up/down/left/right), the face buttons (south/east/west/north), the shoulders (L1/L2, R1/R2) and the sticks with their click (L3/R3). A label bound to one input of a group points at the group and, where that's ambiguous, at the input itself.
  • Each label's line is made for each pad input it can be bound to, so a rebind picks the right line at run time (host/prompts.c already writes the line of the bound input).
  • Labels placed on the side and in the order of their parts on that face, so lines don't cross.

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.

### 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.py` builds 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.py` `parts`). 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**: 1. **Any controller:** every face (Switch, Xbox, PS4, PS5, Steam Deck), and a generic SDL pad that falls back to one of them. 2. **Any mapping:** a control rebound to another pad input (Controls page, Input 1 / Input 2) gets its line to that input's part. 3. **Any language:** the labels' text width changes per language; a line starts at its label's bar whatever the text. 4. **Any resolution:** the page is drawn at every output size (720p to 4K, ultrawide) without the lines drifting off their parts. **Proposed approach:** a line from any label to any pad input, routed per face (not fixed rows from the Pro Controller): - **Groups** with one shared frame and individual inputs inside: the **d-pad** (up/down/left/right), the **face buttons** (south/east/west/north), the **shoulders** (L1/L2, R1/R2) and the sticks with their click (L3/R3). A label bound to one input of a group points at the group and, where that's ambiguous, at the input itself. - Each label's line is made for each pad input it can be bound to, so a rebind picks the right line at run time (`host/prompts.c` already writes the line of the bound input). - Labels placed on the side and in the order of their parts on that face, so lines don't cross. ### 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.
Collaborator

Possibly related, for context:

  • #409 Idea: DualSense-accurate button glyphs for the PlayStation face — Related button-prompt face assets and their alignment, but this is about glyph artwork rather than the System page’s mapping leader lines.
  • #84 Game: Switch prompts no longer match a PowerA pad after restart — Related issue about controller prompts not matching physical controls; its symptom is incorrect prompt/controller identification after restart.
Possibly related, for context: - #409 Idea: DualSense-accurate button glyphs for the PlayStation face — Related button-prompt face assets and their alignment, but this is about glyph artwork rather than the System page’s mapping leader lines. - #84 Game: Switch prompts no longer match a PowerA pad after restart — Related issue about controller prompts not matching physical controls; its symptom is incorrect prompt/controller identification after restart.
Author
Member

Screenshots. Build: main @ 615b2498 plus 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.

PS5 at start: the page

PS5 at start, zoomed in

With PS5 from the start (the picture and the lines both PS5's):

  • Target (L2) and Quick Select Items (L1) end on the same dot, on L1's top edge. L2's line doesn't reach the trigger.
  • Use Item (R2)'s line ends on a dot in empty space above R1, off the controller.
  • The d-pad has no label, so no line.

The five faces set live, left to right and down: Switch, Xbox, PS4, PS5, Steam Deck

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:

  • Switch, Xbox: Move (L) ends on the PS5's d-pad, where those pads have their left stick. Rotate Camera (R) ends between the sticks.
  • Steam Deck: the face-button frame sits off the buttons, beside them. Move's line runs to the d-pad's corner.
  • PS4: close to PS5, but the L2 and L1 dots are still shared.

So the fix covers two things:

  1. Lines routed per face and per binding, as described above: groups (d-pad, face buttons, L1/L2, R1/R2) with each input's own end inside, each trigger and bumper reached on its own, and no dot off the controller.
  2. The picture and its lines from the same face at all times, including after a live change: both swapped together, or the lines kept for the picture shown.

Still to check: other languages (label width), other resolutions and ultrawide, and a rebound control (Controls page) on this page.

Full screenshots per face:

Switch
Xbox
PS4
Steam Deck

**Screenshots.** Build: main @ 615b2498 plus 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. ![PS5 at start: the page](https://git.magicbean.dev/attachments/b1aa7ca4-341e-42e5-b5a3-8f4c7f6e6989) ![PS5 at start, zoomed in](https://git.magicbean.dev/attachments/c0f51607-f49b-43f3-8af5-d1d97f0c1a6e) **With PS5 from the start (the picture and the lines both PS5's):** - **Target (L2)** and **Quick Select Items (L1)** end on the same dot, on L1's top edge. L2's line doesn't reach the trigger. - **Use Item (R2)**'s line ends on a dot in empty space above R1, off the controller. - The **d-pad** has no label, so no line. ![The five faces set live, left to right and down: Switch, Xbox, PS4, PS5, Steam Deck](https://git.magicbean.dev/attachments/5ca32083-6840-4f2a-b124-071995998752) **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: - **Switch, Xbox:** **Move (L)** ends on the PS5's **d-pad**, where those pads have their left stick. **Rotate Camera (R)** ends between the sticks. - **Steam Deck:** the face-button frame sits off the buttons, beside them. **Move**'s line runs to the d-pad's corner. - **PS4:** close to PS5, but the L2 and L1 dots are still shared. So the fix covers two things: 1. **Lines routed per face and per binding**, as described above: groups (d-pad, face buttons, L1/L2, R1/R2) with each input's own end inside, each trigger and bumper reached on its own, and no dot off the controller. 2. **The picture and its lines from the same face at all times,** including after a live change: both swapped together, or the lines kept for the picture shown. Still to check: other languages (label width), other resolutions and ultrawide, and a rebound control (Controls page) on this page. Full screenshots per face: ![Switch](https://git.magicbean.dev/attachments/7262858b-02f0-4ae3-a0ef-221094cca6ce) ![Xbox](https://git.magicbean.dev/attachments/35f4644e-36ac-4b2d-91dc-4817ae510fcb) ![PS4](https://git.magicbean.dev/attachments/426fb525-876c-46da-a108-bbfd6aa6e4b3) ![Steam Deck](https://git.magicbean.dev/attachments/7f203c06-93cf-4ad5-bfd6-838a8398e336)
Author
Member

We might need a hidden button map layer on the texture itself to do that

We might need a hidden button map layer on the texture itself to do that
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1211
No description provided.