On 8/25/2025 at 1:21 AM, Reset XPDR said:

I'm looking in to this now and in non-expert mode, which I assume you were refering to as you referenced DecCloudQNonExpert, cloud quality is never changed for MSFS 2024. This is the settings initialisation code for MSFS 2024: 

if (isMSFS2024)
  {
  DecCloudQ[(int)appProfiles.NonExpert] = false;
  ReduceCloudQ[(int)appProfiles.NonExpert] = false;
  }

If you actually meant expert mode, they can be disabled too, even when using auto settings reduction higher than LODs only as long as you choose Custom,  as follows:

As such, I don't see anything that needs to be changed to achieve what you want. Did you mean something else?

Apologies I completely forgot to respond 😊Ok that's great, I think therefore I was just seeing MSFS2024 behaving badly (as it does), I did a flight yesterday with non-expert and the clouds never changed, so perhaps I saw something else before, Thanks 🙂 

2 hours ago, Lucky38i said:

Hi @Reset XPDR having a great time so far, was wondering if the expert settings can be graphics mode specific. For example I like to switch back to flat screen once in cruise and would like expert settings that are specific to NFR that I wouldn't use with VR.

I have not made them graphics mode specific because there are 6 different profiles that can be configured however you want and most users use a specific graphics mode all the time anyway. I do get what you are saying about VR and switching back to 2D for the cruise for longer IFR flights, as I do the same thing myself. It has never really bothered me though as I find the settings I use for VR are suitable for 2D as well, but I can see how others like yourself may want higher settings because performance in 2D is better.

The issue with implementing what you ask is that the profiles in the app now were an afterthought and because of that their implementation is somewhat convoluted compared to being designed that way initially and this may add another layer of convolution to that again, making the code difficult to maintain.

Nonetheless, I will take a look and see whether it is possible without creating spaghetti code. If it is not, another option I could look that may not be too hard to implement could be that if you name two profiles of the existing 6 profiles the same but have VR tagged on the the end of one of them, I could have the app look for that when it detects a VR to 2D and vice versa graphics mode switch and to auto switch to the relevant profile. eg. you could have one named IFR and another IFR VR and it could auto switch between the two of them depending on active graphics mode. 

24 minutes ago, Reset XPDR said:

I have not made them graphics mode specific because there are 6 different profiles that can be configured however you want and most users use a specific graphics mode all the time anyway. I do get what you are saying about VR and switching back to 2D for the cruise for longer IFR flights, as I do the same thing myself. It has never really bothered me though as I find the settings I use for VR are suitable for 2D as well, but I can see how others like yourself may want higher settings because performance in 2D is better.

The issue with implementing what you ask is that the profiles in the app now were an afterthought and because of that their implementation is somewhat convoluted compared to being designed that way initially and this may add another layer of convolution to that again, making the code difficult to maintain.

Nonetheless, I will take a look and see whether it is possible without creating spaghetti code. If it is not, another option I could look that may not be too hard to implement could be that if you name two profiles of the existing 6 profiles the same but have VR tagged on the the end of one of them, I could have the app look for that when it detects a VR to 2D and vice versa graphics mode switch and to auto switch to the relevant profile. eg. you could have one named IFR and another IFR VR and it could auto switch between the two of them depending on active graphics mode. 

Wonderful, I appreciate you look into it but perfectly understand if it's not possible as I'm fairing just fine regardless

I keep seeing a pop-up saying my "system cap (30) is under the Target 40" or something every now and then, I'm not really understanding that as I have no System FPS cap set anywhere, the in game Dynamc setting is Off, nVidia CP setting is Off (default), so what does it mean by System cap?

4 hours ago, MarcG said:

I keep seeing a pop-up saying my "system cap (30) is under the Target 40" or something every now and then, I'm not really understanding that as I have no System FPS cap set anywhere, the in game Dynamc setting is Off, nVidia CP setting is Off (default), so what does it mean by System cap?

It means that the detected FPS over the last 20 seconds has been extremely stable at the detected value, and rarely if ever going over that value, and therefore appears to be a system FPS cap of some kind. This is usually caused by you manually setting a system FPS cap somewhere, eg. RTSS, nVidia CP, but it can also occur when having vsync enabled at the vsync interval specified. eg. if your Windows refresh rate is 60 Hz and you enable vsync in-game in MSFS with a half-refresh interval, that is the equivalent of having a system FPS cap of 30 FPS because FPS cannot go any higher than this.

The reason you are getting a warning for this is that FPS sensitivity or tolerance mode will not function correctly if your FPS is not going above your target FPS, because these modes need that for TLOD automation to work properly. You can select the option to no longer be warned of this again, but if you leave things as they are your TLOD will never increase above TLOD Min.

1 hour ago, Reset XPDR said:

It means that the detected FPS over the last 20 seconds has been extremely stable at the detected value, and rarely if ever going over that value, and therefore appears to be a system FPS cap of some kind. This is usually caused by you manually setting a system FPS cap somewhere, eg. RTSS, nVidia CP, but it can also occur when having vsync enabled at the vsync interval specified. eg. if your Windows refresh rate is 60 Hz and you enable vsync in-game in MSFS with a half-refresh interval, that is the equivalent of having a system FPS cap of 30 FPS because FPS cannot go any higher than this.

The reason you are getting a warning for this is that FPS sensitivity or tolerance mode will not function correctly if your FPS is not going above your target FPS, because these modes need that for TLOD automation to work properly. You can select the option to no longer be warned of this again, but if you leave things as they are your TLOD will never increase above TLOD Min.

As mentioned I've not set a cap anywhere and I'm running in VR so their is no vsync (this is also off in 2D settings),  using non-expert mode 🤔

Well, I have to say that this app has been quite a revelation since I started using it this week.

I never imagined I’d be able to regularly and consistently hit a TLOD of 900. Makes such a difference to the clarity of textures further out. 

Wish I’d tried it sooner!

9 hours ago, MarcG said:

As mentioned I've not set a cap anywhere and I'm running in VR so their is no vsync (this is also off in 2D settings),  using non-expert mode 🤔

Then just click no when it next pops up and you should never see that message again.

Ok, next attempt: I am now pretty happy with a framelock in the usercfg.opt at 36, resulting in 72FPS ingame after frame generation. This with TLOD 200. Of course, on super heavy scenarios, FPS dip below that threshold, so I wanted to go for a FPS threshold using AutoFPS. And of course I hope the overhead I get at 37000ft will be used for high TLOD. What do I set up? 72FPS sharp or 74FPS for a slight overhead? And hopefully TLOD and OLOD will do the trick, I dont want my other settings being altered if not necessary...

5 minutes ago, AnkH said:

Ok, next attempt: I am now pretty happy with a framelock in the usercfg.opt at 36, resulting in 72FPS ingame after frame generation. This with TLOD 200. Of course, on super heavy scenarios, FPS dip below that threshold, so I wanted to go for a FPS threshold using AutoFPS. And of course I hope the overhead I get at 37000ft will be used for high TLOD. What do I set up? 72FPS sharp or 74FPS for a slight overhead? And hopefully TLOD and OLOD will do the trick, I dont want my other settings being altered if not necessary...

If you are using expert mode, use FPS Cap mode with a frame lock like you have set and set it to 72 to match your resultant frame generated FPS.

13 hours ago, MarcG said:

As mentioned I've not set a cap anywhere and I'm running in VR so their is no vsync (this is also off in 2D settings),  using non-expert mode 🤔

I should add that if you are using motion re-projection in VR with a base locked  FPS of 30 doubled up to 60, then that is the same as an FPS cap of 30 from the app's perspective. In that case, your FPS won't go above 30 so setting your target FPS to 40 will not allow TLOD automation to work and hence the warning is valid.

On my setup, I use motion projection with my Quest 3 with a base FPS of 40, which doubles up to 80 FPS in the headset, and so I use FPS Cap mode with a target FPS of 40 and it all works well.

6 minutes ago, Reset XPDR said:

I should add that if you are using motion re-projection in VR with a base locked  FPS of 30 doubled up to 60, then that is the same as an FPS cap of 30 from the app's perspective. In that case, your FPS won't go above 30 so setting your target FPS to 40 will not allow TLOD automation to work and hence the warning is valid.

On my setup, I use motion projection with my Quest 3 with a base FPS of 40, which doubles up to 80 FPS in the headset, and so I use FPS Cap mode with a target FPS of 40 and it all works well.

Ok that's fine but I have no reprojection going on, but that has triggered a memory of my Pico 3 getting "stuck" at half-rate (45/46fps) in racing sims whereby even though 90 was easily achievable it wouldn't budge out of that half-rate mode. I remember going into detail about it trying to figure out why it would do that months ago, but never eventually finding out why (My Reverb G1/G2 before it never did that).

So perhaps that is what AutoFPS thinks is going on with the Cap when I haven't manually set one, either way I've clicked No on the pop up box so I won't see that again but I just hope that doesn't hinder AutoFPS from doing it's (magnificent!) job in those moments 🙂most of the time it's running as expected.

It seems like the taxiway lines are only being drawn out a little ways before me when taxiing and the popping in as I approach. Is there a way to fix this? I just use IFR and auto settings in the app.

4 hours ago, Evan said:

It seems like the taxiway lines are only being drawn out a little ways before me when taxiing and the popping in as I approach. Is there a way to fix this? I just use IFR and auto settings in the app.

This something I remarked too, but only lines going straight in front of me.

Lines going left or right do not have that issue.

 

May i ask a question: 
I use the Cap option, with FG on limited to 60/sec. Works like charm. But sometimes, AutoFPS tries to increase the TLOD, framerate drops a little bit, but TLOD is lowered more than it has been before. For example, i am at FL400 over Germany, which seems to be very demanding on TLOD. So I am very happy seeing a TLOD of 275 or even 300. Then, AutoFPS starts a new seeking phase, but after increasing just a little bit, 280 or 305, it decreases instantly to 225 or 250. So I end up with less TLOD than before. It makes sense to lower TLOD significantly to stabilize frames in demanding situations, but is there a way to recover to the level before? Or to decrease in smaller steps?

Thank you so much!

Matthias

Edited August 30, 2025Aug 30 by ankh21