Well, purchased it and here's my thoughts. On MS2020, performance is worse than Fenix. I would say on par with ini A350. I have a 4090 and 7800x3d with 64gb ram for reference. Definitely a different flow to doing things than what I am used to with Fenix but it's nice to change things up to prevent boredom so no issues. Sounds are good but the winner IMO is Fenix in that regard, same with textures. System-wise, very, very, in-depth, no complaints there. Two things I would change, option to have GSX outside the EFB and would encourage them to look at VRAM consumption and get better performance out of it.  

Is the FSLabs A321NEO supported by the Winwing Hardware EFIS_L- FCU and the MCDU ( SimAppPro software only please )?

Not this: 1.FCU+EFIS+MCDU supports MSFS's FlightSimLabs A321 IAE/CFM, FlightSimLabs A321-SL IAE/CFM  - this is supported since SimAppPro 1.16.34

Thanks..

cheers 😉

13 minutes ago, pmplayer said:

Is the FSLabs A321NEO supported by the Winwing Hardware EFIS_L- FCU and the MCDU ( SimAppPro software only please )?

Not this: 1.FCU+EFIS+MCDU supports MSFS's FlightSimLabs A321 IAE/CFM, FlightSimLabs A321-SL IAE/CFM  - this is supported since SimAppPro 1.16.34

Thanks..

cheers 😉

Yes, used it last night with the NEO and no issues. Only thing I don’t like is there is no Streamdeck profile for the FSL stuff. Nobody seems interested in making one.

Edited June 21, 2025Jun 21 by B777ER

I just bought it and this is my first ever FSLabs product.  I always found their prices to be over the top compared to the competition so I was pleasntly surprised to see a $70 dollar price tag.

I have to say for now I'm disappointed. Here are my reasons.  MSFS2020, i7 13000k, 4800 Super, 64GB Ram.

1. The cockpit looks good but there are a few areas where the textures are downright FS9 quality.  Right in front of the throttle, they just made a low res flat panel with pictures of screw heads.  What's wierd is they did it right on the window and put the screwhead models and gave them depth, Just an attention to detail thing.

2. It feels more like PMDG that Fenix.  The EFB is kind of an afterthought .  Like PMDG Doors, Maint, W&B, is all controlled through the FMC/MCDU. I prefer the Fenix/FBW method of loading it in the EFB.  The onscreen keyboard is idiotic.  The fact you can't just type, is a big face palm to me. I got used to it, but I still don't like it.

3. Frame rate is worse than Fenix for me, In the cockpit it's not so bad until you load in BeyondATC traffic and go to a complex airport. I tried iniBuilds LAX and it was pretty bad, i'd get a microstutter every 5 seconds.  Asobo DFW was not as bad even with traffic.  But the worst part is the cabin and exterior views.  I set cabin views and the stuttering was horrendous, every time it rotated into a new view it would pause for a second before finally panning  in a stuttering mess. Same with the outside view.  However, I will say, you have to give it time.  I recommend that you don't play right after installing it.  Load it, look all around it, set your views and preferences and what have you. Leave the game and restart the computer launch it again and it will be way smoother. After I did that there is a slight lag, but now I can cycle through all the views quickly and pan in the cockpit without any big stutters.  I assume this is because the textures are now loaded to cache. 

Even still the frame rates for me are not as good as Fenix, but I also believe like Fenix when it was new, the frame rates will be improved. 

4. Some of the textures on the Exterior are not good looking, especially the vents on the bottom of the engine. The bottom of the plane is just lacking.  There is a wierd double texturing.  The American Repaint is the worst.  So maybe the fault of the livery painter?  The American repaint also has odd striations of random color like when a low res image is used.  It looks ugly. 

5. Flight dynamics, the jury is still out for me. Seems to be twitching too much on final approach with the AP/AT on. Also, seems to climb too fast. Even at 176k lbs. I was climbing 4-5k FPM up to 10,000 feet.  It shallowed out the climb when it nosed down to keep 290kts, and stayed at an 1,100 to 2200 FPM climb up to 28000 then about 1,100 FPM above 30k feet.       I know 2,700-3,000 FPM is reasonable but 4-5k FPM seems a bit over powered for being so heavy. In my opinion. This is an MSFS problem though, all planes climb at too high of rate to 10k feet.

Other than that system depth are fantastic,  GSX integrations is very good, hand flies pretty good, lands pretty easy, MCDU depth is crazy, and it works perfectly, I couldn't make it mess up.  It's fully worth $70 considering how deep the systems are. I was finding stuff I didn't even know existed because Fenix doesn't model it.  IF they can fix the texturing and performance and add wing flex, it would be a perfect airplane. I think they will.  And we will get the additional variants for free not a crazy upcharge, which is something FSL was notorious for on P3D and why I never bought their products.  I was Impressed with iFly so I decided to throw this developer a bone. 

Cockpit isn't as nice as Fenix.

Wierd striations on the American repaint

Strange ghosted textures, looks like bleed over from a different texture file or something.

These vents and the way the textures don't line up are awful and need to be fixed.  Ithought maybe it just this reapaint...nope it's a bunch of them.

1 hour ago, BrammyH said:

Has anyone who had performance issues in the Fenix in 2024 tried the FSL in 24? Curious if it is easier on the frames for those of use with low VRAM.

It’s not quite what you asked, but I have no performance issues with the Fenix and significant issues with VRAM saturation with the FSLabs. Have done four flights so far, and three landings were a stutter-fest. Un-flyable. 
 

Based on this, I’d suggest to stay away if the Fenix is giving you trouble. 
 

There is a thread on this in the FSLabs forum, and I’m certainly not alone. 

1 hour ago, BrammyH said:

Has anyone who had performance issues in the Fenix in 2024 tried the FSL in 24? Curious if it is easier on the frames for those of use with low VRAM.

It's worse. Much worse. I have the Fenix and it screams in FS 24. The FSL (both CEO and NEO) struggles greatly with VRAM consumption, stuttering, low frames in 24. So if you are struggling already with the Fenix in 24, you'll most likely do worse. YMMV of course.

Great to have a complex payware 321 Neo. But much prefer GSX control outside the FMS. Also would agree with the observations that fps not good. Last landing was a stutter fest.

But overall, sounds are great including in cabin music.

On 6/19/2025 at 9:32 AM, virtuali said:

Some little known facts about this new release from FsLabs, which has always been noted for their deep integration with GSX, which now goes ever further:

- When you install a new Livery from the FsLabs CC, it will automatically resync all Seated Passengers, so you won't have to remember to go back in the FSDT Installer, open the GSX Config page, confirm passengers are enabled, and exit. Easy to forget, so you start your flight, and the new livery has either missing passengers or pink textures. Not happening anymore, now it's all automated.

- Normally, Seated Passengers are only visible in VC if you open the cockpit door (they are always visible in external views). But what if you want to *remain* in VC mode, maybe because you want to just pan around the view (or use a 3rd party camera) and you still want to see passengers without going in external view ? Now you can: the FsLabs has now an option in the MCDU, where you can set a preference if you want to see GSX Passegners only with the cockpit door (default method), or always.

These are just minor things, but very welcome QOL improvements to make the whole experience as seamless as possible. This is what happens when two developers TALK with each other...

I have never bought GSX and honestly never researched it in any depth. That said now that I have both the CEO and NEO I am going to have a closer look at just what it is and how it works.....hopefully simple to work, lol.

I have also purchased their NEO as my first FSLabs product and I am using it with 2020.

It is a very complex aircraft but my main issues thus far is that it has the worst performance of any aircraft that I own, between Fenix, all PMDG and iniBuilds aircrafts. On the ground while engines are turned off, it has fairly good performance, but once engines are turned on it loses to any of other products that I own. Another issue that I have is that the EFB has very laggy animations and the integration with GSX is not that great, specially for refuelling, boarding and deboarding. 

14 minutes ago, AndreMP said:

I have also purchased their NEO as my first FSLabs product and I am using it with 2020.

It is a very complex aircraft but my main issues thus far is that it has the worst performance of any aircraft that I own, between Fenix, all PMDG and iniBuilds aircrafts. On the ground while engines are turned off, it has fairly good performance, but once engines are turned on it loses to any of other products that I own. Another issue that I have is that the EFB has very laggy animations and the integration with GSX is not that great, specially for refuelling, boarding and deboarding. 

In P3D ,GSX and the ATSU in the MCDU worked really well with automation as i recall it. This has now moved to EFB only?

Michael Moe 

Edited June 21, 2025Jun 21 by Michael Moe

13 minutes ago, AndreMP said:

I have also purchased their NEO as my first FSLabs product and I am using it with 2020.

It is a very complex aircraft but my main issues thus far is that it has the worst performance of any aircraft that I own, between Fenix, all PMDG and iniBuilds aircrafts. On the ground while engines are turned off, it has fairly good performance, but once engines are turned on it loses to any of other products that I own. Another issue that I have is that the EFB has very laggy animations and the integration with GSX is not that great, specially for refuelling, boarding and deboarding. 

My system is a 7800x3d, 5070ti, 64 gigs ram, m.2 drives and a 49" msi monitor.

Settings are cranked right up. In 2020 it is taking just about all my video card can do but FPS is high and smooth. 

In 2024  more FPS with the GPU not working as hard.

I'm curious if with GSX my system in 2020 can keep the same high settings I am using now. With 2024 it does not look like it will be a factor - famous last words.

11 minutes ago, Michael Moe said:

In P3D ,GSX and the ATSU in the MCDU worked really well with automation as i recall it. This has now moved to EFB only?

Michael Moe 

No, you can still do through ATSU in the MCDU, which is the way that I do.

7 minutes ago, dbw1 said:

My system is a 7800x3d, 5070ti, 64 gigs ram, m.2 drives and a 49" msi monitor.

Settings are cranked right up. In 2020 it is taking just about all my video card can do but FPS is high and smooth. 

In 2024  more FPS with the GPU not working as hard.

I'm curious if with GSX my system in 2020 can keep the same high settings I am using now. With 2024 it does not look like it will be a factor - famous last words.

I have a 5800X3D paired with a 4070Ti and 32GB RAM with a M.2 SSD. To have a clear comparison, during cruise without FG the FSLabs A321neo has between 25-30fps for me while the Fenix is around 35-40fps.

9 hours ago, aniiran said:

. Flight dynamics, the jury is still out for me. Seems to be twitching too much on final approach with the AP/AT on. Also, seems to climb too fast. Even at 176k lbs. I was climbing 4-5k FPM up to 10,000 feet.  It shallowed out the climb when it nosed down to keep 290kts, and stayed at an 1,100 to 2200 FPM climb up to 28000 then about 1,100 FPM above 30k feet.       I know 2,700-3,000 FPM is reasonable but 4-5k FPM seems a bit over powered for being so heavy. In my opinion. This is an MSFS problem though, all planes climb at too high of rate to 10k feet.

The NEO is overpowered IRL. Even at MTOW you get about 3000fpm to 10K at 250kts. At 80000kgs 4-5K is definitely possible

1 hour ago, suncoastflyer said:

The NEO is overpowered IRL. Even at MTOW you get about 3000fpm to 10K at 250kts. At 80000kgs 4-5K is definitely possible

Maybe you have some sort of authority on the Airbus as a captain or something but I can't find any A21N in real life achieving 4-5k FPM climb rate.  3k I can certianly see, but not 4-5k.  I looked at over 30 flights in the A21N with American that would have put the weight around 180,000 lbs and none of them were achieving greater than 3,000 FPM. 

https://www.flightaware.com/live/flight/AAL1703/history/20250621/2157Z/KDFW/KCLT/tracklog

https://www.flightaware.com/live/flight/AAL442/history/20250621/1645Z/KDFW/KLAX/tracklog

https://www.flightaware.com/live/flight/AAL2090/history/20250621/0156Z/KDFW/KMIA/tracklog

 

https://www.flightaware.com/live/flight/AAL1052/history/20250621/1711Z/KCLT/KORD/tracklog

This short CLT ORD flight levels off at under 8,000ft for the JOJJO5 SID, but has no restriction below 8000 feet. but despite being much below MTOW they don't climb at 5k FPM. 

Sure maybe at 80T and TOGA power 5k is achievable.  My point is that in the SIM, even tough the airplane is not at TOGA power, it's in CLB for 240kts and at 88-92% N1 it's managing 5k FPM. That does not seem realistic. 

 

Edited June 22, 2025Jun 22 by aniiran

a good example of the level of detail of FSL.

Currently sittng on stand 101 at EGKK next to the bridge,  as in the real world the ecam is pinging me a ADS-B RPTG 2 fault,  which you get at EGKK when taxiing under the bridge.

just brillant 

 

Edited June 22, 2025Jun 22 by fluffyflops