JayDee1974

I am talking about the ARK receiver frequencies you set up in mission editor in the aircrafts config tabs.

The thing is, that when you set the LAND switch up, the yellow needle isn´t showing RSBN, but the selected ADF channel. And if you have not programmed ADF channels for that airport and there is no other NDB in Range, the needle spins. I guess in LAND mode it is more important to show you where the outer/inner beacons are, than some RSBN, so you get guided into the ILS path better. If it is the realistic behaviour of the MIG29, I dont know. But in DCS it shows ADF.

The west directions are only active if there is enough wind from west (6-8 knots minimum). Else the east direction PRMG are active.

Thanks for that clarification. Tested and confirmed it. Would never ever had thought that the map is not showing the plain actual altitude, but something else. Cheers

I was just checking the indicated Baro and Radar Altitude, with the acutal Altitude on the map and noticed quite the difference. The indicated Baro Altitude (Gauge and HUD) with correct Kohlsmann Altimeter Setting is off by roughly 300ft less then on the map!!!!! The indicated Radar Altitude (HUD) is roughly 30 ft less, then actual height, and die Radar Altitude Analog Gauge is completely wrong. But even if I consider the aicraft thinking us beeing lower then a we actually are, the indicated slant range in the HUD should not be higher then the true slant range but lower. But it still is the other way around. And when the laser comes on, there is zero change in the indicated Slant Range, as if the slant range without the laser was already the same, as with laser ON. Something is really OFF here IMO. EDIT: Ignore my findings. Thanks a lot for pointing out, that the map altitude is not the plain actual altitude, but the density altitude.

I am not seeing the same range scaling on my HUD. When bombing it always is clamped to 2.5 range scale. Has anyone else the same problem?

I know that. But it makes no difference. And the higher the angle the less the difference. Laser won´t even sometimes come on, when manually engaged. Here screenshots with laser on. manually calculated slant range is 2.016 and it shows less than 2 in HUD. I used the altitudes from the map to calculate.

Can some please try to also check the bombing slant range? I just took a calculator and the slant range during bombing is always a minimum of 0.1 NM and sometimes more short. That equals more then 100 feet ground distance. I my bombs also always fall short, even though I do the same as mr. Wagner in his video. Here are 3 screenshot pairs. With simple math one can calculate the slant range = SquareRoot of Distance Squared + Height Squared. In one case the slant range was even less then the flat ground distance (1st screenshot pair). I tried with and without Laser On. Maybe I am missing something, I am not the youngest anymore. I also reported this as a bug on the Discord. Also the range scaling during bombing doesn´t work. It always is fixed on 2.5 nm range scale. During Rocketing the scale startes at 12.5 NM. Cheers

I dont see any problems with the rudder at Takeoff and I definitely would not cut the max output. And you need a lot of rudder during takeoff, as one would expect (over 50% pedal with ~35% curve if you dont trim). Of course it is less, if you use trim, becauset trim works different then in real life. In real life you would neeed the same amount of rudder deflection regardless of trim setting, you just would need less force to hold or reach it. In the sim you need less joystick deflection, because of the trim the neutral point shifted. So if you would just not trim for takeoff at all, you would see how much rudder you would actually need. and that is something a really would recommend to use, if you wanna judge the flight model. So dont use trim for takeoff and landing, instead just use "more" right hardware rudder and right hardware stick, so you have feeling about the actuall deflections you need. Only trim during flight when you feel the need to do so. (Just to be clear, this all is just for non Force Feedback Hardware, which I assume is the case for the topic creator) Cheers

Two very important things are reuqired for it to work: - dynamic cargo has to be enabled in mission editor on the farp - when you spawn crates and barrels, you actually have to spawn them with content, else they are just empty and add nothing on unloading to the farp

nullI had those constant crashes on loading into the mission too. Always at world 1 or 2/60. For me it helped to delete the fxo and metashaders2 in the saved games/dcs (or dcs.openbeta) folder. Since then not one single crash on loading into the mission. null