HL2DM Shiny Guns..

[Roger]

I've moved the whole half-life 2 deathmatch folder out of steamapps so it would build a new one, but this problem is still here.

I play HL2DM in Directx 7 cos I've got an old CPU, but when I was testing my map with all of the gfx options up and in DX9, the guns looked stupid and some of the walls and floors looked too shiny as well.

Could this also be why my HDR Skybox isn't blooming? Another topic, I know..

[Lobstar]

I think you messed it up by mooving everything, i think its the cubemaps acting up and i would advice you to "Delete Local Content" instead of mixing with maps in the future. Let steam build the file integrity for you, that way you wont get errors.

[Roger]

Erm, ok..

Backed up/moved the folder and deleted local content. Installed/downloaded hl2dm from steam and it loads with this message (see pic).

[spare8ball]

looks cool to me. lol

[Pink Panther]

Try launching the game in DirectX8 (Or even 7) and see if that fixes the crash on startup. -dxlevel 80 in the launch parameters for DirectX8 and 70 for DirectX7. Also, try verifying cache integrity and defragging local content in case something was corrupted on download.

[Valar]

GPU driver - latest?

[Roger]

This game has given me loads of problems.

Reinstalled XP + DirectX 9 + 9.3 Cataylst drivers + Steam + HL2:DM and whatever settings, the game is very, very choppy

Lockdown map - hit a barrel with the gravity gun and it flips slowly with loads of frames missing. The fps counter says it's doing 70. If I shoot the barrel, it explodes and the fps go into the red. It also makes the mouse very stiff and difficult to turn without getting stuck. Sure the mouse isn't the problem tho.

I have no idea what's making this happen.

[Valar]

you got Wait For Vertical Sync turned on by any chance?

[Roger]

All game settings on lowest so it's off. And all ATI settings on high performance or disabled.

I'm taking out sticks of ram now and trying different combinations then playing the game. Anyone think it may be RAM?

I started up Lost Coast just before and it just stayed on the blurred menu screen. There was a system beep but I couldn't get back to windows to see what it was. After rebooting, I found it in the event log and it said:

Half-Life 2: Lost Coast: hl2.exe - Application Error : The instruction at "0x241fe49b" referenced memory at "0x0e5bf438". The memory could not be "read".

[Roger]

On one stick of ram it's crazy! You walk forward and 2 seconds later you're there. Like a teleport.

3D is well messed up. Don't die on me, computer!!

[Valar]

you might be looking at a deceased GPU mate :[
try running a stress test

[Roger]

Oh..

It was second hand bought a month ago. Gonna try an old Nvidia card to make sure. What stress test program do you recommend? Thanks.

[stoopdapoop]

I think he means a source stress test

there's one with that comes with the SDK base, and one that comes with CS:S

but if you don't wanna run a source test the "3d mark" series is excellent. you can grab them at the madonion website.

[Valar]

this has decent hype with adv users http://www.ozone3d.net/smf/index.php?topic=1440.0

[Roger]

Oh, I've got the stress test in Lost Coast, but it wouldn't load up before.

But er, I'm using an old Nvidia now and the game's still the same..Delayed reactions, juttering, 'teleporting'

CPU is bad isn't it?