jojo

Yet AIM-54 are eager for chaffs :music_whistling: (even AIM-54C).

When you contact carrier’s ATC, it will answer you with BRC (Base Reference Course) which is carrier course. So just set that as course on HSI TACAN, and you will be able to reference it for downwind heading and stuff like that. On case 3, +10 because you will align directly on angled deck. For HARM, DCE script destroys HARM in flight to simulate the effect of loosing track, so memory doesn’t have any effect...

Yes, VR is great. Refueling on S-3B Viking, lowering the seat made a great difference for me too. With normal position is barely se the tanker and struggle to maintain good visual reference. A question about the S-3B: does it have a maximum amount of fuel to deliver ? I know a F-14B could dry it down. But I can't go above 12 2000lbs, which must be less than 4 000lbs delivered. (Rift S VR recording) Or am I doing something wrong ? I can't even contact the S-3B anymore after that. It disappear from Jester and coms menu.

In DCE they have a script to simulate SAM turning off radar making HARM to miss. Actually in game, SAM is turning off, and HARM self destruct. IMHO, even if HARM is known to have miss a lot (2000 shot during Desert Storm, 700 over Bosnia), it worse in DCS since it's very difficult to have proper SEAD tactics, and no EA-6B Prowler stand off jamming. But from memory, you should be able to turn off that HARM script in campaign settings. For the TACAN you should set BRC given by aircraft carrier ATC on radio for CAT 1, and final bearing (BRC + 10) for CAT 3 (IFR).

That's why I love "PAL" radar mode. 15Nm range :smilewink:

:lol: Your buddy is certainly good, probably better than me, but I come from the M-2000C, and I think it’s easier with it, much easier flight control, better visibility. Same with the Hornet. Each one his own :smilewink:

It’s a bug. What’s the problem with Viper TGP ? I did try TGP with GBU-12 scoring direct hits... I don’t know for the rest, probably, but we had some nice updates about AA lately with MAV mode for Magic 2, some radar bugs corrections and RDO function.

I will add that Mirage 2000C RDI was tasked for “on call” CAS, patrolling over Bosnia (1994) with SAMP 250kg or Mk-82. I’m not aware of live firing though. Mirage 2000N did perform live attack on military targets, and CCPL is essentially the same (but with Antilope V radar instead of RDI).

Yes there is misalignment. But the bombs will land on the same spot with consistency. Work around is dive between 20 to 30 degrees, aim with top of the diamond, and release at least bombs in pair. Anyway, that’s pretty much what they would do in real life, shallow dive designation is inaccurate with radar ranging in real life too. DCS has its share of the problem with lack of radius damage effect. But anyway, no one expect consistent direct hit with dumb bombs. And yes, Mirage 2000C isn’t Tornado, but at least you can shine above FL200 :D

It's a point since Tomcat doesn't carry only the AIM-54. :smilewink:

Give us your DCS gamma settings and we'll see :smilewink:

I had expectation that "lock enemy contact ahead" would work better. There is a shortcut command,and it would be more convenient to use than Jester contextual menu. But yes, I have to work around that...

My opening post was about struggling to lock a MiG-29 in BVR :smilewink: I'm fine with dogfight modes.

I re-flew the mission using "lock contact ahead" and it did work. But my complain is still that when there is one single contact in the air in front of me, I would like Jester to be more pro-active with IFF. "Lock friendly ahead" (still unknown on the radar indeed) "No can't do" "Lock contact ahead" "We've locked a friendly" No kidding...:D It's worse when you have a single MiG-29 in front of you, hard lock "29" on RWR and Jester making the RWR calls, but won't "lock enemy target ahead" :doh:

I thought that TWS AUTO was automatic after AIM-54 firing from TWS ?

I did cycle between TWS and RWS, until I got shot at by MiG-29 with R-27R and had to break away. But yeah, it drives me nut that we got a 29 spike dead ahead, contact on RWS, on TWS and when asking lock he puts the TWS on tilt limit to the right to scan nothing ! On another flight I was asking him to lock friendly target to rejoim for some formation flight. The E-2C was the only plane flying. "No can't do" I guess Jester doesn't know where the IFF button is ?

MiG 29 head on, 50 RWS. Switching to TWS, still on scope. Asking to STT lock Enenmy ahead...Jester scan to the right, loosing the target !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Unfit for duty :mad::mad::mad:

+1 :thumbup:

According to Flight International article, dated from 02 April 1983, RDI range on fighter size target (RCS 5m2) in look up would be 66Nm, and between 18 to 50Nm in look down, depending on ground clutter and closing speed. Ian Black, former Tornado F3 pilot who did an exchange on Mirage 2000C RDI also rated the radar as good, and I would bet the Tornado F3 has good radar too. Currently in game the M-2000C would detect a big fighter (F-15C/ Su-27) in look up & head on at 47Nm, even if we tune down to compensate for Thomson CSF advertising, I think 47Nm is on the low side. But in game RCS for these fighters is set at 5.5m2, which I think is a low for this kind of aircraft. Bombers and transport aircraft hot aspect will be detected near 80Nm which is OK. If target turn cold, detection range will be much shorter (from memory around 15Nm to 18Nm) The difference seems huge, but it’s approximately the same thing for FC3 F-15C. Would need to test better on more advanced modules. That being said, considering Super 530D range, 47Nm is workable range. M-2000C is best used with GCI support or AWACS. Using SRS on servers like Blue Flag you can have human GCI, and this is great.:thumbup: F-16 head on should be detected at 40Nm...check radar elevation. And I think M-2000C is in much better state on OB currently.

Off course, nobody asked to replace the current behavior, just an option to adapt on widely available HOTAS available on the market. I would be interested to have a look at your HOTAS solution though :thumbup:

I'm short of 4 ways HAT on my throttle :smilewink:

Wake turbulence ruin aircraft and can murder fps. I don't see the benefit of it :music_whistling:

I come back on this. I too feel it's little bit washed on my gaming computer screen and in the Rift S. But I know for a fact that my screen is too bright. I tuned down gamma to 1.8. But from time to time I record some short clips of my flights. And when watching on other screens (like my Galaxy phone, iPad and most of all, a laptop with screen calibrated with external sensor to deal with photography)...at 1.8 it's too dark, while at 2.0 it's perfect. I'm back at 2.0. So if you have to play at gamma 1.0, you should really consider tweaking your screen.

Why do we need ATFLIR ? Because it can track birds in flight :megalol:

With the S-3B, it's really close !