Py

I tried your steps 1-3 exactly just to see (since I usually select AA mode manually as step 1.5) and it went normally into boresight mode for me. I have never installed any mods, on the latest beta. Not sure what to suggest, except check your sensor control binding is set properly and isn't conflicting with anything?

I noticed this issue in the previous version, but it appears to be fixed (for me at least) after the latest release.

They work, just need a laser supplied by another plane eg A-10/harrier or by a JTAC.

Probably it is assumed that you will change to A/A mode before you are engaged, with time in a safe place to check your stores then change it to EW (or put EW on the HUD). I also find it annoying, but if it's realistic then that's how it should be.

I think they are bound to the account unfortunately.

Is the option to synchronise to HOTAS at mission start set?

I also found it frustrating to refuel and felt like shooting down the tanker...until I heard "look at the tanker, not the basket". Seriously it sounds like a minor thing but for me it is the difference between incredible frustration and a minor challenge. This is with a MS FFB2 that has a hardware deadzone just to make small movements even harder to do :ermm: That said, it would be good to have an easy refuel option for people learning and just getting into DCS. It can be overwhelming with so much to learn. Those of us who can AA refuel can always leave it off (it should be off by default).

It's not absolute, but a proportional control when mapped to an axis. It really needs to be on a spring centred axis. In the centre, the radar doesn't move (needs a deadzone to make sure it doesn't creep). The further from the centre the axis goes, the faster the radar slews up/down. I think it works better mapped to buttons rather than an axis, but you can get the same effect by playing around with the axis curve. I think on the real hornet it's a self-centering 3-position switch(?)

Not only that, Wags has stated that they are working on doing it already. https://forums.eagle.ru/showpost.php?p=3720837&postcount=101

I have a track, but it's useless. The problem is that when you play the track back, the gunsight appears in the correct position!!! The image I posted showing the difference between bugged and not bugged is the same flight, once during the flight (bugged) and once when I played back the track (not bugged) :dunno:

I know it depends on the threat, but what is a good number of chaff/flares and what timing do people use in the case of just 2 programs? Eg 2 chaff or flares 3 times with 0.5s delay is what I currently use, but that is just guessing. There's always a balance between using the countermeasures up too quickly and increasing the odds of decoying a missile too.

I'm just wondering how everyone is setting up their countermeasures. Of most interest is the setup of people who successfully evade missiles of course :) Do you prefer bypass mode? Or if you use the countermeasures programs, how do you like to set it up?

That's the advantage of passive missiles! For the person launching anyway. Some aircraft like the A-10 can detect the IR signature of a launch and warn you, but the hornet doesn't have such a system. The only way to detect them is to constantly look around and hope you see the smoke trail. Good luck!

It's a fly-by-wire aircraft, so you don't have direct control over ANY of the control surfaces. Especially at low speed and high AOA it will be moving lots of things at once to try and give you what you command with the stick/rudders.

It's not that much heavier (420 lb) than an AMRAAM (335 lb) and quite close to the centreline though (according to wikipedia). The effect of an emptying fuel tank on one wing seems like it would be much more of a trimming issue.

From what I've picked up, the ATFLIR is mounted instead of an AMRAAM on one of the fuselage mounts.

TRACK FILE Here is a track file showing the issue (as short as I could make it). mavf_no_timer.trk

You'll like this :)

It's a pretty major problem I think, especially since so many reported bugs get ignored with a [NO TRACK FILE] tag. Lately I have been attempting to record track files for some of these bugs so they can get fixed, but I have given up since the tracks usually screw up so badly that they don't show the bug. Eg I just recorded a track to show the F/A-18C MAVF bug where after you fire some MAVFs and reload, the cooldown timer doesn't show any more. I fired off 4 mavericks, landed on the carrier and reloaded more, then showed the bug. I then saved and replayed the track... It shows me fire 1 maverick, look at the ground and try to lock a random bit of dirt for a bit, then crash into the sea. It didn't reach the point where I could show the bug. How can ED expect us to show bugs in track files when the playback is THAT bad?? Pleeease fix or at least improve this!

I have had this bug too but can't find what causes it. It seems to be related to dropping bombs then switching to gun, but sometimes it happens sometimes it doesn't. You can tell if the bug is happening even while flying straight, just from the low position of the pipper compared to usual, so I don't think it is related to CCIP calculations. See the attached image. Both images are actually almost the same moment, it was bugged so I took a screenshot and saved a track, but on playback the bug does NOT happen so I took another screenshot of that. The sight appears in the correct position on playback?! Edit: OK it's not to do with bombs. I just took off from the carrier, turned the gun on, and it was bugged.

I tried the same thing with no luck. A ground JTAC (well in range) looks ok in the mission editor but says no targets in the mission. Interestingly, using a reaper drone as JTAC, in the mission editor it won't even let me select the ship group as targets. Are we doing something wrong or is it a bug?

Yes, run DCS_updater with the parameter "update". Either type "DCS_updater.exe update" from the bin directory, or make a shortcut to DCS_updater and edit it to add the "update" parameter.

I have found this too and recorded a track file. It happens after repairing either on land or a carrier, and the woop woop stops if your gear is down (but resumes if you put it up again). I didn't try setting the radar altimeter trigger level lower like Jafferson did, but I had it set to 370ft and tried flying above and below this limit (end of track) but there was no change to the constant woop-woop. This was on a custom single player map, using the latest open beta. woopwoop.trk

All it needs is an upgrade to the version with a HMD for designating ground targets.

Very interesting article! It says that in order to use the longest range (and "best") modes of the HARM, an additional targeting pod is needed. For the F/A-18 that's a "TAS" pod (Targeting Avionics System). There's mention of it on the F/A-18C in 1996 so hopefully we will get it later in DCS, though I've heard no mention of it so far...