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
This topic has been locked 
Discussions Rules and Guidelines
Report this post
There are several cases this happens and a different solution to each one.
Is there a bug splat?
Does anything happen?
Do you see any windows?
Did you interrupt the game window while it is loading?
Do you see only black screen?
Game launches, gets past the splash screens, then goes to a black screen, even though I can hear the audio in the background. A few moments later, I get a message on my PC stating that Killing Floor 2 has stopped responding. After closing that prompt & killing the game, Steam itself ends up crashing also. It's also crashing my Volume Mixer (included with Windows) if I have it open when starting the game.
No changes after a Local Cache check. Don't expect uninstalling or reinstalling either after reading the comments here.
I'm currently running on Windows 7 64-bit Ultimate, all PC specs should be sufficiant to run the game (I've run it in the past), which can be found about two-thirds (2/3s) down the page on my profile. I can provide a dxdiag report if necessary.
I've purchased the Digital Deluxe version twice on Steam (once for myself & once for a friend, I believe it was during a sale) & also own the Epic Games version (that one was a giveaway, not having enough trust in the platform to put any more money into it after buying Fortnite when only PvE was available), but I haven't really played that version yet & don't intend on playing it on that platform. Quite frankly, I lost interest in anything on that platform or running the Unreal Engine after they locked V-Bucks in Fortnite behind the BR mode (a mode I don't play, effectively stealing 4+ years of my life from me collecting them in the StW mode, the main reason I kept playing/streaming it after they broke Twitch dailies), haven't really even ran the Epic Games launcher since that change in March, even if I was pretty heavy into Dauntless when this happened...
EDIT:
I don't really do reviews on Steam anymore (moving them to my personal website back in 2017 after getting hit with mass attacks that affected EVERY REVIEW I had published on Steam), but I have a temporary one up on this game until the issue is fixed giving details about the game not being playable after this update.
I guess we have to hope and pray they add more updates and it eventually works.
Yeah im just annoyed tbh :/ I really wanna play with friends but who knows if it will fix again, I might do some more research and keep you posted if I do end up getting it working.
-Have you tried the common solutions in the pinned guide? Especially the c++ one?
No KillingFloor2 folder found...
No special compatibility settings set, although I might attempt to run the game as Admin later to see if that helps.
No gamepads currently connected to the PC, webcams are also disconnected. There are currently multiple keyboards & mice connected, so the other set can be used when using Steam Link on my nVidia Shield TV in the front room through the USB extension cables. (I'll try disconnecting the USB hub later to see if the multiple keyboards & mice is contributing to the issue)
Made one change in the Global Settings on the nVidia Control Panel, changed Power management mode from Optimal power to Prefer maximum performance.
RESOLUTION:
The last step I listed of changing the setting in the nVidia Control Panel's Global Settings (or changed on the game itself if you don't want this as normal for everything) seems to have helped in fixing the problem with the game crashing with a "stopped responding". Of course I have a friend on Steam that also plays the game, he stated over the Steam messenger that it just takes a while for the game to start up, so I let the game sit there on the black screen for somewhere between 1 to 2 minutes without clicking or pressing anything on the keyboard (still having the windows default loading circle when I pressed the Windows Key to see if I had a crash error behind the game), so that might have also contributed to why it didn't crash this time around (meaning it may not have been the change in the nVidia Control Panel, but taking what my friend said to heart when he saw my review of the game crashing).
Doesn't look like the Steam Link app is playing a part in the crash either, it's just impatience given it takes over a minute to load the menu screen after the splash screens are gone, so even skipping the splash screens on startup with clicks or button presses can cause Windows to see the game as "not responding" & responds with a message stating that it needs to be closed, giving players who don't know better that it appears to just be repeatedly crashing if they are clicking or pressing anything on their keyboard before the menu finishes loading.
Another possibility might be a permission level issue, meaning the game & Steam may not be running on the same permission level (it don't always need to be running on the same level, but in some cases it's necessary). So if Steam is running as Admin, the game would technically need to be running as Admin also. If Steam is not running as Admin, but the game is launching as Admin, this might also cause this problem. An option if the Deep Cache Verification from the guide don't work, try running both the game & Steam as Admin.
You can tell what apps are running on what permission level by looking at the Processes tab in your Task Manager (right-click on your taskbar, then click on Start Task Manager or press Ctrl+Alt+Del, then click on the Start Task Manager button to start it, you may need to also click on the Show processes for all users button as well if you don't see the processes you are looking for).
Typically once set, if Steam is running as Admin, this permission level is carried over to games that are run through Steam, but this isn't always the case (especially if it's run through a sub-launcher or batch startup file or if you are running the game directly from the executable; this last method is something I have to do in a few games because they didn't work correctly if I launched them directly from Steam). Because KF2 is just silently closing on your PC, it might be hard to tell what permission level KF2 is running under, so you might re-enable UAC prompts if you have them disabled. I typically leave this on to help protect my PC & prevent malicious processes from running, it also helps me to determine when a program is attempting to run as Admin, even if I didn't set it specifically to do so.