35 minutes ago, carlanthony24 said:

Not to mention that it took FSLabs a whole MSFS game and over 4 years just to release a 321CEO and miss what I suspect is a load of buyers. Oh and still bring bugs from P3D in the 4+ years it took them to come to MSFS. We didn't have an update from FSLabs at all. At least we got updates from developers. IFly works fine just like the Fenix works fine in 24 regardless if its not fully native or supportive they do help to troubleshoot some things with 24 though so support is still given.

Have to agree with RNAVV19R the IFly flies so much better than PMDG.

LMFO FSLab nevers annonced any aircraft for MSFS before mid 2022 ... and FSLAB release Concorde  for P3D late 2023. so your argument is invalid 

Edited July 20, 2025Jul 20 by seb851

39 minutes ago, seb851 said:

LMFO FSLab nevers annonced any aircraft for MSFS before mid 2022 ... and FSLAB release Concorde  for P3D late 2023. so your argument is invalid 

Exactly my point May 2022 they confirmed development plans. MSFS 24 was already out by the time they released. Nearly 2 years of silence before that and then guess what more silence for a few more years.  My argument is very valid. Near enough 2 years after MSFS 2020 was released. Again with P3D bugs still in the aircraft. So much time for development still to release with the same old bugs from P3D. Mean while most developers had started converting over or had already released first batch of aircrafts. How late would you like them to be. Releasing Concorde for P3D was a big mistake and generally the community all said they should of released the A330 or at least the NEO not nearly 5 years down the line.

Its funny when facts are presented to you, you try to counteract them. Face it they were very late to releasing.

Edited July 20, 2025Jul 20 by carlanthony24

4 hours ago, carlanthony24 said:

Exactly my point May 2022 they confirmed development plans. MSFS 24 was already out by the time they released. Nearly 2 years of silence before that and then guess what more silence for a few more years.  My argument is very valid. Near enough 2 years after MSFS 2020 was released. Again with P3D bugs still in the aircraft. So much time for development still to release with the same old bugs from P3D. Mean while most developers had started converting over or had already released first batch of aircrafts. How late would you like them to be. Releasing Concorde for P3D was a big mistake and generally the community all said they should of released the A330 or at least the NEO not nearly 5 years down the line.

Its funny when facts are presented to you, you try to counteract them. Face it they were very late to releasing.

Don't argue with a FSL word not allowed  you will never win. Just avoid him.

 

5 hours ago, carlanthony24 said:

 

Have to agree with RNAVV19R the IFly flies so much better than PMDG.

To be honest I do not know about that  but we can agree or dissagre.

11 hours ago, flyingpicket said:

and cannot get any of my TCA joystick buttons, or keyboard binds, to work on the overhead light switches; strobes, taxi lights etc. totally baffled.

I use FSUIPC console to identify the rotor brake codes when operating the switches, then bind them to controller buttons. The codes can also be found in the 'FSLA32X_Interior.xml‘ file located in the aircraft folder (for example):

D:\MSFS\FlightSimLabs2024\fsl-common\FSLabs\EFB\FileSystem\SimObjects\Airplanes\FSLabs A321-NEO LEAP\Model

Look for a heading like 'VC_GSLD_CP_EFIS_Baro_Knob'...

Edited July 20, 2025Jul 20 by flyingscampi

1 hour ago, flyingscampi said:

I use FSUIPC console to identify the rotor brake codes when operating the switches, then bind them to controller buttons. The codes can also be found in the 'FSLA32X_Interior.xml‘ file located in the aircraft folder (for example):

D:\MSFS\FlightSimLabs2024\fsl-common\FSLabs\EFB\FileSystem\SimObjects\Airplanes\FSLabs A321-NEO LEAP\Model

Look for a heading like 'VC_GSLD_CP_EFIS_Baro_Knob'...

I miss mouse macros SOOOOO much. Could setup a whole plane in 10 mins before, now it takes a day if a dev uses unconventional commands, animations and procedure calls. It's 2025 why can't I click a button on screen and the sim assign a hardware button to that hook? 

Open up the sdk already ASOBO. 

3 hours ago, flyingscampi said:

I use FSUIPC console to identify the rotor brake codes when operating the switches, then bind them to controller buttons. The codes can also be found in the 'FSLA32X_Interior.xml‘ file located in the aircraft folder (for example):

D:\MSFS\FlightSimLabs2024\fsl-common\FSLabs\EFB\FileSystem\SimObjects\Airplanes\FSLabs A321-NEO LEAP\Model

Look for a heading like 'VC_GSLD_CP_EFIS_Baro_Knob'...

Thanks for the info', will take a look.

2 hours ago, sloppysmusic said:

I miss mouse macros SOOOOO much. Could setup a whole plane in 10 mins before, now it takes a day if a dev uses unconventional commands, animations and procedure calls. It's 2025 why can't I click a button on screen and the sim assign a hardware button to that hook? 

Open up the sdk already ASOBO. 

Now you're talking my language.  There are SO MANY kinds of events...B, H, K, LVars.  This all needs to be cleaned up.  It's too much and inconsistent.  And devs need to provide mappings.

Back to hangar. 

Yes, it's P3D FSLbus, nothing more, nothing less. Ugly visuals kill all the immersion. Back to FENIX. 

The FSLabs 321, and apparently their new NEO too, has problems with the pitch required on final app... Too high! Lands at an attitude very close to that of tail strike for a 321 😕

Even the default 321 LR by Inibuilds does it way more realistically.

Look at this vid :

https://youtu.be/MGFlf6klqK8?t=531

and compare to this one in the default 321 LR :

https://youtu.be/D8_RfZz2wI8?t=475

 

Edited July 20, 2025Jul 20 by jcomm

On 7/18/2025 at 4:06 PM, carlanthony24 said:

So is FSLabs its not what it once was.

Yeah you are right. its much better than what it was

6 hours ago, G-YMML1 said:

Back to hangar. 

Yes, it's P3D FSLbus, nothing more, nothing less. Ugly visuals kill all the immersion. Back to FENIX. 

I've owned fenix since release. Have hundreds of hours on it. I purchased the FSLabs CEO when released for 2020 and now the Neo. Guess whick airbuses I no longer fly? Yes the Fenix. The FSLABs has a much better simulation and systems. 

Edited July 20, 2025Jul 20 by YukonPete

BUT MUH GRAPHICS!!!

1 hour ago, sultanofswing said:

BUT MUH GRAPHICS!!!

Why are you using MSFS in the first place if graphics do not matter for you? Is this some variation of a P3D vs MSFS discussion from the year 2021? We know how that ended...
Graphics are and always have been (!) a major part of flight simming and most people - even the hardcore simmers - legitimately care about graphics. Fenix can do it, iFly can do it, JustFlight can do it, PMDG can do it, Ini can do it... there's really no excuse for neglecting the visual aspect of a home simulator that people can only see and hear.

13 minutes ago, Fiorentoni said:

Why are you using MSFS in the first place if graphics do not matter for you? Is this some variation of a P3D vs MSFS discussion from the year 2021? We know how that ended...
Graphics are and always have been (!) a major part of flight simming and most people - even the hardcore simmers - legitimately care about graphics. Fenix can do it, iFly can do it, JustFlight can do it, PMDG can do it, Ini can do it... there's really no excuse for neglecting the visual aspect of a home simulator that people can only see and hear.

What makes you assume that I only fly MSFS? 
I also fly XP12 and fly Toliss quite often, i'd love to see your opinion of Toliss Cockpit visuals.