VFA41_Lion

64-99 X/Y AA TACAN still works though

Better wipe it down with some lysol then :noexpression: :D

I've seen a Burke try to engage it but its very ineffective at launching in time.

Unfortunately in this case its bugged, neutral coalition planes will show up as HOSTILE red HAFU instead of yellow neutral. AWACS will also report them as HOSTILE when asked to DECLARE.

as a side note, I also encountered the problem with 4x mk83s colliding when released together and blowing me up at low altitude. Setting an interval greater than 1 or 2 feet fixes it.... but still weird.

Sorry if already reported, forum search is not coming up with anything. I'm unable to directly select the A/G radar mode from the TAC menu, as it brings up the A/A radar display instead and also none of the functions work. Only way to select A/G radar is to first enter the A/G master mode and use the automatically switched MFD for that. :(

Detail: On 160 nm display, the A/G radar will not render past 80 nm if the player is looking anywhere other than the radar. Moreover, it erases what was previously there and takes a full sweep or two to begin rendering it again.

Track and mission attached. According to this post https://forums.eagle.ru/showpost.php?p=3821502&postcount=139 channel 68X for A/A should either not be working at all or provide degraded Link16 functionality, yet I still receive perfectly good A/A info as well as full SA datalink functionality. :noexpression: :detective: TACAN broke.miz tacan not degraded.trk

ha, blue fog is back

I get this too, but only on high gamma, like 1.8 to 2.2

Its an option if you take up the squadron to attack a group of vessels. Sorry, but thats how it is in modern naval warfare.

you need at least 8 Hornets with 4x harpoons each. And then some F-14s with TALDs because no Russian ships have individual damage modeling for radars. And even then you'll probably only sink two.

https://forums.eagle.ru/showthread.php?t=276460

i did some testing. I dunno if warhead values are messed up or something but it took 6x JSOW-Cs or 6x GBU-31Vs to destroy one shelter.

....no? its just delayed until after the FLIR engine updates.

this is WAD iirc. You need to use the cursor offset to slew the TPOD when in ATRK/PTRK. https://forums.eagle.ru/showpost.php?p=4372935&postcount=188

I did not see that problem in testing. Do you have a track or .miz file?

did you try using HIDDEN ON MAP, as I suggested? Because that blocks it from showing up in SA. Not HIDDEN ON PLANNER.

man that is way dark. Try 2.2 gamma? mine looks great with it.

https://www.ausairpower.net/TE-Harpoon.html from this article it seems like the GPS receiver was never used as good enough for a fire-and-forget to hit precision coordinates, and always used the datalink to guide it in for terminal phase.

Thats just the way the sim works right now. :shrug:

i agree, hornet radar does not see any targets except with boresight ACM. hornet radar nonfunctional.trk

SLAMs inertial navigation drifts a lot more than most weapons. It needs to be guided in via datalink if you want accuracy from standoff range.

Not a bug, use "HIDDEN ON MAP" and the SA page is not dynamic for SAM threats, think of it as pre-loaded threat rings.

Did I encounter a UFO or something? Was testing a mission, radar locked onto a target that did not show up on SA, and AWACS called clean on bogey dope and silent on DECLARE. AIM-120 in TWS went stupid, AIM-9X was slaved via radar but also went stupid (could not achieve heat lock), and closing to visual range, there was.... nothing. Incident occurs after refueling with KC-135MPRS. :joystick: p.s. track too big for forum so its attached here --->: http://s000.tinyupload.com/index.php?file_id=87449324821554182108