STORE COMMUNITY ABOUT SUPPORT
login | language
简体中文 (Simplified Chinese) 繁體中文 (Traditional Chinese) 日本語 (Japanese) 한국어 (Korean) ไทย (Thai) Български (Bulgarian) Čeština (Czech) Dansk (Danish) Deutsch (German) Español - España (Spanish - Spain) Español - Latinoamérica (Spanish - Latin America) Ελληνικά (Greek) Français (French) Italiano (Italian) Magyar (Hungarian) Nederlands (Dutch) Norsk (Norwegian) Polski (Polish) Português (Portuguese - Portugal) Português - Brasil (Portuguese - Brazil) Română (Romanian) Русский (Russian) Suomi (Finnish) Svenska (Swedish) Türkçe (Turkish) Tiếng Việt (Vietnamese) Українська (Ukrainian) Report a translation problem
I've been trying to find the default binding file and edit it, but I'm not sure where I need to modify. Any ideas?
If I ever get steam to work in Linux again (or somehow manage to get debug/terminal output from steam in windows) I'll probably continue to develop this guide further.
I've actually never heard of volatile the game! Once in the dawn of time I chose this username cause I liked the volatile pragma used in the programming language C.
In "title" it's possible to call context layers e.g.: "title" "#Chat" in Big Pitcture, instead of just "Chat", (just "Chat" will only work with original set name "preset_1000004" for some reason). Last but not least, when creating a layer, if you wish to overlap the parent layer for joysticks, trackpads, etc... I think it's good practice to dispose gameactions as follows:
"child_name" "parent_name action"
inside the "child" group, will work only if the layer isn't related to a different "virtual mode" than the "parent". I'm still not sure what is a "virtual mode", but I'm guessing it's the same as what I called "context layer" but for layers and sets.
Thank you so much, Volatile, one more time. I wonder if you're related to the developing team of Volatile the game.