BreaKKer

Also on the TALD, I was curious whether we were ever going to see the other 2 variants of the TALD; the chaff one and the passive RF one. Or even if the active RF of the 141A that we have is modeled.

It’s not a super carrier bug. It’s been a thing since the Stennis

There’s a function on the CAP category that allows you to merge previous tracks with new ones. Not implemented yet.

This is some great work. Hopefully this can be considered/implemented to be in DCS.

I'm seeing the same thing. Probably in the depths of a VX squadron weapon separation test lies any sort of TER loadout like that.

With the introduction of custom aircraft ground spawn locations with DCS 2.7, I was curious when we will see the same for the super carrier. Bow spawns, stern spawns, etc. My squadron and air wing as a whole could really use custom spawn locations, since we have more than the 16 aircraft that need to spawn in, and half of those being Tomcats. This would allow us to have spawns on the angle deck when aircraft are not recovering. "ME. Added ability to place all Player/Client Aircraft on ground without parking spot"

Couldn't find any photos, but I was looking for the dual TALD on the TER, like A-6s had in desert storm.

That’s what I was thinking. Definitely not an approved loadout

1997 NAS Oceana - VF-101 F-14B-145-GR BuNo 162923 AIM-9M, followed by 5-inch Zuni's, TALD, and then on the right side of the TER, 2.75-inch Zuni's

Yes, but as more modern missile radars are created, the harder it is to notch the missile. Hence, the AIM-54C and 120C being less notchable than something like the AIM-7F or even AIM-54A

The vNavy restricted me to take video of the brightness knob being broken. Only screenshots

I was flying around TODAY and noticed I can’t adjust the brightness of the PTID anymore. Any ideas why it isn’t working?

Nope. C+ came before the sealed

Also, AIM-54C+ Sent from my TID using UHF1

Yes, but then on servers like hoggit where the players don't choose their address, they wouldn't be able to communicate with tomcats taken off of other airfields/carriers. I think the kneeboard thing would be more ideal, just like editing laser codes.

Yep, that's why I didn't stick it in bugs and problems. The F-14 manual says that's how it works, which is why I had it as a request. Tomcats from other flights would have been very helpful in the scenario my squadron was in. Thanks

My squadron recently had a combat flight where we had no AWACS. F/F datalink was briefed for this contingency, and we all went onto a common datalink frequency. Though, the tomcats of Panther 1 flight, and Panther 2 flight(my flight) were unable to communicate. Addresses for the Jester tomcats were stuck on their preset wingman number, and the reply switch remained in CANC. So, I have some requests. 1. ability to edit datalink addresses in the Jester datalink menu 2. add the reply switch NORM function to jester's list of F/F datalink procedure 3. add the ability for tomcats to communicate with other tomcats outside of their own flight. If you would like to test this to prove me wrong, you can hop on a multiplayer server with a friend. Both select 2 different aircraft in 2 different flights. Then, set F/F datalink to the same frequency.

If you have official documentation that describes this process, you should consider messaging one of the Heatblur developers. They are aware of it.

Read some documents. The AIM-54C is supposed to go active with the loss of PDSTT lock. As far as TWS track loss, I think it’s the same deal where I’d goes active with track loss. That was one of the major selling points of the AIM-54C and it’s subvariants.

poke

It happens in TWS. Pretty sure it’s intentional, but it gets in the way sometimes

Shouldn't be, because it counts perfectly for every other ALE-39 loadout. One of the L10 or R10 in the ALE-29(The chaff/flare dispenser ports in the beaver tail) is not being filled

As the title states, chaff count is cut by 10 when ALE-39 is set to 30F 30C and 20F 30C. LAU-138 is set to be loaded with chaff, so chaff count in the jet should add 40 onto the ALE-39 chaff count. I verified this by loading the ALE-39 in the ME, hopping in the RIO seat, and observing the chaff and flare count. As it looks, only the chaff count is effected.

The current behavior doesn't allow bearing and range to be displayed from a datalinked waypoint