StrikeTrigger

I am also noticing that the MIP light in the PCN which is not supposed to be functional (data cartridge inserted) is permanently illuminated. Maybe due to this now no data entry at all is possible? All missions of M-2000C now manual entry of coordinates is impossible for alignment, not just the training. Anyhow thanks for the workaround, with Waypoint 20 it's working. Also I'm now noticing that the PCN only accepts data in XX degrees YY.Y minutes format and not XX degrees YY minutes ZZ seconds. So I put seconds in fraction of 1 minute, right? So 41 deg 36 mins 45 secs will mean 41 deg 36.8 mins to be entered? Because BUT 00 is auto-set at 41 deg 36.4 mins.

I just want to confirm, the 2.7 stable requires 8.1 or higher, however does the 2.7 open beta also require that or does it allow running on Windows 7? Since stability is not a priority for beta and DX11 is used. I'm not in a position to update beyond Windows 7 due to work reasons.

I'm probably necroing but this is happening for my Su-25T as well. I was playing the training mission for CCRP bombing and one landing was slightly botched up. My tyres are intact but bent, this causes my plane to veer left at all times. However requesting repair never fixes this. Rearm/refuel is fine. Minvody is my base (it's the default RTB base anyway). The RShift + RCtrl + Tab to respawn also does not work.

SAAHS bit check still not happening? I hit the button in the BITS page and the highlight disappears and the training even continues, but I didn't see any indication that it was conducted.

This. Plus The Rafale and the Gripen.

There is a pocket guide that just lists the sequences to do during preflight, takeoff landing and so on. But a proper illustrated cockpit description and flight manual is not present, like they have for M2000-C, also made by RAZBAM. Can we have one any time soon? I am having difficulty locating various gauges and indicators that the instructor is referring to all of a sudden.

Don't want to get into Open Beta, at the same time DCS modules are complicated enough that I'd need some handholding with comprehensive training chapters. Guess I'll have no choice but to uninstall this one, good thing I chose Hornet over this when the sale was on (both cost the same). Any particular reason F-16 tuts are open beta exclusive? The software updates can wait till stabilization, but a mission created cannot be that buggy, right?

+1 and not just for this module... Just allow assigning a key to let the text go away.

Why so, even though the actual product is not beta-only? What crime did stable users commit to be kept out of this? JF-17 I could understand since the whole thing, even when paid, is beta exclusive. This one even installed on my stable copy, the missions also start, just I'm unable to control a warthog because of the activation thing. Does ED just want people to use beta more and as an incetive give free trials on beta only? Then why keep the stable version and call beta a "beta"?

You know, one with all the maps and legends of all the airbases like they have for Caucasus aerodromes. Also is it mentioned for Su-25T what are the airbase IDs? Su-25T manual has them for Caucasus but not other maps.

Did anyone else notice that after starting up one engine in the pilot cold start tutorial the aircraft slowwwwly keeps sliding backwards? In spite of parking brakes on? Is this normal? :lookaround:

Then why is the tutorial expecting me to check it? I just get a weekend to test it for free and given complexity of DCS modules I will barely clear just the tutorials before it expires. Not enough time to even decide whether it's worth buying given it always gets the least discount during sales (finally got Persian Gulf and F/A-18) and I'm running into broken stuff in the very first cold start tutorial itself... Please fix the module or the tutorial.

Okay... And no resolution thus far? And to avoid confusion, in flight if one of the engines fail, which engine control/display gauge will correspond to which actual engine?

I tried to do the freebie Su-25T CCIP bombing tutorial with these on. I even selected to "use these settings for all missions" but nope, fuel keeps going down and bombs don't reload when launched. I repeatedly have to fly back to an airbase nearby (compared to which a restart is faster). Can't these settings be applied for tutorials?

I just went towards the TACAN selected heading at very low speed and got into within 10 nm, after which I checked out runway shape and then maneuvered to visually line up with the runway heading, hoping I'm not taking the 180 degrees opposite heading XD Later on I just started checking the Caucasus aerodrome chart to figure out the right heading for my runway.

This is exactly what I'm expecting. In which case, they need to do the exact same thing for INS update. When you update, displacement vector between actual wp and your position is the drift that need apply to all waypoints in the course.

I don't really understand DCS SDK coding but can it be really that difficult? Basically the PREP'd waypoint lat/long has to be copy-pasted directly into current aircraft lat/long position, as soon as you hit the rec button, that'd be all it's gonna take. After val, all waypoints as recognized by INS get shifted by the same offset vector w.r.t. flight plan wpts as the current deviation between your PREP selected flight plan wpt and your set position for that wpt (provided perhaps your rec value also has some minor error). Now for radar correction it can be a little bit more complicated, depending on where the radar diamond is pointing and distance to that point.

Also apparently the glideslope an heading are inversely placed in the INS even when properly setup. In the ILS tut, when I'm checking airfield waypt in the tutorial, it shows 3 and 310. Presumably 3 is the glideslope (as per aerodrome chart also) and 310 is the heading (?), but when modifying, it treats the left value as heading and right value as glideslope (left value allows for 3.1 digits, right value 2.1).

Set the radar from warmup to emit (if using English cockpit). In older versions this was not necessary apparently, in the latest version (probably realistically) it is. The voiceover/instruction is not updated I guess.

Yup, even the updated manual page 150 says RD not implemented. But then why the in-game instructor expects me to use and follow it as if it's implemented in-game? Best was not to include in the first place to avoid confusion (and just move on to the next lesson in the mission instead - I need fuel to keep flying lol).

Finally through, thanks for the work. Mirage 2k is the most gamer friendly aircraft so far, especially with the stick control (no other plane has its stick return to neutral position when I pull using the keyboard; it stays pulled... gets worst for the Su-25 and FC3 planes which I can never control properly with the keyboard). There are a few more inconsistencies between the voiceover instructions and the cockpit buttons though, but at least those I can figure out from manual and a few youtube videos. For example the fact that radar needs to be in "emit" mode for radar-based INS update to work is not stated. There is also no "ENC" button anymore to prevent waypoint change. But anyway this does the trick for now, overall I'm enjoying the degree of convenient control this one offers.

Is this pushed to stable release yet? As of yesterday it was still happening for me.

Can we have the tutorial M1 update soon? I recently bought the M-2000C in a sale, but trying to learn it for the first time I can't get past radios because of this. Please at least make the radios skippable so I can finish the tutorial for the time being. Alternatively, is there a way to roll back and use the old version of M-2000C so the tutorial works properly?