Fenix - as usual - works fine. Did a quick hop LOWI-EBBR in the A320. All perfect. Graphics are just great with real wheather. And that smoothness… 

The smoothness makes this a whole new sim. SU3 - SU4 is a massive jump. Not just during the flight - the whole sim is faster. Menus, clicking around, going between different screens.. everything is faster and effortless. 

6 hours ago, JonathanC said:

The smoothness makes this a whole new sim. SU3 - SU4 is a massive jump. Not just during the flight - the whole sim is faster. Menus, clicking around, going between different screens.. everything is faster and effortless. 

This. And that annoying switching between controller profiles delay is gone too. That was frustrating. 

57 minutes ago, rick celik said:

This. And that annoying switching between controller profiles delay is gone too. That was frustrating. 

Just to point out - the profile issue was resolved in SU3. But I agree - it was frustrating.

has anyone else noticed in this release the PAPI's are not displayed correctly.  Seems whenever I am on an ils approach even though I am on the correct glideslope the PAPI's display four redlights indicating I am too low.

40 minutes ago, Shrek1970 said:

has anyone else noticed in this release the PAPI's are not displayed correctly.  Seems whenever I am on an ils approach even though I am on the correct glideslope the PAPI's display four redlights indicating I am too low.

That's a very old problem. Many glidelsopes are simply incorrect in the sim. The Papi's are usually correct.

29 minutes ago, Farlis said:

That's a very old problem. Many glidelsopes are simply incorrect in the sim. The Papi's are usually correct.

Quite an issue for a FlightSim wouldnt you all agree. Like a car simulator were all crossroad stoplights are all red or all green😆😁

The controller menu bug was indeed frustrating but still nice i dont need to fiidle with them when switching plane types. MSFS2020 is a pain in that regards

Michael Moe

With the latest beta build the exposure BuG is back, at least in VR. Flying from Daytime into Night time causes at arrival extrem bright white Airport Lights and black cockpit textures. Switch to external view does solve it....when back into cockpit view issue comes back again. 

Anyone else noticed this? 

I have voted a topic on this in MSFS Forums Beta section. 

But am Interested if anyone else has seen this

3 hours ago, Farlis said:

That's a very old problem. Many glidelsopes are simply incorrect in the sim. The Papi's are usually correct.

The MSFS glideslope transmitters are placed based on the exact latitude/longitude data of the real G/S from AIRAC data. In the US that data comes from the FAA - not sure of the source for other counties. 

I have checked countless glideslopes and localizers in MSFS airports using the FAA master data files at https://adip.faa.gov and have never found even one that is in the wrong location. I have a utility program that I obtained from FSDeveloper that can read glideslope or localizer lat/lon from the NAX BGL files that MSFS uses to define navaid parameters.

PAPIs are another matter. These are scenery objects that airport scenery developers have to manually place in the correct locations. That can only be done by zooming in close to the airport’s aerial/satellite imagery when in the airport design environment of DEV mode to try to “drop” the PAPI where it is shown (from above) in the aerial imagery. That isn’t always easy to get right, depending on the quality/resolution of the imagery.

TL:DR Glideslopes in MSFS are almost always placed correctly in relation to the runway - it is the placement of PAPIs that are often erroneous.

Even if the PAPIs are placed correctly, there are many r/w airports where the visual glide path generated by the PAPI does not match the electronic ILS glideslope. The approach chart will usually have a note advising when this situation exists for a particular runway

1 hour ago, JRBarrett said:

I have checked countless glideslopes and localizers in MSFS airports using the FAA master data files at https://adip.faa.gov 

Interesting. I have seen a lot of posts claiming that either glideslopes or papis are wrong in msfs. Hopefully when the world Hub launches things like misplaced papis will be fixed by the community.

22 hours ago, JonathanC said:

The smoothness makes this a whole new sim. SU3 - SU4 is a massive jump. Not just during the flight - the whole sim is faster. Menus, clicking around, going between different screens.. everything is faster and effortless. 

This is what always struck me with the original '24 videos I saw and now it looks even better.

There was a fluidity that was unique to '24,(at least I hadn't seen it before in 44+ years of simming, even though I am only 52 lol ) so I am really hoping that the performance gains in the beta remain in the final SU4 release.  

I know I am getting redundant but I keep saying the progress around resolving the main thread issue and taking better advantage of the GPU is the equivalent of P3D going from 32 to 64 bit.  

It shouldn't be overlooked by anyone, it's one of those no pun intended game changing developments that is a foundational change. 

So, what I am gathering is the Fenix and PMDG 777 are working. AvroRJ and other JF planes (airliners) are having some issues. The inibuilds is ok? Some are getting CTDs. I left the beta about a month ago and get the occasional CTD in SU3 from the menu. 

Wondering if I should give SU4 beta another chance? 

On 10/25/2025 at 5:01 AM, bobcat999 said:

Yes it's strange.  I have been flying the Piper Dakota, Default C172, and the YS-11.  If I go to outside view, move the camera around a bit, and then go back inside, the gauges redraw slowly. 

Other times, I can be outside for a minute or two, move the camera around a lot and take in a lot of scenery from different angles, and when I go back in the gauges load instantly - it's really weird. 
I would expect it the other way around.

No issues at all in SU3 on the same settings and same aircraft.

Just an FYI but I am getting slow VC redraw with the YS-11 on SU3 and it's been like that since the YS-11 launched.  Happens almost every time I fly it especially when going from outside view back to VC.  I don't think that bug is limited to SU4.

I believe that I can solve this by downloading the YS-11 / storing it locally.  I haven't tried to do that yet though, supposedly we can do it now since SU3.   I normally don't fly anything unless it's stored locally, and this is why.  I am surprised you haven't downloaded it!  Is it not possible?

9 hours ago, Sonosusto said:

So, what I am gathering is the Fenix and PMDG 777 are working. AvroRJ and other JF planes (airliners) are having some issues. The inibuilds is ok? Some are getting CTDs. I left the beta about a month ago and get the occasional CTD in SU3 from the menu. 

Wondering if I should give SU4 beta another chance? 

Fenix, 777 and Avro are working wonderfully for me. Great performance using autofps and dynamic settings combined, FPS sensitivity to 3 and TLOD min 50 to max 275. WOW. 

KJFK, BATC traffic all around 5-6, active sky, RAAS, FSrealistic, gsx, headtracking and lock fps at 31 and let fg kick it up to 62. Finally hopefully it stays this way for a bit. 

Edited October 28, 2025Oct 28 by Sonosusto

9 hours ago, Mace said:

Just an FYI but I am getting slow VC redraw with the YS-11 on SU3 and it's been like that since the YS-11 launched.  Happens almost every time I fly it especially when going from outside view back to VC.  I don't think that bug is limited to SU4.

I believe that I can solve this by downloading the YS-11 / storing it locally.  I haven't tried to do that yet though, supposedly we can do it now since SU3.   I normally don't fly anything unless it's stored locally, and this is why.  I am surprised you haven't downloaded it!  Is it not possible?

True, the YS-11 cockpit can redraw a bit slowly in SU3, but it was taking up to 5 seconds in SU4b, which is a lot slower again, and obviously, just not flyable like this.

I tried downloading the Carenado Dakota and the 2024 F33A and it made no difference for me. 
The Community folder and the rolling cache are placed on a 2GB Samsung 980Pro, my fastest drive, but it made no difference at all to the problem

Also.  I managed to capture a screenshot of the partially drawn cockpit in the Piper Dakota when this happens. 
Incredibly, the 'cardboard cut-out' type image that initially appears is quite a bit different from the finally displayed cockpit, which adds another layer of intrigue.
The Attitude Indicator for example is a completely different model until over-drawn by the correct instrument - it's really weird!
It is almost like a low resolution 2D image of the cockpit before it gets overdrawn.  

Other things tried are clearing all caches including the rolling cache, increasing windows virtual memory to double, rolling cache to 64gb.  Obviously leaving the sim in between changes and sometimes even rebooting the PC.
But I must emphasise, this problem is not present in SU3, so there must be a solution for this, but I am just about out of ideas.  

Once again, I will rejoin the beta at the next update to test, just in case they solve it, as  I notice not all changes are listed in the change logs. 
I can't find a thread over on the official beta forum about this, which worries me.  I may have to start one.