LukeSkyBellic

Well, it's those who know how to get their hands on it who don't seem to care.🤤

I read a post from August 2024 where a user complained that the jetways at OMAA (Terminal 3) weren't moving. Since someone said "we'll take a look," but... the jetways still aren't working... I'll try reopening the discussion. The changelog for the latest version v1.0.3 says it's been fixed, but that's not the case. I enabled and then disabled the jetways in FSTD, but nothing changed.

the a330 now finally allows screen tabbing... any news on a Mobiflight or SymAppPro profile for the MCDU?????

Unfortunately, this is a problem I've encountered and am currently experiencing with the A333. I'm flying KJFK-EIDW with "adjust vertical speed" and "maintain vertical speed" constantly. This problem has occurred with the A350 and A330, but they're also the only IniBuilds aircraft I fly. Will it be resolved?

...two months later and after a few updates, the problem persists. I have absolutely no traffic, yet I still have the red warning in V/S. It lasted the entire flight (10 hours). I tried deactivating TCAS and reactivating it, but it relentlessly returns. To remove the warning, I have to set it to TA Only or deactivate it completely.

I hope someone can answer me, because it seems to me that for free planes, there is little support. But I hope I'm wrong!! Since I wear glasses and like me many people have multiple monitors for the instruments, I was wondering if it was possible to implement, as for any other MSFS plane, the ability to bring the instruments on external monitors. Especially ND and PFD. Thank you very much!!

the same thing has happened to me several times. Yesterday it happened to me on final after a 7 hour flight. I noticed that they tend not to respond regarding "free" planes

since he didn't get any answers but it interests me too......

Have you had any improvements since the release of 1.0.9?

L'ultimo volo l'ho fatto con l'SU2, seguendo meticolosamente le istruzioni sull'eliminazione delle cartelle ecc. ecc... e dopo 6 ore di volo la cabina di pilotaggio si è bloccata. Il simulatore funzionava, ma l'aereo era bloccato. Era la quarta volta che provavo EGLL-RKSI con Asiana!!

the last flight I did with the SU2 and following the instructions meticulously on deleting folders etc etc... and after 6 hours of flight the cockpit froze. The simulator worked but the plane was stuck. It was the fourth time I tried EGLL-RKSI with Asiana!!

I just had to abort a flight EGLL-RKSI for the same reason!! Never had anything like this happen with previous versions. Before 1.0.8 everything worked perfectly!!

I just had to abort an EGLL-RKSI flight because at some point the controls stopped responding! Only the OIS worked but not even well because I launched an autosave now that was never created. Is it not possible to go back to version 1.0.7?? Unfortunately I have not saved the file anywhere, because I update via the Ini Manager. Before the last update everything worked perfectly.

Sure!! Don't worry!! When entering coordinates in the secondary navigation display, you cannot enter values higher than 89.59.9. I have a coordinate of Seoul N37.28.0 E126.26.4 that I cannot enter

Unfortunately it's official: with the latest patch 1.08 there are multiple crashes!! This is the report of the last (my system is in Italian language) Nome dell'applicazione che ha generato l'errore: FlightSimulator2024.exe, versione: 1.3.25.0, timestamp: 0x00000000 Nome del modulo che ha generato l'errore: WTF.dll, versione: 0.0.0.0, timestamp: 0x6749d236 Codice eccezione: 0x80000003 Offset errore 0x00000000000023cb ID processo che ha generato l'errore: 0x0xB28 Ora di avvio dell'applicazione che ha generato l'errore: 0x0x1DBB3B92EEECCF6 Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\Steam\steamapps\common\Limitless\FlightSimulator2024.exe Percorso del modulo che ha generato l'errore: C:\Program Files (x86)\Steam\steamapps\common\Limitless\WTF.dll ID segnalazione: 88419ac3-a99c-4132-8af9-13cad9fbe710 Nome completo pacchetto che ha generato l'errore: ID applicazione relativo al pacchetto che ha generato l'errore: