Jak525 Posted August 1, 2019 Posted August 1, 2019 (edited) In the new update, the HAFU is sometimes colored in STT (donor info and other donor tracks are also displayed, cool!) -- but not consistently. Track attached. EDIT: SEE 1ST REPLY. I've changed the name of this thread to cover the general problem with trackfiles but it doesn't seem to want to update on the main forum page.HAFU STT bug.miz.trk Edited August 6, 2019 by Jak525
Jak525 Posted August 2, 2019 Author Posted August 2, 2019 (edited) I have done some further investigation and I've determined that the HAFU is uncolored/no MSI indication is shown when STT is obtained via TDC depress on the L&S or by an ACM mode. It does appear, which is how I believe it should, when acquired into STT by Automatic Acquisition instead. I think the underlying issue here, which has been a thing for a bit, is that two 'trackfiles' exist: - One, with the MSI(bottom half etc) indication and all proper symbology (e.g. no rank for a friendly) - Another, without the MSI indication and no color in STT, as well as improper symbology (e.g. friendlies still ranked) The first one appears in the following cases: - SA format - RDR ATTK format for a trackfile not cursored over or designated as L&S or DT2 The second appears on the RDR ATTK when: - Designed as the L&S or DT2, or is cursored over, or is put into Single Target Track via TDC depress or ACM. What is odd is that when you acquire the trackfile into STT via AACQ, it appears as though graphically both of these trackfiles is displayed at the same time. You can see the uncolored one "peaking" from behind it and also the Mach / altitude readout is uncolored which seems to be part of the 'improper' trackfile. Edited August 2, 2019 by Jak525
QuiGon Posted August 2, 2019 Posted August 2, 2019 Great observations! :thumbup: I usally lock my targets via TDC depress on the L&S and have wondered why the HAFU always reverts to green then! Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Harker Posted August 2, 2019 Posted August 2, 2019 I have done some further investigation and I've determined that the HAFU is uncolored/no MSI indication is shown when STT is obtained via TDC depress on the L&S or by an ACM mode. It does appear, which is how I believe it should, when acquired into STT by Automatic Acquisition instead. I think the underlying issue here, which has been a thing for a bit, is that two 'trackfiles' exist: - One, with the MSI(bottom half etc) indication and all proper symbology (e.g. no rank for a friendly) - Another, without the MSI indication and no color in STT, as well as improper symbology (e.g. friendlies still ranked) The first one appears in the following cases: - SA format - RDR ATTK format for a trackfile not cursored over or designated as L&S or DT2 The second appears on the RDR ATTK when: - Designed as the L&S or DT2, or is cursored over, or is put into Single Target Track via TDC depress or ACM. What is odd is that when you acquire the trackfile into STT via AACQ, it appears as though graphically both of these trackfiles is displayed at the same time. You can see the uncolored one "peaking" from behind it and also the Mach / altitude readout is uncolored which seems to be part of the 'improper' trackfile. Good observations and especially the last one, with the second trackfile peeking behind the first. I saw it first a couple of days ago and wasn't sure I saw correctly, but I see it's indeed the case. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Recommended Posts