New beta update 1.37.8.0 out

[Cpt_Piett 4,703]

1 hour ago, Reset XPDR said:

hose red numbers mean your system is performing consistently below your target FPS. See the readme for more info on how to configure the app correctly.

Or that FG is being used and MSFS is not in focus hence AutoFPS will interpret this as FPS suddenly being halved?

I get that all the time - everything then goes to red. I just tick "on top" then place focus back to MSFS, so that I can see how the app performs "live". 

Edited March 13 by Cpt_Piett

[MrFuzzy 2,118]

11 hours ago, F737MAX said:

What's the LOD like in this version?

Plenty of complaints in a thread on the official forums that v1.37.7.0 saw a big drop in the visual experience compared to prior beta versions and SU14.

LOD & draw distance will continue to be sacrificed for payware addons, to accommodate the needs of XBox users who lately experienced avionics shutdowns and other issues on addon aircraft.

The "memory optimizations" that Asobo boasted in the last interviews are aimed to that. Something must be offloaded when the shared memory is full and scenery elements are more expendable than avionics. Hence the reduced draw distance and the stuttering when panning the view and reloading the assets.

There was no need to "optimize" memory usage on PC, where we have many sliders to accommodate every kind of configuration and also considering that on high end PCs both RAM and VRAM are underutilized. 

The only hope is that FS 2024 will have this aspect improved, even though FS 2024 will be an XBox Series S title as well.

Sadly, we will never see again in MSFS the graphics quality that it had when it was still a PC game only:

 

[DAD 2,653]

7 hours ago, OneOfMany said:

fug issue

Uh, fug like in what please? Fog? As in low frames in foggy clouds? Fig issues whould not make sense. And word not allowed would be immediately censored

[MadDog 353]

Is it just me... or does everybody's sim always start in windowed mode since the latest patch?  Normally, I reset it to full screen after every update and it sticks; but not anymore.  It's a minor issue; but never had it happen before.

[Cpt_Piett 4,703]

I’m not seeing any LOD issues in this build. Granted, I’ve tweaked my settings until my face have gone blue, including hunting for the best VPN server in order to avoid low bandwidth warnings.

Granted, I’m using AutoFPS’ expert mode. But then again, I’m also flying an experimental aircraft. So that sort of fits…

Every now and then though, MSFS decides to throw a tantrum resulting in incomplete scenery loading and melted buildings. 

Edited March 13 by Cpt_Piett

[boez 85]

2 hours ago, MadDog said:

Is it just me... or does everybody's sim always start in windowed mode since the latest patch?  Normally, I reset it to full screen after every update and it sticks; but not anymore.  It's a minor issue; but never had it happen before.

I reported this in the official forums. Doesn’t appear to be universal (couple of posters said it didn’t happen to them) which has surprised me as no other changes were made to my system except the update.

 

https://forums.flightsimulator.com/t/1-37-8-0-regression-custom-window-size-being-reset-every-time-app-is-started-also-fullscreen-mode-reverting-to-windowed-mode/633921/14

Edited March 13 by boez

[virtuali 4,421]

9 hours ago, Reset XPDR said:

If the app hasn't recognised (actually validated is more accurate) the memory offsets, you would have seen "MSFS compatibility test failed - Read Only mode" as a red status message when you started AutoFPS.

Alright, I never got that message, so it recognizes the new MSFS beta correctly.

 

9 hours ago, Reset XPDR said:

those red numbers mean your system is performing consistently below your target FPS. See the readme for more info on how to configure the app correctly

I think I understood what's happening, and I suspect there might be a problem with the "lock at 50% of monitor rate" option in MSFS when used together with the "TLOD Min on Ground/Landing" in AutoFPS.

I'm not using Frame generation, and my monitor is 60hz, so the fps is locked and steady at 30 fps and I set 30 fps as target in AutoFPS. The MSI Afterburner overlay graph confirms a 30 fps with a flat line, and I could keep 30 fps even if I closed AutoFPS and set TLOD manually at 200.

But since I have the LOD min at 25 so, and I'm on ground, TLOD is 25, it's working as expected.

However, after takeoff, if the fps in the sim is locked at 50% of the monitor rate, AutoFPS doesn't even try to increase it: it just shows TLOD 25 in red and it stays that way. Cloud quality was set to Ultra and never reduced (Decrease Cloud quality is enabled), and I was flying in clear weather anyway.

As soon as I changed the fps lock option to 100% of monitor rate, fps went up, and AutoFPS quickly raised TLOD up to 200 and kept it that way.

If I set the frame rate lock to 50% monitor again when in flight, TLOD stays at 200 as it should.

It seems that, when the fps is already locked at 30 fps in the sim, so you are already on target, if the TLOD Min on Ground/Landing option is used, it never tries to raise the TLOD after transitioning from ground to flight. Here's a video I made:

 

 

Edited March 13 by virtuali

[Ixoye 1,823]

3 hours ago, MadDog said:

Is it just me... or does everybody's sim always start in windowed mode since the latest patch?  Normally, I reset it to full screen after every update and it sticks; but not anymore.  It's a minor issue; but never had it happen before.

No you are not alone.

[bobcat999 8,484]

1 hour ago, Ixoye said:

No you are not alone.

I have had this also, so I have to press 'alt-enter' to get it to full screen.  Not a major problem, just another little annoyance.

My usercfg.opt file shows >

    Windowed 1
    FullscreenBorderless 1

Which seems to be a conflict.

I will edit windowed to 0 and I will see how it goes at next start up (not until this evening).

Edited March 13 by bobcat999

[Cyrex1984 177]

No more fixes for atc. Its still as bad at is was.

[Ixoye 1,823]

41 minutes ago, bobcat999 said:

I will edit windowed to 0 and I will see how it goes at next start up (not until this evening).

I will check this up as well 👍

Upd! Unfortunately, it didn't work to change the file, but ALT+Enter was a quick fix.

Edited March 13 by Ixoye

[Nemo 1,305]

3 hours ago, Cpt_Piett said:

I’m not seeing any LOD issues in this build. Granted, I’ve tweaked my settings until my face have gone blue, including hunting for the best VPN server in order to avoid low bandwidth warnings. ..

Different VPN servers, are there big differences regarding visuals and performance, compared to non-VPN usage??

Edited March 13 by Nemo

[GSalden 4,673]

I had to re-assign my rudder after this update 

And my keyboard assignments too.

[crimplene 634]

6 hours ago, MrFuzzy said:

LOD & draw distance will continue to be sacrificed for payware addons, to accommodate the needs of XBox users who lately experienced avionics shutdowns and other issues on addon aircraft.

The "memory optimizations" that Asobo boasted in the last interviews are aimed to that. Something must be offloaded when the shared memory is full and scenery elements are more expendable than avionics. Hence the reduced draw distance and the stuttering when panning the view and reloading the assets.

There was no need to "optimize" memory usage on PC, where we have many sliders to accommodate every kind of configuration and also considering that on high end PCs both RAM and VRAM are underutilized. 

You obviously know things nobody else knows, not even Asobo or Microsoft. 🙂

The optimizations, Asobo talked about, were memory allocation optimizations they made while programming MSFS 2024. They ported it to MSFS 2020 and provided us with much smoother panning and a much more consistant frame time (aka smoothnes). I am not entirely sure why you claim otherwise but there is no visible reduced draw distance and most certainly no stuttering when panning.

Edited March 13 by crimplene

[Dillon 2,197]

20 hours ago, turbomax said:

World

• Fixed missing aerials 

 

Did the northern Caribbean finally get addressed?