of also moving r_shadows and r_waterquality variables into config.cfg?

I find it a bit complicated to set them externally through autoexec.cfg. And since texture filtering has already been moved... 

I've been really enjoying the winquake build, it runs very well. I ran into this little guy after I disabled mips. He's harmless but has worn out his welcome :) 

just found "showram".

Whenever I get stuck on something I just make a forum post or drop a message on irc so 30 seconds later I can figure it out myself :P never fails. ever. 

Don't know, but I'll think about it.

I worry about mods changing obscure things, causing niche settings to write to config.

Examples:
1) quake.rc, autoexec.cfg
2) QuakeC

Case in point, Malice messes with untold numbers of weird cvars like viewidlescale that most users have never heard of.

Imagine if you exited and everything saved, all those peculiar settings would be part of your config and short of reseting/deleting your config, you wouldn't know how to reset them.

I'll think about it.

But my instincts tell me that no matter what, someone with very specific tastes is always going to find something that needs to be an autoexec.cfg 

Mods will only affect the config in the mod's directory tho. 

Mods should be properly set "gamedir" and yes everything saved, including .sav files .dem and .cfg to that folder.A footprint to a gamedir should mean anything I do here when i quit should save to gamedir. 

that's true except, when you switch gamedirs during a session, the cvars and aliases and keybinds are retained, and when you eventually quit that session they will be written to the last gamedir you switched to. 

Some people use game command (i.e. "game travail"). Some people like R00k probably use gamedir capability more for CTF.

And although no small number of people use the command line either from habit or because of the Quake Injector -- there are those that use "game travail" way.

And these different set of circumstances have to be factored in. 

when implementing the command in fitzquake, i considered writing the config to current gamedir, clearing all values to default and then loading the config in the new gamedir as a way to resolve this, but it could have negative results such as changing your video mode or mouse sensitivity, or other settings that the player doesn't expect to be per-mod.

The core problem is that some settings are global user settings and some are mod settings and there is no formal distinction between the two.

Most experienced players don't feel too much pain from this since they have autoexec.cfg files that force the correct settings (of course this breaks down when a mod includes an autoexec!) 

These are major things that, in addition to the topics noted above and earlier in the thread, are likely to be goals in the spring.

List of some different future possibilities

1. Coopable 3D "Quake Injector" built-in, concept Undergate screenshot About everything needed to finish the concept is in the engine already.

2. iPad/iPhone/Android versions with Minecraft-like controls (Minecraft is very playable on an iPad). I played the awesome Kurok mod for Quake FitzQuake version on a PlayStation Portable and am not likely to be satisfied until I can play Quake on at least an iPad and also like it.

I also did tons of engine modding of PSP Quake engines, so yeah I'm not pleased about not being able to Quake on devices.

3. Kurok capability screenshot. I have added almost every required capability into Mark V, but a small few remain.

4. Multiple-players, same computer. working prototype demonstration. This means studying Microsoft's XInput for game controllers, because the working code does not have the needed input support.

5. Spiked Quakespasm's super-compressed protocol. I like demo rewind and will have plan out right way to achieve it.

6. Playing .zip archives without ever decompressing them. i.e. Travail .zip never gets unzipped.

7. LAN Co-operative peer-to-peer multi-threaded download of required files (Like the client downloading "travail.zip" from the server). Would make LAN co-op setup even easier and Mark V already has a ton of co-op capabilities. Mark V actually has a beta form of capability disabled in the engine for polishing.

(Note: Even a 70 MB download is nothing on a LAN. Over LAN that file could have downloaded hundreds of times while I typed this sentence.)

8. A re-written sound caching system to allow changing sndspeed between 11025, 22050, 44100 at any time.

9. Native Linux without SDL. Will add better support for video capture, hardware gamma.

(Might adopt Spirit/jdhack's Requiem Engine decision to use fmod for mp3 playback, but I still haven't explored all the mp3 options, including some of ericw's thoughts.)

10. Other things mentioned elsewhere in the thread, I'm sure. 

Yeah, exactly. I've invested some time and energy into ideas on how to sort out those issues. 

"when you switch gamedirs during a session, the cvars and aliases and keybinds are retained, and when you eventually quit that session they will be written to the last gamedir you switched to."

Uhh, I just tested, and Mark V does not actually do that. Well, I mean, it does carry over settings, but all config changes seem to save to the directory you started in, always, not the last dir you were in when you quit. But if that's the way you are starting the mod every time, I guess you would end up with all your config settings each time you play anyway....

Though I don't think that's the correct way to go about it.

I'm with Rook on this -- let each game dir house its own cfg stuff for that mod. And I still say it should automatically exec that config stuff upon changing to a new gamedir. This would allow the user to keep settings for each game truly separate. And if someone changes to a new dir, it won't carry over config stuff from a previous dir that perhaps shouldn't apply (assuming there's a setting for the mod that should supersede an old setting -- just retaining defaults is fine). And it wouldn't (shouldn't) save config stuff you change while playing that mod back to the base id1 folder (as it does now if you start in id1 and manually change to the new dir).

So yeah, each game dir should have its own configs, really, which override anything from outside that game dir. And when you quit, the config for your current game dir SHOULD save within that game dir.


I could illustrate a problem with the current approach:

Start Quake normally (plain id1). Let's say you have normally bound "shift" to cycle weapons. Then you want to play FvF or something with a grapple, so after you change "game fvf" and "bind shift +hook" then you quit the game, it saves that binding back in your id1 flder....
Now if you want to play normal Quake again, you have to rebind the shift key.

If it saved your (now altered) bindings in the fvf folder, you wouldn't have a problem. And if it would exec all the configs from the folder you changed to, it would all be set up automatically the next time you change to the gamedir....

Then that would make everything work consistently in the same manner no matter what method someone uses to select a gamedir:

starting:
"marv_v -game fvf"
would behave identically (loading configs) to typing in the console:
"game fvf"

Wouldn't that consistency be better? 

If someone uses the game console command (i.e. "game travail" or such), they start out in id1.

Then switch to travail.

Obviously, if you always start up in id1, you would want any changes to video resolution or setup to also apply to id1.

Since id1 is the config run on startup, yeah, that's where it should save too!

If someone uses -game whatever from the commandline or the Quake Injector, the config saves in game whatever just like you would expect. 

Mark V saves settings every time you exit the settings menu or the console.

So if you wonder why no matter what happens, everything is always saved the console history is always up-to-date.

That's why!

/I prefer to not mention these little niceties and polish-ups because I just consider it part of polish.

Like how Mark V forces a WASD default key setup and makes the mousewheel do previous weapon/next weapon by default. 

makes me want to rip out my autoexec cfg and do some gamedir testing... i think if i do a gamedir AD then my current gamedir should save config.cfg first switch dirs then load config.cfg from there, and vice versa. I hope this is the case already if not i'll have to change it. I have added a writealias command that dumps an alias.cfg for each gamedir but the user then has to make an autoexec.cfg to exec alias.cfg or maybe i should make it do that automatically...hmm 

my levels menu doesn't work in the quakespasm folder. I have the quake HRP and the menu graphics change. What does this? In the DP folder works fine.

DX9 version is great, it kills on my R9 280.

Also what graphical things are supported? Just unpacked textures? Can it ever support things like dp pretty water? 

Is it possible? 

"Single"

"New Game"
"Load
"Save"
"Levels" (Only appears if nothing above graphically replaced)
-----

So if an exceptionally rare mod (X-Men, for instance) replaces a graphics there ...

Or if a user is using high definition graphics for those menu items ...

Rather than present the user a "Levels" graphic that clashes with the appearance of the menu, it simply disables itself ;-)

I'm just rather picky and I'd rather have menus that look nice than a menu with an item that clashes with the rest of the items on-screen. 

Mark V can save multiplayer games, including co-op games which was the main target.

/If it isn't working, let me know. 

Also what graphical things are supported? Just unpacked textures? Can it ever support things like dp pretty water?

QMB particle option in menu, MH waterwarp (defaults on), MH volumetric shadows (r_shadows 3).

The Open GL version (not DX9) has a raw test implementation of bloom that needs more work in the future.

Eventually, it'll be run through the gauntlet, maybe possibly sometime in the spring, but not necessarily because isn't high priority item.

External textures use the same names as DarkPlaces. Mark V only supports .tga files. 

That would need a VERY significant overhaul of the entire renderer.

It might not be immediately obvious, but DP pretty water needs shaders. Then you're in a position where, in order to have other effects be consistent, you have to implement *everything* in shaders.

Another thing is: the reason why DP runs slower is because it does all these effects. If you start with another engine that runs faster, port DP's effects to it, then ... the other engine will also end up running slower. End result is that somebody's time has just been wasted in rewriting DarkPlaces.

I've always been of the opinion that it's a big world and there should be room for lots of engine options in it. Each engine has different goals. If you want to "pimp my Quake" then DarkPlaces is the engine for you, but other engines don't share that goal to the same extent. 

DX9 version is great, it kills on my R9 280.

MH did an incredible job with the DX9.

One of the rare (and fun) examples of something going from simply non-existent to polished in just over 3 weeks.

The awesome beta-testers here who help out and provide fast, high quality feedback is unimaginably helpful to engine development.

Most incredible beta-testers ever! Engine development is hard, but smart detailed-oriented testing can take quite the edge off! 

Lol, I had no idea. I thought it was like standard quakes implementation. Plus the save option sits under the single player menu 

Stuff like DP dies on AD, down to 7fps. Other games, ie Q2, Q4 run much better at the same resolution with HD and extra effects cranked.

I've had the best luck with this engine and quakespasm spiked.

For instance ad_fuma... markv/dp = slowdown right at the start by the lift. markvDX9 = smooth.

>QMB particle option in menu, MH waterwarp (defaults on), MH volumetric shadows (r_shadows 3)

I found the particles and if waterwarp is on by default I just have to try the shadows. My transparent water in QSS has issues rendering, wrong things or distant things will show up.

>>Rather than present the user a "Levels" graphic that clashes with the appearance of the menu, it simply disables itself ;-)

I wish I could override this. Typing map is somewhat of a substitute. I do 1080P on a 42" screen so I really like the high res. See your point on shaders though; I remember playing quake and quake2 on voodoo2 back in the day and to see it keel over with a quad, 16gb of ram and a card faster than the original PC is shocking. 

Remove or rename gfx\sp_menu.tga (or gfx\sp_menu.lmp) and will probably load, if that is what is going on.

Possible (non-ideal) workaround.