Despayre

Unless you've deliberately narrowed your radar cone, that looks like you have the Weapons System CMD FWD active, you have to release that with Weapons System CMD AFT before you can change the range again.

Have you played both campaigns by Baltic Dragon? I enjoyed both of those, the second one is for the Nevada map though.

Thank you, no pun intended, but this is a game changer! I'm already tired of manually asking for ground power and air when in the Tomcat... and yes, I do realize, it took almost 10 yrs for someone to show appreciation of your post, but hey! The wait is over! Thanks!

Have you tried this?

Hey! Bravely running away is my best combat tactic, don't knock it!

Have you tried reducing the radar travel? You can adjust how wide a beam your radar goes through, there's a switch on the left side, near the B scope switch, that allows you to narrow your search cone to narrower sweeps, that will get more returns more often (but covers a smaller arc), and should provide a better lock. You can also confirm that your radar antenna is pointed at the right elevation, and after that, I'd probably check to see if you're using the high freq, low, or both. Past that, I think there's also a switch to adjust wingspan size of targets, that should be set to small if I recall correctly. What's the type, range, and altitude, speed and angle of your bogey when you tried this? Is it possible you're just experimenting with a veteran AI, and it's notching you? I think also, if you see a big yellow "B" on your radar,, or a "BROU" in your HUD, that would mean you're being jammed, and that would explain your issue too. As well, if you've turned on your own jammer to the override mode, that also knocks out your own radar intermittently as well. That's all I can think of, hope something there helps!

... and just to throw another wrench into everything, the recently updated M2000-C had a manual that was 139 pages. After the update was released, so was the new manual, 689 pages. *shrug* Sooo... at the very least, Go Razbam!

Ok, I hopped on the Sidewinder server, at Kutaisi, I don't see how you could set the red radio to the ATC freq of 252.50 since it's not one of the presets, but whatever, when I manually punch in that freq on the green radio, ATC does not respond, either on the ground, nor on approach, so, good news, I guess it's not just you after all! (or, worse, now it's "us" ). As a completely unhelpful workaround, try using MP servers that run SRS Overlordbot, you can actually talk to it and it will respond, no need to click on canned options. The Overlord bot has a lot of useful features, and runs ATC and AWACS on most servers that have it. EG of a useful function "Overlord, set tripwire, 40 miles"... it will keep track and let you know any time a bandit is within 40 miles of you. There are lots of other commands you can use too, there's an overlordbot wiki around somewhere... (and yes, I realize that doesn't solve your problem, but it's still much more immersive with the bot).

That's not really definitive. You did it right during single player, and you did something else while in multiplayer, makes the most sense. It's unlikely to be a multiplayer issue, or a plane issue, so that only leaves user issue. (I fly the M2000 on multiplayer just about every week, and have never had this problem). As a suggestion, turn off the "realistic frequency repeater" (I think that's what it's called) in Special, under the options for the M2000, that way you can visually confirm the frequency for both the red and the green radios. Then see if you can find your ATC frequency on either radio (preferably both), and test each that way. I've never had the problem you're having, but I have played some missions where you're told to use a certain freq on red, and if you use green instead, same freq, it doesn't work. I don't think that's likely related to your issue, but maybe... Anyway, in short, it's gotta be a user issue, but without more info, it's hard to come up with ideas beyond that. Some questions that might help us figure it out: 1) What MP server were you using? 2) What airport are you trying to contact/what is the freq you're using? 3) Are you on the ground or in the air when this happens? 4) can you send a screenshot of your "unrealistic" freq repeater when trying to contact the ATC? 5) red radio, or green? 6) if you set "easy comms", does it work again? There might be a clue for us somewhere in those answers... and I'm sure someone will check out that MP server and see if they have the same issue, that will at least prove/eliminate any server causes for this.

If you're on glideslope and have ILS, the Mirage's synthetic runway should take you right in. Having said that, I personally find it difficult to get that synthetic runway to appear, however... the autopilot landing mode is pretty impressive for that, all you have to do is point the plane in the direction of the runway and keep monitoring the throttle (once you're on glideslope). edit: sorry, I just realized that the topic clearly states "no ILS"... so... just ignore all this.

He posted the coordinates... grab a plane with INS navigation, and punch it in. The coords are: 50°00'55.1"S 71°50'51.9"W

Like that's never happened before... how do you think we get the term shanghaied? (also seems fitting for a Chinese jet )

I think that's a really relevant question, cuz I can't find that either.

Just fired up openbeta, decided to try A2A refueling, the mission starts, you're a little behind the tanker... and at some point you'll probably notice the same thing I did... There's no refueling probe attached to my cockpit! I'm at 10,000ft, can someone bring me some jerry cans? I know we can add the refueling probe via the ground crew options, but obvs, that's not gonna work here... am I missing something? (other than a refueling probe!)

"Dr, it hurts when I do this...."... "Well then, don't do that.".

Did I read something about new landing gear somewhere, or am I just imagining they look better now?

Do you use the same curves for pitch, roll, and yaw? And what do you do about X,Y,Z axes?

Ok, first of all, ignore the epic failure on the world's easiest road landing, lol... the oncoming traffic threw me off... ya, that's what I'm going with... but still, here's the question... how does this jet, with no engine (if there were, it should be in afterburner, and you could see the exhaust), no wheels, but still somehow showing 100% rpm, and airbrakes on, in the dirt... roll *backwards* across the flat road? (I do realize, that this should "probably" in no way affect general flying of any kind, it's just not realistic, or does the Mirage have some cool retro-thrusters up front I was unaware of? ) Nope.trk

I just played both (Red Flag was the other one for the Mirage that I ran through) campaigns recently, I can't speak to how they used to play, but I didn't notice any major issues related to the plane when I went through them. The trickiest part was making sure that the radios were always on the correct freq. Even though both radios can be tuned to the same freqs, if the comms tell you to switch to channel X on red, and you select the same freq on green instead, I didn't always hear what I was supposed to. Other than that, I was able to complete all the missions, and I do know that the author, Baltic Dragon is responsive here and maintains them. (I noticed a couple of typos that I posted about, and within a couple days he responded that he would fix them in the next update).

Why isn't it Tomweasel? I'll also show myself out...

Seems odd to have a plane that can't idle without trying to go somewhere, but if that's more realistic, I guess it is what it is... but that still seems ... counter-productive. Oh well, I'm off to map the handbrake to the HOTAS now...

Since the update, I've noticed my fuel flow at idle is 15, it used to be 12. Now, when I come to a stop, and release the brakes, it starts to roll again unless I apply the handbrake. Is there a reason for this?

Thank you for the guide, much appreciated. One tiny issue... There's a typo on page 86. Item 30 on the list is the Ground Start button, however, in the picture, it's incorrectly labeled as "20". (and it only took me 15 mins to figure out why I couldn't find a "30" anywhere... )

It wouldn't be fair to all the F-18's if our plane was just better at *everything*!

Newp. Buddy-lase or JTAC only.