"Cvars "deathmatch" and "coop" not reset when loading a SinglePlayer game."

In function Host_Loadgame_f() of host_cmd.c, look for...
#ifdef QUAKE2
Cvar_SetValue ("deathmatch", 0);
Cvar_SetValue ("coop", 0);
Cvar_SetValue ("teamplay", 0);
#endif

DarkPlaces certainly doesn't have that "fix". DarkPlaces can save multiplayer games!

One of the biggest annoyances in coop ... let's say two people are playing, say, Travail or some single player deal that absolutely cannot be played non-stop in a reasonable period of time ...

How do you save and continue that game?

Well ... you don't. Because you can't. 

Well, that's not an answer but random sidetracking.

FWIW, hexen2 does reset those cvars when beginning to load because it also can save net games and it actually saves those vars along so they are restored to their intended states. Therefore hexen2 is immune to that funniness whereas quake is not. I don't know how dp handles the situation. 

I thought about bringing up that.

Quake's save game system is intended to save the state of the server.

And as you, it doesn't because it does not save the cvars. And this creates a real mess. Since server-side cvars belong to the QuakeC modder, any given one could be used or abused in a mod. Some mods use cvars in unexpected ways or use them for "inter-level storage" or for hacks and so forth.

Any attempt to "solve" the problem is likely to break something, any attempt to alter the behavior is likely to break something.

One idea is to make and/or propose a save game 1.10 format or just do it. Some people might say "your engine save game files cannot be read by <my favorite quake engine>", but that is mighty uncommon. [Can save files fail in other engines gracefully based on version? I have not checked ...]

Although I have absorbed quite a bit of information in 5 years of paying attention to these kinds of things, my level of experience on the technical aspects of these matters is way below a metlslime, FrikaC, Necros, Spike, MH, leileilol type of 15-year expert. 

One of the more fun aspects of engine development is the freedom to fix/correct/enhance/play around without regard to exact compatibility.

DarkPlaces is an example of an engine that doesn't worry about breaking things versus, say, FitzQuake which is so conservative as to require typing +mlook in the console for mouse look.

This isn't the golden heyday of Quake and most of the mods that would get broke by "fixing" stuff probably rarely get played.

JoeQuake did this by stating that the engine was intended for use with id1 Quake and the 2 mission packs.

If you want to stick with the mainstream use of engines like id1, Quoth, Warpspasm, Mission Packs and DMSP/Frikbot kind of stuff ... do it.

An engine being developed is more important than a few oddball mods from 14 years ago that no one uses. Besides, that's what bug reports are for.

I might have too much influence from aguirRe and Spirit, aguirRe was very big on compatibility and assisted me a lot when I started engine coding and more or less kept me from breaking standard behavior on accident. 

...It's quite possible that RMQ is going to require an extended save game format shortly. One issue we've definitely encountered is use of "stuffcmd" to set some cvars and other things (like v_cshift) which are not being retained across sessions (or are being retained when they shouldn't be if the player changes or reloads the map). That's probably something more appropriate for a fuller discussion on I3D but I think it would be a good idea to at least co-ordinate efforts as this is a common enough problem with mods in general. 

can get around that easily with unsaved variables which you can use to force a cshift check on loading maps.
for loading new games, just put a catch all in putClientInServer or something.
in an older mod (which i lost) i was storing cshift in a .vector and .float on the player (rgb + intensity).
this allowed me to blend multiple colour shifts together and then use normalize on the rgb vector to keep things for washing out. 

One of the things I have been working on with the "game state" is the end of the game state.

v_cshift obviously as a cvar does not reset upon the end of a map or when the client does "disconnect" or a QuakeC error or a client error that causes a disconnect state by error ("model xyz.mdl not found").

Have also been working on what cvars may be sent to the client. Well, actually not what ones that may be "sent" ... but rather ones that the client will acknowledge that either a server or demo may alter and the mechanism to reseting these upon "disconnect".

This is to finish a far more complete concept of "gamedir switching". 

I have updated the Mac OS X release of QuakeSpasm to 0.85.5. The binary works on Mac OS X 10.4 and up on 32bit and 64bit Intel and 32bit PPC systems.

Download here: http://quakespasm.sourceforge.net/download.htm 

In QuakeSpasm 0.85.5 for Windows, Shambler's lightning animation is not lerped (interpolated, smoothed). It's the only thing that's not smooth, even if you clear the "r_nolerp_list" cvar. 

That's intentional, QS doesn't interpolate when an entity goes into a muzzleflash frame. 

Version 0.85.6 of QuakeSpasm is released.

Happy new year to all. 

QS v0.85.6, WinXP:

- if you Alt+Tab out of game, MWHEELUP and MWHEELDOWN cease to function. also, gamma resets to zero but that's a classic OpenGL issue, I believe

- if the zoom function (default key: F11) is used, mouse sensitivity resets

(but still the best engine :D) 

the F11 zoom behavior is a bug in default.cfg isn't it? 

yeah, iirc, the f11 is just a basic alias that has a present sensitivity setting. you need to overwrite that yourself to match your original mouse sensitivity. 

It will sound noobish, but where exactly is default.cfg located? Can't find it in any of Quake's directories, is it in a PAK file? 

Is in a PAK file, yeah. And it is an old bug from 1996; the zoom aliases eventually reset sensitivity to 3 (IIRC) and because default.cfg is forced on you your only real option is to put aliases into your autoexec that override these (does QuakeSpasm exec quake.rc or the 3 .cfg file? Can't remeber right now, but quake.rc is another potential source of evil). 

there's nothing wrong with quake.rc;
quake.rc just execs the config files, nothing more.

anyway, what you want to do is open up your own config.cfg file and add this to the end (or anywhere, really...)

// zoom
alias zoom_in "sensitivity 2;fov 90;wait;fov 70;wait;fov 50;wait;fov 30;wait;fov 10;wait;fov 5;bind F11 zoom_out"
alias zoom_out "sensitivity 4;fov 5;wait;fov 10;wait;fov 30;wait;fov 50;wait;fov 70;wait;fov 90;bind F11 zoom_in; sensitivity 3"
bind F11 zoom_in
and change the sensitivity values appropriately. 

Hmm.. is it possible to have back the playtime in status bar without recompiling the engine? 

Mods can and do contain a custom quake.rc that sets cvars and issues commands itself (e.g if a mod wanted to force water alpha it might add "r_wateralpha 0.4" to it's quake.rc after exec'ing the configs). 

right, it's there to provide a way to add in custom commands without messing with autoexec and config.cfg.
i did that myself with ne_ruins. i enforced developer 0 by running a config file after stuffcmds, for example, because in the past, players had tendency to play with developer mode on and then complain about console spam. :P 

AguirRe had a set of commands built in to pause rewind and FF demos.. haven't got around to asking him the how yet. 

JoeQuake has demo pause, rewind, fast forward.

Demo pause is an easy engine modification. Likewise, so is fast forward will more or less changes the timing of a frame similar to how host_framerate does or the FitzQuake host_timescale cvar does.

Demo rewind ... and I haven't looked at this code to think about it in 5 months or so (I was trying to get interpolation to work right in reverse. And I did (or at least so close the couple of remaining flaws would never be casually noticed). At least with everything except dynamic lights fade timing.) ...

But if memory serves correctly, it builds a stack of locations that point to the demo read positions of the previous demo frames within the demo. So to play in reverse, instead of going forward it picks the previous location from the array and uses that. And if there is no previous location, you are at the start of the demo.

You also have to create an extra "client time" storage unit because cl.time is still important for things like sounds ... you cannot play sounds in reverse so they still need to end after X seconds and only a "forward-only" time instance can do that. In fact, this is also true of particle animations and some other things. But there is also the "demo neutral time" that can go backwards and this should be used for reversible events like animation interpolation, movement interpolation, the display of the clock if you press TAB to see the true time in the demo, etc.

Also, by looking at the current demo read position and comparing against the length of the demo file, you can estimate the percent of demo playback to show a demo progress bar (!!!). 

Start the engine with "-fitz" option restores playtime in statusbar, among a few other things 

I never understood why the game time display was removed from QS. It's fairly useful, unlike the skill display. This would be better off as a console setting instead of a command line switch.

aguirRe's demo script was an alias config that had the cursor keys increase or decrease host_framerate by by 0.1 steps. No rewind, only fast forward and slow motion. 

I ported JoeQuake's demo rewind code a while back. It was ... "fun".

I think that Fitz's host_timescale is an infinitely more sensible option than host_framerate for controlling demo speed, but of course it needs engine support.