• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/
  • Weve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:


    We've incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We've added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.



    For more information about our privacy practices, please review the new Privacy Policy found here: https://tripwireinteractive.com/#/privacy-notice

General Performance

KniteWulf

FNG / Fresh Meat
May 14, 2009
10
0
0
After playing for 3 hours or so, I've come across a few bugs. Before you say "Your PC sucks," read my specs at the bottom of this post.

For one, the game will randomly lock for 5 seconds or so and then continue where it left off. Extremely annoying as it only happens during waves (as far as I remember.)

Secondly, after some lock-ups, graphical corruption occurs. Alt-Tabbing fixes the way things look, but I notice my graphics cards are running at their power-save specs after that happens. After force-quitting the process, my computer will CHUG like Thomas the Tank Engine with 1,000 cars trying to go up a 45
 

Attachments

Last edited:

Zetsumei

FNG / Fresh Meat
Nov 22, 2005
12,459
1,433
0
31
Falmouth UK
Its an nvidia issue with Unreal Engine 2.5 games.

Try updating to the latest driver and dx version.
Turn vsync and trilineair filtering or tripple buffering (the one on the left) on as well.
 

casual123

FNG / Fresh Meat
May 14, 2009
24
1
0
everyone seems to be having problems with this game yet, i have had none whatsoever. hmm
 

Zetsumei

FNG / Fresh Meat
Nov 22, 2005
12,459
1,433
0
31
Falmouth UK
there aint that many issues tbh and i've seen most of em so far. Most issues are actually people being a bit unfamiliar with UE2.5 ;)
 

KniteWulf

FNG / Fresh Meat
May 14, 2009
10
0
0
Its an nvidia issue with Unreal Engine 2.5 games.

Try updating to the latest driver and dx version.
Turn vsync and trilineair filtering or tripple buffering (the one on the left) on as well.
How does UT2.5 handle SLI? I was able to force it through the Nvidia Control Panel, and noticed both cards running at full speed after that, but does the engine actually use both cards? I know it's a dated engine, but SLI has been around for a good bit of time.
 

Mkilbride2599

FNG / Fresh Meat
Apr 27, 2009
304
3
0
How does UT2.5 handle SLI? I was able to force it through the Nvidia Control Panel, and noticed both cards running at full speed after that, but does the engine actually use both cards? I know it's a dated engine, but SLI has been around for a good bit of time.

It does not support SLi or Crossfire unless the Devs added it. If it's not in their now, then no, it doesn't.
 

Zetsumei

FNG / Fresh Meat
Nov 22, 2005
12,459
1,433
0
31
Falmouth UK
sli support and crossfire support for all games needs to be implemented by nvidia and ati. If there is an ut2004 crossfire/sli profile then that will work for killingfloor.
 

Davidface

FNG / Fresh Meat
May 16, 2009
2
0
0
I also had unusual lag and horribly gameplay try changing the render device to either DIrect3d or software helped me and maybe will help you.
 

KniteWulf

FNG / Fresh Meat
May 14, 2009
10
0
0
I also had unusual lag and horribly gameplay try changing the render device to either DIrect3d or software helped me and maybe will help you.
Changing the render device to Direct3D simply ran the game without taking my cards out of power-save mode. I was playing with them running at 300MHz instead of the full 702MHz. Changing it to software gave a General Fault error, and I had to edit KillingFloor.ini to get the render device back to something different.

I've included a KillingFloor.log that was generated after a crash. Have a look through that and let me know what's up.