Shively

You guys spoil us, you know that?

Ditto on this one.. mine's out of action so far as the fishbed's concerned right now, as well. Update's looking good otherwise, can't wait to see what's in store later on.

Will try this in a bit, wouldn't this cause problems with server integrity checks once they're reinstated though? Probably not an issue for the time being however.

That's all well and good (and massively self-gratifying for you, it appears), I just want to be able to fly the Mirage (already massively gimped against Blufor's F-15, what with its mediocre range on the Super 530D and its own slew of radar-related issues, until it gets WVR) alongside my friends on Red team, though. We're a MiG-21-based unit, so this change would normally be absolutely SWELL for us, it's just that the MiG-21's radar has been broken for over a month now and has kind of collectively sapped our will to fly the module. Even with GCI support, it's entirely possible to be in the right position, staring down your radar scope, and be absolutely blind until you dive a bit more, below a target you were already well enough below for the radar to be able to detect. Time you spend searching for a target during an engagement is time you in which you can count yourself effectively dead, and the MiG-21 was already dying a lot to begin with. MiG ops aren't particularly enjoyable for us right now. We aren't holding our breath and waiting for it to be patched by the time Blue Flag starts, because we like being alive. Now we're going to be having to choose between the MiG-21, MiG-29, and Su-27. You know, maybe I want to fly something that isn't either dysfunctional in combat or FC3-fidelity "simulation?" Let's not forget that even with the MiG-21bis being exclusive to Redfor, it still only ever gets like, two, spawns per airfield, meaning my unit, were we to use the MiG-21 is going to be perpetually wasting time in order to coordinate with each other, always having to fly varying distances to reach objectives, possibly needing to refuel and rearm along the way, if we ever want to field more than two Fishbeds at a time. In short, I really would rather fly the Mirage if everything about the MiG-21 is going to be suffering for my friends and I during this event. Got it?

Given the recent changes to air-to-air weapon availability and the as-of-yet unexplained changes to MiG-21/Mirage availability, yes, it very much does seem like that. You can keep the AIM-120, just let me fly Mirage on Red (or MiG-21 on Blue for anyone that's a bad enough dude to gimp themselves so terribly by choosing an outdated plane with a semi-dysfunctional radar), or else there's going to be more R-27ET coming your way, Blue. I desperately don't want to have to fly FC3 aircraft or relegate myself to air-to-ground only for the next week or two. Please don't make me do it. If you want to make this change, at least wait for the MiG-21bis' updated radar system to be implemented, hopefully by the time Blue Flag 7 runs. Right now it's just too broken for the Mirage 2000 v. Mig-21bis matchup to ever approach being "fair," not that the two planes were a fair match for each other to begin with. Maybe if we had the Mirage III or 5 instead. If Blufor wins Blue Flag 6, it won't be because of superior strategy or pilots, from the look of things.

I'm still trying to get the faction restrictions of MiG-21 and Mirage 2k undone (or at least explained), respectively. Seeing as I registered for BF over a month ago and can't read much of the Buddy Spike forums because no one ever got around to changing the status of my account there, would someone mind explaining to me the rationale between giving Blue the Mirage and Red the MiG-21, when previously both planes had been available to both coalitions? I'm more than a little in the dark here, seeing as the change hasn't been explained (or mentioned, really) anywhere in these threads. This would possibly approach realms of "fairness" and balance (okay, it wouldn't, the capabilites of MiG-21bis and Mirage 2k in a dogfight aren't at all quite evenly matched for each other) if the MiG-21bis' radar was functioning as intended. It isn't, however, and despite the Leatherneck bugtracker having claimed this issue to be fixed in the past, has been broken for a month now and doesn't seem to be getting resolved any time soon. Couldn't we just keep both factions being able to use both so that people who want to fly a certain non-FC3 module aren't restricted to playing on a team that likely won't even contain any of their friends/squadron mates? Do we really need to be in the business of fixing things about Blue Flag that weren't broken to begin with? Unless, you know, you plan to take REDFOR aircraft from Blue team, which would be devastating to the balance situation (and everyone would rightfully be confused about this change). I'm assuming the reason Mirage 2k went Blue only and MiG-21 is Red only doesn't have anything to do with coalition/real-life availability for this reason.

So wait, us Red players are stuck between choosing the Su-27 and a plane with a dysfunctional radar scan arc? Well, that seems perfectly fair and balanced, don't you think? Both factions should be allowed both planes, unless you're trying to game this event in the favor a certain team. In which case, go right ahead, just don't expect people to thank you for it. Yeah, I assume that's the same reason the Su-25T and Ka-50 are on Blue and the A-10C is on Red. Coalition/plane options were already FUBAR. Changing the MiG-21/Mirage around doesn't substantially contribute to fixing this problem, and only has a negative effect on the current balance of Blue Flag, skewing it in the favor of a certain team that was incredibly vocal after their defeat in the previous event. I wonder who that may be?

Just connected to the server, and it appears there are no longer any spawns at any airfield on red team for the Mirage. What gives?

If you've got the exact parameters of the new cone memorized, by all means, do tell. (Seriously, I'd like to be able to fly the MiG again before it gets fixed). For me it's functionally identical to having a reduced range, just sayin'.

Right now you're basically lucky to get the sapphire to lock from that distance.. But yeah, the R-3R is overperforming. It won't be doing much of that while its necessary guidance tool is functionally kaput, however.

It's amazing to me that you're making this much of a fuss over a change that would return to a situation that gave you a slight advantage, arguably moreso than the one AIM-120C provides over R-27ER. But people don't always argue their own best interests, after all.

Hey, I don't know if this is currently a bug or a feature, but the Mirage 2000 doesn't seem to be having to undergo the same fuel-up process as the Su-27/F-15C. Could very well be that this is intended, and I certainly don't mind, being a Mirage/MiG-21 pilot myself, but just want to make sure I'm not getting any unfair advantages. Is this going to be in addition to Case Blue/Korean Blue Flag variants, meaning there should be 4 versions of the event moving forward if modern and 80's-style BFs are included? Sounds neat.

I'd like to second complaints about the relaxation of weapons limitations for air-to-air engagement, but in a rather selfish manner, as I frankly don't want to be eating AIM-120 for breakfast, lunch, and dinner for the next week or so. That said, if there's Sukhois forcefeeding the enemy a load of R-27ET/ER, I think everything should come out about even. We'll have to see how it plays out in testing and during the event if it's not changed, may turn out to be ultimately a negligible difference.

Did you try hitting the switch, or looking at the other thread posted not even 24 hours ago on this very same topic? http://forums.eagle.ru/showthread.php?t=164813 Otherwise, it could be a bug introduced with today's patch, just double-check that you've got the switch on and in the correct position, as the switches in the Mirage can be a tiny bit confusing, info about proper position of switches (middle generally being the "on" position) is available in the thread.

Did another repair/restart and managed to get it working again. Will make a track if it crops up again. Confirm there's no effect on the starter, not certain why I thought there was.

Yeah, just did a restart of my machine and did a run of the repair tool. Still no joy however. Problem appears to be with the starter itself - I've got the throttle in the "off" detent position now, but I'm not getting any visible depression of the button in the cockpit and no sound effect when I press the starter. Again, I tried to get around it by using the "engine start" keybind, but that didn't seem to produce any results.

Had some issue with my "sync cockpit controls with HOTAS at spawn-in" setting, but deactivated that to do some more testing. At the moment I'm not having any better luck after double-checking my throttle was in the "off" detent. I'm beginning to think I might be going crazy over this one, toggled all the switches in the startup panel off and back on again to double-check and make certain I had everything right, and I'm still not getting her to start.

Hate to bump this, but it seems that this bug is now present in the "stable" version. I'm not certain, but it appears that the engine starter itself is the problem, doesn't seem to be depressing (showing the animation at least) in the cockpit despite going through startup as per usual. Additionally, the throttle is no longer "locked" on spawn-in and unable to be pushed past the "idle" position until the engine is started - could that have to do with the starter not functioning? As noted, the keybind doesn't seem to be working either. I'm assuming auto-start works, but I haven't given that a shot just yet. Have noticed this in singleplayer missions and multiplayer, going to create a new mission from scratch to see if it's broken there too. Edit: Seems like squadron members of mine have it working, however the same startup procedure I was using last night (Left/right boost pump switches up, open up the cover on the starter, throttle to idle and hold starter) doesn't seem to be getting any ignition.

MBot, sorry to bug you about this since you're focusing on DCE right now, but would there be any adverse effects from my removing the "Vaziani Ground Personnel" spawns around the airbase? I've noticed that their patrols can sometimes meander into the taxiway and prevent the AI MiGs from going up while the poor singleplayer goon has to deal with 16+ hostiles on his own. Excellent work with this campaign by the way, and DCE's looking very interesting as well. Can't wait for you to get it rolled out, but don't release it until you're happy with it obviously.

Hey Greg, I'd like to sign myself up as a lonewolf on REDFOR for BF6 or the next event like it featuring modules I can use. Callsign: Shively Pref. aircraft: MiG-21bis, M-2000C, also like the Sukhois from FC3. Own the A-10C and Ka-50 as well but I'm pretty rusty with them. Also nevermind the post count, I've been lurking for months! Will update this post later (or maybe send you a PM/make a second post later if it's been a few pages) if I wind up getting sucked into a squadron that's participating in this, am looking to become more active in multiplayer in general over the next few weeks. Look forward to flying with you guys.