vk: Restructure present mechanism

[kd-11]

• Removes frame submission control from the application and relies on the driver to do it automatically for us. This avoids the NVIDIA fullscreen deadlock issue entirely and also improves framepacing a lot.
• Remove a lot of no-longer-necessary code from the window classes. This includes the win32 hooks and the renderer-side window management polling code. May slightly improve performance due to less overhead.
• Implements frame management when window is minimized, allowing resources to be released properly.

Fixes #5351

[Whatcookie]

You can remove the log message that I added the other day in VKhelpers.h at line 440 now.
Perfomance is good in amdvlk and window resizing still works.

Edit: Thanks as well for the framepacing fix, 60hz games feel dramatically smoother on my 120hz monitor

[vsub]

Now this is really good commit,not only fixes the #5351 which was bothering a lot of people but it also fixes #6043 #5508 and #5202

Edit:And forgot to mention,fullscreen<=>window switching is MUCH faster and smoother

[13xforever]

Yakuza 4 frame time pacing improvements

[MsDarkLow]

Completely fixes the microstutering in Yakuza Games. (No more 15fps at 1% and 0.1%!)

Yakuza Kenzan:
Master

PR

[blackecos]

Thanks for this, will this come to the official builds?

[dio-gh]

@blackecos It's merged, so it's already in the official build.

[blackecos]

@dio-gh
Mhm then It doesnt work for me in the official build.
With 0.0.6-8197.3e620f14 Alpha it works fine.
With the latest official build I still get crashes in fullscreen mode ;/

Just to be honest Im not sure thats the same thing here... I come from a link from this page:
#5351
Github confuse me all time... <.<

[dio-gh]

With 0.0.6-8197.3e620f14 Alpha it works fine.

That's a build from before this PR was merged. This changeset is in master since 0.0.6-8204. This PR fixed a long-standing issue of people getting crashes in fullscreen when using nvidia hardware. If you say things were working fine in that quoted build (as in, you didn't get crashes), then you're experiencing a different issue.

[blackecos]

Then should I go with the latest build -> wait for a crash and post some logs or something? x(

[13xforever]

This issue has been confirmed to be fixed. Your issue is most likely unrelated at all. Stop spamming github please, ask in Discord if you need further help.

[dio-gh]

@blackecos I meant that what you are saying logically doesn't check out, and thus you're probably experiencing a different issue. By default, this would mean that you could/should open a new, separate issue, and post logs and issue description there. However, it'd be preferable if you visited our Discord server first as 13x says, and clarified that it's indeed a real issue, not a settings mishap or something.