Config.vdf

[Nguyet Edmondson]

Thehidden one is the correct one. The visible one is used as a decoy to throw off dumb users who fell for scam sites back in the day that prompted them to upload their sentry files. It always contains the same content.

The numbers don't really have any meaning. Steam does keep a reference to the correct sentry file in config/config.vdf under InstallConfigStore>Software>Valve>Steam>SentryFile, but if you only have one hidden sentry file then that's the correct one.

To use the PinOne controller with Steam, all you need to do is create a Steam controller mapping and click the save button to update your Steam VDF file or set it up as a generic controller and paste the configuration into the Steam calibration screen. To do this, follow these steps:

Recently, I have gotten reports of a bug in the Steam controller calibration that does not allow the "paste from clipboard" option to work. In order to bypass this bug, you can manually adjust the "config.vdf" file found in "C:\Program Files (x86)\Steam\config" Instructions for this are in the next section below

In case pasting the data into Steam does not work, you can easily add the controller configuration to the Steam config file. Simply open the config file "C:\Program Files (x86)\Steam\config\config.vdf" in any text editor and add the configuration in the "SDL_GamepadBind" section. Once you have added the configuration for the controller, it will look like the text below:

@svnt: you'll have to use gamepadtool

"create a new mapping"

for now pico8 only polls the two bottom-right action buttons, the left stick, and the little menu button to the right. assign those, skip the others. then "copy mapping string", open sdl_controllers.txt from your pico8 home dir (on windows it should be C:\Users\\AppData\Roaming\pico-8 ). paste your string there, save, restart pico8.

I use JoyToKey as a mapper for my NES controller. That way I just map each button to whatever keyboard key I want. Works great and easy to use. I know I could dig into the config but I'd rather have a nice interface that is clear rather than messing around with files in folders...they scare me :)

I keep meaning to write an AHK script to convert analog stick input into 'feathered' keyboard input. Basically use pulse width modulation to simulate analog inputs. It wouldn't work for every game since everyone handles input->motion differently, but it might be a nice start.

@svnt: it looks like you tried to map your dpad to the dpad in the tool, which won't work. your gamepad's dpad is an analog stick in disguise, you have to map it to the left analog stick in the tool. that will work, since pico8 only reads that stick anyway.

hope that makes some sense ;)

If you are running Linux, the SDL Gamepad Tool doesn't work. But if you are running Steam, you can enter Big Picture Mode, map your buttons, then copy the SDL_GamepadBind entry in the config/config.vdf file in your Steam installation directory.

After closing the window the steam gui does not open again after the latest update. The tray icon is still there but i cant access my library the store or anything similar. It only opens up again after deleting config.vdf

On a unrelated note is there a way i can globally change the windows version for wine and proton without doing it from winecfg manually each time? Did not see this issue as something huge enough to make a post over

Didnt do much. I did found the solution on the same wiki page so thanks anyway m8. Turns out it was the new steam ui not working well with the nvidia drivers. Using the old ui with the -vgui parameter or downgrading the nvidia driver solves the issue acording to arch wiki

As of 2016.12.07, ARMA 3 does work using the Nouveau driver with my NVidia GTX 670. Albeit, a bit slow. The game loads maps (and likely other components) significantly faster within Linux versus Windows.

Once you have Steam installed and have either created or logged into your existing account, search for the ARMA 3 game clicking "Games" > "View Games Library" > "SteamOS + Linux" or if you haven't purchased the game, then purchase the game clicking "STORE" just below the top menu bar. The initial download requires 9-12 hours using DSL.

The top root folder for all ARMA 3 folders appears to be "/home/USER/.local/share/bohemiainteractive/arma3/" which appears to contain the AppDataLocal/ AppDataShared/ GameDocuments/. With the exception of GameDocuments being equivalent to the "C:\Users\user\Documents\Arma 3\". (Replace USER with your user name!) This is really nice, as we now have a central location for almost all files, with the exception of the main program files still being located under the Steam root folder.

The following lists the equivalent folder locations for Windows folder locations in comparison to Linux folder locations. Aliasing the folder locations with the cd command within the Bash configuration file is probably a good idea! (ie. cd-arma3, cd-arma3-usercfg, ...)

Workshop content appears to be first downloaded to a temporary sub-folder and then moved to a numbered folder within the same folder. Workshop content (or mods) are then also apparently copied into the main game folder. Workshop content or Mods atypically are prefixed with an "@" sign. (ie. @ADR-97)

Change execute permissions (chmod 755 arma3.sh) and execute the game using this file (./arma3.sh). Do not forget to first, login in to steam. Users would use this solution, if for some reason, they cannot utilize the existing starting wrapper script.

Try running the game manually instead of using the Steam client. This manual execution method is also the apparent method for debugging Steam wine applications/games and being able to specify the extra Wine execution parameters.

First, the Linux ARMA 3 port does not use the MS Windows DirectX method, and requires using SDL2. The ARMA 3 port chose to use Steam Big Picture mode for configuring controllers. First switch to Big Picture mode and verify your controller exists within the Setup > Controllers menu.

If your joystick controller does not show within the Setup > Controllers menu, then find your /dev/input/event device file relative to your joystick and make your /dev/input/event* world readable and possibly writable. (ie. chmod a+rw /dev/input/event15) Restart Steam and navigate back to the controller setup menu and your device should now be found. Also try using the following incantation when starting Steam, "env SDL_JOYSTICK_DEVICE=/dev/input/event15 steam" if you're still having problems.

Since the ARMA 3 Linux port uses the Steam Big Picture mode for controller configurations, as far as I know, this scheme seems to be only engineered for Game Pads and not really meant for joysticks!

Game controller settings are saved to "/home/$USER/.local/share/Steam/config/config.vdf". (You might find others whom have already configured and published their config.vdf controller settings.) You will only get a save dialogue once you've configured most or the required keys. Once you've saved any button mappings, you can likely use games-util/antimicro (and requires Qt5) for customizing or correcting the joystick axis and button mappings within the config.vdf. Another method instead of using AntiMicro for configuring your joystick, starting emerging (or compiling) libsdl2 and break out of the compile. Change to the root build folder containing the test utility folder. (ie. cd /var/tmp/portage/media-libs/libsdl2-2.0.3-r200/work/SDL2-2.0.3/test) Type "./configure" and then "make", should build all the utilities, but you'll just need the ./controllermap utility and can output the SDL2 game controller mapping for use with Steam's SDL_GamepadBind variable. SDL2 game controller mapping definitions can be found here _GameControllerAddMapping or within SDL_gamecontroller.h, further used within SDL_gamecontroller.c. Another tip, once you have the joystick showing within the ARMA 3 Configure > Controllers menu, the joystick may show only within the "Controllers with a Scheme" menu. Disabling this controller within this menu will then show the controller within the "Customizable Controllers" menu. After doing this, the controller will then be detected within the ARMA 3 mapping menus, but only the axis and buttons previously mentioned within the SDL2 SDL_GamepadBind will be detected. (This is as far as I've gotten, and only able to use only one or two buttons and axis. Joystick up axis, left axis, main trigger secondary button, throttle forward axis.) The following text line should be the last line within the config.vdf file.

Also note the config.vdf should be able to handle C style comments (ie. "//" and even '/'), but upon Steam each execution, commented lines appear to be unfortunately removed. Hence, you'll need to manually backup the file instead. As such, this is unhappy hacking for me.

The ARMA 3 Linux port is currently stuck at version 1.42. You or somebody else will need to host an ARMA 3 server using the previous 1.42 version. Per the below references, the ARMA 3 Linux/MAC port may unfortunately never see a newer version.

I speculate having no future version releases for the Linux or MAC ports is due to not having the following features; no BattlEye (anti cheat support), completed joystick support, and advanced helicopter controls. Without these features, many users maybe discouraged from using the Linux or MAC ports.

2016.04.28 Still getting kicked-off Multi-player Linux servers with the error, "You were kicked off the game. (BattlEye: Client not responding.)" I hope the developers realize; without BattlEye and the Linux client version not being up-to-date, there still will not be a huge following. About the only usefulness the game is under Linux, Single player scenarios and using the Editor. In my past experience with Battlefield 1942 and Enemy Territory, there is a demand for these Multi-player games on Linux. They're almost there though, but not quite.

Even after using "-posX=0 -posY=0", taskbar remains visible during fullscreen mode. Try toggling the Configuration > Video > Display size from the largest resolution to smallest, and then back again. This works for me as a workaround, but the workaround incurs some minor additional glitches. (I'm using the DWM window manager.)

3a8082e126