netshadoe

The word “live” is a misnomer in FSLTL…it’s not really a “live” 1:1 mirror of FR24. It uses live data to obtain the information on what to inject into the sim. Once the sim gets hold of the AI, it takes on its own life separate from the real world. The better way to describe what FSLTL provides is a “plausible” world of AI aircraft based on “live” data from FR24

Sorry I haven’t been able to test. I work 12 hour days in my discipline, so I don’t get much sim time during those days!! Today is my Friday, so I hope to take a peek tomorrow….barring the honey-do list isn’t too long! 🤣

Since you’re working on it, I’ll wait unless you need something from me, such as logs. I had another instance yesterday where a Porter Air E2 froze on the taxiway C at CYOW, but the target in RT looked “OK” from the data tag I could see, and took off on Rwy 07 and turned west toward Toronto. The E2 stayed there until the timeout. I get that the data tag is RT’s internal info and may not reflect what PSXT is receiving from the API. It more to point out that RT has a target, and there is a miscommunication somewhere in the system. Thanks again Nico for all you do for the hobby!

So I am clear on this then.... You're saying that the Air Canada 737 I watched PSXT taxi from the terminal to runway 25, using the target data that RT was feeding to PSXT (RT=RealTraffic, the app that PSXT draws data from so we are clear) that I watched on the RT map screen in real time, side-by-side on the same computer....it then taxis out on the runway just like the RT app...then the 737 just sits there on the threshold for five minutes. Meanwhile, the same target on the same RT app that is feeding PSXT does the takeoff and is nearly 40 miles away when the forgotten Air Canada 737 on the threshold is deleted (5 minutes or so). So, what I'm trying to wrap my head around is why would PSXT stop using the data from the same target that remained on the map in RT - it was there - it didn't change or glitch out - it flew for 40 miles from takeoff until the 737 was deleted. It's hard to convey in words what I'm seeing. But, are you saying that the data in RealTraffic is ignored by PSXT when certain parameters and factors are involved?

I’ve seen this too. I was at CYOW on the ramp just watching AI for a bit. An ACA flight lined up on 25. It never took off in the sim, but the “blip” in RT was already moving. The ACA flight just sat there for 5 minutes doing nothing, meanwhile the ACA blip on RT was already about 30-40nm out. Landing traffic just kept coming in over the ghost plane. Littlenav map also showed the ghost ACA plane just sitting there. There was no 2nd ACA plane injected for the actual blip shown by the RT app. I also see ground traffic disappear or cut corners too even though they are smooth on the RT map. I just attributed this as a glitch, but it happened again last night with a Porter Airlines jet. I’ll keep an eye out for it again and send logs if I see it.

Fair enough! 🙂 All good. Thought I'd ask anyway. Been with you right from the beginning. Thanks for everything you do for the hobby!! That's fair too. 🙂

Both. The TCAS diamond disappears, and so does the plane in LNM, and obviously in RT (😉). TCAS would be better than nothing. However, that being said, it would be more immersive to have the AI injected, especially on airways in the South Asia/Oceania area where pop in and pop outs happen more frequently, and is visible when your following 2000 feet underneath it! Would RT doing this calculation be a better solution? Maybe, when the feed is lost on Balt’s end, RT would persist any aircraft over a certain altitude (10000ft for example) for up to XX amount of time (a setting in RT). It would be a different colour on the RT map showing that the “target” is projected, and a telemetry data flag from RT that also indicates this. The data flag can be read by Traffic programs (like PSXT) so that an option to turn the feature on or off can be implemented depending on the user’s tolerance to possible reposition issues when the data becomes live again.

I’m flying around Southern Asia, Indonesia, Australia and the South Pacific islands. Some airlines are better than others. It was just a thought. I get that there can be syncing issues once the feed comes back, and not always desirable, that’s why I mentioned different settings for how long the aircraft would persist...or the option to turn it off if not wanted. It doesn’t have to do anything special. If it was cruising at FL360 at 450knots heading 180, PSXT would just maintain the last valid set of variables until it’s picked up again. Once it hits the selected limit, it would cull the flight. If it’s not feasible, I get it. I was just seeing if there was a way to “fill in the gaps” for a little longer.

Hi Nico, I notice flying in certain parts of the world and over oceans that the traffic pops in and out at times due to limitations of receiving data in those areas, thus RT loses the granular data and basically removes the flight. This causes PSXT to remove the aircraft suddenly and then pops it back in, like a light switch being turned off and on sometimes. 😄 I would like to make a suggestion based on how Flightradar24 works with air traffic on its maps. A quote from their settings: ”An aircraft's position can be estimated for up to 240 minutes after it exits Flightradar24's coverage area.” In these settings, the user can choose to have the aircraft continue on its last course, altitude and speed. The settings are (in minutes) 15, 30, 60, 120, 240, and of course OFF. Could this be added to PSXT where the program would keep the airborne AI in the sim if the feed for that aircraft from RT is lost? Once RT reacquires the aircraft and starts send data again, PSXT would then update accordingly? Thanks for the consideration.

No problem Nico. Like I said, zero rush! Really appreciate all you do. I wish I had the computer skills to contribute something to the hobby, but, alas, my talents lie elsewhere!! 😄

OK. I have a few more answers/clues for you Nico! So, I loaded up the simulator and started RT on the networked machine, and PSXT on the FS machine. All was good, traffic was in the sim, and communication between the two apps was working as expected. Using MSFS, I changed the time (slid the slider back a few hours), and waited for PSXT to update RT with the time change. Nothing changed in RT refecting the new time offset. However, if I killed PSXT and waited until I got the red warning in RT "PSXT Buffering...", and then restarted PSXT, the offset would be set in the remote RT app. Though this worked, further changing of time did not update the offset, and I would have to repeat the steps above to get the offset to "set". *** Alternately, I can get RT offset to update by changing from "RT App" to "RT Direct" and back to "RT App" in PSXT (forces an update). So, in a nutshell, if PSXT and RT are live and running together, the offset doesn't auto update in realtime if I change the sim time. I have to manually shut down PSXT, wait for the red buffering warning in RT, and then restart PSXT to get the offset to "set" properly. Any further movment of the sim time after both apps are running does not update the offset. Hope that makes sense. 🙂 P.S. - Checked the firewall on both machines. Its open to all TCP and UDP and open to all ports for RT and PSXT on their repective machines that I can see.

I’ll try it again later today when I get home. But for the record, yes I did have the setting ”Simulator controls time offset” turned on, and the bar on RT says the time is simulator controlled, but it doesn’t adjust to the offset. I CAN see traffic fine, so it is talking across the network to PSXT. I'd happily work with Balt on this, however, his forum times out on me using either my home internet connection or my cell provider who are both different internet providers here in Canada. I can access his forum once, look at one or two pages, then it just times out on me (servers are not responding). It used to work reliably, but no longer, so I can’t see his forum, and obviously, I can’t post. I’m a pretty computer savvy person, so, that one I’m at a loss unless his phpBB settings are causing it. I have no issues accessing other phpBB forums, so who knows. I’ll test again and see if opening the port in my firewall will help, but like I said, I can see traffic fine, so RT and PSXT are communicating over the network.

I do have a professional license, yes. The RealTraffic offset was working with PSXTraffic when it was local. So, as a test, I ran RealTraffic and PSXT14 together local, and set PSXT to RT App. The time scaling in RT scaled with the sim time. However, when I closed RT on the local, and restarted PSXT and the networked RT app, the time scaling does not adjust. The time selector in RT is locked out, and says it’s simulator controlled, however, it doesn’t adjust to sim time like the local version does. i appreciate all you do for the hobby! No rush on this, just wanted to let you know. I like having the RT app open to see the local weather and traffic, so having it on another screen is an awesome option, but not a show stopper for me! Thanks again!

Hi Nico, I'm running PSXT on the MSFS machine, and RealTraffic on a networked machine. I get traffic injection no problem, however, the PSXT/RealTraffic app does not sync with sim time. I have the "Simulator Controls time offset" selected in the advanced options in RealTraffic, but the time remains static in the RT app. It seems that PSXT is not sending Sim Time to the networked app. Sim Time sync does work in PSXT, though, using RT Direct.

Awesome! Thanks for considering it!