You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Euroscope shows a track heading but this doesn't work for pushbacks,...
I asked the dev from vSMR and he told me it's a problem with how the FSD message is passed to Euroscope, the protocol not being entirely implemented correctly. vSMR does not parse the FSD messages and also gets them straight from Euroscope.
When using the vSMR plugin of Euroscope many flights who are on the ground have an incorrect heading. They are all facing north.
vSMR
https://media.discordapp.net/attachments/734119679806668940/871336383984316448/unknown.png
Euroscope
https://media.discordapp.net/attachments/734119679806668940/871336397913591818/unknown.png
Euroscope shows a track heading but this doesn't work for pushbacks,...
I asked the dev from vSMR and he told me it's a problem with how the FSD message is passed to Euroscope, the protocol not being entirely implemented correctly. vSMR does not parse the FSD messages and also gets them straight from Euroscope.
When working with a similar project (https://github.com/aap007freak/OpenSkyToEuroscope), we came across a this exact issue using an entirely different client. It was eventually fixed, you can check it out here: https://github.com/MatisseBE/FSD-parsing-of-PBH/blob/main/TrackProcessor.h
The problem lies somewhere in the num1 field. You can find more here: norrisng/fsd-doc#3 (comment)
I hope this helps you.
The text was updated successfully, but these errors were encountered: