[bug] glyphs get half overlapped in history feed

thingsiplay commented

2026-09-16 00:36:18 +02:00

(Migrated from github.com)

3dco+ version: 1.2.0

OS: EndeavourOS x86_64
Kernel: Linux 7.2.6-arch2-1
Desktop Environment: KDE Plasma 6.7.5
Window Manager: KWin (Wayland)

I use Steam deck glyphs and they get half overlapped when holding a button, because the glyphs are double in size of normal text. Below is an image what I mean. This especially happens with gyro enabled, and the Steam Controller constantly watches if I touch the handles.

```text 3dco+ version: 1.2.0 ``` ```text OS: EndeavourOS x86_64 Kernel: Linux 7.2.6-arch2-1 Desktop Environment: KDE Plasma 6.7.5 Window Manager: KWin (Wayland) ``` I use Steam deck glyphs and they get half overlapped when holding a button, because the glyphs are double in size of normal text. Below is an image what I mean. This especially happens with gyro enabled, and the Steam Controller constantly watches if I touch the handles. <img width="985" height="529" alt="Image" src="https://github.com/user-attachments/assets/bf3d76eb-f402-4c96-bc1c-08d9203346b2" />

Khyretos commented

2026-09-16 00:56:57 +02:00

(Migrated from github.com)

on it, i can indeed reproduce it, and i will see how i can make the grip sensors not being detected as a holdable button or invert its function.
and also make the table and hold not overlap each other.

on it, i can indeed reproduce it, and i will see how i can make the grip sensors not being detected as a holdable button or invert its function. and also make the table and hold not overlap each other.

thingsiplay commented

2026-09-16 01:16:25 +02:00

(Migrated from github.com)

and i will see how i can make the grip sensors not being detected as a holdable button or invert its function

The grip sensors being detected as holdable buttons is actually correct, because that is a legitimate functionality and configuration in Steam Input (with Steam running). In example I can trigger certain stuff by grip sensor.

I think it would be useful to have a filter, where we can disable certain buttons from being displayed. If that is possible. Otherwise maybe at least a toggle for this specifically.

> and i will see how i can make the grip sensors not being detected as a holdable button or invert its function The grip sensors being detected as holdable buttons is actually correct, because that is a legitimate functionality and configuration in Steam Input (with Steam running). In example I can trigger certain stuff by grip sensor. I think it would be useful to have a filter, where we can disable certain buttons from being displayed. If that is possible. Otherwise maybe at least a toggle for this specifically.

👍 1

Khyretos commented

2026-09-16 01:17:38 +02:00

(Migrated from github.com)

you read my mind! XD.

oke so right now i will add 2 solutions, it wil now check which button is "inverted" in the "model" table, it will then reverse the functionality so when you let go it starts counting and when holding it it stops. but this sensor can be finicky and even though you hold it it sometimes detects a press. so i will add the feature for you to "ignore" certain buttons, this will be done by adding a row to the existing mapping and selecting the button and explicitly ignore it. i will release 1.2.1 soon

you read my mind! XD. oke so right now i will add 2 solutions, it wil now check which button is "inverted" in the "model" table, it will then reverse the functionality so when you let go it starts counting and when holding it it stops. but this sensor can be finicky and even though you hold it it sometimes detects a press. so i will add the feature for you to "ignore" certain buttons, this will be done by adding a row to the existing mapping and selecting the button and explicitly ignore it. i will release 1.2.1 soon

❤️ 1

Khyretos commented

2026-09-20 07:20:47 +02:00

(Migrated from github.com)

v1.3.0 is out and here is an example of how it looks when ignoring buttons:

buttons 23,24 are the thumbsticks touch sensor and 24-25 are the grip sensors.

and now the hold timer and bottom row should always show correctly and not overlap, making the regular input history cut off.

v1.3.0 is out and here is an example of how it looks when ignoring buttons: <img width="892" height="106" alt="Image" src="https://github.com/user-attachments/assets/0d0ce4ec-5392-46e1-83c5-70f7876c92a4" /> buttons 23,24 are the thumbsticks touch sensor and 24-25 are the grip sensors. and now the hold timer and bottom row should always show correctly and not overlap, making the regular input history cut off.

thingsiplay commented

2026-09-20 09:00:02 +02:00

(Migrated from github.com)

Thanks. I can confirm that the history is no longer cut off. So the core issue is solved.

Unfortunately the Ignore Button part doesn't work for me, maybe its a configuration issue. I selected Display Style to be "Steam Deck". Then Created New Glyph Mapping... to ignore the buttons as in your screenshot shown. Then click (choose one) Edit Existing Mapping, choose "Steam Deck" from the list. In the new window to change mappings then on top Combine With "Thumbstick Touch and Grip Sensors". But the new additional rules have no effect.

Thanks. I can confirm that the history is no longer cut off. So the core issue is solved. Unfortunately the Ignore Button part doesn't work for me, maybe its a configuration issue. I selected Display Style to be "Steam Deck". Then Created New Glyph Mapping... to ignore the buttons as in your screenshot shown. Then click (choose one) Edit Existing Mapping, choose "Steam Deck" from the list. In the new window to change mappings then on top Combine With "Thumbstick Touch and Grip Sensors". But the new additional rules have no effect.

Khyretos commented

2026-09-21 11:35:43 +02:00

(Migrated from github.com)

im working on a patch to solve the issue, when the new version comes out ill ask you to try it out again.

Khyretos commented

2026-09-22 05:23:16 +02:00

(Migrated from github.com)

can you verify if v1.3.1 has the ignore buttons working for you?

thingsiplay commented

2026-09-22 06:18:05 +02:00

(Migrated from github.com)

Yes, it works. I tried around to change and reselect the Glyph Mappings from the list, and it correctly "enables" and "disables" the specified keys in the Input History. Thanks for addressing the issue. I will close this now.

Rows
Columns

[bug] glyphs get half overlapped in history feed #2