X-Plane 11.32 continues the evolution of the desktop version of X-Plane. including the Aerosoft CRJ-200 and Daytona Beach and Zurich airports from Aerosoft But assuming we were to share access to Vulkan by SDK means, we would also share access to our async allocation engine, just so we can keep track of plugin allocations.NOW Available for a limited time only: "X-Plane special bundle. Plugins going in and doing their own side allocations would sabotage any of that. Going forward, all memory allocations are async in nature in X-Plane, because of memory pressure and page down activity, we might decide to throttle allocations. VMA sharing will most likely not happen, we have our own allocation handler on top of that. We don't want to be in a situation where we find out that we are inefficient, but have to remain so until the rest of the days because of compatibility. We don't want to opt into capabilities for resources, or guarantee certain image layouts/queue ownerships/queue presence/render passes/execution ordering, because that would mean we have less chance to modify things later on. But I can say that, going forward, we'll be extremely careful what internal resources we are going to share with third parties. Now we are getting into territory where I'll get my fingers chopped off. I just wanted to make it clear for anyone else who just tuned in) (I know you know, given your reply to him. It's still doing the same work, but we can talk to it more efficiently. As /u/Cidoloco implied, your GPU doesn't magically get faster with Vulkan vs OpenGL. Note that in this case in both tests, the system was not GPU bound! This is important, all of the difference comes from spending less time on the CPU. As you can see, AMD and Nvidia performance is more or less on par with Vulkan, and night and day difference on OpenGL. So pardon the compression artifacts.Īnyways, the system is an i7-6700k, 32Gb RAM and it was running either an RX480 or GTX 980Ti. Unfortunately I lost the original screenshot, so I had to take it from a tweet I posted a while ago. Unfortunately when I moved I killed my RX480, so I don't have any recent numbers coming from the same system, but here are some numbers we showed at FSExpo: Yes, in my tests, the performance is pretty even given the same system but with an Nvidia vs AMD GPU. If you've got questions about X-Plane and Vulkan or Metal, let me know (but don't ask questions that marketing would cut me a boo boo for if I answered them) Those are huuuge differences.Īnyways, that's my 2am rambling on a week night. 10 FPS more at 60 FPS is a mere 2ms of improvements, but going from 10 FPS to 20 FPS is 50ms! In both cases the FPS improved by the same 10 FPS, but in one case it took making a frame faster by 50ms whereas in the other it was "just" 2ms. So statements like "double FPS" or "10 FPS" more are meaningless. On the other hand, going from 60 to 120 FPS only requires shaving off 8ms of frame time! So to go from 30 to 60 FPS, you'll need to shave off 16ms of frame time. To double the FPS and get to 60 FPS, you'll need a frame time of 1/60 = 0.016s or 16ms. So for example, if you currently have 30 FPS, that means that a frame will take 1/30 = 0.033s or 33ms.
To double your FPS, you have to halve the time it takes to render a frame. What really matters is how long it takes to render a frame.
X PLANE 10 VS 11 PLUS
Plus FPS is a terrible way to measure performance (and I say that despite being the creator of the charts that OP posted). Of course the other big goal is to have a viable platform for future rendering engine work and improvements, that all require a modern platform to work on.
Plus, the usual disclaimer, the big goal of Vulkan is to get rid of all stutters and make the FPS stable, no matter whether it's 30 or 90.
X PLANE 10 VS 11 DRIVER
It really depends on your system and whether you are currently CPU or GPU bound, and what driver stack you are running. It's 2am here and I'm in no way in the position to write a long post, but I'd urge people not to get hung up on the 10 FPS in the title.
Self-promotion is limited to the weekly self-promotion thread onlyĪccounts younger than 12 hours are now permitted to post both comments and submissions
0 kommentar(er)
