Cepheus76

Well, since there is no "Flight Controls, Flight Controls" warning, but the "Fuel Low" warning is clearly understandable, it can be safely assumed that the paddle switch wasn't engaged.

I tested in ST and MT with the Hornet before updating to 2.9.1.48355 and with the Hornet and the Tomcat after updating in MT, in each instance both the break and the pattern mode. Worked perfect for me in all test runs. Thank you for fixing the mission!

I have the same issue.

But you have to allow for fuel burn during refueling, too. Let's assume a burn of 3000 lbs/ h per engine, the fuel consumption during that 9.5 minutes would be 950 lbs. So the fuel transfer rate would be roughly 800 lbs/ min.

I had the interesting observation, that, when doing AAR with the Tomcat, the basket starts to jitter only after making contact.

It is the signal transmitted by the emergency locator transmitter, a radio beacon which helps to locate a downed aircraft and/ or airman. Should transmit on 121.50 MHz, 243.00 Mhz and 406 Mhz (or 406.5 MHz- I am not sure on this one) Some of them are portable, others afixed to the aircraft and I think that the military uses the portable variety.

I usually line up the horizon line on the HUD just inside of the outermost "bird slicer" antenna on the nose. As the aircraft slows down and can't maintain altitude at that bank angle any more, I ease of the bank. This puts me normally between 1.2 and 1.4 nm abeam the carrier/ runway. Turning base with an bank angle of around 30 degrees when passing the runway end should get you on the centreline.

Would be much more fun, if they would get stuck asymmetrically... I am quite sure that would discourage people from abusing the flaps in no time.

When in Dual Target Track mode, the antenna is driven on regular intervals to the bearing of the target(s) outside the current scan volume. You can see this when monitoring the caret indicating the antenna train angle on the bottom of the radar display. Most of the time it will move between the lines indicating the showing the azimuth, but in regular intervals it moves to the contact bearings tracked in DTT. I'am not sure, but I think the antenna will then scan only along the bearing to the contact, pretty much like in STT, before returning to the commanded scan azimuth.

Please consider to add key bindings for adjusting the ASI speed bugs.

This is probably the solution- Thanks for the quick reply!

Hello all, when trying to target an early warning radar in the HARM pre briefed mode, the missile remains in standby mode and never becomes ready for launch. In the attached track, I am trying to target 1L13 and a 55Zh6 EWRs in the pre briefed mode, and the missile remains in standby. As a quick check, I also target a SA-8 Gecko and the missile switches from standby to ready without any problems. For ease of reference, the test mission file is included in the uploads. Caucasus Harm PB Test.miz Caucasus HARM PB Test.trk

Might be, but somehow I am disinclined to mess with the resolution etc. For what it is worth, I just did a quick test with Bankler's mission in ST and there the lights are easy to observe.

Just tested again and found the lights- but they are not really bright indeed.

Just tried the re-saving trick, alas it didn't work. Also, I tried the stock Case 3 Recovery mission, with the same result, no line up lights.

Thank you for the tip, I'll try it and report back.

Quick question: According to the changelog, the issue with the line up lights should have been fixed with the June, 8th update. However, when I hopped into Bankler's Case 1 Training mission, the line up lights were still u/s. Does anyone else have still this issue?

I have the same issue, even after adjusting the system time.

One of the "Through the Inferno" missions by Deadlyfishes might be for you. It is available for a variety of maps and creates various tasks with different difficulties every time you start the mission proper. Also, if you want to improve you skills flying around the carrier, you might want to check out Bankler's Case 1 Recovery Trainer.

Glad that I could be of help. Happy hunting in the virtual skies!

I think that is because the Viper's flight control system is designed in such a way thst stick displacement doesn't command a discrete control surface displacement but a desired rate of change- that is, if I remember correctly.

Well, first of all, using the paddle switch in a dogfight is sort of cheating, but if you must, then I suggest the following: Can you use the paddle switch to disengage the autopilot and/ or nose wheel steering? If yes, then you have confirmation that your key bindings are working Do you use any joystick curves for the pitch axis, which might prevent you reaching full aft deflection of the stick? The g limit override can only be engaged when the stick is near full aft. Therefore, if you have a curve set, reset it to the default and test the switch again- the paddle switch should work then.

Just stumbled across this thread. I haven't done any night flying around the carrier for quite some time, but when I did it yesterday, I too found that the carrier is almost invisible. I do not run any mods, btw.

Could it be that in this particular case the target can't be picked up because of similar (ground)speeds, resulting in zero (or too small) dopplershift? Heatblur describes this type of blindspot in their Tomcat manual, page 225. [Edit: Typo- and Grammar-Correction]

Amen to that!