Divij

That’s interesting. Would you be able to check if this setting is there in the VR Graphics section as well? Or is this only in the regular graphics section?

Really looking forward to performance improvement in V2!

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

This sounds interesting. I run an FPS cap so was wondering how this might change things.

I can confirm I am seeing the DX12 texture bug with SU15 beta using the latest version (3.7Reset)

Yes in theory this should cut scenarios where adaption kicks in for those 1 second fps drops. Looks good to me! Would like to give it a go and see if it works as we think it should ..

Fantastic. Look forward to trying this out!

I do use LOD Step Max set at a value of 10 so I don’t actually notice the adaption kicking in visually. But when I look it at the log I see that it did kick in so I did some testing and narrowed it down to GSX events being called in my case. Sometimes it could also be due to Vatsim traffic being loaded in. Basically a one second dip in FPS due to being CPU limited. Yes it would be fantastic if we can iron out these one second dips. Your idea of setting the number to 120 seems to make a lot of sense and in theory could work really well by removing unnecessary instances of FPS Adaption kicking in.

@Reset XPDR Thank you for your continued development of this wonderful utility. I have run into one slight issue with FPS Adaption where when calling any GSX service the frame rate drops momentarily below my threshold of 27. This causes FPS Adaption to kick in which isn’t ideal. Is there anyway to increase the deadzone for FPS Adaption to kick in? For example say 2 seconds of conisistent FPS below 27 for it to kick in. The ‘Reduce For’ setting doesn’t really help here because even if I set it to a low value like 2s, on occasions when in heavy traffic and scenery this plays havoc and keeps going up and down which is why I prefer keeping this number higher than 10 seconds. Would love to hear your thoughts on potentially adding a deadzone setting for FPS adaption.

Just gave this 3.5 test version a go and things are looking promising. Thank you for your continued development of this fantastic utility! I might give FPS Adaption another go after you have changed it to step up / down. One request that I have for FPS Adaption is, would it be possible for it to work only on the ground? I do not want the LOD changes to happen in the air due to frame rate hiccups. I need it mainly on the ground for the occasions when landing in a heavy airport with lots of Vatsim traffic. If that could be done (with a checkbox) then I would happily give FPS Adaption another go.

Thank you for your help!

Got it. So would this edited code work for what I am looking to do? global appP2A:="ahk_exe Navigraph Charts.exe" global appP3A:="ahk_exe vpilot.exe" global mfs:="ahk_exe FlightSimulator.exe" 1Joy20:: { if not WinExist(appP2A) return switchApp("1Joy20",appP2A) } 1Joy5:: { if not WinExist(appP3A) return switchApp("1Joy5",appP3A) } switchApp(key,app) { OutX:=0 OutY:=0 OutWidth:=0 OutHeight:=0 SendInput "{Blind}!{Tab}" Sleep 100 WinActivate app WinGetClientPos &OutX, &OutY, &OutWidth, &OutHeight MouseMove OutWidth/2,OutHeight/2 KeyWait key SendInput "{Blind}!{Tab}" WinActivate mfs } Apologies for all the trouble but this is truly a gamechanger for me if I can get it to work 🙂

Understood, thanks! This makes using Charts so much faster in VR rather than relying on the airplane EFB. Is it possible to edit this code for it to work with 2 Programs (Charts +vPilot). So using the same joystick hot key for mouse interaction but for 2 apps depending on which one is in focus in the Kneeboard.

Thank you! That was the problem. Using Navigraph Charts in VR this way feels a lot smoother. Out of curiosity, is there a performance hit using Open Kneeboard in VR in MSFS?

Tried running this script but I get an error on line 67 (WinGetClientPos &OutX, &OutY, &OutWidth, &OutHeight) saying that this line contains no recognized action. Any help will be appreciated, thanks!