PiedDroit

Don't hesitate to ask for advice, most advanced functions can be achieved in an elegant way, when you know what to use :thumbup:

One remark: you should a different REXEC ID for the rudder trim (it's the same as X's, 0). Looks good to me, good snippets to take example from :thumbup:

For fun, Colomban MC-10? I don't know how racing aircraft would fit in too (Gee Bee R1, AKA "Death Trap").

I usually don't have this issue, contacts sometimes disappear during a sweep but they reappear on next sweep most of the time. Trk or miz would be help if possible.

Even if no one asked for landing tips, this clarification is useful for the initial question :thumbup: This will help OP understand why his FPM is not doing what he wants whatever the airbrake setting he's using.

I think this is taught or repeated "as is" without explanation (or understanding). I tried to fly using those principles without much success too. Only thing I found that could relate a bit to this proverb is that in approach, adjusting power while keeping the AoA helps to fine fune sink rate. And using attitude helps finding the good AoA (and therefore, speed), however while doing that you need to keep adjusting throttle to maintain sink rate. Therefore both are interconnected, use throttle while maintaining AoA to correct sink rate, and use attitude to correct AoA while maintaining sink rate. That's how it works for me... (edit) but you could very well read it the other way as both work together anyway.

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:

No worries, it doesn't take too much time. And if it does I'll tell it. If you are already using TARGET you should be able to use the ministick like I indicated as a temporary solution. However if you don't use TARGET, it means that you'll to have to remap a lot of stuff because TARGET creates a virtual controller which is different from the bare joystick and throttle, this can be time consuming, so maybe it's not so good idea (you probably know that already ;)).

Yes exactly. That code will only work with hotas warthog script editor (you should be able to achieve the same effect with target GUI but I don't know the syntax). If you're using a different stick you'll have to figure out how to do that by yourself, using that stick's software. This method will become obsolete once we have a working TDC axis.

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.

You can use this method until the axis becomes available: KeyAxis(&Throttle, SCX, 0,AXMAP2(3,'j',0,'l')); KeyAxis(&Throttle, SCY, 0,AXMAP2(3,'i',0,'k')); This will split your axis into 3 zones (can be more, just change the number and add more possible values), and assign a button press to each zone.

I don't know about those mappings, probably they were from the base.lua file and were not put in the new default.lua. To switch waypoint, use the DEST button (big yellow square button) on the INS panel. The INS is very basic at the moment, once it is fully implemented we should get a bunch of shortcut that control it.

No, you were right, canopy open/close default keyboard mapping was added in 2.0 update but not in 1.5.2 update. I have attached another modified file that adds the default keyboard mappings that were included in 2.0 but not in 1.5.2: - open/close caopny - engine and flight controls - lights and hud brightness - fire and jettison weapons switch default.lua default.lua.2.patch.txt

Actually, canopy open/close was one of the default keybinding coming from base...lua (that is not anymore included). They added it in M-2000C/default.lua but there is no default mapping for it: {down = iCommandPlaneFonar, name = _('Canopy Open/Close'), category = _('Systems')}, P.S: full patch of the 1.5.2.49392.141 update attached, so yo ucan see what was added and removed. default.lua.patch-of-1.5.2.49392.141-update.txt

I wasn't necessary because those compatibility problems were mostly comming from the inclusion of base_keyboard_binding.lua instead of common_keyboard_binding.lua. Fixed file attached, I tested it with an empty .diff.lua, everything worked. 'K' worked as radar piper down, I suppose you still need to change it or remap "show kneeboard" to have the kneeboard. Mods/Aircraft/M-2000C/Input/keyboard/default.lua P.S.: I added the patch file, you don't need to copy it anywhere, I provide it only to indicate the changes between the current file and the modified one. EDIT2: a better file is available a few post after this one, adding flight controls and other missing default mappings for 1.5.2 default.lua default.lua.patch.txt

I had this too, I just remapped them. Edit: A better fix would be to update Mods/Aircraft/M-2000C/Input/keyboard/default.lua, to avoid filling the .diff.lua with unecessary bindings. Here's what was changed (it's a sample): old: update: The default key was removed, what has to be done is to add it back: fix:

Yeah it's interesting topic. Here in Montreal the declination is -14.5°, nasty ;) Also, not to be confused with magnetic deviation which is the magnetic influence of the own ship, which is (I think it should be) compensated by the instruments so you don't have to worry about it :smartass:

I think the FPM is correct, it's the HUD horizon line that is not (when you turn the HUD horizon is shifting). There was a bug report about it a while ago, try using rudder and the HUD horizon should be affected even more. On your video, when you are level, the HUD horizon line is above earth horizon, but when you bank it is right under it. The HUD horizon line is at the same altitude as your aircraft, so when you are high the HUD horizon line should be high too.

I noticed it too, lateral trim seem to capped to a very small value. It doesn't affect symetrical load but once you're asymmetrical there's not enough trim available to compensate.

:thumbup: one bug smashed! Take that, filthy insects!

This wouldn't be a bug if magnetic declination is implemented in DCS. Magnetic declination is 6° in Georgia, so 40° magnetic heading correctly translates to 46° true heading. Instruments are suposed to show magnetic heading, unless you select Cv (Cap Vrai = True Heading) on the HSI.

Some of the keyboard shortcuts were unset with the update (I didn't modify them, they were default ones), maybe you had this too, try remap them.

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.