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
There is the obvious problem: mechanical buttons on these consoles aren't enough to cover all required keybinds. So, we could solve this problem by placing these keybinds as buttons on touchscreen. Here are examples of such buttons:
Voice chat button
Inventory slot selecting buttons (from 0 to 9, this is commonly used for in-game map voting or custom buymenu)
Buymenu displaying button (for mods such as CS 1.6)
Scoreboard displaying button
Player custom decal spraying button
I'm absolutely not aware of how does all things around touchscreen works in engine, but I guess such things could be derived from Android port touch configurations. This would be very good if somebody will help with it. Also this does not seems a hard work for somebody who already familiar with touch configs :)
The text was updated successfully, but these errors were encountered:
Yep, I see this as a problem even on Steam Deck, which even has 4 extra buttons and touchpads.
We absolutely need per-platform global-ish configuration files, so we don't have to ship them in valve folder. This is something that was also requested for video.cfg and <renderer>.cfg earlier.
There is the obvious problem: mechanical buttons on these consoles aren't enough to cover all required keybinds. So, we could solve this problem by placing these keybinds as buttons on touchscreen. Here are examples of such buttons:
I'm absolutely not aware of how does all things around touchscreen works in engine, but I guess such things could be derived from Android port touch configurations. This would be very good if somebody will help with it. Also this does not seems a hard work for somebody who already familiar with touch configs :)
The text was updated successfully, but these errors were encountered: