"Failed to start game -- App already running"

[S Flynn]

I'm still getting this error whenever I play.

It's like the game starts twice.

It doesn't stop me from playing or anything.

Do the code monkeys know about this? I'm guessing it isn't a good thing.

[HarrierDuBois]

Originally posted by Myself9:

Do the code monkeys know about this?

I think so.

[Mayena]

I keep getting the same error, but only when I start in -vr mode. Sometimes it starts, most times it wont, really annoying. I keep reading on this forum that it's fixed for ages, but it isn't for me.

[HarrierDuBois]

Originally posted by e.wallet:

I keep getting the same error, but only when I start in -vr mode. Sometimes it starts, most times it wont, really annoying. I keep reading on this forum that it's fixed for ages, but it isn't for me.

Sorry for my ignorance, what is -vr mode?

[Umbreawesome]

Um... Seriously? You guys have never had this problem with another game? The fix is simple use your task manager to shut down all steam processes then restart steam. If the problem persists restart your computer its a steam issue not a game issue.

[Injun]

Originally posted by cw53543:

Um... Seriously? You guys have never had this problem with another game? The fix is simple use your task manager to shut down all steam processes then restart steam. If the problem persists restart your computer its a steam issue not a game issue.

Ummm... NO, I have not.

And what it ACTUALLY means is that.R3E has a memory leak or other such issue that would cause parts of it to remain running in RAM after shutdown.

Force shutting down Steam with Task Manager effectively ends all processes that are tied to it, Yes. But that is neither workaround nor solution because you still don't know what the cause is. For those who can play from the same machine they host the server on (I am NOT one who can.) having to shut down Steam isn't viable.

Mine does the same thing... Start the game THE 2nd TIME, get the "Already Running" notice, click "OK" Game starts. No problems. I NEVER get that message starting up Raceroom first thing after booting my PC. Still, no problem starting at either time.

Where this becomes a problem is when you try to start up Dedicated Server AFTER running a few laps on your favorite track. The same thing that is throwing the "already running" notice doesn't allow the Dedicated Server front end to load.

So, if you don't mind, please explain in detail exactly how you came to your conclusion that this is a Steam issue when the only products affected by it are those of Sector 3. Why, because you manhandled Steam and it gave you a result that was acceptable to perhaps, only you? That's rather like pounding carpet tacks with a 20 lb sledgehammer. I think I want Sector 3's programmers or someone who at least knows how computers and programs work together better than I do to have a look-see and maybe fix it.

Instead of hiding issues by making them "magically go away" forcibly such as with Task Manager's end task feature, how about dropping a word here like the OP did and getting reliable sources and DEV's actively seeking both answers and solutions?

[darrellb]

I get this error every time if I start the game from the "Play" button. If I double click on RRE in the list to the left instead I never get this error. I use the Detail View in the installed games library btw.

[Umbreawesome]

How I came to my conclusion is that this problem happens with other games as well not just Sector 3's and everytime it happens I just force shutdown steam and it handles the problem and I'm able to play the game again. I have had the problem a few times with War thunder, TF2, Dirty Bomb, and a few others already.

[harryorlsen]

Thats a relict from race07 - hope they will fix this one time ;)

[Injun]

Originally posted by cw53543:

How I came to my conclusion is that this problem happens with other games as well not just Sector 3's and everytime it happens I just force shutdown steam and it handles the problem and I'm able to play the game again. I have had the problem a few times with War thunder, TF2, Dirty Bomb, and a few others already.

Here, let me explain to you the purpose of a Feedback and Support Forum for a W.I.P. Game. Maybe then you'll see where your suggestion is in conflict with a smootly running application or game.

1) To report any issues encountered to the Dev's so they can investigate (recreate the issue) and then implement changes to rectify the issue (updates/patches).

2) To help users encountering technical difficulties resolve their issues. Maybe it's a PC configuration issue maybe it's the software. HERE is where that gets figured out.

3) To create a 2 way venue of communication between user and developer. Also to allow Developers to deliver News and Annoucements in a timely fashion.


Nowhere in there do you see anything about advising users to implement any action that would hide, or ignore an issue. That is exactly what your "solution" (term used extremely loosely; borderline sarcastic, even...) does is ignore, and hide the issue. If this works for you, GREAT! But don't come here and belittle others for using this resource for it's intended purpose. If you don't want to be part of the real solution process that's your choice. I personally do not want people not reporting the small, annoying things like the "Already Running" thing.

What else down the road will be affected by not fixing this? This software needs to work with a brand new operating system that rolls out to users in less than 3 weeks. If it's throwing errors now, what will be the effect of those errors compounded with the new OS? I don't know. You don't know.

So, lets not offer suggestions telling people to ignore/hide the errors they encounter, Hmmm? You need to re-read the original post below; specifically the part I underlined and made bold.

Myself9

"Failed to start game -- App already running"
I'm still getting this error whenever I play.

It's like the game starts twice.

It doesn't stop me from playing or anything.

Do the code monkeys know about this? I'm guessing it isn't a good thing.

[Umbreawesome]

Originally posted by ♥♥♥♥♥:

Originally posted by cw53543:

How I came to my conclusion is that this problem happens with other games as well not just Sector 3's and everytime it happens I just force shutdown steam and it handles the problem and I'm able to play the game again. I have had the problem a few times with War thunder, TF2, Dirty Bomb, and a few others already.

Here, let me explain to you the purpose of a Feedback and Support Forum for a W.I.P. Game. Maybe then you'll see where your suggestion is in conflict with a smootly running application or game.

1) To report any issues encountered to the Dev's so they can investigate (recreate the issue) and then implement changes to rectify the issue (updates/patches).

2) To help users encountering technical difficulties resolve their issues. Maybe it's a PC configuration issue maybe it's the software. HERE is where that gets figured out.

3) To create a 2 way venue of communication between user and developer. Also to allow Developers to deliver News and Annoucements in a timely fashion.


Nowhere in there do you see anything about advising users to implement any action that would hide, or ignore an issue. That is exactly what your "solution" (term used extremely loosely; borderline sarcastic, even...) does is ignore, and hide the issue. If this works for you, GREAT! But don't come here and belittle others for using this resource for it's intended purpose. If you don't want to be part of the real solution process that's your choice. I personally do not want people not reporting the small, annoying things like the "Already Running" thing.

What else down the road will be affected by not fixing this? This software needs to work with a brand new operating system that rolls out to users in less than 3 weeks. If it's throwing errors now, what will be the effect of those errors compounded with the new OS? I don't know. You don't know.

So, lets not offer suggestions telling people to ignore/hide the errors they encounter, Hmmm? You need to re-read the original post below; specifically the part I underlined and made bold.

Myself9

"Failed to start game -- App already running"
I'm still getting this error whenever I play.

It's like the game starts twice.

It doesn't stop me from playing or anything.

Do the code monkeys know about this? I'm guessing it isn't a good thing.

My point is I assume my computers the problem because it is relitively low end so I'm dealing with the problem from a different thought process than you. This is why I mentioned this is not the only game this problem happens in and steam is used to launch the game.

It is STEAM saying the app is already running not the game saying the game is already running. My point is right there its either on the steam or the computer side it doesn't just happen because of any 1 particular game. I listed multiple.

[Injun]

My whole point is that using Task Manager to kill processes that DO NOT AFFECT whether or not a program (game in this case) starts up is overkill. The software WORKS even though Steam's throwing an error. There is NO NEED to snipe processes. KEY PHRASE "DOESN"T STOP ME FROM PLAYING!" Mind you that if the software DIDN'T start, I would be agreeing with you about using Task Manager and End Task. But that's not the case here and now, is it?

[HarrierDuBois]

Please take it easy everyone.

There could be something in the game (and the others mentioned) causing steam to act the way it does. There's definitely something wrong with the dedi tool, seeing that it doesn't load after the game has been running before launching the dedi app.

I for one have never experienced this issue and it might just be on the steam client, it not handling the process the way it's meant to because of some corrupted/outdated files. Restarting steam or the PC might sometimes help sort such things, as might refreshing steams files: https://support.steampowered.com/kb_article.php?ref=3134-TIAL-4638&l=english

It's worth to give it a shot and report back if it helped.

[Injun]

I've said my piece. If cw54543 doesn't see the validity in the points I make it's because he doesn't want to. Or, perhaps he just likes to argue. There is a usefulness in his suggestion just not in this context. In his original post he is condescending and rude. If I was the OP and it was my first forum post looking for help I wouldn't come back. That certainly is not the atmosphere needed.

[HarrierDuBois]

Originally posted by ♥♥♥♥♥:

And what it ACTUALLY means is that.R3E has a memory leak or other such issue that would cause parts of it to remain running in RAM after shutdown.

I think you're right in saying this but couldn't that also be caused by the steam client, not the game itself? Really just asking as I'm not that familiar with how steam handles such processes actually.

[Umbreawesome]

Your point is valid. I get that and I understand any anger twords me but what I was trying to establish is that steam may be more at fault than the game itself.