1 hour ago, daztheman70 said:

Hi All,

 

I have recently had to reformat my PC so need to install this again and went back to the start of this thread and the original download link is not working please could someone kindly post the link to download this again please.

 

Thanks

 

Daz

I just checked and the link on the first page does still work, taking you to an redirect webpage which does contain the link to the latest app version here.

I have a question. I hav RTSS Framerate Limit set to 40. In the sim I don't set max framerate but have Dynamic Settings also set to 40. autoFPS is showing a framerate of 45 (this is in VR). So why, if RTSS has a framerate limit set to 40, am I getting 45 fps? In autoFPS I have it set to use RTSS for framerate.

Thanks.

1 hour ago, Rob G said:

I have a question. I hav RTSS Framerate Limit set to 40. In the sim I don't set max framerate but have Dynamic Settings also set to 40. autoFPS is showing a framerate of 45 (this is in VR). So why, if RTSS has a framerate limit set to 40, am I getting 45 fps? In autoFPS I have it set to use RTSS for framerate.

Thanks.

When set to use RTSS as the source, AutoFPS shows the FPS that RTSS is telling it, without alteration for everything except LSFG. If you can decipher it, the display code is simply this:

                if (serviceModel.fpsSourceRTSS)
                {
                    if (serviceModel.LsModeEnabled) return serviceModel.fpsAverage * serviceModel.LsModeMultiplier;
                    else return (float)Math.Round(serviceModel.fpsAverage);
                }

 

This strongly suggests that your RTSS framerate limit is not currently active. You can verify by using another FPS reporting source, such as the FPS overlay with the OpenXRToolkit, the MSFS in-game FPS view or even the the nVidia overlay. With the latter two methods, you will obviously need to lift your headset off to see them.

My recommendation, for VR in particular and is what I do, is to set Max Frame Rate in MSFS to 40 and remove all doubt about whether the frame rate limit is active or not and also for the optimal experience with having Dynamic Settings set to the same value, which in my testing results in expected behaviour when used in conjunction with AutoFPS.

Ok I will switch over. I have one more question. If I didn’t want to limit the maximum frame but just wanted action taken if it got too low, would it be as simple as just removing the max frame rate or is there something else I would have to do. 

7 minutes ago, Rob G said:

Ok I will switch over. I have one more question. If I didn’t want to limit the maximum frame but just wanted action taken if it got too low, would it be as simple as just removing the max frame rate or is there something else I would have to do. 

I am not understanding what you are trying to achieve. Can you please clarify.

29 minutes ago, Reset XPDR said:

I am not understanding what you are trying to achieve. Can you please clarify.

I want to not limit frame rate upper limit but take action if it falls below a certain limit with your tool. So if I can get say 45 for, great, but if it falls below 35, take action. I know your tool works that way but will it work if I don’t set any max framerate in the sim and just set dynamic settings to say 35. 

48 minutes ago, Rob G said:

I want to not limit frame rate upper limit but take action if it falls below a certain limit with your tool. So if I can get say 45 for, great, but if it falls below 35, take action. I know your tool works that way but will it work if I don’t set any max framerate in the sim and just set dynamic settings to say 35. 

OK, in that case don't set MSFS Max Frame Rate and just use Manual Target FPS and set it to say 40 FPS so that it takes action before getting to your Dynamic Settings 35 FPS threshold. Just be aware that with 0.5.0.0-RC that if you are capping frame rate to 45 somewhere, even it is only in your VR headset, and your FPS sits locked at that FPS because performance conditions are so good, then to the app it is indistguishable from a Fixed FPS and it may warn you via changing the background of affected settings to orange to 30 seconds and providing corrective advice in the tooltip. You can just ignore it of course, as it is not a common occurrence, and you probably won't see it in VR anyway, unless you have AutoFPS visible by something like OpenKneeboard. 

In short, yes what you are suggesting should work 😊

Edited April 29Apr 29 by Reset XPDR