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.

SU9 beta live, release notes

Featured Replies

30 minutes ago, Fiorentoni said:

I'm not talking about having bugs in a beta, I am talking about having absolutely non-related bugs coming out of nowhere. There was no work on ground equipment in this SU, was there?

Actually, you just hit the nail on the head in terms of how things like this can easily and understandably slip through the cracks in the first place. With any application as complex as MSFS (e.g. all modern simulators), there are hundreds of individual systems that all feed off the same environmental variables (temp, air pressure, etc...), and routines that determine how things respond to those variables that are also shared across the application.

A simple change to a variable in one routine can have unintended consequences for unrelated systems because they use the same subroutine. Let say Asobo changes the "coefficient of friction for rubber" to correct an issue with the new CFD model for the c172. That could unknowingly impact and break ground traffic if it uses the same rubber friction model - especially if the dev for ground traffic had some fudging in their model to make traffic behave more realistically. 

Here's where you hit the nail on the head: Asobo is probably also saying "There was no work on ground equipment in this SU, was there?" and therefore not closely testing that system in their internal QA. It's not possible to test every system in an application like this every time you change something. it's also not possible to test every possible combination of add-ons, graphics cards, peripherals, etc... 

And THAT is why public betas like this are so important. You should expect issues - especially early in the release, since the purpose of the program is QA. 

Final comment: the other way to avoid issues like this is to over simplify things, and "fake it" rather than modeling everything based on authentic physics and environmental variables. I'd much rather spend the time to help out with QA than have them revert to dumbing things down.

  • Replies 215
  • Views 33.9k
  • Created
  • Last Reply

Is the CRJ working, it doesn't load in my case? 😕 

AMD Ryzen 7 7800X3D, 64GB DDR5 6000MHZ RAM, RX7900XT, FreeSync 165hz 1440p display 

14 hours ago, rocketlaunch said:

Point 12 

  1. Fixed attenuation distance in cockpit for AI SimObjects using legacy wavedata pipeline

What language is this? 

I believe this is technobabble for "screaming noise in the cockpit caused by AI aircraft in the vicinity".

Flightsim rig:
CPU: AMD 5900x  | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL
Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 
Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking

1 hour ago, omarsmak30 said:

Is the CRJ working, it doesn't load in my case? 😕 

Good point. Will check once landed at ESGG with the FBW exp

EDIT Loads fine here, will not be able though to fly now. family time first

spacer.png

spacer.png

Edited by DAD

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

1 hour ago, omarsmak30 said:

Is the CRJ working, it doesn't load in my case? 😕 

The CRJ will load - but it might take up to 50 minutes the first time you try to load it in SU9. There are several WASM files that have to be compiled into a DLL the very first time you run the CRJ - either after initial installation, or when a new version of the sim executable is released, as is the case with a sim update.

In the past this initial file compilation has taken up to 10 minutes. Now it takes much longer. Other testers on the beta test Discord are seeing the same thing. I’m sure Hans will report this to Asobo, but for the moment if you load the CRJ it would probably be best to walk away for an hour or so until the initial WASM file creation is complete. Once the files are created, the CRJ should load quickly on subsequent runs.

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

5 minutes ago, JRBarrett said:

The CRJ will load - but it might take up to 50 minutes the first time you try to load it in SU9. There are several WASM files that have to be compiled into a DLL the very first time you run the CRJ - either after initial installation, or when a new version of the sim executable is released, as is the case with a sim update.

In the past this initial file compilation has taken up to 10 minutes. Now it takes much longer. Other testers on the beta test Discord are seeing the same thing. I’m sure Hans will report this to Asobo, but for the moment if you load the CRJ it would probably be best to walk away for an hour or so until the initial WASM file creation is complete. Once the files are created, the CRJ should load quickly on subsequent runs.

50min!! No wonder I thought it was just stuck lol. Though FBW loads fast with the WASM compilations, so I wonder if this is an issue from CRJ or MSFS. Thanks for the report! 

AMD Ryzen 7 7800X3D, 64GB DDR5 6000MHZ RAM, RX7900XT, FreeSync 165hz 1440p display 

2 hours ago, abrams_tank said:

Microsoft/Asobo hasn't even started optimizing MSFS for DirectX 12 yet. I don't even recall seeing a single task completed with respect to optimizing for DirectX 12 in the last two Sim Update release notes.  

Just use DirectX 11 for now.  I doubt we will see any optimizations for DirectX 12 until the latter part of this year.

Fair enough, I thought I’d seen something about early DX12 optimisations, I’m back to DX11 now anyway. 

New PC Ryzen 9850X3D - 32gb ddr5 6000Mhz - MSI MAG B850 Tomahawk wifi - Gigabyte wind force gaming OC 5090 - 2TB Sabrent NVMe. Old PC - Ryzen 5900x - 32gb 3600Mhz RAM - Asus Strix X570-F Motherboard - ASUS TUF OC RTX 3090 - 1TB Sabrent NVMe. AOC AGON 32" 144Hz - Honeycomb Yoke - Thrustmaster HOTAS Warthog. T Flight Rudder Pedals - Trackir.

23 minutes ago, omarsmak30 said:

50min!! No wonder I thought it was just stuck lol. Though FBW loads fast with the WASM compilations, so I wonder if this is an issue from CRJ or MSFS. Thanks for the report! 

I haven’t verified the problem myself yet. I just got SU9 beta installed a few minutes ago, but other CRJ testers have mentioned the extremely long load time on first run with SU9.

The FBW uses WASM for some of the more mathematically complex autopilot and FMS functions, but graphics are still done with JavaScript/HTML. The CRJ uses WASM for everything, including graphics. That may be the difference.tt

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

1 minute ago, JRBarrett said:

extremely long load time on first run with SU9

Strange. Did not take the time but it was definitely not longer than 10 mins here on my end

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

4 hours ago, Fiorentoni said:

How do they do this stuff? How do they completely wreck non-related stuff in their updates? It's like they do it on purpose.

This kind of common reaction always bothers me, as it appears to imply that this comes from incompetence. That's absolutely not the case. 

This is actually a very common reality of working with complex software. Systems are interconnected. Ground vehicles interact with ATC, so it's likely that the changes made to ATC caused this. That's why betas are useful.

Edited by Abriael

spacer.png

Editor-in-Chief at SimulationDaily.com

spacer.png

Completed a 3 hour flight with the Kodiak 100. No issues. 

3 minutes ago, Abriael said:

This kind of common reaction always bothers me

It's a reaction born of ignorance and you see it somewhat frequently here from people who are clueless about MS/A's prioritization scheme and the interconnectedness of so many components in this simulation of a ginourmous real world.  Thank you for trying to educate others.

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

24 mins to do the initial load of the CRJ here. PC Specs below (it was about 6 mins prior to SU9)

AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung  NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive

4 hours ago, virtuali said:

Actually, SU9 comes with a catastrophic bug, that affects ALL ground vehicles. Basically, most animations that depends on code and variables are completely broken, this even with default Ground Vehicles and nothing in the Community folder.

Asobo style!

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

Just now, edpatino said:

Asobo style!

It's called "making changes to complex software" style. 

spacer.png

Editor-in-Chief at SimulationDaily.com

spacer.png

Archived

This topic is now archived and is closed to further replies.

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.