Jump to content

Recommended Posts

Proposed change when in FG mode to hopefully clarify the Target FG FPS to be the Target FG Active FPS, so that when the user puts the Windows focus on the app and the status line says FG Mode Inactive they realise that the target FPS with FG is for when it is active, not inactive as it currently is. Is this any better?

Also, I have already removed auto pause from non-expert settings mode, as you can see by no Auto PAUSE status message showing in the screen shot.

Oh, and I have moved the priority status to the status line because OLOD's reappearance took its spot in the Sim Value section.

image.png?ex=65f018bb&is=65dda3bb&hm=b74

Edited by Reset XPDR
  • Like 3

Ryzen 7 5800X3D | Gigabyte RTX 4090 Gaming OC 24GB | 32GB 3200MHz RAM | 2TB + 1TB NVME SSD | 2GB SSD | 2GB HDD | Corsair RM850 PSU | 240mm AIO | Buttkicker Gamer 2 | Thrustmaster T.16000M Flight Pack | 75" 4K60 TV | 40" 4K60 TV | Quest 3 | DOF Reality H3 Motion Platform

MSFS @ 4K Ultra DLSS Performance with 2.0x Secondary Scaling |  VR VDXR Godlike 80Hz SSW OXRTK @ 5200x5200 Custom FFR CAS 50% | MSFS VR Ultra DLSS Performance - Windows 11

Share this post


Link to post
Share on other sites

New AutoFPS test version available here. Getting down to small fixes now so it will probably be released tomorrow, pending no major issues raised.

I am surprised the new auto OLOD functionality seems to be working without any major issues with it, well other than other than overly ambitious settings causing stuttering but that's to be expected. If you have found any notable issues with the test version, not just auto OLOD, please let me know within the next day before I release it formally.

New test version 27Feb240940Z changes are:

  • Fixed sim value colouring to work correctly when FG is on but inactive.
  • Changed Target FPS for FG label to say Target FG Active FPS to further clarify this setting is for when FG is active, not inactive when the app has the focus.
  • Changed non Use Expert Settings default for Auto pause to be off instead of on.

image.png?ex=65f018bb&is=65dda3bb&hm=b74

  • Like 5

Ryzen 7 5800X3D | Gigabyte RTX 4090 Gaming OC 24GB | 32GB 3200MHz RAM | 2TB + 1TB NVME SSD | 2GB SSD | 2GB HDD | Corsair RM850 PSU | 240mm AIO | Buttkicker Gamer 2 | Thrustmaster T.16000M Flight Pack | 75" 4K60 TV | 40" 4K60 TV | Quest 3 | DOF Reality H3 Motion Platform

MSFS @ 4K Ultra DLSS Performance with 2.0x Secondary Scaling |  VR VDXR Godlike 80Hz SSW OXRTK @ 5200x5200 Custom FFR CAS 50% | MSFS VR Ultra DLSS Performance - Windows 11

Share this post


Link to post
Share on other sites
4 hours ago, Reset XPDR said:

Also, this confused me somewhat as I gather you are talking about the AutoFPS installer here. If so, it has two Autostart options: FSUIPC or MSFS. ie. there is no Steam Autostart option in the installer. Can you please clarify what you meant. Thanks.

I apologize!  That's my old age showing... the comment had nothing to do with Auto_FPS.  It was from a totally different app and I probably didn't even get THAT right🙄

Sometimes I really surprise myself🙂 

  • Like 1

Share this post


Link to post
Share on other sites
5 hours ago, Reset XPDR said:

Would anyone object to me disabling auto pause by default?

Not unless the option will still be available in expert settings 🙂 

3 hours ago, Reset XPDR said:

Proposed change when in FG mode to hopefully clarify the Target FG FPS to be the Target FG Active FPS, so that when the user puts the Windows focus on the app and the status line says FG Mode Inactive they realise that the target FPS with FG is for when it is active, not inactive as it currently is. Is this any better?

I think this should make it much easier to understand for most people.

3 hours ago, Reset XPDR said:

I am surprised the new auto OLOD functionality seems to be working without any major issues with it, well other than other than overly ambitious settings causing stuttering but that's to be expected.

For me this proves to a greater degree the robustness of the app as it can handle extreme settings really well. The stutters I experienced was more on an objective/academic level and barely subjectively noticeable.

Edited by Cpt_Piett
  • Like 1
  • Upvote 1

i9-12900KF @ 5.1GHz | MSI Trio Gaming X RTX4090 | MSI MPG Z690 Carbon EK X | G.Skill Trident Z5 32GB DDR5 | WD Black SN850 2TB SSD | Samsung 970 EVO Plus 500GB SSD | 2x Samsung 960 EVO 500GB SSDs | Hela 850R Platinum PCIe 5.0 w/ 12VHPWR cable | Corsair RM750X | LG 77" OLED 3840x2160 | Thrustmaster HOTAS Warthog | MFG Crosswind pedals | Thrustmaster TCA Captain Pack X Airbus Edition

“Intensify the forward batteries. I don’t want anything to get through”

dYn55y0_d.jpg?maxwidth=520&shape=thumb&f

Share this post


Link to post
Share on other sites
33 minutes ago, Cpt_Piett said:

For me this proves to a greater degree the robustness of the app as it can handle extreme settings really well. The stutters I experienced was more on an objective/academic level and barely subjectively noticeable.

Agreed. I have been changing settings to make it less likely to stutter. TLOD is a weird setting in that even a really high setting (600) results in terrain popping at distance at cruise altitudes. Flying at FL350, varying between 250-600 for TLOD, I could see that all I was changing was the distance at which terrain elements would appear. I'm think I'm going to settle on 300-400.

I've also changed the OLOD settings to be 1000@1000 and 100@10000.

  • Like 1

Share this post


Link to post
Share on other sites

I’m thinking that in my next test run I’ll try a narrower range of TLOD 1000 to 20 using same AGL of min 1000 max 5000.


i9-12900KF @ 5.1GHz | MSI Trio Gaming X RTX4090 | MSI MPG Z690 Carbon EK X | G.Skill Trident Z5 32GB DDR5 | WD Black SN850 2TB SSD | Samsung 970 EVO Plus 500GB SSD | 2x Samsung 960 EVO 500GB SSDs | Hela 850R Platinum PCIe 5.0 w/ 12VHPWR cable | Corsair RM750X | LG 77" OLED 3840x2160 | Thrustmaster HOTAS Warthog | MFG Crosswind pedals | Thrustmaster TCA Captain Pack X Airbus Edition

“Intensify the forward batteries. I don’t want anything to get through”

dYn55y0_d.jpg?maxwidth=520&shape=thumb&f

Share this post


Link to post
Share on other sites
23 minutes ago, Cpt_Piett said:

I’m thinking that in my next test run I’ll try a narrower range of TLOD 1000 to 20 using same AGL of min 1000 max 5000.

That looks like the same range you tested before.

Share this post


Link to post
Share on other sites
26 minutes ago, mmcmah said:

That looks like the same range you tested before.

You’re right, I misspelled. I meant 1000 to 100. Or:

1 hour ago, mmcmah said:

I've also changed the OLOD settings to be 1000@1000 and 100@10000.

 


i9-12900KF @ 5.1GHz | MSI Trio Gaming X RTX4090 | MSI MPG Z690 Carbon EK X | G.Skill Trident Z5 32GB DDR5 | WD Black SN850 2TB SSD | Samsung 970 EVO Plus 500GB SSD | 2x Samsung 960 EVO 500GB SSDs | Hela 850R Platinum PCIe 5.0 w/ 12VHPWR cable | Corsair RM750X | LG 77" OLED 3840x2160 | Thrustmaster HOTAS Warthog | MFG Crosswind pedals | Thrustmaster TCA Captain Pack X Airbus Edition

“Intensify the forward batteries. I don’t want anything to get through”

dYn55y0_d.jpg?maxwidth=520&shape=thumb&f

Share this post


Link to post
Share on other sites

Hello,

I seem to be having an issue with the latest test version in VR, where even though TLOD Min on Gnd / Landing is not checked, when entering VR the tlod is set to minimum. This does not happen when I exit VR back to 2D where the TLOD starts rising. Also an issue with it not setting the FPS target at 33 for VR as I had under Expert Settings. I had to change this in the configuration file. 

Here is the log file:

2024-02-27 19:38:58.376 [INF] [ ServiceController:ServiceLoop    ] Starting Service Loop 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Initial LODs PC 90 / 100 and VR 90 / 100 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Initial cloud quality PC 1 / VR 1 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Setting TLOD Min on ground 50 
2024-02-27 19:38:58.378 [INF] [ ServiceController:ServiceLoop    ] Setting OLOD @ Base on ground 150 
2024-02-27 19:58:02.375 [INF] [ MainWindow:LoadSettings          ] Expert: True Mode: VR Target: 40 Tol: 5 TMin: 50 TMax: 140 CloudQ: False CRecovT: 100 Pause: True TMaxGL: False 
2024-02-27 19:58:21.364 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:30.373 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:39.370 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:48.361 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:57.372 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:06.373 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:15.392 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:24.381 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 0 Clouds: Medium 
2024-02-27 19:59:33.385 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 19:59:42.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 19:59:51.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 3 Clouds: Medium 
2024-02-27 20:00:00.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -5 Clouds: Medium 
2024-02-27 20:00:09.388 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 0 Clouds: Medium 
2024-02-27 20:00:18.380 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:19.387 [INF] [ MainWindow:LoadSettings          ] Expert: True Mode: PC Target: 33 Tol: 5 TMin: 50 TMax: 140 CloudQ: False CRecovT: 100 Pause: True TMaxGL: False 
2024-02-27 20:00:27.391 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 54 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:36.385 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 72 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:58.856 [INF] [ ServiceController:ServiceLoop    ] ServiceLoop ended 

 

Edited by Divij

Share this post


Link to post
Share on other sites

Has anyone found good VR settings using virtual desktop and quest 3? I'm pairing that with a 7900 XTX and ryzen 7900x with 32gb ram. I either get stutters as it's changing the settings or it just doesn't work/change anything. I have tried with and without ASW, and usually put 32-36FPS as that's half of the 72 I'm running in headset. If I keep ASW off, frames look good and steady at 36 and latency is good (under 60) but every head movement is a stuttering mess. If I leave it on, it's smooth while turning your head but it stutters constantly as it's changing the TLOD. Thanks!

Share this post


Link to post
Share on other sites

Hey Guys,

Has anyone seen any stuttering with the latest version and using the OLOD feature?

I was getting some stuttering around Toronto this morning and I put it down too a combination of the terrible photogrammetry and FLYTamper CYYZ which is pretty resource intensive. I was using the latest version 4.1 with a base OLOD of 200 at 1000ft and then 20 at 6000 feet. I decided to back to Liverpool to rule out what I thought may have been scenery related, and start from runway 27 in the PMDG 737 and run a CapFrameX capture for 15 minutes. Here is the results first with 4.1 and using the auto OLOD

ee90f15.jpg

 

Then I closed the sim and removed AutoFPS 4.1 and installed the latest version of 4.0 and did the exact same 15 minute test again. It would appear something odd is happening even though my OLOD settings were not crazy and I left plenty of altitude between the two values

 

d9WwFT9.jpg

Edited by RJC68

 

Richard

i7-12700K | Noctua NH-D15S Black Version | MSI Pro Z690 - A | 32 GB DDR4 3600 | Gigabyte Gaming OC 4090 | 1TB WD Blue NMVe (MSFS 2020) | 500 GB WD Black Gen 4 NVMe | 4TB WD Black Conventional | Fractal Design Torrent Case | Seasonic 1000W Gold Plus PSU | Thrustmaster Boeing Yoke | Honeycomb Throttle | Airbus Side Stick | Virpil Rudder Pedals | Sony X90K 55 Inch TV |

mmBbmS1.png

 

Share this post


Link to post
Share on other sites

Would it be possible to have a minimum TLOD setting on the ground that's different from the one on landing?

There's another thread that has to do with the ability to pick out runways at a distance and the optimal TLOD value that I came up with after testing was 250-300. This was flying into LEPA, so clearly something like KJFK or KLAX would not require that level of detail due to the lights and area taken up by the runways, buildings, etc.

I'm trying to think of a way to have a high TLOD until you're basically lined up (1,500ft?) and then bring it down gradually, or allow the mod to go below the configured minimum if the system still can't handle it?

Share this post


Link to post
Share on other sites
3 hours ago, Divij said:

Hello,

I seem to be having an issue with the latest test version in VR, where even though TLOD Min on Gnd / Landing is not checked, when entering VR the tlod is set to minimum. This does not happen when I exit VR back to 2D where the TLOD starts rising. Also an issue with it not setting the FPS target at 33 for VR as I had under Expert Settings. I had to change this in the configuration file. 

Here is the log file:

2024-02-27 19:38:58.376 [INF] [ ServiceController:ServiceLoop    ] Starting Service Loop 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Initial LODs PC 90 / 100 and VR 90 / 100 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Initial cloud quality PC 1 / VR 1 
2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Setting TLOD Min on ground 50 
2024-02-27 19:38:58.378 [INF] [ ServiceController:ServiceLoop    ] Setting OLOD @ Base on ground 150 
2024-02-27 19:58:02.375 [INF] [ MainWindow:LoadSettings          ] Expert: True Mode: VR Target: 40 Tol: 5 TMin: 50 TMax: 140 CloudQ: False CRecovT: 100 Pause: True TMaxGL: False 
2024-02-27 19:58:21.364 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:30.373 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:39.370 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:48.361 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:58:57.372 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:06.373 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:15.392 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -0 Clouds: Medium 
2024-02-27 19:59:24.381 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 0 Clouds: Medium 
2024-02-27 19:59:33.385 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 19:59:42.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 19:59:51.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 3 Clouds: Medium 
2024-02-27 20:00:00.379 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: -5 Clouds: Medium 
2024-02-27 20:00:09.388 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 0 Clouds: Medium 
2024-02-27 20:00:18.380 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 50 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:19.387 [INF] [ MainWindow:LoadSettings          ] Expert: True Mode: PC Target: 33 Tol: 5 TMin: 50 TMax: 140 CloudQ: False CRecovT: 100 Pause: True TMaxGL: False 
2024-02-27 20:00:27.391 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 54 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:36.385 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 36 TLOD: 72 OLOD: 150 AGL: 9 FPM: 1 Clouds: Medium 
2024-02-27 20:00:58.856 [INF] [ ServiceController:ServiceLoop    ] ServiceLoop ended 

 

Thanks for including the relevant log section, especially with the extra Sim Value logging in test mode.

What this is telling me is that you have your Target VR FPS set to 40 and it is setting your TLOD to TLOD min. It will do this if either TLOD Min on Ground/Landing is checked, which it isn't so its not that, or because your actual FPS is lower than the Target VR FPS and TLOD has gone as low as it  can to recover, and that's what seems to be the case. When you switch out of VR back to PC mode, your Target PC FPS is set to 33, you are achieving 36 FPS, so TLOD can start rising, which also looks correct.

4 hours ago, Divij said:

Also an issue with it not setting the FPS target at 33 for VR as I had under Expert Settings. I had to change this in the configuration file.

This is where I think the issue lays. You can only set your Target FPS in the app for a particular graphics mode (PC, FG, VR) when you are in that mode. For VR, you need to switch MSFS to VR, then the app should show Target VR FPS on your monitor and you enter your desired VR FPS then.

4 hours ago, Divij said:

2024-02-27 19:38:58.377 [INF] [ ServiceController:ServiceLoop    ] Setting TLOD Min on ground 50 

BTW, your log file helped me identify that this line shouldn't be there when TLOD Min on Ground/Landing is not being used and it turns out I had the logic flipped for this one relating to Use Expert Setting, which I have now fixed, so thanks for that.

  • Like 3

Ryzen 7 5800X3D | Gigabyte RTX 4090 Gaming OC 24GB | 32GB 3200MHz RAM | 2TB + 1TB NVME SSD | 2GB SSD | 2GB HDD | Corsair RM850 PSU | 240mm AIO | Buttkicker Gamer 2 | Thrustmaster T.16000M Flight Pack | 75" 4K60 TV | 40" 4K60 TV | Quest 3 | DOF Reality H3 Motion Platform

MSFS @ 4K Ultra DLSS Performance with 2.0x Secondary Scaling |  VR VDXR Godlike 80Hz SSW OXRTK @ 5200x5200 Custom FFR CAS 50% | MSFS VR Ultra DLSS Performance - Windows 11

Share this post


Link to post
Share on other sites
3 hours ago, Godwisper said:

trying to install this but am getting 

 

Could not determine package path error 

Is your MSFS installed in a custom location?

  • Like 1

Ryzen 7 5800X3D | Gigabyte RTX 4090 Gaming OC 24GB | 32GB 3200MHz RAM | 2TB + 1TB NVME SSD | 2GB SSD | 2GB HDD | Corsair RM850 PSU | 240mm AIO | Buttkicker Gamer 2 | Thrustmaster T.16000M Flight Pack | 75" 4K60 TV | 40" 4K60 TV | Quest 3 | DOF Reality H3 Motion Platform

MSFS @ 4K Ultra DLSS Performance with 2.0x Secondary Scaling |  VR VDXR Godlike 80Hz SSW OXRTK @ 5200x5200 Custom FFR CAS 50% | MSFS VR Ultra DLSS Performance - Windows 11

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...