Dusk

Did you read the response from Sabre-TLA Seems clear to me. Compensation has not been mentioned up to this point. Do you have a different interpretation of the above comment? Of course things may change.

Thank you for your clarification. Purchasing through the ED store is the best solution which I fully support ongoing. I understand that ED do not wish to do a key exchange for existing campaign user :( Please do. Understood for my current system and correct me if this is wrong, but after the year (given your quote regarding re-assessing the situation) if I update my PC hardware, say 2018, then my only option will be to re-purchase the A-10C package via the ED store. This will be an expensive exercise as I have the full A10-C campaign package :( Will certainly purchase further campaigns via the store, look forward to them being available.:) Agree it's the 'cleanest' and best solution going forward. At the end it's a sorry situation for existing customers whom have supported MapleFlags, but as they say 'se la vie'.

That's in the present and understood. My question is that the statement would suggest that they will no longer support the SUID/Keys after a year. Now if this means the software support will finish that's fine and understandable, but if they will not issue new keys on a hardware change after one year then that's a different matter. Just would like clarification from the 'horses mouth' so to speak.

Have all the A-10C missions and congratulate you on them, have proved to be very useful in my learning. Can you clarify the above point regarding support of the SUID/Mission key system, if I change my PC after the year has expired will you no longer accept a new SUID to issue new keys?

Are you running any mods like Reshade or SweetFX, if so try disabling them and see if it works. The inactive will change to active once you complete your first mission.

Also pre-purchased NTTR in September, but when I click 'get serial number' it says you don't have any serial numbers for this product? Any advice appreciated.

Lol, good point :doh: But in my defence it was the 'on par' bit which made me think twice about it.

Have successfully upgraded to 1.5 from 1.2 :thumbup: Would you then suggest keeping 1.5 open beta as a test platform for future updates? Thanks to the team for your great work.

Thanks for the clear explanation. What I tried was to start with the switch in the middle position and then switch it forward (JOY_BTN23), but it would take 3-4 switch actions (back to middle and forward again) before the switch would be recognised in the Add Assignment Panel, the same for switch back (JOY_BTN22). Regardless the landing gear in sim did not react to the switch being used on takeoff or landing. I’m relatively new to DCS and though I know what you mean by the LUA files, I do not have enough experience yet to understand how the LUA files are structured or which files are associated with various functions. Need to learn more about the scripting language :music_whistling:

In the French version of the flight manual the first thing it mentions should be turned on (Marche) are the BATT, TRN, ALT1 and ALT2. So it does seem odd that that is not mentioned first in the procedure.

Ended up doing the same, but really wanted it on the FLAPS button. However it just doesn't seem to want to map to it correctly. Maybe to do with the fact it's a 3 position switch.

LShift+B / LCtrl+B do not seem to work. Pressing B on it's own will raise/lower the airbrakes. I have assigned JOY_BTN8 to 'Airbrake' on my HOTAS throttle and it works fine. Hope it helps.