My first time with a v24 beta.

EGLL to LFMN in the Fenix A320 latest update, traffic injected by FSLTL. Uneventful, smooth flight. 

I didn’t get the huge performance improvement reported by some. But the framerate seemed to take less of a hit than before when adding FSLTL traffic, which I guess is consistent with there being more “headroom” in the new version: maybe better use of multi-threading?

Just did a test flight in the Fenix. Great flight. Much better performance in VR than with SU3. The 5090 is fully utilized at 100% at a large airport such as EDDF (in VR with a Pimax Crystal Light at full resolution with DLSS Balanced). They definitely have improved the code so that it takes more advantage of the GPU. Great step in the right direction.

Edited September 10, 2025Sep 10 by carlito777

3 hours ago, iborg1979 said:

Trying to load the Turbine Duke in SU4 resulted in a CTD; then in the FSR500 my Octavi IFR1 FMS buttons didn't control the G1000 rotaries anymore (the ones for switching menus).

Only to work again in a subsequent flight, having relaunched MSFS.

I have no problem using the Turbine Duke in SU4. Perhaps something else in your community folder is interfering.

7 hours ago, rick celik said:

I'm getting exteneral lights stuck on in the Fenix, anyone else?

Yep.. Can confirm..  Even when they are retracted.

I dont see any multiplayer aircraft in SU4beta, think I tried all relevant settings, but apparently not so (I have 4000+ experience with the sim). Is it a bug, how do other set this up?

New Beta available now

2.6 GB download for me.

RELEASE NOTES Sim Update 4 Beta - 1.6.5.0

If you are playing on PC, outdated packages in your community folder may have an unexpected impact on the title’s performance and behavior.

If you suffer from stability issues or long loading times, move your community package(s) to another folder before relaunching the title.

Known Issue

• This build contains a known issue that can cause infinite loading times on certain flights. A fix is in development for a future build. Areas that can cause this issue include, but may not be limited to, the following:

  • Cardiff
  • Cliffs of Moher
  • Darwin
  • Dublin
  • Melbourne

Stability & Performance

• Fixed an infinite loading when starting a flight with a scenery from a package, then stopping the flight and disabling the package, and restarting a flight at the same location.

General Bug Fixes

• Fixed an issue where a stutter would appear after a short while in the ATC
• Fixed an issue where the traffic was resetting when opening the weather panel
• Fixed the multi-window delete button in the general advanced options
• Fixed non-Latin characters not being rendered on the company name

Physics

• Fixed OBJ_EA1_SURFACE calculation of airfoil surface normal (Z component)
• Fixed initialization of “modifier_position_scalar” & “modifier_surface_relative_position_scalar” in “[OBJ_EA1_*]” sections of flight_model.cfg when not explicitely specified.

Aircraft Tech

• Added checks for missing interaction file upon loading navigation graphs (this will help aircraft developers detect mistakes that may break these interactions)

Missions

• Fixed cruise back on track in ferry flight, cargo transport, private charter and, commercial flight.

Search & Rescue

• Fixed bush takeoff objective missing “Remove parking brakes” step
• Fixed back on track happening when player is outside the aircraft

DevMode

Project Editor

• Added INPUT_PROFILE content-type to the project editor which can be use as a filter in the Marketplace

SDK

Exporter Blender

• Reworked material emissive scale to improve viewport visualization and make value ranges easier to interpret. See EMISSIVE_PREV.md for details on setting up the viewport for correct preview
• Added automatic ‘make relative’ on save: external files (textures, links, libraries, etc.) are now saved with relative paths instead of absolute ones, preventing missing file issues when sharing .blend files. This behavior can be disabled in the add-onpreferences.

No WASM fix yet.  Pity.  Beta testing can be a slog.

-B

AutoFPS no longer working with tonights new update.  Jetways do not work either when requested through either the Fenix EFB or via GSX.  In GSX I get a Bad Jetway Data message.  Whats the story with jetways as I seen something mentioned a day or so ago somewhere?

3 hours ago, cj-ibbotson said:

AutoFPS no longer working with tonights new update.  Jetways do not work either when requested through either the Fenix EFB or via GSX.  In GSX I get a Bad Jetway Data message.  Whats the story with jetways as I seen something mentioned a day or so ago somewhere?

The jetways were already broken in the initial beta release. Apparently the Fenix "lights always on" issue has been fixed in the latest build.

Edited September 10, 2025Sep 10 by Speedbird 217

3 hours ago, carlito777 said:

Just did a test flight in the Fenix. Great flight. Much better performance in VR than with SU3. The 5090 is fully utilized at 100% at a large airport such as EDDF (in VR with a Pimax Crystal Light at full resolution with DLSS Balanced). They definitely have improved the code so that it takes more advantage of the GPU. Great step in the right direction.

That's probably bad for me as my 4080 is already maxed in SU3 lol.  I get resource messages constantly at payware airports with payware aircraft.  I hope they are also optimizing VRAM usage.

I just realized after going off the runway and into a building that SU4 has completely screwed up the brakes lol.

Honestly, I think it’s safe to say they’re using AI for coding because how on earth do you mess up the brakes? Even the landing lights don’t work on most planes.

1 hour ago, rjack1282 said:

Fixed an issue where the traffic was resetting when opening the weather panel

The very definition of spaghetti code 😆

On 9/9/2025 at 2:25 AM, RTK1972 said:

until you try to land.... Same stutter sh.. as with SU3 for  me. But yes, until landing super smooth

With SU3, the performance and visuals are now quite good and I am assuming SU4 will make further improvements.  However, the one area that continues to be a problem with SU3, and as far as I am concerned a show stopper, is the terrible landing performance during the last approximately 500' AGL until touchdown and the initial rollout.  I spent quite a bit of time on enhancing the performance of MSFS 2024 and it now runs well except in this final segment of the flight.  No performance issues in the same airport when taking off on the same runway from the start of the takeoff roll to about 1000' AGL so I have to believe this landing performance problem is fixable.  This is what keeps sending me back to MSFS 2020 and I am really hoping SU4 either fixes this or some direction is provided how to tune the performance of this segment of the flight. 

1 hour ago, rjack1282 said:

 

• This build contains a known issue that can cause infinite loading times on certain flights. A fix is in development for a future build. Areas that can cause this issue include, but may not be limited to, the following:

  • Cardiff
  • Cliffs of Moher
  • Darwin
  • Dublin
  • Melbourne

 

add newcastle egnt to the list