hein22

No I am not expecting a top and bottom HAFU, as that's is not realistic in HMD. I am expecting an always bottom HAFU just like it should. If you paint the contact the MSI logic dictates that the HAFU should be offboard. At least that's how Wags always explained it. Maybe I am wrong, totally possible, but that's how I understand it now. Again, if what you say is correct and the HMD is a MIDS exclusive shower, then the top hafu would not be there.

The distance setup works perfectly, but the priority doesn't. I tried dozens of combinations and the flight members are always in the top priority despite the settings. SURV contacts are under the donor settings rather than other (not sure if this one is incorrect or not though).

I know about that bug, I posted it in OP and it was me who provided the tracks. Again, if what you say is correct, then we have a bug here. You state that the HMD SHOULD display MIDS information... Well... it isn't. If you paint a contact then the MIDS information is lost and you get stuck with your own HAFU status which is bugged and should be replaced by donor's, and that goes against your statement of HMD displaying MIDS information.

If what you say correct then we'd have a major bug in the implementation. Did you see the track? If you paint a contact you LOSE the datalink HAFU. So if datalink hafus are the hmd thing, this would mean a big mistake. I think it is like I said, with the inheritance of the bug.

How? I tried but a moving tank is barely visible even in exp3 and commanding a track wont do anything.

Why does GMT exist if we can track moving targets with FTT?

But I don't have that problem. Mine is rock steady until the FOV ends. Maybe a repair?

Again, that's because the hornet's HMD FOV is SO narrow that it makes you think the symbol drifts, but it is not. I do not have this problem, just tested it a couple of times. The scorpion has a massive FOV. The JHMCS has it so low that it merely goes a couple of centimeters.

I watched your track and there is nothing wrong in it. What you probably didn't know is that helmets have a very narrow FOV and when you actually see the aircraft doesn't mean the FOV of the helmet as currently positioned is within the aircraft that you see with your own eyes. There is no bug here.

But does FTT track the moving contact? I don't understand.

May I ask where in the plans does this bug fix fall into? Thanks.

is this when using VR only? The link16 in the hornet has a 12 seconds update rate (not realistic according to Mover). So whatever movement they contact makes will have to wait the remaining time to be updated, leaving you with an old symbol in the wrong place. SADL in the A10c is real time updated (or 1 second Im not sure). The only thing the hornet does well with the HMD Datalink symbols is extrapolating them when your own aircraft moves.

Hi, while testing the new HMD datalink symbols (awesome by the way), I realized that the very old MSI bug was transferred to this system as well, which is a very annoying thing to have in combat and most probably get you killed as the system is actually confusing you. Old bug https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/270017-reported-ltws-bricks?t=267824 The bug in words: If your radar isn't painting the target then the HMD will show you the bottom portion correctly. But when your own radar is painting the target you only see your current HAFU status losing the Donor's. This is a LTWS + MSI bug that's been here for ages now. Up until now this bug only messed up the LTWS feature, but now it is also messing up the HMD datalink. Track attached. I hope ED can finally resolve this issue before throwing more features into the Hornet. Thanks for your time. msi bug transferred to hmd.trk

Do I bother using the HSI today or the bug is still present? I could not download the updated yet.

Ok I just solved this problem. For me at least it was the fact that I was editing while the exe was running. If you edit while everything is off then it doesn't revert back to anything. Also I was not putting "" for break lines. Hope it helps someone.

Also agree. For at least I am more comfortable with this way than the one it used to be. IMHO.

I agree.

Yeah, at least provide some feedback for people like me that doesn't know what is that all about.

I reported this in 2019 and still no fix. They did this on purpose so it can be coherent with awacs calls which are all in true north in DCS to support the non clickable cockpits.

huh?

Is this actually working or am I trying to do something with no end?

If I leave the file open and restart the server with the web gui it says that another program made modifications and if I load it again it reverts to the previous state. Before the previous state was blank but now it is the word test that I used when Viff replied today. So.... what's going on?¡

Do you mean the server exe as admin? This is driving me crazy. Never worked since day 1 I dont know why. When you replied to me today the first time I went and did it anyway and wrote the word test on it. Now the word stayed there and I can't change it, and whatever changes I made are overwritten by the word test. What is happening to me???

Thanks Viff. It looks like if it reverts back to blank once any change is done in the server, like the mission or any setting. Yes it does have permission, even without run as admin. Maybe that's the problem? Because it is entering the file and changing it?

I agree, I'm not saying it doesn't need adjustments, but it serves a better purpose than before (having the lights on).