Current Situation / Problem
XPMP2 has built-in support for a set of shared dataRefs to provide textual aircraft information. This pre-dates the TCAS Override approach and hence uses an older and more cumbersome model of naming the dataRefs...but, hey, it's there.
The Remote Client cannot currently populate reasonable values there.
Suggested Solution
Transfer necessary values to the Remote Client, likely by extending the existing RemoteAcDetailTy message. (Alternative would be to use a new message...but that triggers follow-up issue for how to create new planes and how to synch starting Remote Clients.)
[x] Add required fields to RemoteAcDetailTy message, requiring a new version of that message
[x] Thorough cross-version compatibility testing (also required for #25, so deliver them together)
[x] Document the shared dataRefs in the developer's documentation...they are apparently yet missing.
Benefits
More info to the world, also for the remote instances. FSTramp does use it already.
Additional context
Lacking support noted when entering issue #26.
Current Situation / Problem XPMP2 has built-in support for a set of shared dataRefs to provide textual aircraft information. This pre-dates the TCAS Override approach and hence uses an older and more cumbersome model of naming the dataRefs...but, hey, it's there.
The Remote Client cannot currently populate reasonable values there.
Suggested Solution
Transfer necessary values to the Remote Client, likely by extending the existing
RemoteAcDetailTymessage. (Alternative would be to use a new message...but that triggers follow-up issue for how to create new planes and how to synch starting Remote Clients.)RemoteAcDetailTymessage, requiring a new version of that messageBenefits More info to the world, also for the remote instances. FSTramp does use it already.
Additional context Lacking support noted when entering issue #26.