the camera/aircraft – need to know exactly where they are at the moment the frame will get displayed, otherwise you might have smooth frames but non-smooth motion). Well, the whole vsync topic is indeed much more complex than one would think (we did not even talk about the physics calculations: Before the graphics rendering starts, all objects – esp. So, IMHO, though it makes the fps numbers look worse, this is one of the best improvements regarding smoothness since Vulkan started. But, so, with tearing.īTW, as I already wrote on last b15 thread, it also (on my system) works perfectly together with g-sync/freesync. When XP goes to the background, probably vsync gets deactivated and so you get the best possible frame rate, regardless of monitor refresh. And AFAIK triple buffering would not help, because in the end the GPU still has to distribute 45 (or whatever) frames on 60 monitor refresh cycles. (All above given, you have a 60 Hz monitor and vsync activated.) A typical “I have a micro stutter once every second”. 59 fps would be 59 frames for 1 refresh cycle and then 1 frame for 2 cycles. 45 fps, because 45 fps could only be achieved by showing 1 frame for 1 monitor refresh and next frame for 2 refresh cycles and next again for 1 refresh cycle and so on. Again, this was not an issue in beta 13 (I still have a copy of it).Ĭorrect me anybody if I’m wrong, but I think going down to 30 fps as long as 60 fps can’t be maintained, is not a bug, but the best solution.Ĭonstant 30 fps are much smoother than e.g. My Nvidia vsync is set to ON (full) with triple buffering as always, but it seems to be the checkbox in X-Plane that triggers the issue. I later found after my initial bug report (with multiple ETW traces attached) that if I go into the graphics menu and deselect the vsync checkbox, the sim FPS behaved consistently well but in the sim and out of the sim at all viewing angles. To add to this oddity, if I alt-tabbed to a small window such as the task manager with X-Plane still showing in the background, the frames shot up to 55-60.
#X PLANE 11 MAC BOOK PRO 15 INCH 2017 FULL#
I found an interesting issue that may be related to the vsync checkbox while flying in full screen mode, but I wasn’t sure if there’s some new way I should set things? … I had recently reported that after beta 13, I notice in b14, 15, and 16 my FPS would go from 60 on the airport ramp down to a fixed 30 when viewed at certain angles from above, but oddly the cpu and gpu readings in the output would not change for the worse. We are also drowning in performance bug reports at this point we don’t have bandwidth to triage additional ones right now. Given that we have two performance issues fully diagnosed but not fixed, there’s no point in collecting more data – the two existing problems would mask other ones. (XPD-10898)įrom what we can tell, a huge percentage of the blog comment complaints about performance are all XPD-10898.Īt this point, with beta 16, we do not want any additional performance bug reports. The cause is slower draw time when we draw 3-d scenery out of system memory while we wait for the DMA to VRAM to finish. If your frame rate is smooth and good when flying and then temporarily slows down only when your view changes as lot (e.g circling, turning your head, etc.), that’s this bug.
#X PLANE 11 MAC BOOK PRO 15 INCH 2017 WINDOWS#
X-Plane 11.50 beta 15 made CPU performance worse on AMD cards on Windows during panel drawing – the same bugs that caused the incorrect plugin drawing hit performance as well.I accidentally turned off optimized off-screen clouds. X-Plane 11.50 beta 14 made cloud performance significantly worse on the GPU.Sidney and I spent a bunch of time over the last week looking at performance. Full notes here.Īt this point we think we are good in terms of plugin compatibility APIs – if your add-on still acts funny in beta 16, please let us know ASAP. Probably the most important bug fix is the set of fixes for broken plugin drawing–this affected SkyMaxx Pro and a number of add-ons in pop-out windows.
0 kommentar(er)
