Stardrifter

Oh, that was much simpler than I expected. Thank you -0303-!

I have the latest standalone version of DCS. I originally had the Steam version but I transitioned to standalone recently. I own the following modules: FC3, A-10C, F-86F, AJS-37, and F-5E. In my DCS profile, I see that I have 5 licenses, for those exact modules. I don't own and have never owned the P-51D Mustang. Every time I launch I get the same message: "P-51D Mustang" is not authorized to be used with your account. Please, provide a valid serial number. If I click skip, it tells me "Authorization is valid for 2d 23h 53m. The following DLCs are not authorized and will be disabled", but it tells me the same thing every time I launch. Also, if I provide my FC3 serial number thinking maybe that's what it's from (from Steam where I originally bought it) it accepts the serial number with no error, but the next time I launch DCS it asks for a serial number again. I have run DCS clean and repair commands. I'm not sure what else to try. Thanks!

Okay, so after quite a bit of time spent creating a TARGET profile for the Su-25T, I realized that I have no idea of which executable to use in the target path when creating an association. I tried Lancher.exe and DCS.exe inside the bin folder (I'm using Steam version.) I also tried doing what the TARGET manual said and copy/paste the target from the desktop shortcut created by Steam, but that doesn't work as the desktop shortcut is actually an internet shortcut that calls upon Steam. Anyone know which executable I should be using? Also, I am seeing that the .lua files used to be easy to edit to add the "up" and "down" position of switches, however the new files seem to have no such way to add those changes. For instance, the middle position of the flaps is not technically a "button" recognized by Windows or DCS, so I can't add it in now that the .lua files are different. Any ideas? I'm going to try to find the files that the A-10C uses and see what is different about them that causes them to recognize all of the switch states. I'm assuming they're either older .lua files... will report back if I solve my own problem but if anyone else has already gone through this, please let me know. Thanks! EDIT: So, indeed the A-10C is using the older .lua format which allows for much more intensive editing of switch states such as recognition of both up and down positions. I'm going to read up on how to use this format for DCS World if possible.

Thanks for the replies. I messed around with TARGET when I first got the Warthog and was fairly overwhelmed, but I'll re-approach if because I'll definitely sleep better at night about my purchase with a fully functioning setup. I had a hard time understanding how the program worked, but it seems like TARGET allows you to "define" buttons or switches that DCS will then recognize in the control setup? I will make a project out of it tomorrow. I generally fly only one plane per MP session so that shouldn't be a problem.

I recently purchased a HOTAS Warthog and wanted to play around with the Su-25T. I was disappointed to find that in the settings, there was no way to get the throttle quadrant's switches to work properly (that I could find.) For instance, the flaps switch has 3 settings: Up, Maneuver and Down. The game however only recognizes 2 of those positions (up and down). This is true for all other switches. For instance, I wanted to map my Laser Designator to the EAC switch on the throttle, but it will only recognize the "up" or on position of that switch, not the down switch. So to turn the laser off after turning it on, I have to flip the switch down and then back up. Every switch behaves like this. Is there some way to fix this? I've looked for tutorials and .lua profiles that utilize the switches to no avail. I figured if any game could make full use of the Warthog, it would be DCS.