So... I had been playin with software quake for ages but when i bought new computer I had to switch to gl since these problems occurred with software-qw running on the new computer:

my keyboard won't work properly, it's laggy as hell and jams all the time (i'm moving wrong directions and when i shouldnt) (wont happen in gl)

i get just 72 hz with my monitor with which i get 160 in gl.

first i got just 60fps but dibonly fixed that.

Sometimes i get some colours get mixed and stuff.

I've a laptop. I hope that isnt an issue.
Graphic card: Radeon Xpress 200
Running on Windows XP
I hope someone could help me, so.. thanks in advance

Hi Pek, I dont know if you have solved this yet but Ill try answer it anyway.
First off, make sure VSync is disabled in the graphical card settings this will probably fix the hz problems, if it doesnt the problem is because of your laptop moniotr, which surley doesnt really support them low resolutions.
The keyboard error is a neat little fucker, make sure you have sys_priority on high as well as sys_cpu.
About the colors, make sure to set your bpp in your cmdline equal to the bpp on your desktop, like so -bpp 32.

If that doesnt work, download the latest fQuake definition here: fquake.f.nu (I think ), make a full installation and try to use both ezQuake and FuhQuake and see if the errors are the same

Please get back to this thread.

Cheers, Iskall

Ok, I've to try that out.

I'm running on ezQuake 1525 but had the same problems with Fuh.

fuhquake and ezquake both use the mgl library (from scitech, and an old version of it).
My personal findings of this library are far from favourable. I _always_ end up with a blue start button, most people cannot start it without -dibonly, and it hogs the cpu stopping other programs from running (meaning you can get lagged input with many usb devices).
As an experiment, try running FTE (http://www.fteqw.com), which does not use this library. FTE's software renderer is not the most stable, no, but the experiment is in the video library rather than the renderer. If it crashes, just start it up again.
If FTE does perform better than ezquake, you should moan at the ezquake folk to do the right thing and ditch mgl.

You may also find that sys_priority and stuff should never be anything greater than 'normal' priority, or input drivers (and at least on my computer, modem drivers) can halt/freeze/disconnect/crash. It depends on the hardware as to weather you can get away with it. With mgl around, you may even need to consider setting quake to a low cpu priority.

OK, thanks alot Spike, I'll test FTE also.. but I'm playin in NQR and EQL so I can't use that in official matches, oh what a pitty.

Well, I'm not saying you should only use FTE, mearly demonstrate that it's all mgl's fault so that ezquake will finally ditch mgl too. FTE's software renderer isn't really stable enough anyway. Alternativly, if ftesw crashes too much, you could see if Q2 works properly, whichever is easiest for you to run.
ezquake people: Please _please_ ditch mgl.

when I was working on ZQuake SDL I found the software binary to be faster than the MGL/X11/svgalib ones. perhaps we should also release a software sdl ezquake client

Another question; in Fuh 0.30 accorrued following problem; it took some 5-20 mins to disconnect from a server (sometimes also on connecting), also loading up Fuh took some serious amounts of time. I didnt have problems with 0.29(or 0.28, whatever) mqwcl or qwcl. Same problem with Fuh 0.31, ezquake 1525 is a bit faster.

This is on my older computer, which is rather slow ( p2 400mhz, 64mb, matrox millennium).

I'm just wondering which ingredients/changes from 0.29 to 0.30 made the fuh so darn heavy.

if it takes 20 minutes to disconnect from a server, why not just close the client instead of waiting for the disconnect?

i take it you mean seconds, not minutes

i would be worried if it really is minutes )

yes, it's minutes.

if i accidentally press "reconnect" during game the game is over untill i'm back.

Empezar, If I quit it still disconnects, or atleast it's takes forever to quit when i'm on a server.

You can imagine that this is sometimes a bit irritating.

Regarding the 20 'minuites' thing - probably 24bit textures. pngs, pcxs, tgas, jpegs for every model and wall texture in the game. there's a commandline parameter to speed it up a bit by disabling all this stuff. -no24bit or something. The more game directories you have, the slower it'll go. A fat32 filesystem doesn't help.

i assume he's talking about the software client so external textures wouldn't be an issue

correct