You have ARB_buffer_storage.
Here's how it works. It lists any extensions you don't have. Pinned_Memory is on there, as expected, so the verbosity is set correctly. If you didn't have ARB_buffer_storage it would be listed in that file.
From a bunch of testing before and after the change, BufferStorage is comparable to the VSH's performance in most scenarios. I'm guessing that Metroid Prime just does something that the VSH skipped or was a little bit faster at.
drhycodan:
Stop bitching here about your performance. We all try to get the best experience for everyone and some changes will speed up, others will slow down. In the end, I think, dolphin now runs faster than 3.5. The usual way to answer is "Buy better hardware" but you seem to be rich enough to already have the best available. In fact, no dev has such an equipment - be happy and stop bothering us.
Your log prooves that ARB_buffer_storage is available and used (like I've said before), so I guess the remaining "slowdown" is because of the syncing (which is also skipped in VSH). As this seems only to happen on gtx 780 + titan. It's fine to note this _once_, but why are you crying for having one of the expensivest gpu available?
Do you want me to debug this issue? I just need such a gpu. Do you want to donate one?
Do you know, dolphin is open source? Did you contribute to the project at all but to pollute our forum?
I know that the VSH removal also affects (all) tesla based gpu and I feel sympathy for them as there are lots of people who can't purchase a new one.
But for them I've already reimplemented the VSH:
https://code.google.com/p/dolphin-emu/source/detail?r=bfd0b7275e8dee8a72563a1b897e7e53b09c9076 (But they also have to compile on their own)
Just start looking how to improve dolphin for yourself and stop crying because we don't do what you want.
Do you know that we don't develop dolphin for the users to play games? We don't benfit if someone play games, we only benefit from users wanting to improve dolphin.
So if you just want to play games, go away and use your wii - or at least stop borthering us.
Else, have fun forking dolphin.
drhycodon: Degasus worked on this with me on IRC, and the devs realized Windows may be doing something stupid. See if this build helps you out. You may also have to disable vsync in NVIDIA's control panel to get performance back to normal until another Windows quirk is fixed.
http://dl.dolphin-emu.org/wips/degasus-dolphin-master-4.0-720+-x64.7z
(01-28-2014, 10:16 PM)JMC47 Wrote: [ -> ]drhycodon: Degasus worked on this with me on IRC, and the devs realized Windows may be doing something stupid. See if this build helps you out. You may also have to disable vsync in NVIDIA's control panel to get performance back to normal until another Windows quirk is fixed.
http://dl.dolphin-emu.org/wips/degasus-dolphin-master-4.0-720+-x64.7z
I was going to post about that a while back but I figured it was something on my end. It's true though the only way for me to get my speed back is to manually disable vsync in the control panel. I'll try this build.
EDIT: I was using 4.0-712 with Paper Mario: The Thousand Year Door BTW
EDIT 2: Just tried the build and got the same result except it was slower. Before (in 4.0-712) it capped at 130 FPS. In that build it capped at 111 FPS
Oh, and I still needed to disable vsync in the NVIDIA Control Panel
Hope this helps in one way or another
Well, sorry for causing you devs so much "trouble" as I was just trying to do my part in helping with the project. Everyone is saying they're getting the same speed with buffer_storage as with VSH, but here it seems buffer_storage has really no effect as I was getting the exact same speed I get with VSH off. So it seems there is an issue with the GTX 780/Titan afterall.
Regardless of right or wrong, the incessant way of making tons of threads + repeatedly berating the build didn't help things. What helps is actual performance metrics, finding the build that causes the issue, making well filled out issue reports that explain how to reproduce, etc.
Just bitching that something is wrong ends up with situations like this. A ton of issues pile up to the point where it's hard to pin down exactly what's wrong, and a bunch of people have to do some digging. This is definitely a lesson for both sides, I had Metroid Prime on my computer, and there were builds before the vsync glitch that I could have checked and likely confirmed what was going on. I'm just glad the positive outcome was fixing the problem and restoring things to the way they were. Why Metroid Prime and Twilight Princess were hit so hard is beyond me.
>Why Metroid Prime and Twilight Princess were hit so hard is beyond me.
Because they have tons of shit to upload to the GPU, naturally.
Yes, thank you JMC47 and degasus and whoever else helped to fix this issue. The performance seems to be back to normal now =)
I too was having this issue, but didn't feel like piling on. Glad it's been addressed. I'll test it later when I'm home.