zachlog

During a flight departing WSSS, BATC's instructions to taxi from Terminal 2 to the active RWY 02C were via taxiways C1 EP E11. When I looked at the airport chart in Navigraph (chart 10-9, dated 31 July 2026), these taxiways did not lead to the RWY 02C threshold. My initial reaction was that BATC had given me incorrect taxi instructions. When I started taxiing, I noticed that the airport signs were an exact match with the BATC taxi instructions. The odd man out here was the Navigraph chart. Has anyone else seen these inconsistencies ? Do Navigraph airport charts not match what's in the simulator frequently ? What's the user experience on this issue ?

OK but where is this Option ? In the MFD, there is the Simbrief button and then REQUEST and IMPORT.

In the C700 Longitude, loading a FPL from Simbrief has stopped working. I already reinstalled the plug-in, same results. This does not appear to be an authentication issue because accessing Navigraph's Charts application from the MFD works fine. Below are the steps I go through prior to seeing the error. If there is anyone who has seen this problem, please let me know. Request the FPL from the MFD/Simbrief. The option to IMPORT the FPL appears and I click on it. The IMPORT starts but does not complete. Initially, the ORGN and DEST airports are visible in the FPL but no waypoints are present. When I attempt to add a waypoint manually, "Searching....." does not find the waypoint and subsequently I get error message: An Unexpected error occurred when importing a flight from Simbrief. Error: FacilityLoader: facility could not be retrieved for ICAO WK6 BIGGY At this point, the ORGN and DEST airports disappear and the FPL is blank as if the IMPORT was never executed.

It might pickup an altitude I enter in the AP but how will it know which AP entry is THE CRZ flight level ? As the A/C climbs, multiple altitude entries are made in the AP.....ATC insists on this !

I am new to this aircraft and have a couple of questions. After loading a flight plan (FP) from Simbrief, the altitude/flight level for each waypoint in the FP was blank. After entering the CRZ flight level for one waypoint, all subsequent waypoints acquired the flight level I had entered. When in the flight plan and I select VNAV, I can enter the CRZ speed but I don't see a field for entering the CRZ flight level initially and potentially updating it later during the flight. Where is the CRZ flight level managed ? What I am looking for is the equivalent functionality of the FMS CRZ page in Boeing and Airbus aircraft. Secondly, when landing and the wheels touch the runway, is the AUTO deployment of the spoilers possible in this aircraft ?

When asking for help in this or other forum, you are looking for specific actions you must take to accomplish your objective so your question must also be very specific. Currently it is not. List the steps that you executed, and for EACH STEP, specify what you were trying to accomplish in that step (e.g., turn-on the AP), how did you execute that step (e.g., clicked the AP button on the MCP) and what did you observe after executing that step (e.g., expecting the AP light to illuminate but it did not).

Good enough, I was just looking for an approximate number....thanks.

How many liveries are included in the base product ?

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).