-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Config gets erased when I bootup Viper #228
Comments
I'll add that titanfall is installed on an SSD |
Huh, that's weird, does this happen every time you bootup Viper? Is there at any point where Viper is functioning as intended? Is the gamepath on a separate drive from where Windows is installed? That error should only popup if a gamepath that was previously valid, becomes invalid, either because a folder was renamed, a disk isn't mounted/plugged in, or similar, but it shouldn't erase the entire config file... |
Happens everytime, I haven't even seen any of the menus. I moved it to my F drive, which is my external hard drive. Also, It happens whenever I add my gamepath to my config gile. |
When you click "Ok" does it just close? Can you try running Viper through PowerShell or command prompt, simply drag the |
And yes, it closes when I hit ok |
My slashes were the wrong direction... |
Wait, what was the error? Did you manually set the gamepath and have it use forward slashes? |
Yes, and after restarting my pc, it went back to having no game path |
Also, Northstar is crashes when I boot it up |
nslog2024-04-10 22-15-46.txt |
Can you try running this in PowerShell and tell me what it outputs: Get-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Respawn\Titanfall2\ -Name "Install Dir"
Does it work fine when you run |
When I add the correct gamepath to the config file, and bootup Viper, it gives me the error in the screenshot, and reduces the config file to just
{}
.The text was updated successfully, but these errors were encountered: