A workaround for this has been found by @Steve_Clogg_PACK_LEA who secures legendary status with me. If you run OBS (it doesn’t have to be actually doing anything!) then there’s no stutter and no flicker at any frame rate. Zwift still need to fix this issue so that OBS isn’t required(!), but it’s an alternative to running the old launcher like before.
Also explains why various people are saying they don’t see any of these problems, as does the fact that the same workaround can be acheived by installing and running GeForce Experience. Which I suspect a lot of people do, for example if the first bit of advice they see online is to ensure they’re running the latest Nvidia drivers so update manually (which isn’t necessary at all).
@shooj for info
I’m gonna hazard a guess that ZHQ employees all have OBS installed on their work machines under Group Policy, or more likely they have the full GeForce Experience package (yuck) installed on whatever systems they code/debug/test on. Perhaps both, or maybe some other screen capture/overlay software to help them work remotely and share stuff. But as a result, whatever’s wrong with the 1.0.51 and 1.0.52 launchers/installers has never shown up as an issue.
I’ve never installed any of these bits of software, on any rig I’ve built for Zwift. So that’s why it’s not been masked for me.
What a friggin hero - thanks @Steve_Clogg_PACK_LEA !!!
This didn’t affect me but I know how much grief it caused people so thanks @Steve_Clogg_PACK_LEA for this
Could someone from zwift try it without these installed and see fi they can get to the source of the issue?
My guess is, knowing zwift, there is a workaround and that’ll be the last we hear of it.
Hopefully it’s an easy fix.
The other thing about this though is it raises questions about what else the devs have installed on their systems when bug testing etc (stop sniggering). Could explain the frequent Bluetooth issues, for example. Clearly they can’t account for the billions of hardware/software combinations out there, but what they can and should be doing is making sure the game runs as expected on a clean install of any given OS, to eliminate the possibility of creating these sort of dependencies.
So, where is the fix posted?
What do i have to do to fix it?
The fix is in the post.
I’ll PM you some step by step instructions. Don’t want to put them on the open thread in case it messes up someone’s system and/or ZHQ don’t want me linking to third party software here.
With HQ’s blessing, here are the steps to follow for anyone getting this stutter and flickering on the current launcher. In case anyone’s not aware of what it is, OBS is a well-respected open source piece of software for streaming/capturing from your PC. The likes of GPLama use it to produce content. You don’t need to actually do anything with it though, just install and set it running.
- This is a workaround, not a permanent fix.
- What follows is clearly not designed as any sort of proper guide for OBS, it’s for the purpose of eliminating these specific issues only.
- OBS is a significantly smaller download than GeForce Experience, and doesn’t require an account. That’s why it’s the better option. Other capturing software may also work, but I can vouch for this one.
- If you’re having any other issues than those described, this probably won’t help.
- Download and install OBS from here, you want the big blue ‘Download Installer’ button: Download | OBS
- Run it when installed, and when the auto-configuration wizard pops up, select ‘I will only be using the virtual camera’, then click Next and finally Apply Settings.
- Now go into File > Settings (in OBS itself), untick ‘Automatically check for updates on startup’ and tick ‘Minimise to system tray when started’, before hitting Apply and OK.
- Minimise OBS.
- Copy the shortcut to OBS into your shell:startup folder.
If you’ve followed the steps correctly, OBS will now run silently at system startup, and Zwift will work properly without the stutter and flickering issues associated with the newer launcher(s).
Even though all indications point at my system not needing this, I’m going to give it a shot. Thank you very much Dave. This is very useful information.
Check to see if you have GeForce Experience installed and running, if so then there’s no need to also do this.
Ok I did solve the flickering for me!
Change the lanchers compatibility mode to “windows 7”.
right click the zwift.exe > properties > compatibility > compatibility mode > change to windows 7
Interesting, I’ll try that out.
I have used the Xbox Game Bar (which Windows somehow installed for me unasked) for screen recording, would that be enough to solve this as well? (Not really asking for myself, my current potato isn’t powerful enough to have these kinds of problems in the first place.)
This didn’t work on my system.
I can’t usually get the Game Bar to recognise Zwift. But I usually disable that so I tried it, didn’t work for me. As you say it’s possible that the capturing element resolves these issues though, where people can use it.
any idea what OBS adds to the equation that fixes the problem?
Not really, no. It’s something to do with how the game and driver sync to the display, that’s all I can offer. As though having some form of capturing software or overlay is creating a reference point, and if that’s not present the driver is unable to sync the frames coming from the game with the tick of the display. Clearly on the previous launchers that reference point wasn’t required.
A few of my regular rides and races later, and the OBS workaround is still working a treat. Lovely and smooth with no flickering, like the game was on the old launchers.
RivaTuner shows the frame rate consistency immediately going crazy when you close OBS. Very weird.
Glad you have found a new workaround that seems to do the trick.
Would be interesting to see why this fixes it but my guess is that as there is a workaround zwift will consider it fixed.