Search results

Deleting both cache.ini and killingfloor.ini did nothing, game worked fine until today Here is the crashlog: 1 a216d493ab9e68c05877eeb639f0ea8b 11 9905 1383788304 AppleMacPro.local 11 1 1 0 3339 (128.29).1092.1055 0 Oct 31 2013 16:05:37 5.997487 UOpenGLRenderDevice::UpdateGamma <-...

While I am sure everyone appreciates you trying to help, your assertion is incorrect. Please read my explanation and workaround solution given above. Please note that I have tested this with my own servers that ONLY had AntiBlocker installed and I can confirm this issue several times over.

This appears to be due to an issue with loading mutators out of the Cache folder, I've given a workaround for this here: http://forums.tripwireinteractive.com/showpost.php?p=980935&postcount=8

One of the best things to do is to turn off the Motion Blur, it helps greatly with the wash-out and funky lighting flashes.

It doesn't fit with everything else. If you can beat it in 4 waves then there isn't much point of even worrying about an exploit. Beating the map legitimately on long will only be for personal experience, which could be done preferably without even using the exploit.

Was it fixed to make it so the IceCave achievements only work with the long setting like all the others? Currently it is possible to do them with the medium and short length games.

Try this and see if this sorts it: http://forums.tripwireinteractive.co...35&postcount=8

Try this and see if this sorts it: http://forums.tripwireinteractive.com/showpost.php?p=980935&postcount=8

Try this and see if this sorts it: http://forums.tripwireinteractive.com/showpost.php?p=980935&postcount=8

Were you ever able to access this area? If yes, try this: http://forums.tripwireinteractive.com/showpost.php?p=980935&postcount=8 If no, you might wish to try that anyhow but I can't be so sure on that one. Let us know in a reply here how this goes.

You may wish to set AppleVA to 0 in your KillingFloor.ini as referenced in the other thread. I have seen it resolve other issues, one being the screen would flush totally red when health is low instead of just having a red overlay. This may stop that issue for you as well, let us know here if...

What graphics adapter is your Macbook running? Please note that Intel chipsets are not supported and this is shown on the store page for the game.

As an FYI, this patch was just a temp fix I believe. It will set AppleVA to 0 for you if you don't already have it set when you use NVIDIA chips on Lion. So you can leave it a 0, or it will just disable it anyhow when the game is run.

Check at about 3:30pm EST

I can confirm this issue on a Mac Mini running the 320M and using the AppleVA=0 fix. I will test this tonight with an ATI iMac that did not require this fix and will report back. WORKAROUND: Go into your display settings and change to Custom. Then you will want to change the Scope Detail...

The AppleVA turned off works just fine on the 320M, which really isn't that great of a chip. So I would say it is a more than satisfactory workaround for however long it takes. I sent you a tweet on http://forums.tripwireinteractive.com/showthread.php?t=48642 , if it gets the chance to be...

That doesn't seem right, but I ended up on a Medium (7 wave) server and sure enough I got the achievement. This doesn't mesh with any of the other achievements for any of the other maps, is it supposed to be this way?

I'll be honest, the frame rate loss with this flag seems negligible to me and that is on a 320M. This is certainly workable enough permanent fix for AppleVA or no fix. Now all we need is for the cache problem to be fixed and we are in business, at least both workarounds are swell for now. :)

I can confirm that this still occurs on a Mac Mini 320M running Lion 10.7.2. I am looking into this now and will hopefully get us some help on this issue. For Windows, this issue would happen if you joined a server with any character other than the base 4. I believe that has been fixed for...

Thanks for responding to my request Ryan, I can confirm what the user above stated that this setting prevents the crash from occurring. It definitely did appear to be an NVIDIA driver issue with my previous tests and hopefully this will help you to narrow it down. In my tests this issue...