KMQuake2 set-up

[Berzerker]

OK I'm back at trying to get this to work
I figured out the colormap.pcx and now I get this:



Couldn't find maps.lst
which maps.lst is it looking for the one in the pak files ??
do I need to use pakexplorer or Qped to unpack the file ?? And where do I put it ?

[spirit]

I think your problem is the glGetError thingie. Guess it was already there before the colormap and maps.lst stuff, you can ignore those two I think.

Maybe the q2 video mode is set to 3dfx while it should be opengl. fix it in the config.

maps.lst is only a textfile that holds the map list if you're running a server. a valid maps.lst can look like this:

quake2/baseq2/maps.lst:

q2dm1


as I said I doubt that this is your problem though

[Berzerker]

it is set to opengl
I got it to start but again its like its in slow motion it takes 5 mins to get to the loading screen. and when it gets there it like its stuck. You know the sound you get when you scroll from game to multiplayer or video as your going through your menu that little thud well it keeps doing that without touching it. And when I do finally get it to load when its done it either stops before it finishes loading or loops back !!

[spirit]

Your problem sounds as if your video card was not detected and the game ran in software-mode.

I have no idea whether that's true but I think I read that q2 has problems running with the latest nvidia video drivers.

The maintainers of multiple modern q2 engines said they had fixed the issues, maybe you should try another q2 client.

[knightmare]

I've also fixed that nVidia driver crash in a hotfix. And when it does happen, it won't cause an error that shows up in the console, it will crash outright.

It looks like your OpenGL driver may be crashed or not installed (i.e. falling back on Windows' default software OpenGL driver). And that it can't find maps.lst is a sign of a really screwed up Q2 installation, maybe with a corrupt pak file or problems with file permissions.

There's a copy button that copies the entire contents of that debug console, you should use it and post it here.

[Berzerker]

I have an ATI video card and everything seems to be set right. I have two QII's on my computer one in C:\QuakeII and one in my Quake IV folder thats where my ground zero and the Reckoning are which is actually C:\program Files\Id software\QuakeII. The first one starts and is slow, So I put it in the other and when I try to start it I get a path error:



So I don't know whats happening

[spirit]

Hm, sorry but I have no idea neither. But I can tell you that I also bought that Q4 special edition with Q2 included and I never managed to get the q2 version that came with it to work. Neither on my Windows XP box, nor on the Vista box of my brother. I ended up copying Q2 from a friend. No problem since I got a license but still annoying.

[knightmare]

It's either the length of that path or its use of spaces. The Q2 engine has a hard-coded maximum length of 128 chars for the path of any file it tries to open, and I don't think it was coded with filenames with spaces in mind.

Try moving your Q4-bundled Q2 install to a different folder in the root of your hard drive (such as C:\Quake2).

The optimal approach would be to have a hard drive partition just for games, instead of installing them to C:\Program Files. This way you won't need to reinstall most of your games the next time you format and reinstall Windows. The Q2 install I'm using dates back at least 10 years over 6 hard drives in 5 different systems.

[Paril]

I agree with KM, the Q2 path was intended to be x:\quake2\, and a lot of tools and docs state that for proper working-ness that's what it should be, although most new engines can handle now-standard paths (EGL is the one that springs to mind). Looking at your error message, it seems you have single quotes around the path, but one double-quote on the left; is this a bug in the message box or the way you set up the shortcut?

-P

[Berzerker]

Nov 30, 2009 0:53:13 GMT -5 Paril said:

I agree with KM, the Q2 path was intended to be x:\quake2\, and a lot of tools and docs state that for proper working-ness that's what it should be, although most new engines can handle now-standard paths (EGL is the one that springs to mind). Looking at your error message, it seems you have single quotes around the path, but one double-quote on the left; is this a bug in the message box or the way you set up the shortcut?

-P

Didn't notice this I will change it and see what happens

Thanks paril