Device sorting and DX button mapping issues.
-
On the 4.36 I was using devreorder to keep my joysticks in order for Falcon(and hide the ones I did not want). But now, on 4.37 that doesn’t seem to work anymore.
For instance, my Saitek Throttle Quadrant is now the DX 800’s or so, and my Thrustmaster Cougar MFD 3 is going to 500 instead of starting at 128.
This is the devicesorting.txt that I have, and added it as readonly. But it seems that, for some reason Falcon is not reading it properly.
Is there a way for me to hide the joysticks I don’t want? (like the duplicate Warthogs, since TARGET is unable to hide it from windows)Checking on the Axes assignment in ADVANCED, it obviously seems to sort out in the order of devicesorting.txt but for some reason the buttons itself does not.
Is this a bug? Is it me? Does anyone know of an alternative like devreorder to make this work again?
{FFFF044F-0000-0000-0000-504944564944} "Thrustmaster Combined" {B351044F-0000-0000-0000-504944564944} "F16 MFD 1" {B352044F-0000-0000-0000-504944564944} "F16 MFD 2" {B353044F-0000-0000-0000-504944564944} "F16 MFD 3" {B354044F-0000-0000-0000-504944564944} "F16 MFD 4" {B679044F-0000-0000-0000-504944564944} "T-Rudder" {0C2D06A3-0000-0000-0000-504944564944} "Flight Throttle Quadrant" {0C2D06A3-0000-0000-0000-504944564944} "Flight Throttle Quadrant" {BEAD1234-0000-0000-0000-504944564944} "vJoy Device" {E401081F-0000-0000-0000-504944564944} "USB gamepad " {0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog"
EDIT:
I shifted the devices and that sorted out one of the problems, now the non hidden devices like “Joystick - HOTAS Warthog” are interferring with the buttons. The Devicesorting.txt looks like this now.
{FFFF044F-0000-0000-0000-504944564944} "Thrustmaster Combined" {B353044F-0000-0000-0000-504944564944} "F16 MFD 3" {B354044F-0000-0000-0000-504944564944} "F16 MFD 4" {0C2D06A3-0000-0000-0000-504944564944} "Flight Throttle Quadrant" {0C2D06A3-0000-0000-0000-504944564944} "Flight Throttle Quadrant" {B679044F-0000-0000-0000-504944564944} "T-Rudder" {B351044F-0000-0000-0000-504944564944} "F16 MFD 1" {B352044F-0000-0000-0000-504944564944} "F16 MFD 2" {BEAD1234-0000-0000-0000-504944564944} "vJoy Device" {E401081F-0000-0000-0000-504944564944} "USB gamepad " {0402044F-0000-0000-0000-504944564944} "Joystick - HOTAS Warthog" {0404044F-0000-0000-0000-504944564944} "Throttle - HOTAS Warthog"
-
@drmagnumwolf Can you clarify – are you using the new Alt Launcher experience to define all this (which will manage your button-numbering and write DeviceSorting.txt etc)
Or hand-managing it all?
Each device can have up to 128 buttons so… according to this DeviceSorting.txt, your Cougar MFD3 should occupy the 384-511 range.
Do you have an old hand-managed key file that you’re trying to import?
It’s not clear to me, what you’re trying to do … and what if anything is going wrong.
-
@airtex2019 Those are all manually managed, I’m not using the Alt Launcher.
On the previous versions I was using this DLL to manage the positions and hide the unnecessary devices https://github.com/briankendall/devreorder. But on the 4.37, it seems, this is not working anymore for some reason.Moving the device(MFD3) into the new position solved one of the problems. The other is the duplicate devices that I never managed to make TARGET hide (Joystick, Throttle and MFD 1 and MFD 2), so having it visible is causing falcon to receive some weird duplicate signals or something. Despite it shouldn’t? Since it would be read on position 10 and 11.(and the DX number being far higher), even though on the controllers setting it pops out button 1000(or something).
But now it is flyable, so I can live with it.
-
@drmagnumwolf Win10 or 11? Core Isolation enabled or disabled?
I know very little about Target or devreorder but I suspect the way they go about “hiding” HID devices, no longer works.
-
@airtex2019 “Core Isolation” partly enabled, “Microsoft Vulnerable Driver Blocklist” is enabled but the “Memory Integrity” is disabled.
Yeah, I suspected as much. But I got it working with the work around for now. If it becomes too annoying I may get back to this again.
I still suspect an user error(aka me) than Falcon itself. But who knows, it is better to ask.Thank you very much for the replies and the attempt to help though.
-
@drmagnumwolf I’m a dev working on the Alt Launcher experience … I know there are some open issues, with how virtual-device inputs show up at same time as physical-device inputs … so, makes it difficult to select axes and press buttons.
But if you do manage to get the “hide physical-layer devices” aspect of your system sorted out, then I’d recommend you give AL a try for managing the DeviceSorting.txt and all the painstaking button-numbering.
-
@airtex2019
Thank you.
I moved the devices around on DeviceSorting.txt. Fixed one problem, but unfortunately Falcon does not hide the devices. I suspect BMS is not actually using dinput8.dll to read the devices but something else entirely, or it is bypassing it somehow and reading the one from windows.I haven’t used the alt launcher in a while, due to the fact it wouldn’t lock the devices as i wished. Has that changed?
I suggest you talk to HomeFries, if you want I can give you his contact. He is responsible for the CTS for DCS(multiple profiles on the fly for the TARGET WARTHOG). I think he will be able to be more helpful than me. As he works a lot on these things, and it will certainly help a lot on both.