zachlog

I understand that there is no positional data coming from FR24 and frankly AI aircraft positional accuracy does not interest me. What I am interested in is BATC coordinating the positions of my A/C and AI aircraft so that there are no "collisions"/positional conflicts. This is where native MSFS 2024 AI traffic fails miserably and FSLTL mitigates the risk of such occurrences with its in-cockpit RESET TRAFFIC capability. Is my expectation of BATC unrealistic ? Will the product not manage positional coordination ?

This "more often than not you get cleared to taxi into AI traffic (or them through you)." is a big problem, perhaps the biggest. It is the single most important reason I will not use native MSFS 2024 AI. FSLTL has the same problem but this risk is mitigated with the in-cockpit menu to reset traffic during critical times on the ground. I highlighted BATC's AI traffic management shortcomings in the survey they are running currently (subscribers only). With the upcoming integration of FR24 traffic into BATC, it sounds like this is a focus area for them. I hope I am right.

Not strange but I bet you're seeing only static aircraft. I too noticed this because I forgot to change my desktop's shortcut and I was executing Injector v1.9.x (thus my problem above). After fixing the shortcut, I was able to authenticate with Injector v2.0. However, I see lots of parked aircraft but nothing moving. Not sure how long it takes for active traffic to appear.

I followed the instructions for installing the Injector 2.0, all went well, was prompted for the "y", saw the various FSLTL messages in the command/terminal window.....but the web page to authenticate with NAVIGRAPH did not open. How do I fix this ? Is there a URL I can open manually ? Thanks

Thanks for clarifying.

For products that inject traffic, for me the single most important factor is AI traffic being aware of my aircraft's presence and AI aircraft adjusting their behavior accordingly. AI aircraft going through my aircraft like a hot knife going through butter, especially at intersections and runway holding points, is a show stopper regardless of the level of sophistication of other features. How will the new FSHud release manage AI aircraft behavior with respect to my aircraft ?

I gave the default Real-Time traffic a try and it seems to work fine just like FSLTL with one major exception. With either FSLTL or default Real-Time traffic, the biggest problem for me with these uncontrolled A/C roaming around in airports is that they are.... uncontrolled- they cut you off at taxiways, go through you, etc. so what we gain in realism visually, we lose functionally. FSLTL had mitigated this problem via the in-flight menu by giving us the option to remove nearby A/C or reset air traffic. For me being able to avoid such occurrences at critical times, e.g., while taking off or landing was key. There is no such option with the default Real-Time traffic and for me this is a show stopper. Taxiing becomes a video game especially in busy airports. In the near-term I will continue to use FSLTL since the eye candy aspect of flight simulation is low on my priority list and make a longer-term decision later (I have seen the various posts with other options).

What are some of these alternatives to which to which you are alluding ?

I think you are misinterpreting "commercially dead". It means no new development, no new products for MSFS 2020. It does not mean they do not support products developed previously for this platform. If you own a PMDG product, you can go to the OC3 Support page and take a look at the workflow to open a ticket. In the dropdown to select the simulator where the problem is occurring, MSFS 2020 is very much one of the options among quite a few others. In the future, they might very well drop support for MSFS 2020 but it will be announced in no uncertain terms and they will not rely on some ambiguous term.

I am assuming this path is what you specified in the PMDG OC3 settings as the Community Path (regardless if it's MSFS 2020 or 2024). If this is the case, does this path match the path of what you believe to be the simulator's Community folder, i.e., where all the rest of the "community items" reside ? If the answer is "No", this is your problem.

This URL is coming-up as "Invalid Page....".

I tried using the automated pushback and it seems to work but I think I will continue doing manual pushbacks for a couple of reasons. First, the speed of the pushback is too high for 75+ ton aircraft. It is not realistic and I don't think the the speed can be adjusted. Let me know if otherwise. Second the user interface is not very user friendly so I don't want to spend time getting that just right. For me it is not worth the effort. Manual pushback does a great job with customizing the path of the pushback and being able to manage the speed, especially when turning. Thanks

Good question. When I had first attempted to do an automated pushback in MSFS 2024, it did not work. What I cannot remember is if I had re-tried doing automated pushbacks after I had updated the MSFS 2024 Global settings and got the manual pushback to work (my 2nd post further up). I will give it another try.

I do approximately 7-10 flights weekly evenly split between PMDG and Fenix aircraft. I migrated to MSFS 2024 gradually starting mid-2025 and got frustrated immediately with pushback because Pushback Toolbar (PT) was no longer working for PMDG and Fenix aircraft. What was frustrating me was that the simplest but absolutely necessary phase of a flight was not working and there was no way to fix it without installing a complex product. What ticked me off even more was that when PMDG released the B77W, it did not include the pushback functionality that was already in the B738 MSFS 2020 version since the beginning of time. This delayed my migration to MSFS 2024. About 2-3 months ago, 787flyer from this forum (God bless him !) finally pointed me in the right direction. When using PT, Assistance | Realism | ATC Enforce Flight Plan must be OFF. Leaving it ON creates a conflict with PT and the A/C begins to move all over the place. In my case both PMDG and Fenix aircraft were impacted in the same way. It is also possible that several other settings related to native ATC functionality must be OFF as well. I had set these to OFF day #1 so I cannot say with certainty how they impact the PT since they were already OFF even when I was having PT problems. As I indicated in my previous post, prior to starting tug movement, you must remove the chocks and you must release the A/C's parking brake. If you don't, the A/C will start rising as if it it being levitated 😀 and it will come down slowly to the tarmac when pushback is terminated. The PT's automated pushback and voices do not work in MSFS 2024. For me this is a non-issue.

If you're looking for a no frills pushback tool that does not add risk to the stability and reliability of your simulator environment, I recommend the Toolbar Pushback from flightsim.to. It works in MSFS 2024 just like MSFS 2020 but with a couple of limitations. No automated pushback/manual only and no voice support. Both of these limitations are non-issues for me.