Warthog Button Mappings Erased in my ED Profile

[Aussiedroid]

Hey there Warthog users,

I'm still new to my HOTAS, working through mappings and doing some testing etc. Was 99% of the way there, when last night I loaded the game and found my profile had lost all the Throttle & Joystick mappings. The keyboard mappings remained along with some of the other settings but every axis and button was cleared. I had not saved or modified at this point.


Has anyone experienced this before? Do you know what causes it?


My only guess at this point is that the script hadn't loaded up properly by the time ED loaded into the game. This might have mixed up the DX mappings and ED just cleared them .. but just not sure. Seems odd at any rate.

Just hoping to understand more so I can try to avoid in the future.

Cheers!

 

[Hempstead]

Sounds like you are running TARGET.

If so, you must run TARGET before launching ED. What TARGET does is that it programmatically unplugs all the controllers you program in your target script and creats a virtual combined controller. If you configure ED with this virtual controller, save, and next time ED can't find it, ED seems to auto remove the "non-functional" mappings. But if you quit ED and launch TARGET script so the virtual combined controller shows up, and then launch ED, all your mappings should show up (as long as you don's change some mappings and save the settings).

The other situation is... If you just boot up and log into Windows, it may take a minute or two before Windows detects Warthog and other USB devices. If you lanch TARGET before all the USB devices your script uses are enumerated, the script might wait for their "appearance." So the virtual combined controller doesn't show up... If you launch ED at this time.... Well, all your mappings will look like they are "gone."

Launching TARGET after ED does not work.

I ALWAYS go to Devices & Printers to verify that Thrustmaster Combined controller is live and well, including testing all the axis and buttons before I launch ED. Lanching the ship w/o the stick working is pretty much a death sentence, short of "combat logging."

 

[Aussiedroid]

Thanks for the reply.

Yes, running Target Script. I thought it might be what you are suggesting, although I am not sure why my loaded profile didn't create the virtual controller correctly this time. Maybe the exe loaded up faster than the profiles did or something odd delaying it or a drop out on the USB. Hmm, still seems odd all the mappings would automatically clear though - I didn't Apply the profile so it automatically updated. Any rate, will have backups moving forward to avoid this. Its good to know to watch out for this