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
Sounds like you hit an unlucky steam bug.
Might need a fresh installation of steam.
https://steamcommunity.com/app/299720/discussions/0/616188677690629563
http://steamcommunity.com/app/228380/discussions/0/357284767244121671/
Maybe it helps:
Just some copy and paste solutions i found after a quick search:
"I would suggest you guys see if someone in your household was maybe playing a.. not so legal copy of a game with a steam_api file before you're having these errors. That can cause the problem you're describing. "
"Windows 10 ? Try running steam as administrator or disabling anti virus ?It seems to be a common problem with Avast and such"
"Go to the Steam folder and delete appcache folder and restart Steam."
"Make sure that both Steam and the game are not running as administrator. You need to match the privileges of Steam and the game for this to work, otherwise this part of SteamAPI often fails. "
"Before any functions can be used, first SteamAPI_Init() must be called.
A return of true indicates all required interfaces have been acquired and are accessible.
A return of false indicates one of three conditions:
The Steam client isn't running. A running Steam client is required to provide implementations of the various Steamworks interfaces.
The Steam client couldn't determine the AppID of game. Make sure you have Steam_appid.txt in your game directory.
Your application is not running under the same user context as the Steam client, including admin privileges."
"Start via shortcut"
"Try different Windows compatibility modes"
"Log out of steam and then log back in"
Or maybe you should get in contact with stean support..
Go to the Local Files tab, then click Browse Local Files.
In the directory that opens up, right click in the directory and go to New->Text Document.
Name it "steam_appid.txt".
Open the new text file with Notepad and put "228380" into it, then save it.
Now try running Wreckfest.
Another possible solution i was thinking about that could work but is a bit of an elaborate task:
Do you have a second computer? Maybe install it there and if it works on that computer use the steam backup feature:
https://support.steampowered.com/kb_article.php?ref=8794-yphv-2033
ANd then install that working version on the computer where it is currently not working.
You can try to "randomly" delete files from your wreckfest folder and then run the "Verify integrity of game files" -function again,
I would suggest deleting the steam steam_api.dll files and maybe the wreckfest.exe files.
Checking the files will notice the missing parts and hopefully download functioning ones.
You're not using a beta version of the Steam client?
jannesBB: I'm not using the beta version of Steam. What is new since the last time I launched the game is that I use the "family share option" with my brother. I will ask him if he can play the game. But otherwise, I just formated and installed Windows 7 on a SSD and bought a new graphic card.
Second time was due to either due to a third party firewall (Comodo) or anti virus (avast) blocking the .dll file. Add exceptions for the wreckfest install folder if you have any security software running.. I'm not sure if the Windows firewall / defender is capable of blocking to the extent you're getting, but an exception in the whitelist can't hurt.
Ran a little test: i deleted the two steam_api.dll files, ran verify local files, which replaced them. Game launches fine afterwards. Though from your previous comments saying you have tried verify files... My bets on something silly blocking it.
It was a Comodo conflict, now it finally works ! Thanks a lot dude