neutrix

Well going up to 1.07 won't make any difference anyway as people have confirmed the issue is still there in this version. If you don't feel comfortable upgrading until 1.07 is final then I wouldn't worry about it, simply because it won't fix your problem.

Are you on 1.05 as well Leckig? At least I'm not alone with this problem . Has anyone submitted it as a bug to fix on the official bug tracker or shall I do it? (I've never done that before and I'm not exactly sure how).

I'd prefer not to install 1.07 until it is released properly, but I suppose it wouldn't hurt to give it a go. Symbiot, if you are having the same problem under XP then it is unlikely to be a driver issue as I first thought it might be. Is anyone on 1.07 getting this problem? Thanks for the replies.

Crysis is DX10 and DX9, Halo 2 is DX9 only. The reason that they almost definitely won't switch to DX10 is the sheer difference between DX10 and DX9. I don't know here who has programmed using both but in my experience the gap is sizeable enough for them to have to rewrite their whole rendering system for support. That in my opinion would take far to much time...

plaintiff1 is correct, the W buffer was designed to fix those long range issues, but to be honest it doesn't really make any difference any more. There are numerous other ways of fixing that sort of bug. You could scale the scene into a smaller range when doing the vertex transformations (thus bringing most geometry closer to the viewport and increasing precision) or alternatively, you can just use a higher precision depth buffer. I've been playing with D3D10 recently and it looks like you can create a z buffer that is really high precision, so you wouldn't even have to care about the effects of things being a long way away from the viewport.

I tried setting my post processing to low, made no difference to me.

Same, I've got a C2D 6800 @ 3.4 GHz, no problems with anything.

Yeah, unfortunately the radeon 9250 is not supported by the game, you will need a new graphics card.

Unfortunately I have the same performance drop as the rest of you. Core 2 Duo X6800 @ 3.4GHz 2x NVIDIA 8800GTX 768MB 2GB RAM Windows XP

If you have an NVIDIA card, disable 'anisotropic mip filter optimization' from the driver settings. If you have ATI, try turning off the trilinear mipmapping but leave the trilinear optimization enabled in driver settings. I'm not sure if this will fix it but it fixed some other people with similar problems. EDIT : Sorry, just realized someone else has already posted this, ignore me.

Post processing is the processing done to the full screen after a scene has been rendered, for example the depth of field effect is done in the post processing phase, as it involves blurring the final scene render based on the depth of each point on the screen. The screen glow and blur effects are also post processing effects as they are applied after the main scene has been drawn.

People tend to get this problem when they have low video RAM and also after people have played the game for a long time. I recommend dropping the texture detail a bit in graphics options and see if it improves it. I'm hoping that in the next patch or two they will improve the texture loading code, it can be very annoying at times. Another way to conserve video RAM is to switch off antialiasing, that might help a bit also.

Hi, I had the exact same problem, but somehow I managed to get past it, I think I restarted the level after the message came up or something, I don't know what I did, but eventually it let me continue. Sorry for not much help, but I thought that I'd let you know it is possible to get through it.

I have the same thing. 2x8800GTX (not running SLI though as that kills the framerate), EVGA 680i Motherboard, Core 2 Duo 6800 @ 3.4GHz, 2GB RAM, Windows XP and no matter what graphics mode I set it to, I get the same performance, 20-30 FPS. I'm quite annoyed, I hope 1.05 sorts it out. Seeing as the FPS don't change on any graphics mode, this must mean that it is either processor or hard drive limited. The processor is pretty good so it shouldn't be a problem, leaving the Hard drives. I have a RAID 0 array so it should also be pretty quick. I'm completely confused as to why performance is so bad.

I have exactly the same problem. Texture screw ups some of the time, especially when it's a cutscene. It also appears some of the long distance models are being used at close range rather than the high res ones. I also have the same campaign problem. All my graphics options are set to the Maximum (usually "Very High"). System: Core 2 Duo X6800 Processor 2x8800GTX in SLI 2GB RAM Windows XP Professional SP2. Has anyone had any ideas on a fix for this? Thanks.