Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
I think so.
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?
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.
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.
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.