kcjc073

Thanks for the correction. I didn't mean to imply that there was anything wrong with the programme or the logic, in fact I'm very pleased with and respect your contribution. It's just that I was so concerned about the consistency of the RTSS Frame time (not fps )that I neglected to mention that the latest version is optimising the system's capabilities and FPS targets. I found a simple solution after trying to adjust the parameters over and over again throughout the day. Please forgive me if English is not my native language.

After I unchecked the expert mode, the TLOD will change as the altitude up and down. the FPS target is set to the same limit as the RTSS. Perfectly smooth without stuttering.

I'm sorry I don't know how to send attachments or graphics. This is during the descent phase of the aircraft, and shows that the TLOD remains high up to about 1500ft altitude. Sometimes it rises, and there is less of a tendency to see the LOD decrease step by step. RTSS litmit 80fps, fps target 78 or 79, expert mode On

Delete Duplicate

Thanks for your reply. The descent rate of autoflight is fixed at 900. I guess it may be a condition of RTSS fixed frame rate setting. I was too focused on the frame time fluctuation, and the stress on the system caused by the complex and dense high rise buildings in New York. Maybe I am too sensitive to numbers, I need to spend time to observe.

After trying several different settings, the final setting at Target FPS 78 FPS Sensitivity 3 is relatively stable. When climbing steadily from 1500ft to 5000ft, the TLOD will reach Max TLOD 400. During the process, the TLOD increase is steady and the screen is smooth. However, when descending, TLOD does not descend smoothly, but tends to stay at a relatively high TLOD until FPS jitter occurs, then it will descend slightly, and it will start adjusting when it encounters stuttering during the continuous descent, and it will not aggressively descend TLOD until the height of about 2000ft triggers the TLOD min priority. The senses will keep the TLOD high until the TLOD min is triggered during the descent, and then drop the TLOD aggressively after it is triggered, and stuttering will be triggered in the middle of the two states.Although the above phenomenon occurs, the latest update has significantly reduced the prominence of the landscape. Environment setting is RTSS fixed at 80FPS AutoFPS Alt Told base 300ft Avg Descent rate 1000ftm TOLD min 100 Max 400 MSFS SU15 beta. Tested C182 fly at 500-5000ft above Manhattan, New York.

AutoFPS software has been upgraded and kept up to date. I use RTSS to lock the FPS at 80, which allows me to fly with almost no stuttering and keep the picture smooth even when looking at different directions. I also flew with the same AutoFPS parameters （Use Expert Options On ,Start flight at 1500ft）at low altitude in New York, and the overall behaviour was stable, although it varied from update to update. The last update showed a strange behaviour, it was easy to go above LOD300 at low altitude, which led to severe stuttering, sometimes going up to LOD400 at low altitude, which is the highest LOD I have set. Update: Adjusted FPS Sensitivity from 5 to 2, didn't select any plus sign or cloud LOD, flew 1480ft circles over Manhattan. LOD seems to be stable around 220, I need to test it more.

I mostly fly GA aircraft at low altitude with the traffic system turned off, and the graphics settings are usually at high to ultra, only slightly lower in the VR system. A lot of optimization has been done on the system including the use of lasso to assign tasks, the main goal is not to increase FPS but to reduce lag and stuttering. Recently I rarely fly in VR environments, I have not been further testing and confirming, this is based on last week's impression（MSFS SU15 beta）.I'm not sure if SSW calculates the frame with reference to the monitor refresh rate. I was under the impression that SSW was something like a frame generation or frame prediction technique, but as I recall SSW calculates the fake frame with reference to the head movement vector. Since the helmet display is the original frame plus the generated frame, RTSS should be based on the original frame, I do not know why change the RTSS limit can affect the helmet's FPS value. If I set a number less than 80FPS, it will be fixed at that value, which conflicts with the concept of MR, so I'm a bit confused. But in the end it was intuition and observation that did the trick, and it worked fine. I use FSR3toDLSS FG technology on my 2D system. To make it easier to manage, I set the same 80FPS limit as the VR environment.The main reason I use a frame limiter similar to RTSS is that it makes the image smoother and reduces jitter and tearing. It has a significant effect in both 2D and 3D systems.

My Quest3 is using VD 80HZ/120HZ resolution Godlike with SSW activated (on my 3080ti). I limit the FPS to 80 with RTSS and set the AutoFPS target FPS to 76. The helmet displays a steady 80FPS and only very rarely lags, everything is smooth and no stutter. AutoFPS and DynamicLOD perform so well on my system that I rarely turn on my 4090 now. Thanks to XPDR's enthusiastic contribution to the community. the simulation system is less stressful, I am grateful for his assistance in every flight.

From a hardware perspective. Improvements in the semiconductor manufacturing process and a reduction in heat generation have contributed to an increase in the signal-to-noise ratio, which may explain the reduction in output picture noise.

After upgrade world update 3 ,I can't stop A5 when landing on water(flag up ,thrust idle). need to shutdown engine to stop, anyone have this issue?