Route: AROSO3A AROSO Y513 KALIL Y501 RINBA Y503 VPL P628 RK G202 ZB G325 REGET N644 LEMOD A909 NINOP B475 DOLOS B449 MAMED P130 BODKA M747 SULEL N449 INDUR UN161 ERZ UL746 ODERO DCT LUGEB DCT INVED DCT GOTAR DCT AMADI Q113 NAPSA NAPSA1B

WSSS/EDDM

The difference here is like 20fps, that is because i am at a default airport in the middle of the ocean. GCTS
But at any other demanding airport, I get like 35fps (17fps RAW) with crazy stutters.
Third screenshot is at WSSS. Before importing I was doing 90fps.

I have tried reinstalling 4 times, along with clearing WASM plenty of times.

On a related note, the terrain display needs to be optimized as well. The stutters and frame drop from turning it on is insane.

I always had bad performance, it takes usually 4-5 minutes to load the plane once I hit "start flight". I uninstalled it, along with Aerosoft One :(

Route KSFO EPWA
NIITE4 ORRCA Q120 JAJAY DCT SWTHN DCT OSMEE DCT YRL DCT GRAND DCT LAKES/M084F350 DCT TOXIT DCT 60N050W 61N040W 62N030W 62N020W DCT RATSU/N0480F350 DCT BESGA DCT MOCHA DCT RIGVU DCT UNBUD DCT LANTI DCT RASVI DCT GODOG DCT ASVAN DCT MOSIN DCT KOLOB N195 SORIX SORIX6U

The stutters are so bad, its crazy.

BEFORE IMPORTING:

AFTER IMPORTING:


With terrain display:

I have similar problem.

Performance drops when on the ground switching ADIRUS to align mode and then swithing ND to PLAN mode.

Hello,

It seems like there's likely a few different issues going on within this thread, so this reply will primarily be in regard to the initial posting where loading a route will cause the FPS to drops after feedback from the developer.

In general, an FPS decrease is expected after having a flightplan loaded and having the aircraft ready to go, as when the flight plan is loaded it starts all the calculations that the FMGS needs to do. The FPS when in the cold and dark state generally isn't an accurate representation of the FPS once the aircraft is ready to go due to this. Longer flight plans will also have more of an impact.

112 FPS is still much higher than average when fully loaded, but it would be helpful to understand the FPS you get in other aircraft which run entirely in sim when in a ready for takeoff state with flight plans so we can get a better understanding of difference.

I think it's not about FPS but the problem is that at describe situations sim starts to stutter a lot especially when moving cameras. And FPS is just indication that main thread gets overloaded by some heavy processes. So even if there is 112 FPS but it's fluctuating we will see stutters for sure.

I give you another example: I took off from KJFK and everything was smooth till ATC given me instructions change my heading to proceed to some waypoint. When HDG mode was selected simulator immediately became almost unflyable because of stutters. As soon as I switched to managed mode plane was flying perfectly smooth. So I can conclude that something in the plane math makes a very high load on CPU so it causes stuttering. I never had similar issues with another planes. On my system other planes fly smooth as butter.

10 hours ago, Tom said:

Hello,

It seems like there's likely a few different issues going on within this thread, so this reply will primarily be in regard to the initial posting where loading a route will cause the FPS to drops after feedback from the developer.

In general, an FPS decrease is expected after having a flightplan loaded and having the aircraft ready to go, as when the flight plan is loaded it starts all the calculations that the FMGS needs to do. The FPS when in the cold and dark state generally isn't an accurate representation of the FPS once the aircraft is ready to go due to this. Longer flight plans will also have more of an impact.

112 FPS is still much higher than average when fully loaded, but it would be helpful to understand the FPS you get in other aircraft which run entirely in sim when in a ready for takeoff state with flight plans so we can get a better understanding of difference.

I have identified a specific performance bottleneck related to the Navigation Display (ND) rendering logic. The simulator experiences significant stutters and frame time spikes when moving the camera while the ND is active in certain configurations.

Reproduction Steps:

1. Load the A346 at a heavy airport (e.g., KSFO).

2. Create and initialize a long-haul flight plan in the MCDU (e.g., KSFO to VHHH).

3. Set the ND mode to PLAN.

4. Set the ND Range Selector to 10.

5. Move the camera (panning/rotating) inside the cockpit.

Result: Heavy stutters and noticeable FPS drops.

6. Change the ND Range Selector to 40 or higher.

Result: The stutters disappear, and the camera movement becomes smooth again.

7. Turn the ND display OFF (using the brightness/power knob) at any Range setting.

Result: All stutters disappear instantly, confirming the issue is strictly related to display rendering.

Observed Behavior:

The stutters are directly tied to the ND rendering high-density vector data at low range scales (10nm). The performance hit is only present when the ND has to redraw the flight plan path during camera movement. This suggests a MainThread/RdrThread bottleneck in the display's drawing logic rather than a system simulation (FMGC) issue.

Expected Behavior:

ND rendering should be optimized (ideally via GPU acceleration) to prevent blocking the MainThread, regardless of the selected Range or camera movement.

On 4/1/2026 at 9:34 AM, Tom said:

Hello,

It seems like there's likely a few different issues going on within this thread, so this reply will primarily be in regard to the initial posting where loading a route will cause the FPS to drops after feedback from the developer.

In general, an FPS decrease is expected after having a flightplan loaded and having the aircraft ready to go, as when the flight plan is loaded it starts all the calculations that the FMGS needs to do. The FPS when in the cold and dark state generally isn't an accurate representation of the FPS once the aircraft is ready to go due to this. Longer flight plans will also have more of an impact.

112 FPS is still much higher than average when fully loaded, but it would be helpful to understand the FPS you get in other aircraft which run entirely in sim when in a ready for takeoff state with flight plans so we can get a better understanding of difference.

Hello Tom.

Did you have any chance to have a look into the issue? Can you please give us feedback on information I have provided in last post.

On 4/1/2026 at 3:34 AM, Tom said:

Hello,

It seems like there's likely a few different issues going on within this thread, so this reply will primarily be in regard to the initial posting where loading a route will cause the FPS to drops after feedback from the developer.

In general, an FPS decrease is expected after having a flightplan loaded and having the aircraft ready to go, as when the flight plan is loaded it starts all the calculations that the FMGS needs to do. The FPS when in the cold and dark state generally isn't an accurate representation of the FPS once the aircraft is ready to go due to this. Longer flight plans will also have more of an impact.

112 FPS is still much higher than average when fully loaded, but it would be helpful to understand the FPS you get in other aircraft which run entirely in sim when in a ready for takeoff state with flight plans so we can get a better understanding of difference.

@Tom
No, it is NOT expected to have a decrease in FPS after importing a flightplan. The A340 is the first plane I have seen doing this. So it does not justify losing half my FPS over it.

And in my case, if i turn off frame gen, I go from 45fps to 20fps. And don't tell me 20fps is playable.
So clearly, the FMFG computation algorithms are horribly optimized, because this is the first aircraft I have seen doing this.

PMDG 777 before importing flight plan:


After:


NO DIFFERENCE

Fenix before importing:


After:


Also losing 10-15fps cuz i turned the terrain display on is also not expected.

I hope you get my point,
Thank you.

I just have got WASM crash after a few hours of flight and it's getting so much frustrated because I love all Toliss products since XP11 (12) and it always been amazing regarding systems and stability. But now I can't fully enjoy this product because of performance and stability issues. And the more frustrating thing that Aerosoft ignores all tickets I created and not willing to respond on forum as well, I already escaleted this problem directly to Toliss via their ticketting system and hopefully it will help to reach out so silent Aerosoft!

16 minutes ago, banji said:

@Tom
No, it is NOT expected to have a decrease in FPS after importing a flightplan. The A340 is the first plane I have seen doing this. So it does not justify losing half my FPS over it.

And in my case, if i turn off frame gen, I go from 45fps to 20fps. And don't tell me 20fps is playable.
So clearly, the FMFG computation algorithms are horribly optimized, because this is the first aircraft I have seen doing this.

PMDG 777 before importing flight plan:


After:


NO DIFFERENCE

Fenix before importing:


After:


Also losing 10-15fps cuz i turned the terrain display on is also not expected.

I hope you get my point,
Thank you.

Tom just prefers to ignore our messages because he thinks it's just our problem but not Aerosoft. And I will not be silent and I do my best to esalate this ISSUE as much as I can to make it finally accepted as a bug to be FIXED.

I have recorded video which clearly demonstrates the issue with displays rendering and performance drops.

https://discord.com/channels/1024582293563641916/1151809525914009621/1490017565236269159

^Aerosoft Discord

See my newest evidence.

6 hours ago, banji said:

https://discord.com/channels/1024582293563641916/1151809525914009621/1490017565236269159

^Aerosoft Discord

See my newest evidence.

I think this issue should be definitely reported to the devs and considered as a bug.

Hello,

There is quite a bit to go over here, so I'll do my best to cover everything:

On 4/3/2026 at 4:19 PM, Anatoliy said:

Tom just prefers to ignore our messages because he thinks it's just our problem but not Aerosoft. And I will not be silent and I do my best to esalate this ISSUE as much as I can to make it finally accepted as a bug to be FIXED.

I'm not entirely sure if it's fair to say I'm ignoring your messages - There were two work days between my reply and further replies - Friday and Monday (Today) are days we're closed due to the Easter holiday, and we're dealing with lots of customers at once, so we reply where we can on a last staff reply basis. Thanks for your patience.

On 4/3/2026 at 4:00 PM, banji said:

No, it is NOT expected to have a decrease in FPS after importing a flightplan. The A340 is the first plane I have seen doing this. So it does not justify losing half my FPS over it.

I was referring to strictly the A340 in my prior message - Where, per Toliss, an FPS drop is expected. The reason this specifically happens in the A340 is that many of the aircraft calculations do not start when loading in the aircraft, but instead after the flight plan has been imported. The underlying code in every aircraft in the sim handles things in a slightly different way, and this is how it's implemented on the A340.

The A340 is, in general, more performance heavy than the 777, and settings may need to be turned down. It's for this reason we recommend/have in the requirements a minimum or better GPU when compared to the performance of an RTX 2080 or Radeon RX 5700. The GPU you're using appears to be a 4060 (Laptop edition), which is a little below these minimum requirements. We also have requirements for an Intel i7-10700K / Ryzen 7 5700 or better. If you run below these specs, we can't guarantee things are going to run smoothly, especially when it comes to stutters and FPS. It's also worth mentioning that if you're running ATC traffic programs or FFB hardware, this can also drive up the requirements.

On 4/1/2026 at 8:10 AM, Anatoliy said:

I have identified a specific performance bottleneck related to the Navigation Display (ND) rendering logic. The simulator experiences significant stutters and frame time spikes when moving the camera while the ND is active in certain configurations.

The ND is indeed quite performance intensive, and the further you zoom out the more tiles are loaded which will affect performance more. I have been informed this is currently optimized to maximum possible with the current MSFS display drawing capabilities. For this reason, it's not something that is currently considered to be a bug, but optimization is something that is constantly being worked on, and it's something that we'll of course be trying to improve everywhere we can as updates go on. This goes not only for the ND performance, but the entire aircraft.

In terms of your WASM crash(es) (@Anatoliy), I think it may be better suited in a different thread with the relevant details, such as what you were doing at the time, as WASM crashes can be caused by a wide range of things and likely isn't strictly related to what's being discussed in this thread.

13 hours ago, Tom said:

Hello,

There is quite a bit to go over here, so I'll do my best to cover everything:

I'm not entirely sure if it's fair to say I'm ignoring your messages - There were two work days between my reply and further replies - Friday and Monday (Today) are days we're closed due to the Easter holiday, and we're dealing with lots of customers at once, so we reply where we can on a last staff reply basis. Thanks for your patience.

I was referring to strictly the A340 in my prior message - Where, per Toliss, an FPS drop is expected. The reason this specifically happens in the A340 is that many of the aircraft calculations do not start when loading in the aircraft, but instead after the flight plan has been imported. The underlying code in every aircraft in the sim handles things in a slightly different way, and this is how it's implemented on the A340.

The A340 is, in general, more performance heavy than the 777, and settings may need to be turned down. It's for this reason we recommend/have in the requirements a minimum or better GPU when compared to the performance of an RTX 2080 or Radeon RX 5700. The GPU you're using appears to be a 4060 (Laptop edition), which is a little below these minimum requirements. We also have requirements for an Intel i7-10700K / Ryzen 7 5700 or better. If you run below these specs, we can't guarantee things are going to run smoothly, especially when it comes to stutters and FPS. It's also worth mentioning that if you're running ATC traffic programs or FFB hardware, this can also drive up the requirements.

The ND is indeed quite performance intensive, and the further you zoom out the more tiles are loaded which will affect performance more. I have been informed this is currently optimized to maximum possible with the current MSFS display drawing capabilities. For this reason, it's not something that is currently considered to be a bug, but optimization is something that is constantly being worked on, and it's something that we'll of course be trying to improve everywhere we can as updates go on. This goes not only for the ND performance, but the entire aircraft.

In terms of your WASM crash(es) (@Anatoliy), I think it may be better suited in a different thread with the relevant details, such as what you were doing at the time, as WASM crashes can be caused by a wide range of things and likely isn't strictly related to what's being discussed in this thread.

Hello, Tom.

First of all I would like to apologize for being emotional in my previous message.

As for performance issue I would agree with you that is not really bug in terms of code error but it definetelly needs some more optimization. You mentioned in your answer that A346 is quite demanding to the system specs and I agree that due to level of details and math calculations this addon might be heavy but as you could see on my video attached even my quite strong rig (9800 x3D CPU, 4090 GPU and 64 GB of RAM) can't handle well ND rendering during and after FPL loading. And there are a few areas where I saw significant performance drops. 1. On the ground after loading FPL I see ND relared stutters. 2. In the skies I could see a lot of stutters if HDG mode selected during departure.

So it would be nice if the team could optimize screens drawing issues to give us more fluide experience while flying this indeed wonderfull bird.

On 4/7/2026 at 3:28 AM, Anatoliy said:

Hello, Tom.

First of all I would like to apologize for being emotional in my previous message.

As for performance issue I would agree with you that is not really bug in terms of code error but it definetelly needs some more optimization. You mentioned in your answer that A346 is quite demanding to the system specs and I agree that due to level of details and math calculations this addon might be heavy but as you could see on my video attached even my quite strong rig (9800 x3D CPU, 4090 GPU and 64 GB of RAM) can't handle well ND rendering during and after FPL loading. And there are a few areas where I saw significant performance drops. 1. On the ground after loading FPL I see ND relared stutters. 2. In the skies I could see a lot of stutters if HDG mode selected during departure.

So it would be nice if the team could optimize screens drawing issues to give us more fluide experience while flying this indeed wonderfull bird.

No worries - As with most projects, there will be constant ways to optimize it, and I'm sure this is an area Toliss will be working on where they can each update, so I would consider optimization to be a constant work in progress. This is likely something we will be able to comment on more in the future, once the initial bug reports/fixes have been resolved.