MARLAN_

Only breaks in multiplayer.

Datalink seems to be broken on Marianas, possibly Persian Gulf too.

@BIGNEWYDid a bit of testing, spawned just 2 blue FA-18Cs, 1 E-2D. When my wingman is AI I can see him on the helmet every time. When my wingman is client I cannot see him at all, or he shows up as "FA18" (AWACS detecting him, but he is not showing inside fighter-to-fighter datalink group)

I was banking left, as this seems to only occur during reattack. As far as I've been told though, this should not be an issue in the real world.

During a reattack, myself and all of my peers are having issues where STT is failing to acquire a solid lock. It tends to primarily occur during a reattack, which makes me wonder if it has something to do with AOA/AOB/ATA causing the issue. According to a real FA-18 pilot, STT should be nearly instantaneous (similar to how DCS nearly immediately acquires an STT lock in most cases) (In fact, off topic a bit, TWS should take much longer to build a track file, whereas in DCS it tends to be instantaneous. - This is causing a weird case where we are changing our vSqn SOP from using STT to TWS, when in the real world it would be the opposite) stt.trk After viewing the .gif, looks like that track has an enormous mach number (mach 15000??) that could possibly also be related, I've seen that happen a lot in DCS, but I've mostly ignored it thus far.

There is also an additional issue that the NIRD/Launch Parameters are out of date ever since the AMRAAM was improved awhile ago (last year?) thus a perfectly capable shot will display LOST off the rail. I just ignore and tell everyone else in my squadron to ignore the LOST indication right now until it's fixed, because it's totally useless (and confusing for those who don't know) in its current state.

RAID 1LOOK seems to trigger this issue consistently as well, with RAID 1LOOK enabled you will often find yourself STT'ing your own missile, or bandits missile. I would guess any time it attempts to do a RAID look during STT, it's causing you to temporarily lose lock for about half a second, but the radar memory is unable to lock the original target and just picks something at random.

I think the issue lies with RAID 1LOOK is broken. I haven't got around to reporting it yet.

If you do figure it out I'd be interested in this mod!

KC-10 can give bearing, KC-135 cannot.

Shouldn't even have to call ready pre contact, the baskets should be deployed before you get there. Edit: *Is how the game should be, not how it currently is.

@BIGNEWYAny chance of DCS allowing us to colonize CPHR on the Comm 1/Comm 2 UFC? This would allow the guys behind SRS to use that game state to secure our radios in SRS. I would think it should be fairly quick to enable just colonizing CPHR and not actually implementing any secure comm features (since we don't yet have voice in DCS anyways)

@BIGNEWY Attached! STT, PB10, Crank. Note AZ/EL tracks the group, but the B-Sweep on the RDR ATTK does not. TWSAutoPB10.trk

Thanks for testing. As far as I've been informed by a real F18 pilot, this is not accurate.

Reproduce 1) Select GACQ 2) Select AIM-9/AIM-120/AIM-7 Note RDR ATTK, often stuck in 5B, 20d (about 50% of the time) Can be fixed by cycling weapons, however this messes up your flow, and can easily be life or death in combat.

Reproduce: 1) STT a brick. 2) Press PB10 to enter TWS. This should bring you into TWS AUTO. -> You enter TWS AUTO, however the B-Sweep will not follow the L&S

Brevity for a JDAM release is "Thunder"

I've had the same issue recently, I verified TACAN and they did not conflict, nor did we use Laser codes. Verified all of the common mentions like ensuring EPLRS, AWACS etc.

Some tankers do give bearing information, the KC-10 included (the KC-135 however, should not) There are documents out there that list the features of the tankers, I found them before in a deep dive, you can probably find them too if you search around. A close friend of mine is a KC-10 Flight Engineer and has confirmed that there absolutely is bearing on the tacan, however, they do not always transmit bearing (they can choose to shut it off) and it depends on the mission. This is likely the root of the discrepancy if the source of the information is from fighter pilots, not tanker crew.

He's not asking for them to make cipher functional, he's asking for the ability to just colonize CPHR so that other dev's like the guys behind SRS could utilize that to enable PRI/AUX ciphers.

Is this updated for Marianas?

Instead of having a client aircraft suddenly warp through time and space and appear when a client connects/spawns, would be great if there was a check box to have the aircraft always be there as a static and only the pilot will teleport in. Would add a lot to missions and also not cause parking areas to be devoid of life unless clients are connected (can't place statics because they would block spawns)

IRL they used AIC to "Kill Remove" jets if they are determined to have been within valid parameters for a hit. The HUD symbology would mainly help for knowing when to call pitbull/timeout/cheapshot/etc. And for when to execute your out, otherwise you're just guessing. I'll look into that script since apparently a non functional SIM mode is "correct as is" sadly I don't have classified documents so it would be up to ED to verify this. There's absolutely no way it's correct as is for a SIM mode to do nothing except safe the trigger lol.

@BIGNEWYThe video BarTzi posted shows an example of it working which is how I expected, it displays all symbology from a missile launch like normal but without the actual missile launch of course. ACT # / TTG # is shown on the HUD in the video

I don't think a feature shouldn't be added just because a script can kind-of perform a similar function. Mil-Sim groups who don't kill friendlies and do practice BFM/BVR would benefit from this.