Graphic glitches

[jake123]

I'm getting serious graphics glitches with the vehicles (and I think with the infantry too, though it's harder to see). This is as I approach the limit caps; if I only have a couple of dreadnoughts, all seems fine, but as soon as I start to get to the point that I've got a lot of stuff on the board, then it starts to get wonky.

I've got a screenshot that shows what happens:

http://consultron.ca/videoglitch.png (it's a bit on the hefty side).

Note the legless dreadnoughts and the see through predator.

I've got the latest direct x, latest drivers, yadda. I'm running on a dual athlon 2400+ with an nVidia 5600.

I thought I'd include an excerpt from warnings.log. I'm not going to put in the whole thing, because it weighs in at 87 MB in size, 99% of which is the following repeated over and over again:

23:43:26.6 SKINBATCHING -- VB Lock failed.
23:43:26.6 Lock of skin batcher failed. This is a sad day for skin batchers everywhere.
23:43:26.6 Lock of skin batcher failed. This is a sad day for skin batchers everywhere.
23:43:26.6 Lock of skin batcher failed. This is a sad day for skin batchers everywhere.
23:43:26.6 Lock of skin batcher failed. This is a sad day for skin batchers everywhere.

Here's the header information from same:

W40K started at 2005-02-16 19:20
OS NT 5.1, 512MB Physical Memory
RUN-OPTIONS
WORKING-DIR E:\WH40K
USER Jack

19:20:07.5 MATHBOX -- Version=5, Cpu=AMD Athlon:f=6,m=8, Mode=SSE
19:20:07.7 GAME -- Warhammer, 1.20, Build 61639.45376
19:20:07.7 GAME -- Available memory: 511MB RAM, 1200MB Pagefile
19:20:07.8 State::State - set socket send buffer to 131072
19:20:07.8 State::State - set socket receive buffer to 131072
19:20:07.8 HostState - 192.168.1.2:6112 / 192.168.1.2:6112
19:20:07.8 Session : Now Host
19:20:07.8 Session : We are now a Host
19:20:07.8 PeerState - 192.168.1.2:6112 / 192.168.1.2:6112
19:20:07.8 PeerState::ConnectCallbackHost - connecting to host at 255.255.255.255:6112
19:20:07.8 GSTransport::Connect - GT2AddressError
19:20:07.9 SPOOGE - Driver[Dx9 : Hardware TnL] on adapter[0], version[4,32]
19:20:08.1 SPDx9 -- Driver Name = nv4_disp.dll Device = \\.\DISPLAY1 Desc = NVIDIA GeForce FX 5600
19:20:08.1 SPDx9 -- Driver Vendor = 0x10DE Device = 0x0312 SubSys = 0x91261462 Rev = 0x00A1
19:20:08.1 SPDx9 -- Driver Version Product = 0x0006 Version = 0x000E SubVersion = 0x000A Build = 0x1A25 (6693)
19:20:08.1 SPDx9 -- Driver GUID = {D7B71E3E-4052-11CF-F76D-2CB100C2CB35}
19:20:08.5 SPOOGE -- 271.00MB available texture memory
19:20:08.5 SPOOGE -- 271.00MB available texture memory
19:20:09.0 GAME -- Beginning FE

Again, this is happening pretty much every time I play. Any ideas?

Thanks!

Jack

[jake123]

Well, I think I figured it out. Turned out it was being caused by a combination of things: an older system bios, and the fact that write combining was not being properly enabled plus a video aperture that was defaulting to too small a size. When I upgraded the system bios, it got even worse; however, once I figured out that the new bios had added a number of settings to the bios setup program, and after messing around to find the right settings, the problem appears to have gone away. Not only that, but it looks like the performance is a lot lot better than it was before.

I even checked out some of the other games that have "fallen by the wayside" after I got this game (ie- homeworld2 and doom3), and they are also much improved... so I'm def glad that DoW forced the issue.