ProQuake 3.95: Digitally signed for cheat-free

[PapaSmurf]

Any idea why my sensitivity is completely different than in gl 3.5? When I use 3.95 my sensitivity is set the same, yet it feels so slow compared to 3.5

are you using direct input in 3.95 and not in 3.5?

[lennox]

are you using direct input in 3.95 and not in 3.5?

no.

[R00k]

m_directinput ? default 0 or 1

[Baker]

Any idea why my sensitivity is completely different than in gl 3.5? When I use 3.95 my sensitivity is set the same, yet it feels so slow compared to 3.5

There haven't been any changes to the reading of the mouse so mouse movement is identical.

Some things to check:

1. is your sensitivity set the same?
2. make sure directinput is not on in the menu (if you don't normal use that)
3. Make sure your vsync and maxfps settings are identical.
4. What is your command line?

Or could post your 3.50 config and the config 3.95 outputs and we could look at them.

[Baker]

Download: ProQuake 3.96 - 0.8 MB

Source code is available here

In 3.96:

- r_farclip added (defaults to 16384; for large single player maps)
- command line parameter -noassocdem to disable automatic file association with .dem


To do list:

- Check into refresh rate and 60 hz default
- When opportunity permits, look at d3d version some more
- remove vid_conwidth and create new scheme; add to menu
- quit procrastinating and fix outstanding international keyboard issue
- implement DarkPlaces/Quakeworld tcp/ip stuff that will make -ip unnnecessary for clients
- add transparent HUD option
- make 3 changes necessary and release FitzProQuake 3.96

Plus:

1. Pester woods to jack to the max edicts and recompile Mac ProQuake
2. Quit being a weenie and make a Linux ProQuake already ... sheesh!!!

[Canadian*Sniper]

You weenie! Thanks for adding the -noassocdem option

[PapaSmurf]

what does -ip do in the command line? I've never used it.

[Baker]

what does -ip do in the command line? I've never used it.

If you have more than 1 ip address available, it specifies which one to use.

In the case of my DSL example, the 169.254.x.x address (which is ALWAYS invalid) is listed as connection 0, and Quake wants to use that one.

For a server, there might be several valid ip addresses available. For a client, you just want it use a valid one that is the proper address for TCP/IP.

A casual player should NEVER have to deal with this or even know what it is.

[PapaSmurf]

i've never dealt with it or know what it is. i'm still not exactly sure as to when you need to use it.

[Baker]

i've never dealt with it or know what it is. i'm still not exactly sure as to when you need to use it.

Good. And soon I hope, no one else will ever deal with it or know what it is

If you've had the problem, and I know numerous people who have had it, you sure don't want it.

[PapaSmurf]

i don't even know what the problem is. Are you trying to specify to quake what your ip address is? If so, why do you need to do this? My ip address has changed on me before, and it has never prevented me from connecting to a server.

[Baker]

The problem occurs only if you have 2 ip actual addresses. (Someone's ip address changing isn't related to this at all; in that case you still have only 1 ip address but it changed.)

This can occur if:

1. You have dialup + a LAN
2. Just DSL that uses PPPOE and not using a router (my example); the DSL modem occupies ip address #0 and the PPPOE connection uses ip address #1.
3. 2 network cards
4. Some other combinations

Someone using cable is not going to have this problem (typically) and if the DSL uses PPPOE and is authenticated by the router then someone isn't going to have this problem.

[Phenom]

Baker,

Your client has made major changes since the last version I tried 3.92, I actually feel comfortable using it as my main client now its almost identacle to 3.50's feel to me.

I have some graphical and some bindings issues though.

My game looks kind of washed out almost like the contrast is to low, this is probably just fixed by some fine tuning but so far i haven't been able to get a crisp image yet, i'll report back on this

Secondly, for some reason I can't bind MWHEELDOWN and MWHEELUP which I use for weapons, am I missing something?


P.S My mouse periodicly locks up for a half of a second? just noticed this while in a game
Great job! This is one of the best things yet for Quake in the recent years

Also is there a way to make console text bigger?I play Quake in window mode @ 1280x960 and it shrinks my console down to almost unsee'able size thanks!


D:\Quake\glpro.exe -zone 1024 -dinput -mem 32 -nojoy -nocdaudio -noipx

ATI Radeon 9800Pro 128MB dvr 8.442.0.0 (WHQW)

[=peg=]

using 3.96 i get a major fps drop when taking pentagram (from 200-ish to 70-ish)

that cant be a good thing.. can u see if u can fix that baker?

edit:
i did some more testing and this also happens with quad.. not with ring however..

also setting viewblends to classic or deathmatch in the menu does not make any difference..

[Baker]

Your client has made major changes since the last version I tried 3.92, I actually feel comfortable using it as my main client now its almost identacle to 3.50's feel to me.

I want it to feel exactly like 3.50 but more refined. I know that some of the earlier versions (3.70 series) didn't feel right, especially with the particular gamma correction I used.

I have some graphical and some bindings issues though.

My game looks kind of washed out almost like the contrast is to low, this is probably just fixed by some fine tuning but so far i haven't been able to get a crisp image yet, i'll report back on this

If you use -gamma command line parameter, it will look *identical* to ProQuake. The downside, you cannot adjust brightness in the client (it will tell you this if you try).

If you don't use the -gamma command line parameter, it will use hardware gamma correction which almost, but not quite, looks like ProQuake's gamma correction.

(There are actually 2 separate gamma systems in the engine; it was tedious to setup, but I think it is worth it if you are anal about wanting it to look the same even to the slightest nuances).

If you don't use -gamma, there is an unadvertised gl_contrast cvar you can play around with in addition to the brightness slider. I didn't mention this because I wanted to follow the "keep it simple, stupid" philosophy.

Secondly, for some reason I can't bind MWHEELDOWN and MWHEELUP which I use for weapons, am I missing something?

I'll check into that.

P.S My mouse periodicly locks up for a half of a second? just noticed this while in a game

Doesn't seem likely that would be the fault of ProQuake 3.95.

Great job! This is one of the best things yet for Quake in the recent years

Also is there a way to make console text bigger?I play Quake in window mode @ 1280x960 and it shrinks my console down to almost unsee'able size thanks!

Type vid_conwidth 640 in the console.

using 3.96 i get a major fps drop when taking pentagram (from 200-ish to 70-ish)

that cant be a good thing.. can u see if u can fix that baker?

Try using the -gamma command line parameter. If you don't, it uses hardware gamma and has to do some extra work. Or add -bpp 16 to the command line?

NOTE: GL ProQuake 3.95 defaults to your desktop color depth setting (usually 32 bits per pixel)! ProQuake 3.50 defaults to 16 bits per pixel, which is faster. Add -bpp 16 to the command line for faster 16-bit performance. The reason 3.95 defaults to the desktop resolution is for compatibility and it can switch from fullscreen to windowed mode.

viewblends to classic or deathmatch in the menu does not make any difference..

That isn't gl_polyblend; those are the ProQuake viewblends, like ring hue, water hue, quad hue, pent hue.

If you set it to deathmatch, the screen doesn't go halfway green when getting an envirosuit, etc and instead goes about 10% green. You see more clearly.