MBot

Thank you RagnarDa, that is great to hear.

My lysbomb don't drop at all. The Fälld Last light is blinking and no weapon is released. The manual is unclear in which weapon mode you should be to deliver lysbomb (I tried PLAN, RR and ATTACK). The manual states that lysbomb could be delivered in NAV or ANF, but NAV + unsafe does not produce any popup indications in game (ANF does).

I frequently encounter various issues in Landing Nav mode. So much that I would not relay trust it in IFR conditions. As these are difficult do document, I try to collect and describe them here as they appear. -Yesterday I made an TILS approach on runway 09 at Ford airport, Normandy map. I was clearly under TILS guidance but no TILS light was illuminated. -Today I made an approach at Beny-sur-Mer, runway 35. Overhead LS in Nav mode. Then switched to Landing Nav, turned to LB1 and made a flip-flop for a short approach. Approaching the landing circle for the short approach, the HUD gave directions to initiate the turn. Flying along the approach circle, all navigation information on the HUD frequently disappeared for several seconds (only the flight path marker and the altitude remained visible). The ADI direction needle seemed to be stuck in the middle and did not react on me tightening or widening the turn. When the navigation information on the HUD reappeared, it was not visible long enough for me to completely understand in which phase of the approach the system though I was, before all was lost again. -I aborted the Landing Nav approach and switched to Landing P/O. As I approached the runway, the runway center line symbol on the radar system seemed to be stuck. See screenshot (sorry for the quality, it was in VR): Note how the waypoint marker sits right in the middle of the runway marker, with the line extending both above and below. A condition which should never appear as far as I have seen in the manual.

In addition, no bombs drop in Level release (PLAN/ANF) at all. Fälld Last light illuminates but no bombs were dropped.

In mode RR/NAV and RR/ANF, only a single bomb is released (low drag or high drag loaded). Also, I am not sure if this is by design, but there are various differences in weapon safety alt (low selected in mission editor): RR/NAV, M/71LD: commanded altitude 200m RR/ANF, M/71LD: commanded altitude 400m RR/NAV, M/71HD: no commanded altitude (freely settable with reference button), low altitude warning light below 150m RR/ANF, M/71HD: no commanded altitude (freely settable with reference button), no altitude warning light I get that there is a difference in safety altitude between low drag and high drag bombs. But I don't understand that a reference altitude can be chosen with one bomb loaded and not the other. Also strange that the safety altitude differs between nav- and radar-bombing.

In addition, HUD and ADI show steering information to the popup point even if you have selected the target waypoint as your destination.

I can't turn off the TERNAV system with TAKT/IN 581000.

Are you sure this is not a placebo effect? I need exactly the same amount of thrust to move the aircraft with or without parking brake applied. Ergo the parking brake does not brake at all. As addde mentioned, a parking brake is the same as the regular brake. It is simply a mechanism that prevents the release of the regular brake, so it should have the same braking power. By the way, the parking brake which is set on per default during a cold start works, so the function is there. You just can't it turn on yourself.

That is also exactly how it works in the game. The problem is even though you can engage the function visually and audible, it does not do any actual braking.

Will bridges in Nevada get pillars eventually?

The 30mm gunpod seems too big.

Regardless of the actual technique employed, the question is should the TV->T0 behaviour differ between trigger safe and trigger unsafe.

According to the mission editor loadout menu, the RB 75 (+launcher) weights 210 kg and the Rb 75T (+launcher) weights 410 kg. Can this be correct? Standard AGM-65 Mavericks have a warhead weight of 57 kg (HEAT) and 136 kg (HE), so only a 79 kg increase. I somewhat doubt that the Swedes could double the weight of the weapon without the performance plummeting (only the warhead was replaced, propulsion was unchanged as far as I know).

After having locked up a target with RB 75 (TV), there is a discrepancy when releasing to T0 between trigger save and trigger unsafe: Trigger safe: Releasing TV->T0 unlocks the target and bore-sights the Maverick seeker. Trigger unsafe: Releasing TV-T0 keeps the target locked. In order to bore-sight the Maverick seeker you have to go T0->T1->T0 again.

The parking brake can be set in the cockpit visually, but it does not actually engage the brakes.

The manual chaff programs do not dispense when putting the switch into INT or KONT.

According to the manual, the time scale to a popup point should be visible even in LOWNAV HUD mode. In game, it is not. Actual distance from the popup point to the target is only about 50-75% to the value entered. If I enter 10 km, the popup point is just 5 km away. If I enter 15 km, it is 10 km. If I enter 20 km, it is 15 km.

It has to be put into the DCS installation. But I wouldn't fly the campaign right now anyway. SAMs and EWR are bugged since a couple of months, which effectively broke all my dynamic campaigns.

There is some conflicting information in the manual regarding route speeds. A: Here it says that that a set speed will apply until a target waypoint: B: And here it says that the set speed will apply until the first waypoint after the target waypoint: And confusingly, the supplied graphic actually shows both variants, which both cannot be correct at the same time: So what should be the correct implementation of route speeds? Also, how would you change the route speed to the first waypoint B1?

According to the manual, the data panel in mode TID output should display various data when holding down the waypoint buttons (current time on LS, TOT on B1-B9). The problem is that in game when you release the waypoint button, the data panel continues to display this data. By the logic of the manual this should only occur during pushing the button down and upon release, the display should return to output [remaining time to take off/flight time/time error] (whatever is applicable). According to the manual, holding down waypoints B1-B9 should display 000000 if they are not target or ingress points. In game they display 051000.

I was wrong on this one. After opening the base again I could see that the cams were still fixed. What I noticed though was that the screws holding the thread for the stick have become completely loose! After tightening them again, the stick is now perfectly smooth again. Let me recap: After using the T-50 for two weeks, I had: -Screws in grip being loose -Cams coming loose -Screws holding stick-thread becoming loose Don't get my wrong, I love the stick and when it works, it is fantastic. But there seem to be serious quality issues.

A little update on my problem. After the situation became worse (I could now feel a distinct bump when hearing the sound) I opened the base again and could see that the roll cam had some wiggle. I tightened the screws, which solved the problem. After putting the base together again, roll was fine, but now I could notice the same on the pitch axis. I opened the base again and could see that also the pitch cam had some wiggle. The screws were already fully tight but I gave them some more. Putting the base back together the situation improved a bit, but after some minutes of use deteriorated noticeably. Roll is still fine, but I can feel and hear a distinct bump on the pitch axis. Edit: Ok, join me live as my stick falls apart. I can literally feel how my pitch and roll cams come looser and looser. Time to open the thing up for the sixth time... *sigh*

What kind of gunpods are these? They look significant smaller than the ones we have in DCS.

Granted, I have been using DCS 2.1, but in my test mission here, SA-6 never engages. Please note how the launcher tracks the target. It does not follow the target smoothly but intermittently with pauses. I assume each of these pauses resets the reaction delay timer, which is high on the old systems (I think about 40 seconds for the SA-6). Probably a side effect of the recent optimization efforts for the ground AI.

Target elevation was just 60 ft, so neglecting.