bwravencl / controllerbuddy-profiles Goto Github PK

Goal:

The ultimate goal is to add scripts for each target application that automatically apply the necessary configuration changes - i.e. no manual configuration of the target application (axis / button assignments, etc.) should be necessary anymore if the script was run.

Naming and placement convention: each script shall be placed under configs/${PROFILE_NAME}/Configure.xxx

Retrieving the DirectInput instance GUID of the first vJoy device:

• See: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/ee416610(v=vs.85)
• It seems the GUID gets calculated from the device file handle: https://github.com/wine-mirror/wine/blob/a8c1d5c108fc57e4d78e9db126f395c89083a83d/dlls/dinput/joystick_hid.c#L1461-L1462
• Replicating the calculation in Bash will be difficult and error prone, instead we should enumerate the devices via DirectInput and retrieve the GUID that way
• TBD - is it possible to call DirectInput via PowerShell -> https://devblogs.microsoft.com/scripting/use-powershell-to-interact-with-the-windows-api-part-1/

Condor 2:

• The input configs are located under Documents\Condor\Pilots\${PILOT_NAME}\controls.ini
• It must contain blocks for both the keyboard and the vJoy device
• A block begins with [{${DEVICE_INSTANCE_GUID}}]
• TBD: instead of copying a whole prepopulated file, where both GUIDs must be replaced appropriately, it might be enough to simply overwrite the file and add only the block for the vJoy device:

[{${VJOY_DEVICE_INSTANCE_GUID}}]
0=0
1=4
2=20
3=8

• Additionally it must be ensured that the config files located under Documents\Condor\Pilots\${PILOT_NAME}\Setup.ini contains exactly the following input section:

[Input]
ForceFeedback=0
AutoRudder=0
ReverseRudder=0
StickTrim=0
MouseLook=1
LeftButtonForMouseLook=0
AileronsNonLinearity=6
AileronsRatio=10
ElevatorNonLinearity=6
ElevatorRatio=10
RudderNonLinearity=6
RudderRatio=10
StickForceSimulation=4
PedalsForceSimulation=4
ViewSmoothing=3
StickCenterWithHandOff=1
VerticalViewCenter=0

DCS World:

Perform the following steps for both the DCS Stable and Open Beta config directories:

• Copy the config files to their target locations (can be derived from source filename and instance GUID)
• Create / modify the Config\Input\disabled.lua file (should contain all present input devices except vJoy device)

Falcon BMS:

• Locate the BMS directory via registry: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.37\baseDir
• Enumerate all DirectInput devices
• For each input device create the appropriate XML file under Falcon BMS 4.xx\User\Config\Setup.v100.${DEVICE_NAME} {${DEVICE_INSTANCE_GUID}}:
  • vJoy device: an XML with the default assignments
  • all other devices: an XML with no assignments