Quake lagging

[Adaman]

Recently had HDDs wiped and had to reinstall XP. Ever since I've done that quake doesn't work right, it's unresponsive. I feel like I have a 200 ping but my ping appears to be normal (50-80). Since it's not an internet prob, what else could it be? I scoured through my configs and didn't see anything strange (but then again I really wouldn't know). Using the Proquake Launcher and Proquake 3.50.

Just booting up GLpro with no command lines runs flawlessly. Here's the command line ProQuake Launcher uses to load quake:

c:\quake\glpro.exe -width 1280 -height 960 -bpp 32 -gamma .65 -dinput -nocdaudio -iplog -heapsize 131072 -zone 1024 +exec qview.cfg

I'm betting this will be a simple fix. I'd like to get quaking again soon

[Baker]

c:\quake\glpro.exe -width 1280 -height 960 -bpp 32 -gamma .65 -dinput -nocdaudio -iplog -heapsize 131072 -zone 1024 +exec qview.cfg

I'm betting this will be a simple fix.

It is a simple fix.

1. First, when you don't use a command line, Quake uses a default resolution of 640x480 with 16 bit color. That is fast as hell.

Conversely, 1280x960x32 is slow as hell unless you have a real beast of a machine.

Since ProQuake, like GLQuake, uses the standard Quake texture that are very low resolution by today's standards, there is no true advantage of using 1280x960 for a game that was actually designed for graphics in 320x240 resolution.

Additionally, 32 bits per pixel is over kill for a 256 color game. 16 bit is faster and is 65536 colors that 16 bit uses -- far more than adequate for ProQuake.

Answer: 640x480 at 16 bits per pixel, the default Quake resolution, is very fast.

2. You are using a memory allocation of 128 MB! ProQuake does not need nearly that much memory. Without a command line, Quake by default uses 16 MB. I'd go with 32 MB.

Using 128 MB might impair the performance of your system if you don't have at least 512 MB RAM.

Answer: Use a 32 MB memory allocation

I hope that fixes your problem, from your description of the problem I'm sure it will.

[Adaman]

Thanks for the reply.

Well, this is the same resolution/bpp I always used to run at. I never had problems with it. I still get really good FPS, so it's not a video slow down thing I'm pretty sure. I don't use 128 memory for it either, just 32. I was just testing it out at the time to see if it made a difference at all.

I just tested out quake with all the video settings at fastest and still had the same problem. So, the delayed reaction is from somewhere else. Coming from either the proquake launcher or something to do with qview (doubt it). I can boot up GLpro and exec my config and it's fast as it ever was. I don't know what the deal is...I think I'll try making a new quake directory.

[Baker]

Coming from either the proquake launcher or something to do with qview (doubt it).

Hmmm ... the ProQuake Launcher exits when it starts Qview so that seems unlikely.

Try turning "Config Boost" to off in the ProQuake Launcher (forces gl_flashblend 0 and gl_polyblend 1, could make a perform difference). Also if you have transparent water turned on in the ProQuake Launcher, this could make a difference (it doesn't really change anything for me, but who knows). With config boost set to off, it doesn't force these so this could be the difference).

[Zop]

Reinstalling windows makes me think that you may be missing a windows update or service pack... or even new drivers from your video card manufacturer. I don't know if you ever turned off some windows services before the reinstall, but that may help. (Some services are required for things like sound and internet, so don't turn off things you don't know...)

[Adaman]

Anyone else got any ideas? This one has me stumped. It seems no matter how I run quake it starts lagging for no reason once I join a server. Feels like I'm pinging 200 when I have my usual ping (60-75).

[Baker]

http://housecall.trendmicro.com/