netshadoe

MSFS weather for me.

Same here. It was severe clear yesterday here. We went for a walk in the hills in the afternoon to a lookout where I could see 50+ miles. Got to MSFS later yesterday evening, couldn’t even see the city from the airport which is about 5 miles due to the ‘haze’. It’s definitely not the same as before SU7

Clarification from RSR: https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/407552-collaboration-with-gaya-simulations-really?p=407575#post407575

Before people, how about we bring back landing gear?! 😆

You’re the best! Thanks Nico!

Good evening Kiek, Looks like the new FSR model isn't registering properly. I can't find the proper file to correct it to E55P, most likely since the aircraft is a Marketplace aircraft, so the files are either encrypted or streamed. SimConnect: user aircraft title: FSReborn Phenom 300E PRO Manchester Interior model raw: $$:Phenom 300E User aircraft wing span unknown, max is taken instead, please report in my Forum! Thank you once again as usual Kiek! Devin

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.