Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FSLabs A321Neo not good in 2024

Featured Replies

I'm a big Fenix user and just took the FSL A321Neo for my first European round trip. It's really not great and I wish I'd just used the Fenix. Some issues I found:

- FO side PFD and ND froze just before arrival. I ended up getting loads of discrepancy warning messages. Even changing the brightness didn't do anything (it was completely frozen).
- Pressing the 'PEDAL DISC' to allow pedals to steer is just clumsy. It seems to give me all sorts of problems keeping the aircraft straight on the runway during take off. Should I have disconnected it before starting the TO roll? Fenix and PMDG combine rudder and NWS flawlessly...why does this have to be so different? Also, on landing, it appears the button resets itself (even if it's set to sticky in options).
- Thrust lever detent setup is a real pain (nowhere near as easy as in the Fenix). I'm using the Thrustmaster Airbus quadrant. I've followed the tutorial and tried to set it up a number of times but it's still not right. I get warning messages during engine start that the levers are not at all (when they are).
- Another thrust lever issue - whenever I close lever 2 to idle, it keeps engaging reverse, even though reverse is set a lot lower in the detent settings.
- The cabin is really poorly modelled with very low quality textures. I know a lot of people don't care about cabin views, but some do. At least give the option and have more decent cabin interiors if people want it.

I think this is going back into the hangar until FSL sort it out. Back to the Fenix for now.

AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo
64GB (2x32GB) DDR5 6000MHz Corsair Vengeance
32GB GeForce® RTX 5090 Graphics Card

I think you should append "For me" to your topic title.

Many people don't have these problems. I suggest your refer to the FSLabs forums or submit a ticket.

David Porrett

I don't own the NEO, only the 321, but as I arrive home I'll try to leave here soon hints.

I believe some of the quirks you describe aren't actual problems.

Also wonder if you've properly setup the aircraft options, namely the fact that there's an option to disable the FO displays to save processor, or maybe having the malfunctions active?

The throttle setup can be tricky but I have a few numbers I use since FSX and P3D times that might help!

My only problem with the 321 is that it has a too high pitch on final, getting too close to tail strike protection limits... They will surely fix it in a later patch.

Also love the Fenix, the inibuilds default buses, and pretty much everything FS2024... 

Edited by jcomm

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

  • Author

I didn't have any failures set or active...the FO's screens just froze. It wasn't an A321 failure issue...it was an FsLabs issue.

To top it all off as I arrived at the gate and turn off the IRS switches, I got a CTD.

All in all, very unhappy with this aircraft. Back to Fenix and PMDG where I have no problems.

AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo
64GB (2x32GB) DDR5 6000MHz Corsair Vengeance
32GB GeForce® RTX 5090 Graphics Card

Well,

In my case I am using an old x52 Pro HOTAS unit for throttle, so I set it with no reverse on axis, and use a button to toggle reverse.

In the throttle detent custom settings I have always used these since FSX / P3D:

Fwd Idle: -1.00/-0.97 
CL:  .02/.34 
FLX MCT: .55/.81 
TOGA:  .97/1 

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

3 hours ago, BWBriscoe said:

I'm a big Fenix user and just took the FSL A321Neo for my first European round trip. It's really not great and I wish I'd just used the Fenix. Some issues I found:

- Pressing the 'PEDAL DISC' to allow pedals to steer is just clumsy. It seems to give me all sorts of problems keeping the aircraft straight on the runway during take off. Should I have disconnected it before starting the TO roll? Fenix and PMDG combine rudder and NWS flawlessly...why does this have to be so different? Also, on landing, it appears the button resets itself (even if it's set to sticky in options).
- The cabin is really poorly modelled with very low quality textures. I know a lot of people don't care about cabin views, but some do. At least give the option and have more decent cabin interiors if people want it.

I think this is going back into the hangar until FSL sort it out. Back to the Fenix for now.

Pedal Disc is doing the job correctly it disconnects around the 60 knot mark I think if left on. Best option like you said is to disconnect it yourself. Cabin is going to be worked on along with MEL's to go with it. Not experienced any these issues or others you have mentioned. Hoping the panel state function gets fixed autopilot doesn't work unless you do a quick align of the IRS

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.