TacView data wrong for Arras map

[AndyJWest]

Brief description: The .acmi file data for TacView is incorrect when recording from the Arras map.

Detailed description, conditions: 

TacView .acmi files on the WW1 Arras map contain incorrect data. The longitude and latitude in particular are obviously wrong. TacView displays aircraft as being in the vicinity of the area covered by the Stalingrad map, and opening the .acmi file in a text editor confirms that it is the file data for this that is incorrect, rather than an error in TacView. There are also other errors apparent when looking at what TacView displays, e.g. TAS, G values etc aren't plausible, presumably because TacView is deriving them from the incorrect positional data.

 

The error seems to be map related, rather than an issue with WWI aircraft, as testing WW2 aircraft on the Arras map results in the same errors, whereas recording WW1 aircraft on a WW2 map gives correct results.

Edited February 15, 2020 by AndyJWest
clarify

[Alfred_Tupper]

Apologies if this is a bit necro, but the issue still exists.

 

Two of the three Bapaume maps on the Flugpark server exhibit this behaviour, and I am trying to get to the bottom of it. The two Lens maps and one Bapaume map work fine, so will try to use what you've put above Andy to trouble shoot this if I can. Parsing an acmi file I can clearly see that the lat and long values are well off, and putting them into Google maps, yes you end up in Russia exactly where you appear on the Tacview map.

 

Penultimate edit - I've played on three more western front maps on two more different servers, and Tacview works as intended.

 

I have used the mission editor (for the first time) to see if I can spot makes the two Bapaume maps appear in Russia. The only difference I can spot is that the setting for GUI map uses western_front-spring, whereas all the maps that work on Tacview use the setting arras-spring. 

 

I have posted a summary of my thoughts on the Flugpark Discord channel to see if J99_Sizzlor thinks I've found the source of the issue.

 

Hopefully, the outcome here is that Tacview does work fine with FC in the most part, and hopefully we will discover  what was bugging it in these two particular maps on the Flugpark.

 

Cheerio!

 

Final edit - here are J99_Sizzlor's thoughts: Hey Symonds i think the new western front map is the culprit with tacview. Bapaume is ported to the western front map. Maybe tacview needs some data to display the assets on this map correctly. And since that is missing it defaults back to the Stalingrad map. That is my guess. Nothing the mission designer can change. You should forward your observations  to the game developers...

 

So I have updated my query/comment on the Steam discussion forum and will see what the software developer has to say.

 

S!

 

Edited July 3, 2023 by RNAS10_Symonds
spellllling, clarification, updates

[Alfred_Tupper]

Update after speaking to BuzyBee a developer of Tacview on Steam.

 

It seems that the issue is that the map western_front is not (yet) supported in Tacview. So the coordinates maybe do default to the Stalingrad map.

 

I would guess that when AndyJWest posted his issue, at that time the new Arras map was not at that time supported in Tacview.

 

If the devs give me a hint of when western_front will be supported I'll pop back here to post it.