Wizard_03

I don't know if this is the same problem, but the TD diamond seems really jittery when viewed through the HMD. But when looking at the designation with the pod or on the HSI its steady So the designation is fine but the display is jumping around. Its just like the MIDS symbols they're all over the place when you bank and roll.

Loving it so far, great work!

It happens thanks for looking into it!

I think it's one of those situations where, we made it work because we needed it. But in testing found out that to get real PGM capability we need a Digital SMS ergo PTID. However I guarantee that VF-103s F-14A+s had DFCS in 1997.

Confirmed

As long as those helmet textures are fixed I'm happy

Then we need to take Lantirn out as the real F-14Bs used them with PTID. In the late 90s not the early 2000s. PTID was not part of the B(U) upgrade it was part of the digital bus update to give the jet PGM capability and it likely started with F-14As in the first place in the late 90s. Also DFCS was by that time on pretty much every jet. So you see the problem they need to pick a time period, either late 80s because no DCFS so therefore no Lantirn, or mid 90s with PTID and DFCS because it has Lantirn. What we have is an F-14B from the 80s that somehow missed every OFP update and field mod. All the way up until the mid 90s when the crews decided to try and make Lantrin work with the fishbowl in Bosnia maybe (which again was probably F-14As anyway). So no Its not very realistic, but its ok I just don't use Lantirn and pretend. The F-14A they are making will fix all the those discrepancies as its FIRMLY a 1980s bird.

I'm excited because I feel like the A is going to be the more historically accurate version. The B we have is quite the frankenbird, it has Lantirn but no PTID or JDAMs it doesn't have DFCS. No B(U) features or OFP updates. It's both a very specific (super early A+) and a very generic F-14B. To me it just doesn't seem representative of the real jet from that time period. It's really, for all intents and purposes a re-engined A and that's it, and I highly doubt you'd find an F-14B with same combination of features/capablities or lack thereof, as ours from the 90s but it's whatever. I still enjoy it, and they did a good job. The A on the other hand will be much more authentic and representative of the F-14s golden years the 80s. Everything it's gonna have/not have Is realistic for the majority of the F-14 fleet at that time (aside from no glove vanes but that's iffy) and it will be the much truer tomcat experience of the two IMO.

That will be how it works! AFAIK it should follow the action slewing of the segmented diamond with priority assigned to the HUD/HMD too though I'm not sure why Wags didn't put the pod on the DDI in the video. Maybe it's still WIP or something.

Yep the helmet creates a system designation and the lpod, if loaded, will automatically slew to it just like if you were to press WPDSG on the HSI page. It will not however constantly follow the helmet if that's what your wanting, the pod will only slew to a designated point but the helmet will now be capable of making a designation.

This is why I voted for the mission card and MUMI in the Roadmap list as the highest priority, so we can say goodbye to TOO mode and screwing around with coordinates. Because IRL they don't try and drop 4 JDAMS in TOO mode on a single pass with nothing but lpod designations and markpoints. lol They plan out the attack, slap in the cartridge and not worry about it.

Nope, it's USAF/USANG.

. ​​​​​​Yes everyone that you don't know is your enemy, that pretty much sums up Soviet strategy for IFF lol Seriously though it may work great in wartime but that is a fail deadly system, and ensures that accidents/failures are meet with tragic results like Korean flight 007. Multiple correlated IFF responses and sources are essential to preventing mishaps like that in peacetime.

Yes please!

Ah I see very nice, yeah that is a pretty a nifty feature, Its gonna be great for SA to have Multiple targets displayed in the HUD and HMD. Really help in prosecuting timelines for BVR.

I know, nothing, I'm just trying to ball park the capabilities so we can have a discussion. On a side note, I think something like Tranche 1 block 2B - block 5 would be my personal wish for DCS but we'll have to see what they can and can't do of course. Anyways, so one thing that I know the hornet lacks (at least ATM) is COOP target indicators, or the ability to assign wing men to specific contacts during the sorting phase of BVR with just the link information. Is that something the Typhoon is capable of doing? I would imagine yes?

Well I was doing a little reading in manual, and the bricks in LTWS with MSI boxed are displayed when there is no offboard donor trackfile correlated. like you said, earlier but What it does not say is whether SURV icons have the same functionality as F/F. If they do then we should get HAFUs instead of bricks in LTWS and have that identical picture across the formats with a friendly AWACS in the mission Right? But after reading the manual more closely I think its just F/F donor information that can be correlated in LTWS. In that case only F/F can give you the top HAFU in LTWS, and the SURV tracks would disappear when onboard sensor sees them, exactly what we see now. All that is just a guess on my part, after reading the manual a little more. Its somewhat confusing to me, and pretty vague. The other thing I'm sure of is what modes can transmit over MIDS, because if its only TWS then that would explain why it doesn't work with the AI F/F donors either as they don't use TWS AFAIK. However I'm not sure about this correlation bug in TWS, because in that mode I AM seeing the same picture across all three formats?? Correlated full HAFUs on Radar Attack, AZ/EL, and SA?

So assuming we get something like SRP 4.1 does anyone know how well the datalink is integrated with the jets own sensors? Can we expect hornet levels of sensor fusion, such onboard/offboard contacts correlated on the radar B scope, as well on the jets appropriate HSD equivalent? Can they be displayed on the helmet like JHMCS? Or should we expect a more limited functionality, like SADL or Link4 in the Tomcat?

If its there its gotta be tiny. I sure as heck can't see it. As far as the cockpit goes in the B, the wrong Engine displays and no oxygen panel are the biggest glaring problems in my book, and on the outside 3D model the untextured bottom sidewinder rails on the gloves stand out to me much more then the stabs, if they are indeed wrong.

But I always get HAFUs both bottom and tops never bricks. What correlation bug are you referring too?

TWS works perfectly with MSI integration, need to just back port how it handles HAFUs to RWS with MSI boxed

Ok thank you, I appreciate that.

When the RWR nails (yellow triangles) are shown on the the SA page they all only point down regardless of position, just Like on the Radar attack page. However they should/used too point inward toward the own-ship symbol on the SA page around the compass rose like pizza slices. Using Latest Open Beta. 100 percent Repeatable in single player. I can post a screenshot if necessary, but not one for how it used to look.

I mean, why wouldn't you want to assign TDC priority to the FLIR page? From a tactical perspective, If your self designating and you need to switch track modes change polarity or refine the target post launch, you're going to need to be there anyways. Plus IMO a huge benefit of using laser Mavs with the pod is you hardly need to screw around with missile at all, because you can do everything from the FLIR page.

I already did, and heatblur specifically said as a visual option only, as in they won't have any impact on the FM.