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
Have you tried uninstalling and deleting killing floor folder and reinstalling
I have two outcomes - either precisely as you describe, or it loads in windowed mode, and any change to resolution, maximising the window or ANY slight change and it hangs.
I've tried tons of things to try and wrestle it into working (obviously running in windowed mode), various diffierent compatibiluity settings, verifying files all to no avail.
I think it just doesn't like Windows 10 at all. (And no that doesn't mean posting "hey I run on Windows 10 fine" is at all helpful, just in case).
I'm completely out of ideas on this one, so maybe someone can come up with some idea, because the issue seems to be down to as soon as the resolution changes - if you do it within the game menu, it hangs. If you run it in windowed and maximise it, it hangs. If you just leave it in windowed mode and let it load past the menu, it hangs.
How to fix this, I have no idea.
Thanks !
-windowed
It works now !
Frankly, if you're using Windows 10, it wouldn't surprise me as my experience has been that things can just stop doing things for no apparent reason.
I was playing shadowman the other week (for the umpteenth time). I'm laid in bed with my laptop. I save, shut the laptop down, go to sleep.
Wake up, get a cup of tea, turn the laptop on, start shadowman. And it just refuses to start with an error. Took ages of pissing around to get it to work again.
I noticed that for me yesterday there was some background Windows 10 update as I noticed the hard drive usage going up (it does that whenever it updates and it's quite noticeable). So maybe that's what has ♥♥♥♥♥♥ you over?
Suffice to say, I've been experiencing pretty much the exact same issue as OP here and, for the most part, the story has been the exact same. Running the EXE as an admin did nothing to get to the root of the issue, nor did Checking the file integrity.
It would seem that running the game in a window is, at least right now, pretty much the only feasible way to get the game running properly. I've tried scavenging around to see if there's a solution for full-screen display, but so far to no avail.
Also, your graphics settings might be creating the problem. Try using default settings.
Plus, read this discussion
https://steamcommunity.com/app/1250/discussions/0/620695877455801770/
Try Bigguns suggestions in his manual. Or setting the launch options for Killing Floor in the your library suggested by DatWGuy. The launch options will override the KillingFloor.ini settings. Use -windowed or -fullscreen for the desired launch option.
these usually will not work for this issue as stated it being a directX and i noticed it may be a conflict with windows 10, ive been trying several things/aswell as new things
I have done EVERYTHING to no avail except switching to openGL when in windowed mode THEN going fullscreen (works fine) but DirectX right when i switch back over? freezes and locks up the game
I am curious though if this is something with the GTX series because I have several friends having the same issue BUT with the exact same graphics card as me, so who knows. as i am running a GeForce GTX 1650 with Max-Q Design [EV]
but my problem could be that my graphics card is an "EV" (Experimental Version) and not an actual release of the graphics card. but all in all of what ive seen its the DirectX setting i believe that is doing it (the one with the 3).
So...What's the verdict? Sorry, I'm not very technically literate, so I don't quite get what you're talking about.
You're saying that the problem could be because of the way Windows 10 tends to operate the software?