Quip

I've been trying to figure out how to succeed in Mis 2.2 (IFR Nav). As soon as I get into the zone W (yeah, I've looked in the mission), which is just before the marker, I get a mission failed. I don't seem to be able to turn on flag 4 no matter what, and honestly I don't see how I could. Flag 4 requires 5 minutes of flying with flag 3 ON, which has not happened since I'm at takeoff, or that I reach another zone a bit into the mission, inside zone W. Have you really been able to complete mission 2.2 dated 2020-09-13 21:12? If so, I really don't see what I'm doing wrong. Also, as a side note: I don't understand why zone 10 is to the west and zone VOR to the east, since it looks by the triggers that we're expected to hit these zones in the reverse order. But this might just be me missing something. Regards

I think I showed you this already Palten, but in case you or I missed it... https://docs.google.com/presentation/d/e/2PACX-1vRZJOoR_6NxKpN1AwQPeal8fHJ1V9poCUxI2-SX--rKqJNlBxgN7Nnl8AUAFfgX7RbhsaDJBE5Ctfqj/pub?start=false&loop=false&delayms=3000

It's a Swedish missile: passive aggressive. Normal

That's a third thing in fact (I think, if I understand you correctly). So here's a scenario. 1. You have a cartridge with the only runway in it (Swedish military bases at the time had only one runway and never two in parallel!), let's say it's a 09-27. So you load it and the pre-designated runway was the 09. But now you need to takeoff and due to "things"... 2a ...you need to change to 27. In this case you just go to Bana/Gräns (runway/limit) and you press LS once more to switch to 27. In fact, you don't even need to do this as when you start rolling, the automatic reference point update which is made between 100 and 200 km/h will notice if the runway heading is reversed. Or more to the point: it will expect the runway to be the reverse one (27 in our case) if the actual heading (compass) differs from the supposed (BANA) by more than some 40 degrees. So as long as you're on the same runway, you're fine even if you don't manually change the runway heading 2b ...you need to takeoff from a taxiway with the heading 110. In this case you *need* to enter the correct heading in BANA (runway) manually. If you don't the automatic fix will completely mess up everything. Since your heading 110 is "close enough" to 90 it will tell the system "this is 90" and your navigation will be off by +20 degrees. 2c ......you need to takeoff from a taxiway with the heading 180. In this case you *need* to enter the correct heading in BANA (runway) manually. If you don't the automatic fix will completely mess up everything. Since your heading 180 is not close 090, the update will tell the system "this is 270" and your navigation will be off by -90 degrees. So if you've landed at a random airport, not only do you need to do the NAV-BER-LS-NAV dance, but you must also make sure you have the correct heading setup. If you don't the auto reference update during take off will mess up your navigation. Now an important point: If You *don't* do the "dance", then the system isn't in take off mode and won't do the update. This is why it doesn't matter to most sim-pilots. As far as teh CK37 is concerned, you have only flown at 0 km/h and at 0 meters for a while. The HUD (as per your question) doesn't show any of this. This is something you can tell from the yellow marker on the CI/Compass. During take off the HUD shows you three different displays: 1. the correct rotation speed (which switches to) 2. the correct climb attitude (with or without burners) (which switches to) 3. and the correct time to retract gear (which no one ever cares about in real life). This is what the NAV-BER-LS-NAV resets.

I will repeat myself one last time: NAV-BER-LS-NAV resets the CK37 and HUD to its "Take off" configuration. It's *the way* to do that, and the only way to get the HUD to display its take off mode once again upon landing.

No it doesn't. We're not talking of the same thing. The system is built as I explained it. If you want to get the "take off mode" on the HUD you need to to the BER-LS-NAV thing. There's no way around that. This is also the only way you can really setup the NAV system to accept a different airport/runway heading if you relocate. Now, it's not game breaking. You can take off without the HUD setup to display the rotation speed and the correct climb out angles. However, to use the plane properly you can't land and take off without BER.

After a landing you need to switch BER, select LS as waypoint and back to NAV to setup the plane for take-off again. So that trick is a no-go.

I don't think so. I think the push to Stable was done to aid in selling the Super Carrier to a wider audience.

I reported this during the LOMAC beta. They also know all this during pitch black darkness and through overcast.

At least we've got a stable result.

It's "Already reported" because ED know of the bug in OB. That this was the first time it got reported for Stable doesn't seems to matter. That's not how ED work with bugs I understand now. Rather, don't work. My bad.

"Already Reported"?? It sure wasn't reported for this version of the game (Stable 2.5.6.49798) when I posted. It is reported for the Open Beta yes. But that doesn't make it already reported. I fail to see how making something new "already reported" will help... Alas, I digress. Just get it fixed.

This is in fact why I don't support ED having the whole OB vs Stable ordeal. Proven fact: Reported Backwards compatibility breaking bugs (regression testing) in OB don't get attention and are pushed through to Stable. This is not an accident. This is lousy quality control management.

OK, so the bug is there in "Stable" too. See attached mission. This bug is an effect of the new and improved path finding. This will break TONS of missions out there. And what's really needed is a way to make aircraft not taxi on start. Make them "hold" at runways etc. In my opinion, this is a game breaking bug. And I know it's been reported several times in OpenBeta, so why was Stable released with this in effect? test.miz

Guys I haven't seen this previously, so I created it. This is a simple "Tutorial" on how the AJS FR22 is integrated with the Mission Editor and/or the flights that occur in the mission. Hope this helps someone. But the TL;DR is that for this to work (it does) the mission designer must really be on top of the flight names in the mission.

The system is the one developped for the Harpoon (originally for the oh-so-naughty

It depends on on-set. The airframe is strong enough for 12Gs. Both in real and in the game. But you can rip the wings off at 8G too if you don't manage the on-set

Hey I've yet to play with the Group radios in the AJS, but now that I get started I have ran into a problem. Someone maybe has the answer... When I look online for how the Group radios are supposed to work, the Kneeboard is to show the different flights and their corresponding radio groups, such as

Really, no one else?

DON*T DO THAT! I love the fact that you 1. built the limitations of the game into the mission (I'll explain what I often do) and 2. that we don't have them in the pitch black night mission. I often tell people when they fly with one or more wingmen that if the wingman doesn't know how to do a certain thing you just treat that like a systems failure; "I can't use the Mav's properly on the AV8B" = "OK, Two has a Mav malfunction, what do I do now?". It help relieve the stress from everybody flying the mission to always know how to do everything, it allows for learning and it keeps the mission going.

Also don't be sorry. It's fine, it's not important. :) I can live with the problems. If need be I'd edit the log file.

There are more problems related to Banshee 3. Once the mission is over, no one really returns to WP6 and 7 (Truck stop), so the debrief never happens. This means I'm not able to contact approach either so I get stuck. I would really suggest you skip Banshee 3 as real AI and replace them with scripted Flares in Zone... Here's my current mission. Look at the "game time". I *just* got the debrief. Look where Banshee 3 is hanging.

Hey So in mission 7 there's a big problem. When I reach WP4 and report on station, Banshee 3 is supposed to drop flares over the enemy positions. The problem is that they go back to WP1 before starting their attack, so I have to wait for 15-30 min for them to get the job done. I have reflown the mission several times so I know it's not a fluke. See images.

Lately I've ran into a problem quite often. When I hit the cockpit, I don't get the "Blue cross" mouse cursor. The mouse still works as I can hover over button and make them work. Also I do get the "White dot" cursor for the comms menu. The issue is there in any module. I'm on Stable. Only solution I've found is to restart the game and hope for the best. Anyone else? I don't think I'm alone. I have searched for quite some time and I see several similar reports from years back, but never any official confirmation or work-around.

Hey Twice in my attempts I've run out of fuel going home/chased by the F-5's. Ironic. But I feel the mission is a bit long for the MiG-15. Even if it's doable it'll be way past minimum reserves as far as I'm concerned. The problem as I see it is that I get all the way to the last waypoint in the canyon and maybe even a bit past it before I'm let in hot by the AWACS. I tried once doing the run in at full speed, and once holding 800. Maybe something to consider?