Ahmed Posted September 11, 2024 Posted September 11, 2024 (edited) Noticed that I'm getting trackfiles on the SA for the Hawk missiles shot in the attached track, despite being in MAP (A/G) mode. hawk.trk Edited September 12, 2024 by Ahmed
ED Team NineLine Posted September 13, 2024 ED Team Posted September 13, 2024 We believe this is correct based on available, public references. If you have contrary, public evidence, please message me with it. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Harker Posted September 14, 2024 Posted September 14, 2024 (edited) 8 hours ago, NineLine said: We believe this is correct based on available, public references. If you have contrary, public evidence, please message me with it. That should not be happening. MSI trackfiles are only built with A/A radar modes (not VS though) and only in NAV and A/A master modes. Here, the radar is in MAP mode, meaning it's only getting raw returns, not building anything, and the master mode is A/G. MSI trackfiles should not be built in A/G mode at all, even if the radar is in AIR, in RWS mode. An example is in A1-F18AC-742-100, 011 03, pg.3, par.18 This bug becomes even more "visible" if you switch to A/A mode quickly, after noticing the trackfile on the SA. You will observe that the RDR ATTK B-scope display already has several bricks, indicating the missiles were indeed being detected and the radar was generating bricks while the radar was in A/G MAP mode. Edited September 14, 2024 by Harker 4 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
Coyle Posted September 14, 2024 Posted September 14, 2024 (edited) 1 hour ago, Harker said: That should not be happening. MSI trackfiles are only built with A/A radar modes (not VS though) and only in NAV and A/A master modes. Here, the radar is in MAP mode, meaning it's only getting raw returns, not building anything, and the master mode is A/G. MSI trackfiles should not be built in A/G mode at all, even if the radar is in AIR, in RWS mode. An example is in A1-F18AC-742-100, 011 03, pg.3, par.18 This bug becomes even more "visible" if you switch to A/A mode quickly, after noticing the trackfile on the SA. You will observe that the RDR ATTK B-scope display already has several bricks, indicating the missiles were indeed being detected and the radar was generating bricks while the radar was in A/G MAP mode. You of all people should know we haven't a shred of MSI implemented in our hornet, we just have donor tracks and radar tracks with no MSI inbetween. While what you say is accurate (no MSI processing in A/G) I don't believe they are mutually exclusive. There's nothing saying we can't have donor tracks (but not being processed into a MSI trackfile) while in A/G, IE displayed over the SA page. If the A/G radar is building A/A radar tracks while in MAP mode, that's another thing entirely and is the bug. But let's make sure we know what's the difference here between raw hits, trackfiles (radar in this case) and finally MSI (not implemented at all) Edited September 14, 2024 by Coyle 1
Tholozor Posted September 14, 2024 Posted September 14, 2024 (edited) 1 hour ago, Coyle said: But let's make sure we know what's the difference here between raw hits, trackfiles (radar in this case) and finally MSI (not implemented at all) Well if we want to be pedantic, all trackfiles should be MSI trackfiles (there should be no such thing as non-MSI trackfiles in this regard). The main difference being MSI trackfiles with ownship radar contribution (with the contribution circle that's missing in DCS) and those without. That aside (as it's not really central to this particular report), I believe the crux of the issue (as far as I've noticed) is that the system seems to be generating/creating trackfiles in A/G mode, regardless of offboard input. Edited September 14, 2024 by Tholozor 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
ED Team NineLine Posted September 14, 2024 ED Team Posted September 14, 2024 Guys, I just checked our development build and it seems there is no track shown there so it's possible this was fixed already, I was only able to check the release earlier. It's possible that's the reason for some crossed wires in my earlier response. Sorry. Release version: Dev Build at the same time as above 2 Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Harker Posted September 15, 2024 Posted September 15, 2024 On 9/14/2024 at 5:37 AM, Coyle said: You of all people should know we haven't a shred of MSI implemented in our hornet, we just have donor tracks and radar tracks with no MSI inbetween. While what you say is accurate (no MSI processing in A/G) I don't believe they are mutually exclusive. There's nothing saying we can't have donor tracks (but not being processed into a MSI trackfile) while in A/G, IE displayed over the SA page. If the A/G radar is building A/A radar tracks while in MAP mode, that's another thing entirely and is the bug. But let's make sure we know what's the difference here between raw hits, trackfiles (radar in this case) and finally MSI (not implemented at all) We do have a shred of MSI implemented, otherwise we wouldn't be able to correlate ownship and MIDS tracks at all, and MIDS wouldn't be able to contribute to the ROE matrix. Although of course we're missing most of the MSI logic, it is important that all bug reports should consider that MSI should exist, and point out the buggy behavior with that context in mind, so as to avoid creating confusion over how should things work. As @Tholozor said, all on-board tracks should be considered as MSI trackfiles by default, so radar track = MSI trackfile. Lastly, MIDS tracks are never processed as MSI trackfiles right now anyway, the information is just correlated with the ownship trackfile. So those MIDS tracks would be available in any mode. In any event, the only thing we should be getting in A/G mode from the AIR radar is uncorrelated bricks and nothing more, and MIDS tracks that aren't processed into MSI trackfiles. The fact that we're getting MSI trackfiles from the MAP mode is a problem. Thankfully, it does seem that this is not the case in the dev build. I also tested myself and can confirm what @NineLine says, I don't see any trackfiles on the SA, and when I select the AMRAAM to quickly switch to A/A mode and AIR radar, I don't see any pre-existing bricks or trackfiles. 3 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
Recluse Posted September 15, 2024 Posted September 15, 2024 (edited) If this is the same thing, I reported this a year ago. Never saw it get fixed and it still occurs for me. In the reported case, it is the HUD that shows target information for locked (TWS) air targets when in AG mode. Don't know if the posted track still works with the latest build. If needed I can generate another one. Edited September 15, 2024 by Recluse
ED Team NineLine Posted September 15, 2024 ED Team Posted September 15, 2024 It should be in the next release, so you can check again then. Thanks. 1 Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Recommended Posts