ProQuake 3.95: Digitally signed for cheat-free

[Baker]

Thanks! Yeah, only a couple of changes remain and everything is looking very solid. Just need to work thru the -dinput thing and the international keyboard issue.

Then look into the mouse issue Lennox has.

[=peg=]

how about a command/cvar to change the character used for crosshair?

then i could make a custom charset with red, blue, yellow, green colored "+" in it.. and bind that to the "1", "2", "3", "4" keys so it will always make my crosshair the same color as my team color in team games (CAx, team dm, ctf)..

this way there is no need to fiddle with the rendering

[Baker]

I'm thinking about it and will probably reluctantly do it.

The thing is, certain features don't seem very ProQuakey to me. For instance, I added cl_sbar off and transparency and that isn't ProQuakey at all.

So I think I will add this feature at some point quietly but not put it in the menu.

About 99% chance I add this.

/Extra note: -dinput plus -window issues look like they are about to be solved. Oddly enough, and this will only mean something to someone who works on engine code, but Con_SafePrintf must be used during mouse initialization so I can't even do Con_Printf("DirectInput Initialized\n") without it messing up the mouse initialization. Con_Printf causes GL_EndRendering to print text on-screen, which can interrupt mouse initialization because GL_EndRendering fiddles with the mouse a little.

Strange and touchy; this was not what I expected the problem was, heheh

Now I understand why FitzQuake has Con_SafePrintfs all over the place but JoeQuake literally has none, due to the video mode switching.

[PapaSmurf]

gl_smoothfont 0 doesn't save. Everytime i load up glpro399 it reverts back to gl_smoothfont 1.

Also, it would be nice to separate the fontsize of the console from the console resolution size. For example, you could have a small console resolution, but not have huge console fontsize.

[Baker]

gl_smoothfont 0 doesn't save. Everytime i load up glpro399 it reverts back to gl_smoothfont 1.

Also, it would be nice to separate the fontsize of the console from the console resolution size. For example, you could have a small console resolution, but not have huge console fontsize.

gl_smoothfont is a command right now, I could make it a cvar though.

Btw ... did my workaround with cl_sbar < 1 solve the sbar problem?

Also, it would be nice to separate the fontsize of the console from the console resolution size. For example, you could have a small console resolution, but not have huge console fontsize.

I might look into this, DarkPlaces and Qrack let you do this.

[Polarite]

Good job Baker !

The gl_interpolate_model_animation and r_interpolate_model_transform seems to
work without a bugg now.

[PapaSmurf]

Btw ... did my workaround with cl_sbar < 1 solve the sbar problem?

no, but i'm not worried about it anymore.

[Baker]

no, but i'm not worried about it anymore.

Did you try the latest version?

I'm still worried about it.

Good job Baker !

The gl_interpolate_model_animation and r_interpolate_model_transform seems to
work without a bug now.

Good. I haven't tried it lately, but I've been tightening the code up. I must have fixed it on accident

[PapaSmurf]

I tried the latest version, and there is no change. I'll try and explain what occurrs. When I alt-tab back to my desktop, it seems as if it is trying to draw two screens on top of eachother.

Also, I just noticed that this only happens when i'm running 1680x1050 resolution in glpro.

[Baker]

I tried the latest version, and there is no change. I'll try and explain what occurrs. When I alt-tab back to my desktop, it seems as if it is trying to draw two screens on top of eachother.

Also, I just noticed that this only happens when i'm running 1680x1050 resolution in glpro.

I care about this because this means I don't understand enough about the sbar update code to know why it's doing this. It must be something small that I am missing.

I will keep looking at it.

It is important for things like this to be fixed.

[Baker]

Download: ProQuake 3.99q - 0.8 MB

Source code is available here

All mouse issues should be fixed, including mousewheel not triggering binds with -dinput and -window mode.

Short list of remaining things for 4.00

1. International keyboard support and the keypad (and see what can be done about the binds)
2. cl_sbar <1 ALT-TAB issues with Scott's video card at 1680 x 1050 resolution.
3. wqpro status bar acts funky sometimes.

Possibility exists that cl_sbar is temporarily removed for 4.00 and re-added in 4.10; a final stable 4.00 is needed

Future possibilities/todo list (unlikely to be in ProQuake 4.00)

Have gl_smoothfont save to config (not as easy as it sounds)
See if ALT-ENTER plus dinput can be smoothed out; the reinit causes the screen to jitter a little.
CTRL + -/+ brightness, SHIFT -/+ viewsize
maps and demos commands that display JoeQuake-like maps/demos menu
.dz support
Have demos automatically .dz compressed upon completion of recording?
maybe a dir command
colored crosshair option
Optional ability to cap maxedicts to standard Quake 600 for -dedicated server
Investigate old winquake issues with cursor/window positioning with -window and particularly dual monitors
Better/easier diagnostics
Configcopy or copyconfig command
Check into command line cvar
URL catcher for MM
Consider using a standard place for screenshots and demos
extra help screen
rook's admin mute capability
RQuake support (sv_dmflag)
Quit! command for -dedicated servers
thread prioritization

[Baker]

Download: ProQuake 3.99r - 0.8 MB

Source code is available here

New features (from FuhQuake):

1. Disable the annoying windows keys (sys_disablewinkeys 1).
2. Change ProQuake thread priority (sys_highpriority 0 = normal, 1 = high, -1 = low) ... Note: this doesn't save to config as I have a feeling someone that doesn't know what they are doing can cause trouble with that.

Also: http://www.quakeone.com/proquake is going to ProQuake's new home. You can still get to the ProQuake Launcher home page by clicking a picture of it at the bottom of the page.

[Fuzznut]

I got an idea for future versions of proquake. Can we update the interface for the 'identify' command? instead of having to type out 'identify' <insert name here> just click on a name and select the identify function?

Or has this already been done and I'm not aware of it?

[Baker]

I got an idea for future versions of proquake. Can we update the interface for the 'identify' command? instead of having to type out 'identify' <insert name here> just click on a name and select the identify function?

Or has this already been done and I'm not aware of it?

Sometimes I am wondering whether or not all servers shouldn't just hide the ip address like shmack: 26001 and shmack:26002 does, except for those running the servers.

Actually this would make a good thread topic.

Have "public" servers with the ip address shielded and private servers for matches with it not (to be able to confirm identity).

[Fuzznut]

Sometimes I am wondering whether or not all servers shouldn't just hide the ip address like shmack: 26001 and shmack:26002 does, except for those running the servers.

Actually this would make a good thread topic.

Have "public" servers with the ip address shielded and private servers for matches with it not (to be able to confirm identity).

That's fine. Let the server keep its secrets. I was just wondering about the identify command, not status. I'd like to be able to click on a name and have it identify/list all the other aliases that IP has went under, even if it never tells me the IP, or even the partial IP that it currently does.

And another thought/request. Would it be out of the scope of the project to consider implementing the easy(so I hear) movie/video making functionality of Darkplaces?