Update 2020-11-15 15:57 CET: An updated version of the installer has just been uploaded.
The new version version of zwift-login will automatically skip the annoying script error message which just recently started to appear in Zwift’s launcher.
Important notice
Starting with this version of zwift-login the installation package has changed in a couple of important ways:
- The default install location is now the folder %AppData%\ZwiftHacks instead of Documents\Zwift\Scripts
- To reduce the risk of false anti-virus alerts, scripts will only be distributed in their original, un-compiled form. Instead, the installer will do the compilation locally at your PC during installation.
Read more about this in About the installer package.
Hi Jesper,
My wife and I both have a Zwift account but are using the same computer.
Is it possible to have 2 Zwift-Login instances like 1 with my credentials and another with hers ?
Interesting 🤔
Yes, just set them up in separate folders. Run the installer twice with different installation targets, or copy your first installation in Explorer. You’ll have to manually create an extra shortcut to launch the instance which doesn’t have a shortcut in the start menu.
Errr…the script error is still there…for me.
I’ll try the multi folder option tomorrow.
The script error appears but should be closed automatically. If not I’ll have to tweak something 😉
Hahaha… in that time I can type in my wife’s credentials no need for a second instance 😋
The compile isn’t working for me. I let the install do the compile for me. I dont get an error but a example how to compile. For me this a sign there is something wrong with the commandline.
in the end there is no zwift-login.exe to start.
https://iili.io/FoOtql.png link to popup
Which version of AutoHotkey do you have?
Its version v1.2.32.00
After some more fiddling around (zwift is not installed in default folder) I could compile the .ahk by right-clicking and choosing compile. Then move the .exe to the right folder.
I’m fixing the installer right now. It should have required at least AutoHotkey version 1.1.33.1 but the version check was wrong.
The new version can be downloaded now.