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

TF2 crashing on death screen

Hi, i recently upgraded to the new version of Crossover games, and i have found 2 problems to occur:

1) HL2 now loads, however when i go to load a new game it crashes 1 bar before its finished loading, and;
2) The death screen on TF2 now causes the game to crash forcing me to apple-alt-esc out.

TF2 was running fine for me before the new upgrade, so am i to assume my machine can no longer handle it?
X1
Im using an imac with OSX 10.4.11, 2GHz core duo, 1GB 667MHz DDR2 SDRAM, and Radeon X1600.

if anyone has had the same issues and were able to resolve them, any help would be greatly appreciated.

(im not great with computers tho so you'll need to dumb down :P)

thanks!

EDIT: Just to add, I've tried playing on various other servers, and also I have tried setting the graphics to lowest possible, but to no avail :(
plus its really hard to not die. :P

I'm having the same problem. Upgraded to CX Games 7.1,0, now TF2 crashes on the 'Killed By' screen. My specs are similar to Cara's. OS X 10.4.11, 2.33 GHz Core 2 Duo, 2 gigs of ram, Radeon x1600. I'm going to downgrade to version 7.0.0 so I can play again.

Yes, I'm aware of this problem. It does not occur on any of our Macs with X1600 cards, but they all run Leopard, not Tiger. So I'm afraid my fix for the death screens triggers a bug in the Tiger drivers. That's not entirely unexpected, considering that the fix uses a feature that is only partially supported by the hardware, but advertised by the driver.

I'll do a test with Tiger tomorrow and see if I can reproduce the problem.

For the technical background for those that are interested:

Radeon cards up to the X1000 series have a limitation which limits them to textures that have power of two sizes: 1, 2, 4, 8, 16, 32, 64, 128, ... . Nvidia cards from geforce 6 and newer do not have that limitation, but earlier Nvidia cards have it too.

Now ATI cards have conditional support for non power of two textures(e.g. a size like 100x100). This conditional support has certain limitations, for example no mipmaps, and certain texture address modes are prohibited. Team Fortress 2 uses such conditional non power of two textures in the death screen.

Textures in Direct3D and power of two textures in OpenGL use so-called normalized coordinates. Ie, the texture coordinates range from 0.0 to 1.0. So 0.5 specifies the middle of the texture. This applies for conditional non power of two textures as well in d3d.

Now there's an extension for conditional power of two textures in OpenGL: GL_ARB_texture_rectangle. It matches conditional non power of two support in D3D, except that it uses non-normalized coordinates from 0 to with and 0 to height. Ie, width/2 specifies the middle of the texture.

In 7.0 and earlier we used this extension for conditional NP2 textures, with a correction for the coordinates. However, this coordinate correction failed in Team Fortress 2, and it is not possible to get it universally working with shaders.

So now MacOS advertises unconditional NP2 support on radeon cards. Power of two textures created with this emulated NP2 support have normalized coordinates, like in D3D. This universally fixes the addressing problems, but when CrossOver outsteps the limits of conditional NP2 textures, the driver falls back to software.

So now I am using this emulated unconditional NP2 support, but I'm extra-careful not to step out of the conditional NP2 limitations, thus avoiding the software fallback. This works fine on Linux and Leopard, and reportedly fixes the incorrect death screen rendering.

However, apparently Tiger does not like it.

Just a heads-up, I couldn't test that yet. Our only remaining mac with an X1600 card that still runs tiger is out of the office this week, unfortunately.

No problem, I'm in no rush! :P

any update on any solutions?

Yeah, the updated fix here works. It doesn't really fix the death screen, just the crash, but that's good enough for me.

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...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoiNHVyZXRnNXI2U3FtTktmUiIsImdkcHIiOjB9