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.

Can't end a single flight with this Beta :-(

Featured Replies

A couple days ago I wanted to test the new ground physics variables introduced with this latest beta which were activated in the default C172, so I pushed it, but ever since, whenever I try to fly from a nearby aerodrome into Lisbon, in the default C172 (classic instruments) or the PMDG 737 in a flight from Porto (LPPR) to Lisbon (LPPT), when I get near an area not far from the final approach segment into rw02 the program freezes 😕

I can still access the menu bar, I can't change views, I can't quit MSFS, and only going to task manager and killing the process puts an end to the experience ...

I believe I read somewhere a few days ago that even ASOBO had identified a few problems with this beta, but I am not sure if what I've been experiencing can be related to those ?

I'm on the latest Nvidia drivers, using DLSS-FS3, and previously all was perfectly fine.

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)

Have you posted this on the official forums beta section? If not do so, with a much detail as possible, I highly doubt they read these forums for beta bug reports so as much exposure over there is best.

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)

  • Author

I gave up posting there...

All bugs and reports of other aspects of the game I posted there were treated into closed threads or never got a valuable answer...

I assume they're getting feedback from users running Beta, through the application itself, like Laminar get's from users running XP?

Well, it's a Beta, but it's the first to bring me such an unplayable state of affairs... 

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)

21 minutes ago, jcomm said:

Well, it's a Beta, but it's the first to bring me such an unplayable state of affairs... 

I have no issues with this beta, but a few betas before this one some major issues like MSFS not starting at all. In that case the issue was caused by some aircraft from the marketplace as well as some in the community folder.

To troubleshoot you will have to start somewhere so the most logical thing is to rename the Community folder and run the sim without simconnect addons running. If that doesn't work you could try and move some addons from official folder.

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

  • Author

Marketplace aircraft in my install are only the ATR-72 ..

WU is only the Iberian Peninsula...

Happened while running MSFS standalone or with FSHUD...

I'm on DX12 with DLSS-FSR3 trick... I'll revert to DX11 and see how it goes...

Will also consider a Nvidia driver reinstall.

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)

Is the sim only crashing near Lisbon?
I had a string of CTD's on a specific route which were most likely caused by a third party airport addon (Bremen). I discovered that if I changed the flightplan (different SID) the crash did not occur. The issue did not happen when using the default airport so possibly the addon introduced bad navdata which caused MSFS to crash.

It illustrates that a relatively simple issue can cause MSFS to CTD, even if it is quite stable and troubleshooting these can sometimes be very timeconsuming, not to mention frutstrating.

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

  • Author
37 minutes ago, orchestra_nl said:

Is the sim only crashing near Lisbon?
I had a string of CTD's on a specific route which were most likely caused by a third party airport addon (Bremen). I discovered that if I changed the flightplan (different SID) the crash did not occur. The issue did not happen when using the default airport so possibly the addon introduced bad navdata which caused MSFS to crash.

It illustrates that a relatively simple issue can cause MSFS to CTD, even if it is quite stable and troubleshooting these can sometimes be very timeconsuming, not to mention frutstrating.

Thank you for the follow up @orchestra_nl,

I don't believe it is directly related to LPPT, because I have been using this since the Iberian Peninsula WU was released long ago... 

I enabled DX12, just as before SU15 Beta, with DLSS FSR3 (my card is a 360 Ti).

There are no stutters, performance is just great, I keep FPS around 30 ( using adaptive VSync in Nvidia Inspector ) as it always worked perfect!

I just recalled I have "RealTurb CAT areas v2" latest version installed in my Community folder. I'll try to disable it.

Anyway, MSFS has been one of the most stable and performant flight simulation platforms I ever used, so, it's probably a problem on my side or something that will get fixed with SU15 final...

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)

Brand new pc build. New Windows 11 install on fresh SSD. No add-ons. Nothing in my community folder. No tweaks to NCP. Second time i loaded MSFS it crashed. Only happened once so far. Running the beta. 

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

5 hours ago, jcomm said:

I gave up posting there...

All bugs and reports of other aspects of the game I posted there were treated into closed threads or never got a valuable answer...

I assume they're getting feedback from users running Beta, through the application itself, like Laminar get's from users running XP?

Well, it's a Beta, but it's the first to bring me such an unplayable state of affairs... 

Oh you're preaching to the choir there 😀 their bug reporting process during betas is very flawed, they've been advised but they don't listen.

I know they do get crash reports that they can read their end, so that's something I guess, but when it comes to needing more specific details that's where they fall very short.

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)

  • Author

Well, problem apparently solved after I started MSFS 2020 tonight and it issued an update of a few GB...

After the update flew from LPPR to LPPT in the "new" Fenix V2, and no problem...

SU15 Beta appears to "hammer" my CPU /GPU a bit more than previous versions at least with the DLSS-FSR3 enabled in DX12, but it performs smoothly overall...

The problem mentioned in the OP is probably related to the fact that after reinstalling MSFS 2020 from a backup  I had which was pre-SU15, and then starting fetching the Iberian WU and the City Updates, something got broken (?). The update received yesterday appears to congregate all of the SU 15 and smaller step updates released meanwhile, at least two I guess?

All good now !

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)

On 2/28/2024 at 9:13 AM, jcomm said:

I gave up posting there...All bugs and reports of other aspects of the game I posted there were treated into closed threads or never got a valuable answer...

I agree, it's pointless to post on that forum, all threads will get locked within a couple of hours.

System: I ASRock X670E | AMD 7800X3D | 64Gb DDR5 6000 | RTX 4090 | 2TB NVMe | Seasonic Vertex 1000W I LG Ultra Gear 34 UW I

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.