jojo

Yes, you wanted to establish a cap pattern at FL450 If you fly that high, it's just for straight path. Find me another fighter in game performing CAP pattern at FL450... So flying that high depends on you weight. What was your weapon load and fuel state ?

Hey guys, don't you need to know the thrust to compute SFC from fuel flow ? Then how do you know the thrust at 30 000ft ? Because the higher you fly, the less thrust you have. And the thrust also changes with the speed. So if you are taking bench thrust data, you got it wrong. Hornet has the highest fuel fraction of your test and the lowest top speed.

Like Ironhand. I have a paid license, but it doesn't work with full fidelity modules, only FC3. I provided a YouTube video of the engagement. Each time I played the mission, it did happen the same. The HUD target box clearly follows the MiG-29.

On another forum someone just confirmed the same with F-14. And despite STT lock and missile launch, the MiG-29 doesn’t try to avoid the missile which is targeting another aircraft. Every single time I fly this mission, the result is the same, and I have confirmations by other users on YouTube, Discord and Checksix forum. Edit: I have been able to fly the same mission with F-14B, and I have to admit that the AIM-7M did track and hit the intended (MiG-29 leader). And this time the MiG-29 did try to avoid the missile. So it seems the problem may not be the missile, but Hornet radar which is showing one target locked and guiding the missile on another one. In my Hornet flight I begin to asses the situation in TWS, soft lock the MiG-29 leader, then transition to STT with Sensor Control Switch Right. The target bow remains on the MiG-29. A crank to the left then recommit on the right confirms that the HUD target box is on the MiG-29 and not on a Su-24 behind.

I played it again: Alert 5 mission, Caucasus map (same as before). STT lock before firing. AIM-7M settings: RCS SMALL/ no LOFT. Firing on lead MiG-29A, the closest Su-24 is 3.7Nm behind. The AIM-7M goes on a Su-24 behind, totally missing the MiG-29 which doesn't take any defensive action, not releasing any single chaff. AIM-7M is unfit for duty. [Edit] Correction below

I think it may work properly if used with INS drift disabled. Currently it's drifting too fast INS is under re-work...

It was Su-24 in the background I did replay one of the track and it performed like when I played the mission on the system. But if it’s the only proof to debug and it’s playing differently depending on the computer...this is a problem The problem seems to be in cluttered environment. In the 8 Vs 8 Instant Action mission, the 8 Hornet get consistently slaughtered by the Su-27 and MiG-29. Often IA Hornet doesn’t score a kill.

I thought it was just my "time off" from the Hornet and no doubt that plays a factor, but even basic locks seem to be flakey. Or there's no contacts at all displayed when I can almost see them visually. Take care to elevation control. If you are using an axis, you need to reset it to center after changing the elevation or it will be constant input, and you quickly reach the vertical tilt limit. The real Hornet HOTAS have a spring loaded return to center axis, but appart from maybe WinWing throttle, I don't know any with this feature on the market...

And missiles shouldn't go for chaff behind a "hot" target if "speed gate" was used

Enter the code on UFC, turn it "ON" with the UFC button. Box the option with OSB4 on HSI page.

Even when supporting the AIM-120C until pitbull, sometimes it does strange things close to the target. It's most noticeable with AI on "Ace" level and pumping chaffs at maximum rate. But I'll get back to you when I will have it on track. @dorianR666 Yes, it's the same case I submitted. The missile doesn't track the locked target. The locked target doesn't defend, the Su-24 which isn't locked is defending

https://we.tl/t-INeJOsfNTy Here it is. Alert 5 mission. First one with LOFT option, second flight with LOFT disabled. Both time STT lock before firing at 10Nm. Both time the MiG-29 doesn't defend, it doesn't release any chaff at all and both time the AIM-7 goes chasing a Su-27 behind !!! After a crank a,d recommit there is no doubt, the STT target was the MiG-29 So it's beyond finicky... @pyhgYou were right PS: second time I had to stop because I lost picture in my Rift S headset. The cable is dead: if you're wondering...don't buy this headset !

If it's the review from 2 years ago...yes many updates I'm not real pilot, but there are a lot of things to do with the Hornet right now, even if not totally finished.

What are you talking about ?

Radar missiles in DCS are eager for chaff, no matter what the range aspect. But yes, on that mission, I have a missile going dumb for no reason. Only saw in TacView. No chaff at all !

I disable loft on AIM-7. It's doing more bad than good as far as I'm concerned.

I'm trying to have a little bit of fun on instant mission 8 Vs 8 on Caucasus. At least half of my AIM-7 doesn't guide on launch, even with target at 12 o'clock and 10Nm and prior STT lock. Am I the only one ? Edit: https://we.tl/t-INeJOsfNTy

I’m not blaming you. I just checked the manual installed in the game, and it seems it’s outdated too. So it’s up to you if you want to take up the challenge...

In fact, the radar screen has been partially corrected. When you are in search mode, the PID/ PIC indication tells you in what mode you will lock the target. That PID/ PIC indication should disappear once the contact is locked because the VTB symbols should make it obvious what is the current mode between PID and PIC. But that's a a minor bug and you do have "RWS", it's just the documentation lagging behind update flow See a screenshot of TV report: real PID mode, and search mode picture (book scan).

In real life, the Mirage 2000 stick travel forwards about 1/3 of backward movement: the allowed flight envelope is -3.2G/ +9.0G So the stick displacement per G unit is equal in (the stick moves the same distance for +3G and -3G). But in DCS M-2000C, you need full forward stick, when you try to perform inverted flight for instance, it feels weird, you need to move 3 time more to get the same pitch correction. I think ED did the right thing with DCS Hornet.

Yes, but there is an overhaul of the INS system in progress. So IMHO, until we have a notification about the release of the new system behavior, it doesn't worth spending too much time on it.

The dashed line has never been reliable in DCS. Waiting for re-work, it's better to ignore it currently. And overall there is an upgrade in progress on INS system, but that introduced some bugs. It's better to disable INS drift in Special Options to minimize inconveniences...

I hope it's rather 2 steps forward and 1 step back

For now, just disable INS drift in special options. It isn’t realistic, but the drift rate isn’t either.