This is clearly an issue with G-SLNT as both yourself and G-CJAK were seeing each other reliably throughout the trip.
What I failed to mention was that Alan in G-CJAK could see G-SLNT certainly on the first trip and I think on the second trip. So that adds a bit of more confusion.Not sure if he's got any relevant screenshots/tracklog.
In diagnosing this Alan also spotted another aircraft with a different ICAO between PilotAware and transponder. He's going to let him know (looks like a typo between 0 and 9). Surprisingly it didn't seem to cause any problems to us, although I suppose both were overlaid on the display.
[...] unlike G-CJAK and G-XLAM which were both rock solid, G-SLNT was jumping about all over the place like a mad thing - often racing ahead and off to the side of track at supersonic speed, then suddenly jumping back to the ‘group’ - so his position signal is at best ‘intermittent’ and that’s me being ‘polite’ about it.
That's just Kev's flying
I had a bit of jumping about between me and G-CJAK earlier in the trip - noticed because I was jumping behind and ahead of him on screen but only close behind in reality. Didn't have spare brain capacity at the time to figure out whether it was him or me jumping about, but it was probably a somewhat smaller jump.
It’s almost certainly not the case here as you were seeing the others in your group, but remember that appearing on PAW RADAR but not on SkyDemon can simply be to do with your filter settings as your PAW Radar Screen is fed with RAW received data, whereas the data used to drive SkyDemon is subject to any filtering set in PilotAware AND any additional filtering set in SkyDemon. In this case however, you must have had ‘Mode CS’ selected in PilotAware (hopefully ‘+ Filter as you are transponder equipped) as the others are all showing as CSA. Out of interest - what Mode CS ‘Range’ and Vertical Display Range were you running? Same question for SkyDemon - Did you have ‘Show Bearingless Targets’ turned ‘On’ in SD - It’s now ‘Off’ by default and might have defaulted to this on your last SD update so worth checking. What did you have ‘Show Within Vertically’ in SD set to? As I say, almost certainly nothing to do with why G-SLNT wasn’t showing though.
I did wonder whether there was any filtering going on, but I'm not aware of any other than the vertical and horizontal extents. I thought I'd read there was a way to filter traffic (i.e. those you're flying all the way with) on the SkyDemon radar view, but I've never been able to get it to do anything other than show the corner bigger. Interesting that the radar display is RAW but the feed is further filtered in PilotAware before going to SkyDemon.
All settings you mention seem fine:
I assume automatic decluttering doesn't affect aircraft targets?
I was getting some bearingless targets, but presume these were other unsighted aircraft rather than a corruption of G-SLNT (e.g. one had what appeared to be a valid French registration).
You should be able to replay your track files using James Rose’s excellent replay tool at https://aircrew.co.uk/playback/ though I can’t remember if it differentiates between source systems.
I have a few tracklogs due to PilotAware drop-outs that I separately need to resolve, but I've put a large 20MB one on there (
https://aircrew.co.uk/playback/2de11d) and a smaller 642KB one (
https://aircrew.co.uk/playback/afc2f1). This seems to confirm G-SLNT is only received as PilotAware and no transponder, but doesn't explain why the PilotAware position was not shown on my SkyDemon (yet was on the radar).
the strange thing is not being visible in SD but it is in PAW-RADAR
If I can get a track file for this, it may give some clues.
2019-09-01_09-34.trk (20MB)
2019-09-01_12-09.trk (642KB)
What 3rd party connection method is used in SkyDemon ?
PilotAware.