New beta update 1.37.8.0 out

[Ixoye 1,821]

30 minutes ago, YVR_23 said:

LOD issues are still there. Hopefully it's server related.

Strange, I haven't seen any difference in LOD between SU14 and any beta version, I'm using Ultra default settings.

[mobeans10 197]

Using version 0.3.8 of dynamic lod reset edition is working for me with the latest 1.37.8 beta update

Edited March 12 by mobeans10

[mobeans10 197]

Duplicate Post

Edited March 12 by mobeans10

[Fielder 3,681]

In addition to updated O'hare and KLAX... also KJFK and Heathrow

[Fielder 3,681]

One "feature" of this beta version remains: The simrate maximum is 128X ! Way too fast! fps drops to 1 fps.

So if you hold the sim rate button or + key down, the flight becomes a nightmare in about 3 seconds. It can actually crash the sim sometimes.

It seems to me a max simrate of 16X would make more sense. 16X will only cut fps in half approximately.

I use the flightsim.to addon which puts any cap you want on simrate. I set 4X as max. It also displays sim rate.

You can open and close this app from an overhead taskbar icon all its own.

EDIT: https://flightsim.to/file/45543/sim-rate-selector

Edited March 12 by Fielder

[Cpt_Piett 4,694]

1 hour ago, virtuali said:

Doesn't seem to work for me. Red numbers for TLOD and Cloud quality means the app hasn't recognized the memory offsets, right?

I'm testing latest test build now as we speak. No issues in expert mode. Under sim values, red ØFPS means it's too low for target fps. Keep in mind that when using FG-FPS MSFS needs to be in focus though (enable "on top" then change focus back to MSFS). Orange values means they're changing, and green = stable, if I understand it correctly. 

Just checked the other modes (non-expert + non-expert-auto-target-fps) - they both seem to be working fine. 

15 minutes ago, Fielder said:

The simrate maximum is 128X ! Way too fast! fps drops to 1 fps.

Not laughing at your woes, but how on Earth did they think this would be useful? 😅

Edited March 12 by Cpt_Piett

[YVR_23 24]

2 hours ago, Ixoye said:

Strange, I haven't seen any difference in LOD between SU14 and any beta version, I'm using Ultra default settings.

Here's the LOD issue, ultra settings and no rolling cache. The weird thing is a few days I had no issues whatsoever but over the weekend I noticed really bad LOD so I'm thinking it could be a server issue.

 

 

Edited March 12 by YVR_23

[Cpt_Piett 4,694]

44 minutes ago, YVR_23 said:

Here's the LOD issue, ultra settings and no rolling cache. The weird thing is a few days I had no issues whatsoever but over the weekend I noticed really bad LOD so I'm thinking it could be a server issue.

I'm thinking you might be right. I do get it from time to time. 

Meanwhile at KDCA:

KBOS: 

(at least the aircraft on short final did a go-around, so I guess there's some order to the chaos)

Edited March 12 by Cpt_Piett

[DModjo 122]

44 minutes ago, YVR_23 said:

Here's the LOD issue, ultra settings and no rolling cache. The weird thing is a few days I had no issues whatsoever but over the weekend I noticed really bad LOD so I'm thinking it could be a server issue.

 

 

Looks like it might be server related. Photogrammetry is always very hit and miss as there is a high dependency on connection speed, latency and bandwidth.

Edited March 12 by DModjo

[OneOfMany 314]

Looks like they fixed the fug issue this go round. 

[Reset XPDR 1,271]

5 hours ago, virtuali said:

Doesn't seem to work for me. Red numbers for TLOD and Cloud quality means the app hasn't recognized the memory offsets, right?

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.

If you didn't, and I doubt you did as I have received numerous reports that AutoFPS is working fine with the latest SU15 Beta, 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.

 

[Fielder 3,681]

3 hours ago, Cpt_Piett said:

I'm testing latest test build now as we speak. No issues in expert mode. Under sim values, red ØFPS means it's too low for target fps. Keep in mind that when using FG-FPS

MSFS needs to be in focus though (enable "on top" then change focus back to MSFS). Orange values means they're changing, and green = stable, if I understand it correctly. 

Just checked the other modes (non-expert + non-expert-auto-target-fps) - they both seem to be working fine. 

Not laughing at your woes, but how on Earth did they think this would be useful? 😅

Especially irksome because, unlike FSX, MSFS2020 control settings doesn't allow turning repeat off. So when you push down a keyboard key it sends the same command over and over continuously. Whether you want it to do that or not.  Of course with AAO you can have repeat on or off and even set the repeat rate fast, medium, or slow. Or set it in between those 3 speeds. Anyway, I use the above fs.to app to turn the simrate maximum to 4.

[Fielder 3,681]

I also use AAO repeat choices to set 2 different rudder trim keys. One repeats One doesn't repeat. I use the one that repeats to set an approximate trim. And then punch the no repeat trim key to move the trim just a hair. And then keep punching it until the trim is perfect. Fast and easy to do.

[Ojisan_alpha 5]

Anybody else able to confirm that FSR3 Frame Generation is now creating artefacts around aircraft/cockpit glass borders that make it unusable?

 

<edit>
Disregard.
The problem was caused by "lens correction".

Edited March 13 by Ojisan_alpha

[JYW 2,984]

AutoFPS working perfectly with the new  beta version here too.