![]() ![]() If both values are far appart from each other, you might be missing on some possible quality improvements as either your CPU or GPU is being underutilized.įor example if your app CPU is much lower than app GPU, you can try increasing LOD, as long as it doesn’t also increase the app GPU when you do so.Īnother example, if your app GPU is much lower than app CPU, you should try increasing resolution. ![]() To reduce app CPU, you will need to change game settings related to geometry. With OpenXR Toolkit settings, you will only be able to lower the app GPU, by using upscaling to reduce the rendering resolution or using foveated rendering. When it comes to graphics, the app CPU is mostly driven by the geometry (level of detail, complexity of the scene) while app GPU is mostly driven by your resolution and the amount of effects applied by the game. With motion reprojection, you will also want to account for extra overhead (so instead of 1-2ms below target, you want more like 4-6ms). For a third (30 Hz), the value will be 33,333us. If you are using motion reprojection to target for example half of that (45 Hz), then in this case you will want to stay below 22,222us. This is however not achievable in MSFS due to how intensive the game is. In reality, you need to account for other overheads, so even 11.111ms will not get you 90 FPS, you’ll need something like 9-10ms instead. They are ideally below 11,111us = 11ms so you can achieve 90 FPS (assuming the native refresh rate of your headset display is 90 Hz, since 1/90 = 0.011111). You want they to be as low as possible, since lower frame time will lead to higher framerate. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |