0neGal / viper

Launcher+Updater for TF|2 Northstar

Home Page:https://0negal.github.io/viper

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

bug: Viper detects game as running when it's not

JustWantToFixViper opened this issue · comments

So I was using NorthStar Viper with no issues previously. I have opened my game with steam prior, but its no longer accepting the filepath for some reason. I have tried switching it back to the EA path now as well and it is having the same issue. I click launch it loads for a while and then eventually just says 'Change Game Path'. I am not sure what I have done because I haven't had any updates other than Nvidia one that I know of. I certainly haven't deleted the game or anything as I can still open it through Steam or EA app. Any tips or help would be greatly appreciated thank you.

commented

Where are you seeing this "Change Game Path" at? The only place text like that should be in the Viper tab, in the sidebar. And it's just the button you use to change what folder Viper looks in when updating Northstar and alike, it's not a message telling you that something gone wrong with the game path, and that you need to change it.

But I understand the confusion if that's the problem, as others have confused it in the past, and it's something that'll likely be changed or moved to somewhere less confusing.

If that isn't the place, then please do take a screenshot if you're able to.

commented

Hmm, I have seen reports of some people saying Viper thinks the game is running when it actually isn't. Just to confirm, the launch button is saying "Launching..." or "Running...", just to make sure I get this right.

If possible, next time this happens, could you check and see if any programs with a Titanfall, NorthstarLauncher, Origin or EA Desktop logo is in the task manager whilst it is happening, and which one or more of them is running. More precisely the names of the programs would be: Titanfall2.exe, NorthstarLauncher.exe, Origin.exe and EADesktop.exe all respectively...

Further, when it does this, does it fix itself when restarting Viper or does it simply keep doing it?

commented

I honestly don't know, again, I've seen reports of Viper thinking the game is running when it's not, and only fixing itself after a restart, why this happens I do not currently know, but I am still trying to investigate and figure it out.

But am glad it seemed to have fixed itself in your case!

I honestly don't know, again, I've seen reports of Viper thinking the game is running when it's not, and only fixing itself after a restart, why this happens I do not currently know, but I am still trying to investigate and figure it out.

I don't know the cause yet either but I do know that it comes from some process lingering around sometimes after Northstar crashes(?). As that means that a process called NorthstarLauncher.exe is still running, Viper will naturally display the process as running. Of course that also means that restarting the PC naturally fixes this.

The way I "fixed" the issue in FlightCore is that I added a "Kill Northstar process" button in the Repair View that kills the running process and then I just guide the user to that button in the rare cases someone makes a ticket.

You could probably also just have it so that with Northstar running and you hovering the "Play" button it turns into "Kill running Northstar process".

commented

I have been meaning to add some buttons that perform various debugging tasks and alike in the settings page anyway. So I'll likely look into adding a similar button.

I presume it's currently, completely unknown what causes the lingering process to exist in the first place?

I presume it's currently, completely unknown what causes the lingering process to exist in the first place?

Currently, yes. Haven't found a way to reproduce yet so naturally hard to find the cause ^^

I presume it's currently, completely unknown what causes the lingering process to exist in the first place?

Currently, yes. Haven't found a way to reproduce yet so naturally hard to find the cause ^^

It has also been happening to me with my Northstar and Viper installation on my Windows machines. I have noticed that it only occurs when the EA application has not been executed before opening Titanfall through Viper. In the cases where I haven't opened the EA app before running the game, Northstarlauncher.exe appears as a subprocess of Viper, and the game becomes frozen, and I cannot see its screen.