RealTraffic 1.0 beta and updated Foreflight 2.0 beta

[Balt]

Sorry I thought that was evident... let me explain:

PSX has one client always connected for these tests: DFDR. DFDR records everything sent to it, and if the time elapsed between messages is larger than 10ms, it records a timestamp as well. That's how I'm timing the Qs450 messages being received by DFDR above.

When PSX generates its own traffic, one Qs450 message is received every 5 seconds.

When RealTraffic is connected, DFDR receives two identical Qs450 strings every 9 seconds, the injection interval of RealTraffic.

I just saw your edit, and that's a good question. I can't imagine why I'd be sending two traffic strings. I'll double check.

Cheers

- Balt

[Balt]

Hardy, I just had a look. RealTraffic positively sends the Qs450 string only once per 9 seconds.

Cheers

- Balt

[Hardy Heinlin]

I think I have found the cause of the double ejection, and it should be eliminated now in 10.0.2.

This double effect was in TfcPos and also in TfcVel.


Cheers,

|-|ardy


A minor problem in RealTraffic 1.0 beta: When the server disconnects or quits, and restarts, RealTraffic cannot reconnect until RealTraffic is relaunched.

[Balt]

RealTraffic 1.1.14 is now out. It automatically reconnects now when PSX goes away, or when PSX is not there when it starts.

Hardy: This is the second production release, i.e. no longer beta.

Cheers

- Balt

[Hardy Heinlin]

Balt, I'll put a link to your add-ons on the Aerowinx site as soon as my head is free :-)


Cheers,

|-|ardy

[Balt]

Thanks Hardy!

Question: Would it be possible for us addon developers to receive a pre-release 10.0.2 copy to make sure all works as expected? Otherwise it could be a rather mad rush to fix things in case the release breaks anything.

Cheers

- Balt

[Robert Staudinger]

Hi Balt,

thanks again for your efforts to get RealTraffic running.
But, maybe I'm wrong, I think the lines(contrails) behind the targets should be to the opposite direction.

Regards Robert

[Balt]

Hi Robert,

They're not contrails, they're trend vectors, they show where the airplane will be in about 1 minute if speed and direction are maintained. It's all a matter of perspective. You'll get used to it...

Balt

[Robert Staudinger]

O.K

[Balt]

Hi all,

I discovered a flaw with how the address for the traffic broadcasts was derived. That's fixed now for both the Foreflight connector and RealTraffic. Please download the updates. And also note the changed URL: http://www.inside.net/ss/   where ss = simulation software.

I also improved the website a little bit, more coherence between the appearance of the products, and a clear statement what was changed between the versions. I was a bit sloppy beforehand.

Hardy: When you place a link to the Addons page, just send them to the /ss page please. Thanks!


Cheers

- Balt

[Britjet]

Thanks Balt. Still nothing visible on P3D with the new PSX beta by the way..

Britjet..

[dts]

I see them but intermittently, it sort of flashes on and off again.  This is on the latest version

[Balt]

Hi guys,

sorry 10.0.2 doesn't solve it. I just tested 10.0.2 beta 1 and it no longer sends the double Qs450 messages when traffic is being injected. So that appears to not be the problem, sorry.

I really need the input from one of the scenery plugin developers, they're the only ones who can track the traffic data as it makes its way across the network and into the various components that need to know about it... Sorry I can't be of more help with this.

Cheers

- Balt

[Garry Richards]

Hi Balt,

Good news! I've been able to check the TrafficPSX code and found a condition I had forgotten about. I use the PSX traffic mode variable to set external mode when injecting from FSX, but I also check that it is set to one of the PSX output values before accepting traffic from PSX. So it was rejecting all traffic resulting from injection. When I removed the condition I started seeing traffic in the TrafficPSX display.

So good data are being sent from PSX when you inject traffic into it. I will release an update to TrafficPSX soon.

RealTraffic is impressive. Congratulations!

Cheers,

[Balt]

Garry, I'm glad to hear that, thanks for looking into this!

Cheers

- Balt

[GodAtum]

Is the developer of Xview able to have a look into the traffic generation issue too?

[ScudRunner]

G'day Balt,

Firstly, thanks so much for this brilliant add-on.

I had a thought/suggestion that I wanted comment on.

When operating close to  a major airport, RealTraffic is picking up (understandably) aircraft on the ground near to my location. Sometimes to the extent that almost all the 7 `slots' available for injection to PSX are taken up with ground traffic. It may mean that aircraft on final approach to my rwy will not display (or only at the last minute) when I am at the holding point.

Just wondering if an option to filter out ground aircraft (possibly those below some nominal groundspeed value) could be included when building the list of aircraft to be injected?? I do appreciate that the scenery generator people will want to have ground aircraft included hence my suggestion of it being a selectable filter.

thanks again for your hard work
Scud

[Balt]

Hi scud

Indeed that's why originally I filtered out ground traffic. I'll make it a selectable option in the next release.

Cheers

Balt

[Garry Richards]

Hi Balt,

I agree with Scud and recommend that you don't send ground traffic to PSX.

When I inject traffic from FSX into PSX I filter it on these criteria:
. airborne
. within 40 nm laterally
. within 7000 ft vertically

If there are more than seven aircraft in range after filtering I select them on slant distance from PSX, that is by using both lateral and vertical distances.

——————

I have now had time to examine the traffic output from PSX when RealTraffic is injecting and have found some problems in your output. I experienced the same ones at first and found the solution by discussions with Hardy, but the details haven't made it into the documentation.

Two conditions have to be applied to injected traffic data because PSX cannot identify individual aircraft, there being no call signs in the data string. The conditions are:

. When an aircraft is assigned to one of the seven slots it must remain in it and not move to another slot. This enables PSX to track and display it correctly. The slots don't relate to how close the aircraft is to PSX.

. When an aircraft is no longer in the selected seven PSX must be advised by sending empty data (all zeros) for that slot before using it for another aircraft. So two cycles are required to replace one aircraft with another. If aircraft leave and are not replaced then some slots will become and remain empty.

——————

The TfcVel output contains errors. If PSX is generating it instead of RealTraffic then errors would be expected with aircraft changing without notice. The table below shows some captured data:

Code Select Expand

Slot Lat deg Lon deg     Alt MSL   Track ft/min deg/sec kt

1 -34.1038 151.2079 2899 36 0 0.00 0
2 -34.1130 151.1988 2170 15 -1078 -0.10 304
3 -33.9727 151.1928 781 122 15384 -15.20 148
4 -34.1018 151.1004 5225 212 0 -3.39 0
5 -34.1451 151.2699 2289 290 0 0.00 0
6 -33.9422 151.1769 0 344 0 -0.31 15
7 -33.9408 151.1767 0 345 0 0.00 11

1 -34.1038 151.2079 2899 36 0 0.00 0
2 -34.1086 151.2004 2175 15 -1078 -0.10 304
3 -33.9711 151.1915 0 165 15384 -15.20 148
4 -34.1451 151.2699 2289 290 0 -3.39 0
5 -34.1180 151.0896 4925 208 0 0.00 0
6 -33.9424 151.1770 0 345 0 -0.31 15
7 -33.9410 151.1767 0 345 0 0.00 11

1 -34.0987 151.2036 2125 15 0 0.00 0
2 -34.1038 151.2079 2899 36 -1078 -0.10 304
3 -33.9713 151.1919 0 106 15384 -15.20 148
4 -34.1451 151.2699 2289 290 0 -3.39 0
5 -33.9426 151.1787 0 165 0 0.00 0
6 -33.9414 151.1768 0 345 0 -0.31 15
7 -34.1304 151.0875 4725 182 0 0.00 11

1 -34.0913 151.2061 2075 15 0 0.00 0
2 -33.9712 151.1925 0 81 -1078 -0.10 304
3 -34.1451 151.2699 2289 290 15384 -15.20 148
4 -33.9432 151.1789 0 165 0 -3.39 0
5 -33.9409 151.1766 0 345 0 0.00 0
6 -34.1304 151.0875 4725 182 0 -0.31 15
7 -34.0274 151.3469 5761 160 0 0.00 11


Cheers,

[Garry Richards]

For others following this thread, the current version of TrafficPSX has a condition that prevents it responding to external traffic inputs so you still won't see traffic in FSX if Balt provides an update to RealTraffic.

When I have tested any updates to RealTraffic and made the required changes to TrafficPSX I will release an update to TrafficPSX.