Unofficial ProQuake 3.80 (Stable?)

[Baker]

Download: Unofficial ProQuake 3.80 - 0.5 MB

What's new:

1. Reverted to GL ProQuake 3.50 style gamma correct (command line only).
2. Automatic 8 button mouse support under Windows.
3. VSync ON|OFF works (GL only, in Advanced Settings menu).
4. Automatic conwidth and conheight adjustment to avoid historical GLQuake "scrunched" characters.
5. Increased maxedicts so if Linux/Mac versions can be made, more single player maps can be played using the client.

In addition, this version should not have any Linux-unfriendly changes in it.

Main pre-existing features in this engine:

- freelook cvar
- customize controls menu is a lot cleaner (everything is in there)
- FOV fix for affected video cards.
- ALT-TAB fix for affected video cards.
- Pressing - and + adjust sound volume
- +zoom capability (bind mouse3 +zoom)
- Hold down CTRL or ALT for bronzing (making names in console)
- Automatic international keyboard support (from DarkPlaces)
- cmdlist and cvarlist commands
- Many other bug-fixes and small features (see change.log for all of them)
- optional improved weapon invisibility effect (transparent gun instead of darkening of the screen)

Source code is available here.

To my knowledge, this is a stable release with no bugs. If you find any issues with it, please let me know.

Some secondary features, like demo-rewinding, gamedir switching and animation interpolation have been removed from this version and will return in later releases. I want to make sure everything can compile on Linux before re-implementing more complex features.

[PapaSmurf]

I like the volume up volume down thing, but maybe you should put it on the kp_minus and kp_plus keys. The "-" and "=" keys were always sizedown and sizeup, respectively. I also noticed, that even with "bind = sizeup" in my config, it gets overridden to volumeup. My "bind - sizedown" doesn't get altered, however.

Edit: I'm also getting a line that reads:

"" Isn't a valid key.

I don't get this when run glpro, only when i run glpro380, and I'm execing all the same files.

[Baker]

I noticed the "" isn't a valid key. I'll get that fixed. I'm not sure the cause, but it has to be a simple and easily fixed typo.

I like the volume up volume down thing, but maybe you should put it on the kp_minus and kp_plus keys. The "-" and "=" keys were always sizedown and sizeup, respectively

Well, I don't believe sizeup and sizedown have an practical value in a game, do you? The only reason to my knowledge that sizeup and sizedown are even used is to hide the HUD for screenshots and that's in the menu anyway and anyone doing that knows the cvar.

In the next version, pressing ALT + (plus)/(minus) will do the sizeup/sizedown function and CTRL + (plus)/(minus) will adjust brightness.

[Baker]

Target features for next release (probably sooner rather than later):

1. Ability to change/set resolution in-client (like FitzQuake and the latest Qrack)
2. Authentic looking in-client brightness controls
3. "default_fov" feature from FuhQuake so any "FOV 90" received from a server is interpreted by the client as "FOV (your normal FOV)".

[Bong]

Its a nice update for proquake, but why can't I join cheatfree servers ?

[Baker]

It's not digitally signed by Grossman, so it cannot connect to cheat-free servers.

No one seems to be able to contact Grossman and cheat-free is compromised by opengl32.dll cheats that allow wall hacks.

I think there will probably be a new cheat-free in the not so distant future that incorporates the modern and actively developed clients.

[PapaSmurf]

Baker, I just think if you're going to introduce new standards on key bindings you should do it on never before used keys (in winquake/glquake/glpro), namely the numpad keys. This way you will not interfere with whatever people have done with previous keybindings, ie the "-" and "=" keys.

Other people might have say macros assigned to their "-" and "=" keys, and it would be quite annoying if the client overrides this. I know you can exec a config while in game to get back to one's original setup, but I like setting up my autoexec and command line execute commands to get my setup the way I want it. The way it is now, it makes my setup for these two keys obsolete, and I have to re-exec my config in-game to get it back.

I'm a bit confused, however, because one of the keys stays to how I have it in my config, but the other switches to volume control. Not sure why that is.

[Baker]

Download: Updated 3.80 with that "" isn't a valid key issue fixed.

Baker, I just think if you're going to introduce new standards on key bindings you should do it on never before used keys (in winquake/glquake/glpro), namely the numpad keys. This way you will not interfere with whatever people have done with previous keybindings, ie the "-" and "=" keys.

Other people might have say macros assigned to their "-" and "=" keys, and it would be quite annoying if the client overrides this. I know you can exec a config while in game to get back to one's original setup, but I like setting up my autoexec and command line execute commands to get my setup the way I want it. The way it is now, it makes my setup for these two keys obsolete, and I have to re-exec my config in-game to get it back.

I'll think about this more and see I figure out an ideal solution.

[Bong]

It would be great if I could switch azerty to qwerty instead of the default azerty now.

[Baker]

I'm not sure what you mean?

/Unless you are using a non-US keyboard?

[foq]

3. VSync ON|OFF

[Phenom]

Just tried PQ3.80 on my integrated intel graphics card and the sky texture is visible but ALL other brushes are pitch black, explosions show up just fine though?

Outside DM3 next to Pentagram

[Baker]

Does ProQuake 3.50 have this issue as well, or is it just this version?

/Note: Phenom is currently using a very low end system and gets really low FPS (12-60) with every engine.

[Phenom]

Does ProQuake 3.50 have this issue as well, or is it just this version?

/Note: Phenom is currently using a very low end system and gets really low FPS (12-60) with every engine.

Same exact thing in PQ3.50

I have got Qrack 1.83 to work and winQuake so far... But I haven't had ProQuake working on this PC yet

[Baker]

Well, that sucks

The rendering code between GLQuake/ProQuake vs. Qrack are radically different. I don't believe there is really any way I could determine why GL ProQuake does this and Qrack does not.

This machine I use has a Intel Integrated Media chip and will not run any OpenGL Quake engine (I get a black screen; I have dual monitors with the other monitor using a GeForce.), but GL ProQuake works fine on some other Intel Integrated Media PCs I've used.

Does my Direct3D build work on your machine:

http://www.quakeone.com/proquake/uno...-d3dpro370.zip

If so, I will quickly re-add Direct3d support for 3.80 for you. (Direct3D versions do run on my Intel Integrated Media).