Team Fortress 2 Forum

Hi,
I have a hotfix for the Death cam crash of Team Fortress 2(and Guild Wars) on Macs with Radeon cards running Tiger. You can get it on dl.codeweavers.com with the access key "tigerfix", without the quotes.

This is just a single file, wined3d.dll.so. To install it, just download it, and open the directory structure of CrossOver Games.app. In there, copy it to Contents/SharedSupport/CrossOver Games/lib/wine/wined3d.dll.so, overwriting the existing file, and start the game.

Unfortunately I haven't been able to give the final build a life test with TF2 yet - The Steam servers seem to reject my connection currently. I hope it works again later today. So far I have tested it with Guild Wars, which had the same issue.

I'm sorry for the inconvenience this bug caused,
Stefan

EDIT: Fixed the path. Thanks to bunky for spotting this

For the technically interested:
It turned out that the suspicion here was correct: http://www.codeweavers.com/compatibility/browse/name/?app_id=3379;forum=1;msg=37997

MacOS 10.4 has this non power of two texture emulation, and it is basically working. However, there seems to be a race condition somewhere. If the application sends opengl commands in an unlucky order or time sequence, it crashes, causing just the application to exit, or even a window server freeze or even a kernel panic. I added a glFlush() at a specific point to force a partial synchronisation, which avoids the problem. This glFlush is in a codepath that is mostly executed during game loading only, so there should not be a negative performance effect.

Now the servers finally let me in, and I can say that the fix works at least for me.

Hey Stefan, the file needs to go in the wine folder, so the directory structure would be Contents/SharedSupport/CrossOver Games/lib/wine/wined3d.dll.so. Thanks for the fix, I've been itching to play. I'm about to log in and test it out.

Oops, you're right. I fixed it in the above post

As much as I'd like to say that this fix worked perfectly for me .. it didn't. Things aren't any better than they were, unfortunately. Maybe I did something wrong, I'm not sure. What do you suggest?

Yeah, unfortunately I'm still crashing. I actually saw an image instead of the usual garbled text screen, but crashed none the less.

Ok, I've uploaded a new file to the same location. This time I've disabled the death cam fix entirely. This should avoid triggering the bug, while obviously, doesn't fix the death cam.

(update: see the post below for a possible fix that keeps the death cam intact)

Here's another try

I have uploaded a new file wined3d-test2.dll.so to the same location. I've still kept the old file since I don't know if the new one works. If it does, the death cam should be fully functional on Tiger. When you put this file into CrossOver.app, you have to rename it to wined3d.dll.so first, otherwise it won't be used. That's all getting somewhat confusing, sorry about that.

I debugged a problem in our unit tests yesterday, and stumbled upon a software fallback that shouldn't occur. The problem could be related to the TF2 crashes. For some reason the driver falls back to software rendering in glCopyTexSubImage2D if bad filtering settings are used, although filtering should have no effect on glCopyTexSubImage2D. When the driver attempts to compile software shaders(again, I don't see why it would want to do that), the application or entire Mac crashes.

Stefan, I think you did it this time! I just joined a server I frequent and promptly got my behind handed to me. The death screen did not freeze up. There was, however, another freeze that I've never before experienced; I'm not sure what caused it - the screen went white and the sound skipped for a moment. This was while I was still alive though, and had nothing to do at all with the death cam. I'll see if it happens again and if I can figure out the trigger, but for now it seems you've fixed the death cam. :)

Edit: A little update. I played for a while longer and the death cam is still working perfectly. I didn't experience that white screen again; in perhaps 30 minutes of playing after it I only had one brief freeze-up. Thanks very much for fixing this.

i know i sound like a total noob, but i've been searching thru my mac and i cant find where to put the file. i kno it says contents/sharedsupport/ etc... but I can't seem to find it at all! i feel stupid, but maybe someone can assist me? lol

Lex wrote:

i know i sound like a total noob, but i've been searching thru my
mac and i cant find where to put the file. i kno it says
contents/sharedsupport/ etc... but I can't seem to find it at all! i
feel stupid, but maybe someone can assist me? lol

Go into your Applications and locate Crossover Games. CTRL click the icon and navigate the Crossover Games.App menu until you get to the folder you are looking for.

I finally got around to installing the new fix and it works great. As Brighid mentioned, I did notice that white screen for a moment during playing, but I didn't notice anything that would've caused it. I only played long enough to die a couple times though, just to check out the death cam. Thanks for fixing this Stefan! Great work!

bunky wrote:

Lex wrote:

i know i sound like a total noob, but i've been
searching thru my mac and i cant find where to put the file. i kno
it says contents/sharedsupport/ etc... but I can't seem to find it
at all! i feel stupid, but maybe someone can assist me? lol

Go into your Applications and locate Crossover Games. CTRL click the
icon and navigate the Crossover Games.App menu until you get to the
folder you are looking for.

The magic incantation you're looking for is "Show Package Contents". That's an item on the context menu when you Control-click or right-click on the CrossOver Games.app icon.

Hi,

Experienced the "Death cam crash" in Team Fortress 2 while trying out Crossover Games 7.1. Applied the patch as described by Stefan Dösinger, and it solved my problem with crashes each time I was killed.

The only thing was a new quirk showed up, it seems a bit different from what others are describing. In my case, once I died, the background of the screen turned black with white characters spelling gibberish all over it. The HUD of TF2 still showed above it, so I assume it's something with the rendering of the "death cam" itself, althouht it also happens when a TF2-round has ended, in which I have a screenshot from:

My computer is a standard MacBook Pro Core 2 Duo 2.16 Ghz, although with 3GB RAM. The video card is thus a ATI Radeon X1600 with 128MB VRAM. I'm running MacOS X 10.4.11, and I'm using an external display as the main screen with a resolution of 1680x1050.

Frode Danielsen, use the wined3d-test2.dll.so file instead, it fixes this issue. Sorry for the confusion, we'll ship a 7.1.1 build most likely on monday which runs TF2 out of the box again on Tiger.

The problem you are seeing is the one that CrossOver Games 7.0 had. 7.1 had a fix for it that triggered a bug in Tiger. Wined3d.dll.so disables this fix, so it goes back to the 7.0 behavior. wined3d-test2.dll.so fixes the fix to avoid triggering the MacOS bug, so the death cam should work and TF2 not crash.