[Bug Report] After recent updates, Vulkan + VSync = slowdown (Solved)

[Gr3g]

Up until about two weeks ago, I wasn't experiencing any issues but now using VSync with Vulkan results in my framerate being effectively locked to 40 when geometry is on-screen. This issue persists for me at least in 1.7.4854 but is not present in 1.7.4667.

[jesalvein]

In order to help you further with your problem, please make sure the following are all provided.

• Your hardware specs - CPU, Graphics Card, Memory, Operating System.
  
• The version of PCSX2 you are using.
  
• Any non default settings you are using, such as speed hacks or presets.
  
• Your GSdx graphics settings (a picture of the settings dialog is preferred)
  
• What games you are trying to play and if you are playing them from ISO or DVD.
  

Thank You.

[Gr3g]

Specs:
AMD Ryzen 5 5600 (Overclocked and undervolted)
AMD 6800 XT (Overclocked and undervolted)
16GB RAM at 3600MHz
Windows 10

Versions Tested:
Every Nightly build since about 10 days ago. (Issue present)
1.7.4667 Nightly (Issue not present)

Settings: 
Resolution - 6x Native
All others default.
         

Games Tested:
Armored Core 2: Another Age (DVD)
Armored Core 3 (DVD)
Silent Line Armored Core (DVD and ISO)
Gungriffon Blaze (DVD) 
(Most likely occurs with any game)

Misc:
Seems to only occur when in Fullscreen.

[Gr3g]

I would like to confirm that the issue still persists in build 1.7.4878. I've reverted to 1.7.4690 with no issues.

[refraction]

you guys are going to need to narrow it down better than 200 builds if you want us to look at it.

[Gr3g]

Is that really necessary?

[envisaged0ne]

If you want them to narrow down when the bug occurred you're going to have to help them out. You don't have to check every single one. Just check a few until you find one that has the bug, then backtrack a few revisions until you narrow down the correct one. I've done it before and honestly it didn't take me very long

[MrWizard]

You can binary sort this within like 8 tests

1) You know top and bottom revision...
2) Pick the pcsx2 version roughly in the middle... ie 1.7.4780 in your case.
3) If the bug occurs, the issue is in versions lower if it doesn't occur, it's in versions numbered higher than you picked
4) Repeat steps 1-3 cutting the range into half every time.

[Gr3g]

I discovered that enabling no-interlacing patches solves this issue.

[jesalvein]

Ok. Non-existent bug, then