Team Fortress 2 Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Game freezes up when killed

Hello. I thought it would be wise to start a new thread about this.

I recently posted here about how the freezeframe that appears at death showing your killer seems to have been fixed (previously it showed a black screen with weird words), but I have to take it back. The game seems now to freeze every time I'm killed, and I'm stuck hearing "wha-whoosh-wha-whoosh-wha-whoosh" over and over until I force quit Crossover.

This problem is occuring in Day of Defeat: Source as well. I will try to reinstall Crossover and see if that helps.

Regards,
Brighid

Edit: After fully reinstalling not only Crossover but Steam and TF2, the game is running much better. No crashes after over an hour of play; a few brief freezes at the start but after that it was pretty smooth, with the FPS hanging around 20 or so (1440 x 900 windowed). Definitely playable and everything seemed to be working well. I'm not sure what caused the crashes before.

Okay, well, it's happening again. I was playing around with the resolutions while the game was running, and next time I died (the game was otherwise fine) it froze up. I suspect that my changing the resolutions while the game was running was the cause, but I don't really know. Restarting Crossover after having to force it to quit did not solve the problem.

I suppose I will reinstall again and this time I won't change the resolution or whether it is windowed or full screen while the game is running.

So anyway, the problem still exists. Maybe later I'll try a nightly build, but it can wait!

Which system and graphics card do you have? I can imagine that the fix for this issue causes problems because it (ab)uses a driver emulation of a partially unsupported feature(conditional non power of two textures). If crossover accidentally steps out of the bounds of conditional np2 textures the driver now tries to use a software fallback instead of just rendering garbage; the software fallback is either slow or even crashes the game.

I am using an Early 2006 20" iMac with a 2 GHz Intel Core Duo, 2 GB RAM, and my card is an ATI Radeon X1600 with 256 VRAM. I am running OS X 10.4.11.

After fully deleting and reinstalling both Crossover Games (7.1.0) and TF2 itself yet again, it's crashing at every death now, so I'm at a loss.

What can I do?

Brighid, it might have something to do with the server you're using. This is speculation on my part, but can a server be configured to use different graphics or sounds when you're killed? If so, the problem may be due to that.

If you can test with a server that you control, and keep it very vanilla, that might be informative.

Lastly, you can ask Steam to verify the integrity of your game files. If they are getting corrupted over time, you might check your disk using Disk Utility.

As far as I know, none of the servers I've ever played on have used any sort of custom effects of any kind when one dies.

I'll try verifying the files first, and then running Disk Utility. If that doesn't do anything, then I'll try running a plain server on one of our other computers and see if the problem still occurs on it.

Thank you for the suggestions!

Well, I tried all of what you suggested; I tried different servers, I tried verifying files, I repaired permissions with Disk Utility (which was the only thing wrong) .. and it's still doing it every time I die.

I'm going to try installing the latest nightly build and see if that helps, but any other ideas are most welcome.

Edit: I tried the latest nightly and it was exactly the same. I don't know what to do now.

Just to clarify, did you test this on your own server too?

Stefan Dösinger wrote:

Just to clarify, did you test this on your own server too?

Yes, I tested this on a server I started on our other Mac (under Windows) by choosing Create Server in-game. The effect was the same. The server had no modifications that I am aware of and was running on a Valve map (ctf_turbine).

I think it is related to Tiger ☹️

I've written a detailed description of the (suspected) problem here: http://www.codeweavers.com/compatibility/browse/name/?app_id=3379;forum=1;msg=37997

Ugh; one more little motivation to upgrade, I guess. If you find a workaround that would be great, but in the meantime I guess we'll save our pennies. Thank you once more for your help.

My TF2 randomly crashes aswell when I get into spectator. I'm on Leopard 10.5.5, with the Late 2008 Macbook Pro. The game runs perfectly except for crashing. Counter-Strike Source runs fine with no crashing.

1 to 12 of 12

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzM5NTcwNzYwLCJjc3JmX3Rva2VuIjoidVhtNkNyeE5HWnh6UEFSWCIsImdkcHIiOjB9