Tazz Posted August 10, 2018 Posted August 10, 2018 I'm a DCS noob and recently "converted" from BMS - and I picked up A-10C and AV-8B during the Steam summer sale as an impulse purchase, so please do go easy on me :) So my squadron flies the latest 2.5 beta and recommended me to use the stand-alone version as that one is kept more up to date than the Steam version (though the Steam 2.5 beta version is now in sync I believe.) Right, so my A-10C transfers across nicely but I'll still need to use the Steam version for the AV-8B. No matter, I want to get into the A-10C first anyway. So I spend a lot of time setting up my Thrustmaster Cougar for DCS A-10C (Sim of course) in the stand-alone version, and that looks like this: Sweet! But I also want to be able to hop into the A-10C in my Steam version of DCS (public stable and beta). So I load in my cougar.diff.lua file (the same one I saved my stand-alone controller setup in) and I end up with this: All my bindings have jumped one device over to the "right" and have ended up on my Logitech Driving Force GT wheel instead! :cry: As I'm really not looking forward in doing all that work again and maintaining two different profiles going forward, is there a way to easy fix this problem? Surely it must be some sort of a bug of sorts? At least that's me assuming that the stand-alone 2.5 beta build and the steam beta build of the same build number should be exactly the same game, correct? So why is the steam version interpreting my cougar.diff.lua file differently than the stand-alone version? Am I missing something obvious here?
Recommended Posts