Maybe by reducing the graphics to get the FPS to match the display refresh rate, that’s when the “limited by GPU” to stop showing since now it has enough headroom to render frames at the same rate as the display. So I don’t think it’s a bottleneck, that’s just how it is. If people are not having CPU bottleneck, everyone would be getting “Limited by GPU” regardless.
So since most displays are 60 Hz, but for flight simming 30 fps is an acceptable frame rate. That’s just how much that the GPU can do for that graphics settings. That’s when it’s technically “struggling” but while the reality is that it’s actually not. But based on your graphics settings and details, if the GPU is rendering too many high detail and it can’t deliver 60 FPS. Either way, no matter how well or how bad your GPU is rendering the frames, if you have a 60 Hz display, the GPU would try to render 60 FPS to Vsync the display (if it’s turned on). It’s either the GPU can render everything it needs to based on your details and graphics settings, or if it’s struggling. But now the amount of details and quality that needs to be rendered is dependant on the GPU itself.
Thus this shows as “Limited by Mainthread”īut when the CPU is fully utilised, it has processed everything that it needs to process and it’s ready for the GPU to render on the display. If your CPU is underutilised, it can’t process as much data as it needs to, so by the time it’s delivering those assets into the GPU to render, the GPU is also underutilised making you getting low FPS on the display. Well, someone can correct me if I’m wrong, but from what I’m experiencing is that the data flows from CPU into GPU then into your Display. But I’m guessing everyone will have them as long as it’s under the monitor refresh rateĬan you explain what you mean by that? I thought Limited by GPU or Limited by Main Thread wasĭependent on the relative GPU/CPU strength.
0 kommentar(er)
