X-Plane Labels
X-Plane Labels
Further to the bug list regarding label distance reading, I held a group rally last night 8 aircraft on mixed sim platforms and the label positions didn't always remain with the actual aircraft positions, e.g. labels would often display ahead when the aircraft was actually behind. This obviously making it difficult to locate where other aircraft were. I've scoured the forum to see if this bug appears elsewhere but hadn't found. Apologies Pete if you are already aware.
Re: X-Plane Labels
Yes, I found this out last night. Two other people I was flying with had this problem. The strange thing is that I fixed this when I added the feature originally and has been working fine on my X-Plane since. Very strange. Did it suddenly break with a recent update?
Peter
Peter
Re: X-Plane Labels
TBH I noticed it when the labels were first introduced but I didn't think much of it at the time. It only became a noticeable issue when I flew with a larger group and was trying to locate others in the circuit.
Re: X-Plane Labels
Hi Peter. I not sure if this is any use to you, reference the Xplane tags.
Below you can see two views from the same aircraft position. In the distance EGKA Twr is online and is in a fixed position. It appears as though the tag displayed has a mirror image. They look 180 degs opposed to each other. You can't see the text clearly in the pictures but they are showing the same distance and height. Using 2.0.5
Below you can see two views from the same aircraft position. In the distance EGKA Twr is online and is in a fixed position. It appears as though the tag displayed has a mirror image. They look 180 degs opposed to each other. You can't see the text clearly in the pictures but they are showing the same distance and height. Using 2.0.5
Re: X-Plane Labels
I've had a couple of reports of that. I know roughly what it is. The strange thing is that it only happens in certain situations. Sometimes it fixes itself, but I'll see if I can get to the bottom of it.
Peter
Peter
Re: X-Plane Labels
Experienced this issue all the time I was experimenting on Monday evening ( 2.0.4 )