Rune Central

1. I love the default settings. Console transparency, effects, well thought out.

2. No +mlook/-mlook commands. Mouse is always on.

For Qrack's intended audience --> good players, this is great. (I hate to see something like in JoeQuake though, there are keyboarders out there )

I have always thought it was annoying that Quake for some reason can't save +mlook to a config so you have to make it read only.

3. No +speed / -speed commands. This is nice, but cl_forwardspeed and cl_clsidespeed and cl_upseed aren't defaulted to 999 so you must manually type those into the console:



4. -conwidth and -conheight parameters don't work. In 640 x 480 mode, no big deal. In 1024 x 768, the console letters are microscopic and the hud characters are smaller. I like to use conwidth-512 -conheight 384 with 1024x768 resolution.

5. With some of the old JoeQuake Pro releases, under some circumstances I could cause it to crash if I played multiplayer and then did Single Player, New Game. I wasn't able to cause this to happen in 1.52 but I will keep my eye out.

6. I noticed a default hunk allocation of 32 MB ---> good idea. (I would hate to have JoeQuake do this, there are old computers with Win 98 and stuff and JQ will run on them).

Hunk allocation of 32 MB is the same as -heapsize 32768 or -mem 32. If you use high resolution textures, in my experience if you are not using -mem 32 with JoeQuake the sound gets all jerky at times.

Without the high res textures, like if you are using -nobit24, you don't really need the -mem 32, but most newer machines have plenty of RAM.

7. QRack has just about every ProQuake feature in it (pings in status bars, loc support, identify and even the pq_teamscores thing). I didn't check for some of the more obscure ProQuake features like mouse button 4 support.

8. I noticed on initial launch an error message buried in the startup log about couldn't load coronasa8 image (a typo in the source?)

9. SputnikUtah has added some extra effects. I noticed them, but couldn't tell you what they all are (I know coronas + outlining are available because Yellow No. 5told me once).

2. No +mlook/-mlook commands. Mouse is always on.

3. No +speed / -speed commands. This is nice, but cl_forwardspeed and cl_clsidespeed and cl_upseed aren't defaulted to 999 so you must manually type those into the console:

4. -conwidth and -conheight parameters don't work. In 640 x 480 mode, no big deal. In 1024 x 768, the console letters are microscopic and the hud characters are smaller. I like to use conwidth-512 -conheight 384 with 1024x768 resolution.

5. With some of the old JoeQuake Pro releases, under some circumstances I could cause it to crash if I played multiplayer and then did Single Player, New Game. I wasn't able to cause this to happen in 1.52 but I will keep my eye out.

6. I noticed a default hunk allocation of 32 MB ---> good idea. (I would hate to have JoeQuake do this, there are old computers with Win 98 and stuff and JQ will run on them).

8. I noticed on initial launch an error message buried in the startup log about couldn't load coronasa8 image (a typo in the source?)

2. No +mlook/-mlook commands. Mouse is always on.

the new cvar is m_look [0/1] default is 1, and its saved to config.cfg.

There is +speed/-speed. But has changed.
If cl_forwardspeed =< 240 (default walk speed) then pressing +speed will run faster. But if you have ALWAYS RUN ON, your cl_forwardspeed > 200 thus +speed will slow u down, since you cant run any faster... +speed aka togglespeed

The 32meg Hunk is a Maximum. You really wont need more mem for the hunk. Basically used for mod data and server aliases etc...
Qrack uses a dynamic memory scheme much like virtual memory in windows. It will use as much physical memory as it can to keep it running efficient, but after 32megs it caches to the HD in a temp file. Ie, all that texture mem wont use all your physical memory, current map memory will be in ram the leftover is in the cache file.

Note MAXIMUM_WIN_MEMORY does jack shit.
With glquake + 24bit textures, 95% of the game's memory is due to the OpenGL library handling textures. MAXIMUM_WIN_MEMORY has nothing to do with this, it is for memory that quake allocated directly itself. In the 'old' days MAXIMUM_WIN_MEMORY (i.e. hunk) actually meant something useful because 95% of quake's memory was on the hunk. These days hunk only plays a small role.

odd, it looks for 10 corona files... and assigns them if available. and randomizes the images for each lightsource.