Unofficial "ProQuake" 3.70 - Stable

[PapaSmurf]

ProQuake version 3.70? Surely the only person that can upgrade ProQuake is Grossman....

that's why it's called the unofficial proquake.

[Baker]

Some notes really just for me:

Small stuff todo ... not features or anything most people care about, mostly annoyances to fix:

1. I find it annoying that "WinQuake" doesn't center in windowed like GL does.
2. Fix wqpro can't restore after minimize if I haven't AND if this actually happens.
3. Revisit the code that automatically determines resolution in GL; it is starting at 800x600 on a display where I expected 640x480.
4. -window mode in GL should smart size the conwidth/conheight (if not specified) just like it does fullscreen to avoid microscopic letters.
5. Make -novsync command line parameter for now until working on reset of vid mode code
6. Hardcode the -/+ keys for sound volume, no one in their right mind uses -/+ to change the viewsize ... those are terrible Quake default keys. Only if console is not open.
7. Make wqpro able to go on the second screen of a dual monitor setup just like glpro can.
8. How to do shift on the fly brightness in an easy to understand way without using more keys?
9. Have goto menu trigger the Nvidia ALT-TAB fix? And check windowed mode also. On rare occasions I can get the glpro window to "mess up" if I try really hard to confuse it and then it is stuck like that. A console command is meaningless if I can't actually see the console.
10. change pq_* cvars to cl_* cvars? Like pq_maxfps becomes cl_maxfps, pq_drawfps becomes scr_drawfps (?). Make legacy cvars as commands so someone doesn't get confused by the change? Or make both work?
11. Somehow address the default zoom_in/zoom_out aliases in Quake; they are terrible and only good for messing up your setup.
12. Make wqpro use default 640x480 resolution for windowed mode
13. chase_active 1 bug in wqpro; ProQuake has this but WinQuake does not. Determine why and fix.

14. Make sure -window mode does not use the whole available screen space in dual monitor situations and never allow the screensize to be greater than the actual screen. Same with conwidth.

15. Make tilde, semicolon and so forth show as the bind key in the menu,

[Cataklysque]

Some notes really just for me:

Small stuff todo ... not features or anything most people care about, mostly annoyances to fix:

1. Transparent HUD
2. Fix wqpro can't restore after minimize if I haven't AND if this actually happens.
3. Revisit the code that automatically determines resolution in GL; it is starting at 800x600 on a display where I expected 640x480.
4. -window mode in GL should smart size the conwidth/conheight (if not specified) just like it does fullscreen to avoid microscopic letters.
5. Make -novsync command line parameter for now until working on reset of vid mode code
6. Hardcode the -/+ keys for sound volume, no one in their right mind uses -/+ to change the viewsize ... those are terrible Quake default keys. Only if console is not open.
7. Make wqpro able to go on the second screen of a dual monitor setup just like glpro can.
8. How to do shift on the fly brightness in an easy to understand way without using more keys?
9. Have goto menu trigger the Nvidia ALT-TAB fix? And check windowed mode also. On rare occasions I can get the glpro window to "mess up" if I try really hard to confuse it and then it is stuck like that. A console command is meaningless if I can't actually see the console.
10. change pq_* cvars to cl_* cvars? Like pq_maxfps becomes cl_maxfps, pq_drawfps becomes show_fps (?). Make both work.
11. Somehow address the default zoom_in/zoom_out aliases in Quake; they are terrible and only good for messing up your setup.
12. Make wqpro use default 640x480 resolution for windowed mode
13. chase_active 1 bug in wqpro; ProQuake has this but WinQuake does not. Determine why and fix.

I fixed your list

Impressive attention to detail Baker.

[PapaSmurf]

R00k just made a transparent HUD for Qrack; it has the QW transparent hud (weapons on the side) and the traditional transparent HUD.

[Cataklysque]

My only hope of having a transparent HUD on quake.crmod.com is through this client. I do enjoy QRack on other servers.

[Baker]

My only hope of having a transparent HUD on quake.crmod.com is through this client. I do enjoy QRack on other servers.

Yeah, but that isn't true. This isn't your only hope.

quake.crmod.com is the last remaining signficant server that runs ProQuake cheat-free mode, but we all know it is common knowledge that you can cheat on cheat-free servers.

If ProQuake cheat-free can't stop cheating anymore, what sense does it make to have a server running it? Neil made a bot that can play there, many players used that opengl32.dll wall transparency cheat, especially last summer.

Perhaps you and other regulars at quake.crmod.com should consider asking the server operator to remove the cheat-free to allow you to play with the client of your choice. It sounds like you much prefer Qrack, being accustomed to the appearance of Quakeworld clients like ezQuake and FuhQuake, and that you only use ProQuake because you "have to".

5 years ago, someone doing amazing things on a cheat-free was proof positive to me they were legit and not cheating.

Today, cheat-free doesn't mean anything to me and I don't feel those servers are any more cheat-proof than any other server.

Some options:

1. You could ask Slot Zero (email address: slotzero --| at |-- @runequake.com) to remove the cheat-free from quake.crmod.com so that players can use their client of choice. ProQuake/Qrack/DarkPlaces/JoeQuake/this/whatever. Maybe he would do it, maybe not but the worst he could is say no.

2. Slot Zero had a non-cheatfree port 26001 a few months ago. You could ask him to move the cheat-free to port 26001 and make 26000 a non-cheat-free port. Maybe he would do it, maybe not but the worst he could is say no.

3. Maybe your luck will turn out and Grossman will digitally sign my unofficial 3.70. I haven't heard back from him from the email I sent 5 days ago. Maybe the email address I have is invalid, maybe anything with the word "Quake" in it goes to his spam folder.

4. Maybe with information provided to me by LordHavoc and Neil -- who have both defeated cheat-free themselves (it took LordHavoc 15 minutes to do so), I can make it connect to cheat-free myself. What does this say about the cheat-free?!?!?!?

5. For $28 per month for 16 players, someone could get their own CRMOD server in St. Louis and run it in non-cheat-free mode on the same box that quake.crmod.com runs on.

This isn't your only hope. :d

[Net-Tyme]

is anyone else seeing the lag icon in the latest version 3.7?. I didn't have this issue with 3.6 but now have it with 3.7?

[golden_boy]

The source fails to build on Linux. It may be because I'm drunk, but sadly the error messages are pretty clear.

Reason: Lots of things reference winquake.h, which in turn includes ddraw.h, windows.h, dsound.h and stuff like that, which my Gentoo doesn't have.

I remember Proquake 3.50 compiling OK. Must be, because I'm regularly running that.

-> you guys broke something?

Nice try though, I'd love this to work...

Oh and Baker, next time can you please zip the folder, not the individual files? When Unzipping it just dumped all the .c and .h files in my root directory... that's a minor nuisance.

[Baker]

The source fails to build on Linux. It may be because I'm drunk, but sadly the error messages are pretty clear.

Right now, the Linux doesn't build. I added some operating system dependent code (demolist, maplist, time) that use the file system or windows.h.

It may be because I'm drunk, but sadly the error messages are pretty clear.

When I get time, I'll be addressing that because I want this to work on Linux as well.

Btw ... I don't have Linux. Can you post the log? It would make the process of making the Linux compile work easier, it shouldn't be a great deal of work for me to fix that.

[foq]

I would just like to report that when I tried to use it, it seemed to be stuck on 640x480 even though I had the correct command line paramaters set, it had no support for Vsync (I saw alot of tearing too), and somehow it changed the behavior of my dude in the water (like on FVF, if you fly, and you hold space, you fly forward really fast, but I had to reinstall my Quake cause this, even after deleting it, caused my flying character to rise straight up from the water while fly mode was enabled)

[Baker]

I would just like to report that when I tried to use it, it seemed to be stuck on 640x480 even though I had the correct command line paramaters set

What command line did you use? 3.70 never overrides the user supplied -width or -height, but if you typo one of those, it will look thru the available video modes and select one.

it had no support for Vsync (I saw alot of tearing too)

That's known and I posted this in the thread.

and somehow it changed the behavior of my dude in the water (like on FVF, if you fly, and you hold space, you fly forward really fast, but I had to reinstall my Quake cause this

You must have turned on "jump is moveup". :d pq_moveup 1|0 is a feature in ProQuake and when enabled makes it so you can move up much faster in the water.

This is why some players (that have a great config) move much faster than other players (that don't). I put "jump is moveup" in options to level the playing field.

[Baker]

Note to self:

Add to do list
----------------
- REAL cvar resetting like DarkPlaces has. I hate it how "Reset to Defaults" does not truly do that.
- Do not allow a user to set gamma 0 in software renderer. An all-white screen where you can't even read the menu is pointless.

[PapaSmurf]

Baker, have you fixed the lighting issue in version 3.7 yet?

[Baker]

Not yet ... by release 3.80 it will look exactly like ProQuake's lighting at any brightness setting.

I am focusing on some different things before I want to get back to things pertaining to video/rendering. I expect by this time next week it will be done.

[foq]

There was no typo, and I can assure you I was using -width and -height, and I went into video options to see if there was something overriding my command line, and 1024x768x32 was selected, but it looked like 640x480...