search

0neGal / viper

Launcher+Updater for TF|2 Northstar
https://0negal.github.io/viper
GNU General Public License v3.0
151 stars 21 forks source link

bug: Error when Titanfall2 is installed on default EA App path. #238

Open GeckoEidechse opened 2 months ago

GeckoEidechse commented 2 months ago

Describe the bug We got a ticket on the Northstar Discord with a user being unable to install Northstar using Viper

Screenshots Taken directly from their Discord ticket

image

Version: ???

Additional Info As hinted by the issue title, the error is most likely caused by Titanfall2 being installed on the default install path. The reason I know this, is cause this the error message the user got when trying to use FlightCore

image (which is triggered by this check)

GeckoEidechse commented 2 months ago

Note that the ticket was since resolved by the user moving their install and switching to FlightCore so not sure if we can collect any additional info from them anymore... ^^"

0neGal commented 2 months ago

Due to not using Windows I had no idea this was even an issue, out of curiosity, why does FlightCore not allow that install path? Is it some permissions issue or?

GeckoEidechse commented 2 months ago

It's a permission issue, yes. I don't know the exact details, whether it's an EA App thing or a Program Files thing but basically the default directory C:\Program Files\EA Games\Titanfall2 is locked to EA App (and admin ofc). So user level stuff has no write access to it. (I assume to prevent programs modifying other programs logic)

Given that that is essentially what we wanna do to install Northstar, the suggested workaround is to move the game files to another location that is user writeable. (Running as admin would also work but is not recommended as it increases the attack surface)

Note that this only affects EA App, as Origin and Steam both install into Program Files (x86) which does not have the same permission requirements.

0neGal commented 2 months ago

Huh, weird, because there's checks in place to check for whether Viper can write into the gamepath, I guess it's only parts of it that's not writable or something...

Might've to adjust it, and possibly change the permission message to also mention that moving the install path may help.

As currently, when it was previously readable, it just tells the user to adjust the folder's permissions or select a different gamepath, and when the error happens on the initial gamepath selection it only does the latter.