Problems customizing key commands in options menu; possible Win10 issue?

[The_Nephilim]

Hey Guys,

 

 

We have an issue stemming with Win 10 and HomeFries Profile mostly Razbam planes..

 

 

We had a report thread but was closed too Read only so I am making a new post.. now to explain the problem.

 

 

I will keep the plane to the Harrier, When we load the game the profile gets some commands redded out in the Control Options in DCS and the profile will not work with those commands mainly the Sensor Select Switch Up and Left keys on the AV-8B.

 

 

We found a workaround as explained here:

 

 

 

 

Windows versions after 7 have an unholy pair of features that can cause frustration for people with complicated controller setups. First, Windows 8 and above defaults HID devices to be subject to power management in that items that are not providing feedback to the PC (like the Cougar MFDs) are automatically shut down by Windows. Additionally, devices that are unplugged and plugged in (even in the same port) are assigned different Device IDs by Windows; this is even the case for devices that were put to sleep by Windows power management.

 

The TARGET profile alleviates the power management issue to a certain extent, but since the Thrustmaster FAST middleware creates a virtual device every time you load a TARGET script, the device ID issue may be even more prevalent than the issue of simply cycling USB hardware. The extent of the issue is currently unknown, but its instance in DCS World has been seen on multiple occasions with keyboard mappings to the Sensor Select Switch Up and Left keys on the AV-8B Harrier module.

 

OBSERVED BEHAVIOR

 

This issue appears to be limited to the AV-8B module, and specifically the Sensor Select Switch mappings. While most often the default SSw Up and Left mappings show incompatibilities (displayed by red lines as shown in Figure 26 below), this issue may present itself in other instances.

 

Figure 26 Errors due to Conflicting Device IDs

 

While Figure 26 shows a single line and a non-default keymapping, the problem exists for default keymappings as well. The problem likely exists because DCS has assigned the mapping of this particular controller to a different Device ID than Windows currently has assigned to the peripheral (e.g. keyboard).

 

RECOMMENDED WORK-AROUND

 

Note: the following solution assumes that only the keyboard Device ID is causing issues. If you experience this issue with other devices, please follow these steps for those devices as well.

 

Since the issue is that DCS World has saved a diff.lua for a Device ID that is no longer valid, the solution is to remove the existing diff.lua, then re-import the profile’s diff.lua back into DCS World. The procedure is detailed in the following steps, using the AV-8B Keyboard as an example:

1. Navigate to your Saved Games\DCS\Config\Input\AV8BNA\keyboard folder.

2. Delete keyboard.diff.lua.

3. Launch DCS World, navigate to the Options -> Controllers menu, and select the AV8BNA module.

4. Ensure there are no red rows denoting incompatibilities like those shown in Figure 26.

5. Select the Keyboard column, select Load Profile, and load the keyboard diff.lua for the TARGET AV-8B profile.

6. Save and exit from the Options menu.

 

If the incompatibilities involve the Thrustmaster Combined virtual device, you will need to make the following adjustments to the profile:

1. Navigate to Saved Games\DCS\Config\Input\AV8BNA\joystick.

2. Delete Thrustmaster Virtual Game Controller (root) {Device ID}.diff.lua or Thrustmaster Combined {Device ID}.diff.lua.

3. Launch DCS World, navigate to the Options -> Controllers menu, and select the AV8BNA module.

4. Ensure there are no red rows denoting incompatibilities like those shown in Figure 26.

5. Load the Cougar or Warthog diff.lua for the TARGET AV-8B profile.

6. Re-apply the JOY_BTN30 through JOY_BTN32 as described in the Adding Modifiers section.

7. Save and exit from the Options menu.

 

ADDITIONAL INFORMATION

 

Additional information on these Windows issues can be found in the following forums:

https://riseofflight.com/forum/topic...em-windows-10/

https://forum.il2sturmovik.com/topic...tick-id-issue/

https://www.reddit.com/r/starcitizen...arre_and_evil/

Now we had looked for a real fix but so far have not found one.. I wanted to open this thread in the hopes we can get this resolved one way or the other..

 

 

Please see this thread the old one that was set to read only in the area it was in:

 

 

 

 

https://forums.eagle.ru/showthread.php?t=200083

[The_Nephilim]

To provide further stability, and as a workaround for certain newer versions of Windows which seem to have a mind of their own, BMS Update 1 created a new configuration file: "DeviceSorting.txt" in the \User\Config folder. This file will be created automatically if it does not exist. The new file will list all devices (joysticks, MFDs, boards, etc) which are currently connected to BMS in a specific order.

This means that even unplugging stuff and replugging it won't change the DX button numbers anymore. If you want to change the device order simply close BMS, edit the file with a text editor and copy/paste the lines in the file until they are arranged to your liking.

Once the file exists, it will always be loaded and the order followed by BMS. If you connect a new device which is not listed in the file yet, it will be appended to the existing file without changing the specified order. Missing devices will be ignored. The file simply consists of the GUID and the device name for each device, one device per line. Example: {0400044F-0000-0000-0000-504944564944} "Thrustmaster HOTAS Cougar" {B351044F-0000-0000-0000-504944564944} "F16 MFD 1" {B352044F-0000-0000-0000-504944564944} "F16 MFD 2"

Note: you still have to ensure that all devices are plugged in!

 

 

Now if DCS Devs could do something similar maybe it would fix this issue.. I am unsure if this is what happens in DCS but they did mention how Windows messes with the sorting and that is the issue here too..

 

 

I read the RoF thread and it was a similar issue there and the devs fixed it tho in the game itself..

 

 

I am going to see IF I can find out what was done in BMS to fix the sorting issue..

[The_Nephilim]

Well it seems what they did will not fix my issue an their fix is still not guaranteed to work in BMS either..

 

 

I have done some Google searches and seen a few programs pop up like joyid which did not fix this issue..

 

 

I guess unless the devs come up with something on their end I will have to live with the workaround for now..

 

 

I did see this issue mentioned quite a bit here on these forums but none have ever fixed it..