PiedDroit

It's the knob on the bottom left of the HUD console (it's around 15 by default, in meters).

If you pop them only when they are lit, there is a nice animation once they're all gone.

Yep The description isn't very good in that manual. I still think it is a LOC deviation only (as it is currently is RAZBAM's implementation), because displaying a real runway axis in those conditions require 3 additional info: the runway orientation, the distance and the LOC beam width (a LOC beam width depends on the installation, it's not the same on every airport). Alternatively, runway threshold geo position. I didn't see any place we enter the course or the beam width, and the distance to ILS is not displayed either (it looks like there is no DME, since the TACAN is used). This is why the synthetic can only be displayed when a waypoint had been defined. fenetre de guidage can mean whatever you want. Put the aircraft model in the box => put yourself in the glide path. Again, not really conclusive. Also on the same diagram, where the little box is off to the left, the legend says "ECART EXCESSIF LOC", which means "excessive LOC deviation", so this points again to a raw deviation. Dassault is not Airbus nor any Russian manufacturer and civilian aviation is not military aviation. They do what they want, so I don't see how this could be used as an argument. Only a real M-2000C pilot will tell if the current implementation is good or bad, I based my own educated guesses based on my knowledge on avionics and the manual.

Read the real M-2000c manual (there is a pdf), this is how it is meant to be. The dashed line is referred to as the "runway axis, after LOC capture and before GS capture". The little box is referred to as GS and LOC deviations. I believe the equivalent of the FD in this case is the presence of the synthetic runway. On a B737 (or whatever liner), I think the FD can be used because the system knows the runway axis, in the M-2000C that information is not available unless you have a landing waypoint, which makes the synthetic runway available. On the other hand, there is an autopilot mode that can follow the GS/LOC for automatic approach, possibly it could be used for FD as well but I didn't find any reference to it, that would be what you're looking for.

This has been stated somewhere in this forum, iirc backup ADI has it's own gyro, and HUD is using it instead of the SEC mode of INS. edit: found it:

I tried it today (NTTR) and it seems the selector is shifted by one (little bug). A- does nothing 1- corresponds to program 2 in the chart, 2- corresponds to program 3 in the chart, etc 10-corresponds to program 1 in the chart,

MiG-29! It's the sweetest bird ever (and from the other side of the fence). F-16 is not far behind though. So... Both? :D

The prism-shaped glass we see is probably not the sensor itself. Usually the shape of the protective glass is made so if doesn't generate too much distortion on the sensor's input.

The M-61's feed system (drum, etc) adds 300-400lbs depending on the configuration, so it's not as light as you say I think.

I think he only mentioned that the ejector seat was not french made as the rest of the A/C. Here's the quote: Vive La France ! It’s Sexy. It’s French – Dassault make fine aircraft and apart from the ejector seat it pretty much is 100%. Next sentence is: Future-Proofed – The M2000.... Which might have confused you

Wrong thread buddy ;) OP:

Right now I'm flying using this homemade furniture (now painted, with an extension, see last picture), with a 2560x1080 screen, using an IKEA MICKE to support the throttle. Very compact for my small desk area. Feel free to borrow the concept.

Maybe there is some integer rounding error... It looks your stick and profile work fine (I have the same values) , try changing saturation X and see if you stii have the issue.

You can use TARGET's Device Analyzer: - start the profile - start device analyzer - main window will display the "Thrustmaster Combined" output (*) - on the left are displayed the real hardware output values (*) If "Thrustmaster Combined" is not already selected as in the picture, click on the icon on the very top left of the window, there you can select it.

I had this too on one of the axis, I just added a little deadzone at the end of the axis range (adjust "saturation X" to a value below 100, like 95 for example).

LOL I actually noticed your pseudo only after I replied. Then I waited to see if you'd catch the reference :D

threads never die, like the great ancients they wait in the abyss until their awakening.

Using 4 magics was never impossible with the 2000c, but 6 530d is impossible. On your picture the missiles are Mica's (530d can't fit here), the 2000c can't shoot them.

Glad you finally worked it out :thumbup: It was indeed confusing :D

Make sure you don't throttle down below LND power until touchdown, otherwise blown flaps cease to work and you lose a lot of lift. Since flying around seem ok for you and only landing is an issue, I'm confident your stick is not the issue at all. Again, if it's ok for chopper you shouldn't need the deadzone I think (I just mentioned it because you said the stick had a little issue on left, but if this is not bothersome then forget about it) . Read MiG-21 forum for landing tips and redo the trainings ;) P. S. : post a track maybe

Maybe try with a center deadzone instead of curve, if your stick has a jumpy output (if that jumpy output is in the center). Anyway, with all the details you gave, I would guess the issue is simply too low approach speed. Which means that you get assymetric wing stall, which leads to very quick roll :smartass: If you're fine with choppers, there is zero reason why you wouldn't be able to use the stick with fixed wing. Also you said props were OK too (if I remember). So maybe try a higher approach speed (put curve back to 0)? PS: given your sig picture, if the jet you're talking about is MiG-21 then you REALLY need to watch your speed with this thing (and also throttle, to avoid losing high lift systems) :D

Hehe, words of wisdom here :) I started flying those birds recently and almost everytime I got owned, whatever I'm flying (I'd say i had better success with 109, then 51, last 190), I have some experience with IL2 but that doesn't help a lot. It easy to get pissed, especially against veterans so you need to keep cool in order to benefit from those experiences. Give yourself attainable objectives before thinking about air victory otherwise you'll feel you never progress. For example, Level 1: Situational Awareness: manage to avoid being surprised by a bogey in your 6, Level 2: Defensive Maneuvers: try to figure out what works best to shake an opponent off your tail, Level 3: Energy, same as level 2 but with enough left to hope for a counter attack. Etc... I'm currently around level 1.5, except when I encounter someone as green as I am so I can score a victory :D

Yes, exactly, the one with a graph that represents the curve. P.S.: I really think it a setup only issue, I believe your stick is fine as you mention that choppers are OK to fly in DCS.

Can you post a picture of your settings in the axis tune applet? We could see if there is a wrong setting. After that, check in your axis commands section in controls that "roll" axis only has one controller assigned to it. Next step is to validate the axis health: still using the axis tune applet, move your stick smoothly from one side to another and note how the input (on the axis tune graph) behaves: is it smooth? is it going to full range? Is it doing the same thing as the physical stick? Maybe the stick just needs calibration.

Check this https://forums.eagle.ru/showthread.php?t=170126