Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So if you go into your common folder inside the steamapps folder, do you have a game folder for Doom there and does it have files in it as of now ?
If you don't mind, post a screenshot of ALL of your installed programs. You can use imgur.com and post the links here. Don't post personal information by mistake.
Also, post your OS and if you have 32 or 64 bit Windows. Also your other computer specs may be helpful so post those also. Thanks.
And THEN you said...
Other Applications
IOBit Advance System Care
IOBit Start Menu 8
Airfoil
Alcohol 120%
AMD External Event Utility
AOLacsd.exe (AOL connection driver)
ATI Hotkey Poller
ATI Tray Tools
BitTorrent/uTorrent (all clients)
(snip)
So now you see why I am forced to ask for screenshots. Let's start by getting rid of utorrent and rebooting and trying to verify the game files again, please.
EDIT..AND AVG Web Tuneup. What is that for ? Is that not a feature of AVG ? I thought you understood to get rid of everything related to and including AVG.
It does not matter if they run or not, sometimes. Depending on the program, it can make a difference. I have seen it many times here. That is again, why I am forced to ask for screenshots. Because people willfully hold back information when asked for.
When trying to help someone, that will always be a totaly mystery to me why people do that. You are already making assumptions that you should not make in a troubleshooting process if you are assuming they don't matter because they don't run.
Every time you try something that can possibly be the problem, you have to verify the game files again, or at least try to. That way, if what you tried was the problem or part of the problem, getting the files cleaned up and properly installed will ensure or help to ensure your test of the issue gives good results.
After you follow what is suggested in this post, go to your Steam library and click "play" on Doom and describe EXACTLY (in detail even if it takes more than one line for you to type it all out here) what happens next, including any error messages or PC activity or inactivity.
Please, give details as best as you can. Thanks.
I see Steam says in your screenshot that all files successfully validated. So what happens exactly when you click "play" on Doom from your Steam library ?
You said you have the .acf file for Doom in your steamapps folder. You showed that the files have validated successfully. This is where I am personally confused as to what the problem is now because you "should" be able to launch the game now, according to that information.
After you do that for Doom, maybe you can tell if any issues persist.
You have quite a large number of programs on that computer. Surely some of that is running in the background and negatively affecting your performance or otherwise being a problem.
This support page maybe can help you further on that matter.
https://support.steampowered.com/kb_article.php?ref=8043-EUJN-5239
The games I'm talking about do not use VR either, moreover, I remember knowingly deleting OpenVR thinking I'd not have any need for it, at least in the near future.
Believe it's a Steam update problem and it'll probably be fixed quite soon, but still wanna ask for the time being - how do I reinstall OpenVR?
http://steamcommunity.com/groups/SteamClientBeta/discussions/0/364041517009050048/
Seems to be a similar error?
Considering one mentions it works on pre-April 29th's builds, that would suggest the issue is present also on the live client. (Since the live client runs exactly on that build.)