reported Trackfile mach/altitude label displayed incorrectly for non-L&S trackfiles

[Star57]

Track attached below,

Steps to reproduce:

1. Enter TWS mode with at least two targets within your search area

2. Build two trackfiles on these targets

3. Observe that the target which is not an L&S has an incorrectly displayed mach/altitude label, displaying nothing for mach and "0" for altitude.
Upon switching L&S to the second trackfile, its labels will display properly, but the first trackfile will now display nothing for mach and "0" for altitude, unless the cursor is placed over it.
f18twsincorrectlabel.trk

 

Edited November 19, 2023 by Star57

[Lord Vader]

Hi @Star57

I am sorry but we are unable to reproduce the error you describe. Running your track, you only designate one L&S target. In that state, any other track files will not display speed or altitude until you either designate a secondary or move your cursor above it. 

Here's an example of designating a secondary target (diamond) with the indicated speed and altitude on it. 

I never saw that "zero altitude" indicator you mention at all.

I have to ask, are you on Stable or Open Beta? If you are on Open Beta, can you perform a Repair on your DCS and report back?

[Star57]

Hi,

I'm on the latest Open Beta,

I launched the game just now and ran both this track and the track for the other bug I reported, and for me, both tracks did not show the issues.

I then attempted to reproduce both issues in game, and neither would occur.

As I created these tracks after a couple of hours of gameplay on a multiplayer server last night, I will attempt to (roughly) reproduce the conditions and the issues. If this succeeds then I'll run a repair and try again.

For reference, this is what the "0 altitude" trackfile looked like:

[Harker]

I've seen the 0 altitude thing show up when 1 LOOK RAID is selected in the DATA sub-page. Is that the case here?

[Star57]

4 minutes ago, Harker said:

I've seen the 0 altitude thing show up when 1 LOOK RAID is selected in the DATA sub-page. Is that the case here?

Good call! I tested again with 1LOOKRAID enabled, and the 0 alt label is displayed for all non L&S/DT2 trackfiles.
Track for this here: f18twsincorrectlabel1lookraidenabled.trk
The other unexpected difference, and likely what caused this to not be reproduced on your end @Lord Vader, is that the 1LOOKRAID option looks to be persistent through mission restart, so the original track would've had that option disabled.

I also tested the other issue which I reported in a separate thread (STT not going into memory/dropping when it should) in the following trackfile, and as soon as 1LOOKRAID was enabled, this issue returned. Shown in this track: f18twsincorrectlabel1lookraid2.trk

f18twsincorrectlabel1lookraidenabled.trk

[Harker]

50 minutes ago, Star57 said:

Good call! I tested again with 1LOOKRAID enabled, and the 0 alt label is displayed for all non L&S/DT2 trackfiles.
Track for this here: f18twsincorrectlabel1lookraidenabled.trk
The other unexpected difference, and likely what caused this to not be reproduced on your end @Lord Vader, is that the 1LOOKRAID option looks to be persistent through mission restart, so the original track would've had that option disabled.

I also tested the other issue which I reported in a separate thread (STT not going into memory/dropping when it should) in the following trackfile, and as soon as 1LOOKRAID was enabled, this issue returned. Shown in this track: f18twsincorrectlabel1lookraid2.trk

f18twsincorrectlabel1lookraidenabled.trk 117.87 kB · 1 download

Yes, both issues are related to STT with either 1 LOOK RAID or RAID enabled.

[Lord Vader]

Hi again, @Star57

Now I see it. Thanks for the tracks, reported internally for analysis.