M2K-C issues

Hey there, thanks for the quick response!

Sorry I cannot use the auto-formatting of lists, it resets all the numbers.

Here goes:
2. Well, I remember raising this issue with another jet (Dino's T45-C), and IIRC altering the N1/Mach on thrust table to produce 0 thrust until higher values of N1 fixed the issue. It was a pain to get it right but it can be done!
3. Sure. When advancing the throttle, the fuel flow indicator remains at about 11kg/min up until N reaches 50%. I suspect some tweaking in engines.cfg could fix that too. Besides, fuel flow overall is too small. Typically, low level nav (below 1500ft AGL) is flown at 450 KIAS with FF around 50kg/min; in the sim we get less than 40. Similarly, cruising at .95 at FL300ish gives a cruise in the 35~40kg/min depending on loadout; the sim currently yields less than 30 kg/min. I know how hard it is to get consistent values for this from MSFS!
6 and 7. Well one way of handling this would be to disconnect the cockpit setting from the A/P, eg. by having the cockpit altitude selector feed an LVar, and a custom logic that either feeds that value or the current altitude to MSFS's A/P, depending on what's required. The real A/P has two different modes for altitude hold and capture IIRC (plus the "fly through" mode with the asterisk FPV target), so that would be handy anyway.
8. Um, I wonder how that can work, what with AoA depending on speed too. Having the bird between the brackets does not result in a correct AoA if you're flying too slow or too fast.
9. I wish I had a better source, but the aircraft modeled in DCS has it, and IIRC it was used by the French Air Force at some point, so I would believe it to be correct, but I am not 100% sure. It would make sense though, as the analog AoA display is barely visible from a normal sitting position.
10. As it is the aircraft is more sensitive at lower speeds, which is problematic. I guess the only way it can be alleviated is by implementing custom PIDs outside of MSFS's flawed FBW logic.

While we're at it, let me add:
11. The radio altitude mode selector effectively adds the height information in a smaller font below the baro altitude, it does not replace it. It will show eg. "1500 H" to avoid confusion, or "*****" when the aircraft is too high or banking too hard for the radio reading to be reliable.
12. The fuel logic is somewhat wrong. The aircraft cannot burn fuel directly from the external tanks: she has to burn some from the inner feeder tanks first to make room for fuel to be transferred from the external tanks. This is what the "AFF DETOT" switch is there for: the pilot will manually set the DETOT to the amount of fuel they know to be onboard prior to startup, and the aircraft will then decrement it based on actual fuel burn regardless of how much fuel is sensed on board. Also, the readings on the two vertical gauges don't really add up to the total fuel gauge. For example, if you set the fuel to 28% in left and right main tanks (center tank empty), you get about 800kg total fuel, but the gauges show about 420kg on either side. Finally, regardless of the BINGO setting, the "NIVEAU" alarm annunciator should light up when fuel reaches 2x250kg.
13. The red beacons (both top and bottom) are INOP regardless of the ANTI COLL switch position (the white ones on the fin work though)
14. In what you called the BDHI, "Cv" means "Cap vrai" ie. "true heading", as opposed to all the other functions under a "Cm" arc for magnetic heading. Also, VOR/ILS should not be mapped as a separate mode from TACAN: all airbases have a TACAN, and the ILS uses the TACAN's DME it doesn't have one of its own. Therefore both modes must be able to work simultaneously in order to get proper distance information while on approach. On a side note, the "M/A" knob on the VOR/ILS does not stand for Manual/Auto but Marche/Arrêt (ie. on/off).
15. When A/P is on with AFF only (no horizontal mode), when hand flying a turn, rolling out to 0° bank will have the A/P bank the aircraft (in my case, always to the left for some reason). I can think of no reason for this, it is completely unrelated to the position of the HDG bug, not sure what's going on but that looks like a genuine bug.
16. The FPV suffers from the same weird bug as a few other military addons: its vertical position seems to depend on bank. I was able to put the aircraft in a position where it was climbing and the FPV was above when banking right, but below the horizon when banking left, while still maintaining a positive rate of climb. My bet is there is a sin/cos(bank) somewhere in the code that should not be there. Oddly enough, this also depends on the heading. I was flying at FL350 heading north, A/P holding altitude. I initiated a left turn, the FPV went below the horizon until heading ~300, then above to a maximum at heading 210, then back down again when passing heading 120. When turning right, those variations are reversed. It strikes me that the threshold values are 30° off sign changes for cosine, especially when 30° is the commanded bank angle. Something fishy going on here but I haven't started digging into the code just yet.

Well that's it for tonight, I'm going to grab some shuteye. I know it's a lot, but rest assured that my intention is only to help making this aircraft even better than it already is! <3 I love the 2000 and I'd been waiting for a proper rendition in MSFS for a while now, so thanks for filling that void!
All the best