Vel

@Wise87 - I had the exact same experience. There is a checkbox in GSX Settings -> Troubleshooting to "Disable hotfix notifications". I have selected that option to help avoid any further issues! I like the new menu system and appreciate the effort thats been put into V4 but Im seeing mixed results from flight to flight. The once reliable Fenix integration now sometimes works and sometimes doesnt for reasons I cant fathom. I often get refulling but no passenger boarding and sometimes get nothing.

@malichek As I remember it (I was using FSHUD at the time), FSLTL said that FSHUD could not use FSLTL becuase FSHUD was a commercial, paid for product, whereas FSLTL was free to use. That was seen as a contradiction. What confused things at the time and gave some conspiracy theorists something to chew on was that one of the main FSLTL developers joined BATC, a direct competitor to FSHUD around about the same time.

Something is broken in 3.9.6. The interface with the Fenix A320 normally works well but now nothing happens. GSX menu has the select a gate options. It may well be another case, as mentioned earlier in this thread, of the gate I'm parked at being considered too small. Odd if it is becuase Ive used the same gate at EGPF numerous times.

The latest patch seems to have cured my load time problem in FS2024. Tested at a small, stock airport (EGNT) and the load time was less that 2 minutes. Exited the sim and tested again with a custom airport (EDDF) and the load time was again less than 2 minutes.

Thanks for mentioning that @qqwertz. I have experienced the 15 minute wait too and basically gave up on using the aircraft becuase of it. My SIM time is limited enough without waiting for 15mins for an aircraft to load. I'll try the new version and see if it has improved for me.

I wonder if it would be possible for FSLTL to use historic FR24 data as per BATC? Far from ideal but better than nothing?

I simply fill in the Airline (ICAO) code and Flight number on Simbrief as you mention above but do not enter the ATC Callsign. BATC will use the Airline Code + Flight Number for your callsign.

@sd_flyer - It may be due to GSX integration? As part of the pushback call you get the direction to face. It has always been fine until recently.

Ive been happy to live with the various issues with BATC since I bought it. I know its a work in progress. I have to say however, that since the last update it has been markedly worse. In my last flight alone: told to push back and face the wrong direction. had a standoff with another aircraft taxiing towards me. told I was number 2 for takeoff when I was the only aircraft waiting to depart. I never recieved takeoff clerance. Took off and was told to stop immediately. (I didnt.). had an aircraft cleared for takeoff at my arrival airport, on the same runway, when I was already on short final with landing clearance. I know its early acess and I know the development process may well cause bugs to be introduced but the performance of the last release, compared to the improvements listed in the release notes, has been pretty woeful for me. (This is EA release not Experimental).

@CFIJose yes I did read the thread. Thanks for asking. I'd rather wait and see what solution, if any, FSHUD comes up with than buy it now and use an older version of FSLTL.

Pity. I was about to go back to FSHUD (as in buy it for FS2024 - I have the FS2020 version). The latest version of BATC seems to be causing more issues (for me) than Ive ever had before so it seemed worth a try. With no FSLTL I guess I'll have to wait until FSHUD comes up with a solution.

Had the same feeling almost a year ago and went for the AMD RX 9070 XT. I have not regretted it. Worth looking at as an alternative.

@Trinco I had a similar issue. Deleting the WASM files eventually fixed it for me. (I had to do it twice). Make sure that you also delete the Work folder in the directory with the WASM files. For me the WASM folder was at: C:\Users\<your username>\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\aerosoft-aircraft-a346-pro which was a bit odd as Im using FS2024 and the WASM directory has MSFS2020 mentioned in the filename path. Deleting the WASM files meant I had to reregister the product, reconnect to Simbrief and recalibrate the throttles.

Textures seem a bit lacking, wing flex is wrong and the flight model needs some work...😁

I was curious too and Google came up with this... System Specificity (A340/330): While some Airbus models (like the A320) might accept a raw number, the A340, especially in detailed simulations, requires the "F" (or "F" followed by the temperature) to ensure the computer distinguishes it from a DERATE input, where the character "D" might be used.