Idea: DualSense-accurate button glyphs for the PlayStation face #409

Closed
opened 2026-11-14 10:40:53 +00:00 by cirnoice · 1 comment

The idea

The PlayStation prompt face still draws its buttons from the Kenney PS set, so the four face buttons come out as flat generic symbols rather than DualSense-shaped buttons. PR #406 already replaces the controller artwork and the guide lines with a hand-drawn DualSense, but it deliberately does not touch the button icons: the glyphs stay Kenney's, so the face ends up with in-house art and stock icons on top of it.

This is the follow-up, whenever there is spare time: a glyph set that matches the DualSense the face is now drawn around.

Anything else

  • Where it would land: nx2/prompt_faces/ps5/, next to #406's Controller_Pro.png and ControllerGuide_Pro_0*.png, with the parts coordinates in nx2/prompt_faces.py adjusted to the new art.
  • Scope: the four face buttons, the D-pad, L1/R1, L2/R2, L3/R3, Options/Create, touchpad click and the PS/mute button - the same 16 entries prompts: ps5 icons, 16 buttons already enumerates, so the count stays 16.
  • Art: the current set is vendored from Kenney, and DualSense-accurate glyphs would most likely need to be drawn in-house like #406's artwork. If you would rather not own that art, wontfix is a fair answer - I would just like to know which way it goes.
  • If the real goal is "let people pick a glyph style" rather than "make PS look like a DualSense", splitting glyph set from face layout is probably the cleaner change; happy to open that separately.
  • No rush at all, and not a bug. Folding it into #406 is fine if the two land together.
### The idea The PlayStation prompt face still draws its buttons from the Kenney PS set, so the four face buttons come out as flat generic symbols rather than DualSense-shaped buttons. PR #406 already replaces the controller artwork and the guide lines with a hand-drawn DualSense, but it deliberately does not touch the button icons: the glyphs stay Kenney's, so the face ends up with in-house art and stock icons on top of it. This is the follow-up, whenever there is spare time: a glyph set that matches the DualSense the face is now drawn around. ### Anything else - Where it would land: `nx2/prompt_faces/ps5/`, next to #406's `Controller_Pro.png` and `ControllerGuide_Pro_0*.png`, with the `parts` coordinates in `nx2/prompt_faces.py` adjusted to the new art. - Scope: the four face buttons, the D-pad, L1/R1, L2/R2, L3/R3, Options/Create, touchpad click and the PS/mute button - the same 16 entries `prompts: ps5 icons, 16 buttons` already enumerates, so the count stays 16. - Art: the current set is vendored from Kenney, and DualSense-accurate glyphs would most likely need to be drawn in-house like #406's artwork. If you would rather not own that art, wontfix is a fair answer - I would just like to know which way it goes. - If the real goal is "let people pick a glyph style" rather than "make PS look like a DualSense", splitting glyph set from face layout is probably the cleaner change; happy to open that separately. - No rush at all, and not a bug. Folding it into #406 is fine if the two land together.
Author

Withdrawn - I missed that this already exists. The game ships a PlayStation 5 preset in the controller layout dropdown (按键设置 - 手柄布局), with the buttons bound as ○ / × / △ / □ against the A/B/X/Y rows, so the glyph set is a built-in option rather than a gap. My mistake, sorry for the noise to anyone who got notified.

Closing this. Whoever has write access to the repo can delete it outright if that is preferred - as the reporter I do not get a delete option.

Withdrawn - I missed that this already exists. The game ships a PlayStation 5 preset in the controller layout dropdown (按键设置 - 手柄布局), with the buttons bound as ○ / × / △ / □ against the A/B/X/Y rows, so the glyph set is a built-in option rather than a gap. My mistake, sorry for the noise to anyone who got notified. Closing this. Whoever has write access to the repo can delete it outright if that is preferred - as the reporter I do not get a delete option.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#409
No description provided.