Closed GeckoEidechse closed 2 months ago
Sounds a lot like #231 albeit it got fixed, and they're presumable on the latest version. So it's likely just some other error that occurs before the window is created. I would need logs (running Viper in cmd.exe
or powershell.exe
) to diagnose this unfortunately :p
I'll forward
ran it a third time and it had the same output as the second one
@Gecko
Seems to be an issue with parsing the libraryfolders.vdf
file from Steam, while it's fixable without, I wouldn't mind knowing the contents of it (should be at C:\Program Files (x86)\Steam\steamapps\libraryfolders.vdf
), wondering whether it's Viper's fault or the parser. Either way I'll add some more checking to it to fix this.
In the meantime, this could be fixed by either editing the config file (%APPDATA%\viper.json
) manually and setting the path, or simply adding --setpath "<gamepath>"
onto the Viper.exe
command.
Replacing <gamepath>
with the actual gamepath of course.
Seems to still be an issue in 1.12.0
Describe the bug Taken from a recent ticket on Northstar Discord