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.

SU 3 Beta 1.5.10.0 Released June 2025

Featured Replies

5 minutes ago, Piotr007 said:

same performance drawbacks without opportunity to revert. 

I was getting better performance than SU2

Edited by Tuskin38

  • Replies 194
  • Views 23.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • On Avsim the world is upside down: You enjoy the sim, you get called all sorts of names.  You wallow in misery, you're a hero. 😄

  • You are being overdramatic for a beta test Stuff like this is expected, that's why they do these tests. Had this gone live to everyone I'd understand, but this is an optional beta. It's

  • Seems like anytime anything connects via Simconnect, the simulator crashes. Love your work, Asobo!

42 minutes ago, Piotr007 said:

Asobo should know people still play with addons, their back to the cavemen attitude with beta updates is ridiculous.

Nevermind testing items in their own marketplace, it's the untested base game that's the main issue. There is zero regression testing in house, this has been proven time & time again over the past four years of betas. It's so blatantly obvious that everything needs an overhaul, yet Asobo/MS/Jorg/whoever seem completely oblivious as to how a beta stage should be run. Ultimately it smacks of complete incompetence with next to no desire to improve procedures, but hey at least they have the public to do their dog work for them.....that's when the beta isn't a complete mess as has been evidenced during this SU3 cycle.

Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1

Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)

Have they fixed it yet? I dare not fire up the sim until they do. There seems to be a certain tiredness and staleness at Asobo these days. Hope they don't implode. It may be time for fresh new blood and new faces methinks?

Edited by jarmstro

17 minutes ago, jarmstro said:

Have they fixed it yet? I dare not fire up the sim until they do. There seems to be a certain tiredness and staleness at Asobo these days. Hope they don't implode. It may be time for fresh new blood and new faces methinks?

You are being overdramatic for a beta test

Stuff like this is expected, that's why they do these tests.

Had this gone live to everyone I'd understand, but this is an optional beta.

It's possible they just haven't narrowed down the cause yet. Once they fix it, then that build has to go through certification before it can be sent out to the testers.

Edited by Tuskin38

13 minutes ago, Tuskin38 said:

You are being overdramatic for a beta test

Stuff like this is expected, that's why they do these tests.

Had this gone live to everyone I'd understand, but this is an optional beta.

It's possible they just haven't narrowed down the cause yet. Once they fix it, then that build has to go through certification before it can be sent out to the testers.

Well you are right of course. But I'm just not getting the same buzz with 2024 as I did with 2020 as it evolved. 2024 is a bore.

Edited by jarmstro

I suspect MS wishes they had not made declarations about the majority of 2020 add-ons working in 2024. It has proven to be much more difficult than they anticipated to get them working similarly to how they performed in 2020. Whenever I run into issues, whether they be performance, CTD’s or otherwise, it’s almost always with an add-on that was not built natively for 2024. Yes, many products are listed as 2024 compatible and will work, but not as well as if built natively.

I don’t believe Asobo understood just how creative third party devs were in creating products for 2020, nor the complexity of the interdependencies between the add-ons and the sim. Thus, when they make changes to 2024, they don’t know how it might impact all of the 2020 products. I mean I had a single livery and a single airport blocking me from loading into the sim. You just wouldn’t expect those to give you CTD’s, but they did.

So in hindsight, MS/Asobo now know their assumptions were wrong, should have tested for a year, and should have engaged outside developers during the development process to both inform but to also give them time to work on their products compatibility. I would argue they should have known these things in advance, and it really does shock as to their naivety about the complexity of the extended ecosystem, without which MSFS would not be taken as a serious sim.

Edited by Gulf76

1 hour ago, Gulf76 said:

I have the exact same hardware and do not typically experience stuttering when looking around in VR with a Pimax Crystal. 

Don't know, it's annoying.
The more complex the plane add-on the worse the stutters are, Ini A350 is really bad but I do not have those issues in 2020.

--Sean Hart

7 hours ago, Matchstick said:

If you sell products on your OWN STORE, then you should be ensuring those don't break your base sim at the very least.

Marketplace products aren't allowed to call external programs via Simconnect, so they would not be affected.

2 hours ago, Tuskin38 said:

That’s not their job to test. Thats why they have betas.

 

It is absolutely their job to test. And they are terrible at it. That's why the unpaid testing team (us) do it. 

7950X3D | RTX 4090 | 96GB DDR5 | 4K G-Sync | Win11 Pro

I just did a short flight in the default Cirrus Vision Jet, from EDDB to EDAH - I use payware for both airports. 

Sim loaded fast, loading into the flight took less than 30 seconds. Performance was great.  No CTDs,

The only issue was that I had to disable the in-game toolbar mod. 

I'm very satisfied with this beta release. 

32 minutes ago, sultanofswing said:

The more complex the plane add-on the worse the stutters are

This assertion may be overly broad. I have been flying the PMDG B77W in 2024 for the last week or so in FS2024 and have observed very few stutters of any sort. That's not to say that there might not be problems in the beta, but debugging the cause of such stutters would probably be beyond the limited view any of us have into the internals of MSFS in general.

In any case, many thanks to those of you brave pioneers who are participating in the beta of SU3. This looks like a real chore.

John Wiesenfeld KPBI | FAA PPL/SEL/IFR in a galaxy long ago and far away | VATSIM PILOT P2

i7-11700K, 32 GB DDR4 3.6 GHz, MSI RTX 3070ti, Dell 4K monitor

 

32 minutes ago, Funky D said:

Marketplace products aren't allowed to call external programs via Simconnect, so they would not be affected.

That's another reason I only buy from the MP.

GREAT POST BTW!

dd

13 minutes ago, Sky_Pilot071 said:

That's another reason I only buy from the MP.

GREAT POST BTW!

dd

What’s great about it? Without sim connect the sim would be half the sim it is!  You’d be eradicating things like sim haptic addons, force feedback hardware etc… 

Many add-ons, including those for aircraft, scenery, and utilities, utilise SimConnect to communicate with the simulator and enhance the overall experience. 

 

Edited by Ianrivaldosmith

Am I missing something here? Don't PMDG planes use SimConnect? They are sold on the MS Marketplace.

Christopher Low

AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme

UK2000 Beta Tester

  • Commercial Member

I cannot confirm issues with SimConnect on my end (MSFS 2024, 1.5.10.0, latest SimConnect libraries that were released before the SU3 beta began). I have been working on a camera extension all day with zero problems (using a SimConnect client as framework). I haven't been flying though, plane was just sitting on the runway for about 3 hours.

Be mindful that there are several aspects to SimConnect:
- First, there is the "server" part, the API that is an integral part of the simulator. 
- The other is the SimConnect client = the external or internal program accessing the API. 

1. SimConnect is only in play with programmatic assets, so WASM, internal DLL or external EXE. 
2. All of these clients have been compiled with a certain version of the SimConnect libraries. Generally speaking, all clients should be updated using the latest libraries every time the sim itself changes. Not doing that can result in issues - but only the addon developer can actually remedy this (=recompile with the latest libraries)
3. Where WASMs are concerned, there can be trouble with the precompiled packages when the simulator version changes. Make sure to delete those and force a recompile (<sim folder>\LocalState\packages)
4. Personally, I am not a fan of installing the old seperate legacy SimConnect clients from the FSX days. Properly compiled SimConnect addons don't need anything extra to be installed.

(for the record, my Saitek panels are working fine as well. I'm obviously not using SPAD though)

All that being said, the simulator is quite complex, with its own WASM compiler, SimConnect API and whatnot. Participating in a Beta with no option to update (especially legacy) addons means asking for trouble. IMHO.

As far as the promise of backwards compatibility goes - even if all programmatic addons stop working with a sim update, what's left is still "most addons"...

Edited by Lorby_SI

LORBY-SI

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.