You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you push say A button or Select with most controller overlays, there's an indication that the button was pressed (e.g. the button becomes brighter), but that's not the case with most controller overlays, where the d-pad remains the same even when you push the d-pad buttons. There are a few exceptions (but they have bad contrast between pressed and unpressed buttons in general), but the most usable ones are affected by this bug/deficit.
The text was updated successfully, but these errors were encountered:
yeah, the problem is that most of the dpads look very bad if you try to slice up the directions into separate png images, so they keep them as one big image and then use invisible hitboxes for the actual directions.
When you push say A button or Select with most controller overlays, there's an indication that the button was pressed (e.g. the button becomes brighter), but that's not the case with most controller overlays, where the d-pad remains the same even when you push the d-pad buttons. There are a few exceptions (but they have bad contrast between pressed and unpressed buttons in general), but the most usable ones are affected by this bug/deficit.
Hi, you can try my recently added RGPAD, it doesn't have this problem.
When you push say A button or Select with most controller overlays, there's an indication that the button was pressed (e.g. the button becomes brighter), but that's not the case with most controller overlays, where the d-pad remains the same even when you push the d-pad buttons. There are a few exceptions (but they have bad contrast between pressed and unpressed buttons in general), but the most usable ones are affected by this bug/deficit.
The text was updated successfully, but these errors were encountered: