Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
For example
h - start press
e - sub command
l - sub command
p- sub command
l - extra command (start press + fire start delay 50)
o - sub command
c - sub command
a - sub command
l - extra command (start press + fire start delay 100)
Nice, that worked thank you very much. Now what do I do if I want to nest a touch menu behind this command? Because once I type "camera" for example, I'm going to want to see a menu behind it that has _01, _02, _03, _04, _05, _06, _07, _08, _09, that appends this text onto the command.
Do a release press to apply the layer.
Some games require shift to be pressed first and then the other key. For those games you would add the key as an extra command. Then you would put a fire start delay on the key and a fire end delay on shift that is greater than the fire start delay.
shift
_ sub command
or
shift (fire end delay 50)
_ exta command (fire start delay 25)
I think I might be accidentally causing a memory leak by doing this stuff.
To be fair, I am using steam input in a way that I think even valve would have never foreseen in a billion years, to jam pack it with full on commands that sometimes have over 10 letters being pressed one after another per touch menu input. I honestly wish I could do this in front of valve, this is pretty interesting bug-testing edge case data that they might want to know about.