PiedDroit

Most probably the F... It's the one that was in service in the french airforce (traning role only).

They are full open or closed. For landing you should not need them. You can still land with them opened but of course you need to adjust your throttle accordingly, the Mirage can fly fast even with the airbrake extended, so having too much AoA is probably because you're shy on the throttle. When your FPM starts to drift down just increase throttle, keep an eye on it, the delta wing makes things happens much quicker, keep a hand on the throttle ;) Also, if you get too small AoA (without airbrakes) maybe it's because you are coming in too fast, in that case extend the airbrakes until you get almost good AoA then retract them. Happy landing :thumbup:

you won't be able to pull except if everything is firmly attached. You can use a set of pedals that are close together and do everything with one foot (example: CH pro pedals or maybe car racing pedals), by pushing two pedals with same foot alternatively. Or modify one toe brake to have a middle detent and use it as rudder, this is the better option that brings the less strain, but requires a bit of modification. Worth trying IMO.

BOM is an extra unicode character to tell what is the format of the file, unfortunately if the software that read does not understand it, it sees the file as corrupted. Windows' notepad is bad because it adds it without you asking for it (edit: maybe it is not added if you choose ANSI format)... I'll take a look at your settings, BTW :thumbup:

Windows' notepad adds a BOM (Byte Order Mark), several bytes to indicate the endianness of the file.

The list of the beta content was actually posted before release, but this wasn't made sticky so it's easy to miss: Read Zeus' post on first page On initial beta release, what will work, what won't? On 2nd page, this post about IFF: http://forums.eagle.ru/showpost.php?p=2605260&postcount=12

There have been a lot of talks on the subject already.

Use the level autopilot on the SU-25T to trim it (LAlt+3 I think). The autopilot will trim it for you, just make sure to enable while flying straight, it will settle more easily. Other planes have a trim recenter function.

Every feature is important to someone, it's just bad luck that IFF wasn't part of mandatory deliveries. Calling the aircraft useless, and RAZBAM "wrong" for this reason alone is a bit harsh IMO, it is largely outweighted by the benefits of being able to test the aircraft and also give input while it is being refined. As others have pointed out, there are workarounds.

One last trick, calling DX in the script is perfectly legal, this will work too: MapKeyIO(&Joystick, TG1,DX1,DX6); // S3 Pressed only Cannon -S3 Out only MG MapKey(&Joystick, TG2, CHAIN(DX1,DX6)); //Both Simultaneously

This should work, normally you don't need the chain on tg2 but since you can select one or the other on tg1 then you always need to press both on tg2. I use the event viewer of the TARGET editor a lot for testing the sequences, very useful.

I'm afraid you must reassign LAlt+SPC with something else because you will never manage to get LAlt+SPC and SPC at the same time (try it with your keyboard). If you don't want to touch the keyboard mappings, just map first gun to JOY_BTN1, second gun to JOY_BTN6 in DCS, then use DX1 and DX6 (those are default DX buttons for the triggers on the WH) for TG1 and TG2 on the stick and you're all set.

Will try, thanks!

All your radios are always active (listening) and there is one PTT per radio. In DCS those PTTs are also used to switch radio (for game menus).

Yes, the flaps toggle is one the of the button that is not on the virtual controller. Here's how I configured the flaps on the SU-25T for example: // Flaps MapKey (&Throttle, FLAPU, PULSE+L_CTL+'f'); // Flaps up MapKey (&Throttle, FLAPM, PULSE+'f'); // Flaps toggle MapKey (&Throttle, FLAPD, PULSE+L_SHIFT+'f'); // Flaps landing Those flaps have 3 position, there is a shortcut for clean and full flaps positions and one shortcut to toggle flaps. Note that there is no real FLAPM button (it is the neutral position between the UP and DOWN buttons) but the target software emulates it.

If you run target, some buttons of the throttle are not mapped because only 32 can be mapped on the virtual joystick. You have 2 options, don't use target (the joystick and throttle will be seen as 2 separate controllers). Or - use target and configure the non working buttons to send keystrokes (make sure to send a pulse for switches that stay in position like the flaps switch). Option 1 works right out of the box for the A-10c, the throttle and stick are preconfigured in DCS

I'd prefer a less protruding hud console instead of smaller VTB screen ;) This would have the added benefit to make AoA and G indicators visible too (see that other thread on the subject)

I must've done something wrong, my wingman never attacks. I'd be very interested to get a track from you to see how you deal with the BVR part, as I'm really bad with it :thumbup:

Wingmen don't react... I managed to beat that mission only once or twice, by surviving until the merge (lots of turning + chaffs) and shooting them all at close range (with Magics and guns). I never managed to connect a Super 530D without being shot down myself.

Yes, that was my first assumption (although I didn't phrase it that way).

That's exact what it should do, it takes either programming tricks or a problem not to have this behaviour. OP's problem is precisely that he doesn't have this, which is problematic. Just one question, something that slipped, what is that "hold" and why would you need to use that? Keep it simple and it should work. Anyway, it seems you believe that TG1 will be disabled the moment TG2 is pressed but no it will stay pressed, so no need to do anything fancy.

The code above keeps the first button pressed so reaching TG2 will have both buttons pressed (P and Space). What can happen is that the shortcuts involve a modifier which makes the first command not working. Maybe if you post your script here I can pinpoint the problem.

Not a bad question, no (I just didn't see it in the flow of posts...). Are you using TARGET? Here's my code for the A-10, works fine: MapKey(&Joystick, TG1, 'p'); // PAC1 MapKey(&Joystick, TG2, SPC); // PAC2 / shoot

lol do not try that :) better put it that way: is your airbrake on? put it off.

Those are binaries, only ED can do something useful with it I'm afraid. There should also be some text files (dcs.log) in your Saved Games\DCS\Logs directory, they might contain useful stuff. Did yo check your windows event viewer after hard crash (not sure what to look for, you'll have to search)? This might help too: http://www.resplendence.com/whocrashed Edit: the .crash are text files actually, but nothing useful in there