but it seems FMv has turn the wrong direction.

Why in the world the engine has to install the mods instead of you?

i don't get it. What's next, the engine that playing the game instead of you're?

there's more and more similarities between this engine and DP (no double penetrate confused) 

I could add a command line parameter that disables those 2 commands.

The main purpose is to allow the Quake server in a LAN coop game to share the archive to other computers.

Instead of downloading each map, model, sound.

Which doesn't work for single player releases because:
1) Skyboxes. QuakeC doesn't know about these.
2) .lit files. QuakeC doesn't know about them.
3) Other misc files that are part of a single player experience that is a .mdl, .spr, .bsp or .wav

I know most people don't care about coop, but it is a major interest of mine. 

This is actually a Very Good feature.

For the likes of you and me it's unnecessary. For the casual player or newcomer to Quake it's absolutely essential. Installing mods, making sure you get the right files into the right directories, setting up dependencies - these are all huge barriers and while you may think they're basic enough, you'd be surprised at how much difficulty the non-technical end user can have in getting them done. Even something as simple as getting the engine executable into the correct directory is something I've personally witnessed people having trouble with. 

Pretty nifty feature, not entirely sure if I will use it really since you have to know what you're looking for beforehand. If there was a way to browse before you install.

Could be worth having a list feature, maybe "install list"? While we're on the subject of lists, I can't remember which engine had the feature but it'd be cool if there was a way of having things in the console have rows/columns rather than say 1 item per line. (like if you remember in DOS you could put /p /w and it would fill the screen so you didn't have to scroll so much). 

i'm really sorry for my expression. 

For the casual player or newcomer to Quake it's absolutely essential.

Actually i'm not sure the newcomer that never installed the mod in a "proper way", would install the mod via console command using the engine. 

A feature that definitely IS for newcomers is the "Levels" menu option. I absolutely love it since it makes level packs that come without start map (e.g. one of the Retro Jam releases) very easy to use. You can choose any map without using the console at all.

The bottom line is: If you really want the feature to be accessible, it may need to work via the game menu. 

How many newcomers does Quake 1 get these days? 

More than usual, just judging from this thread.

I don't really agree that a menu option is top priority, though. 

Kind of interesting to reflect on what you'd want to do to make a perfectly accessible engine for a newcomer to Quake; say someone who took up gaming in the last 5 years and only has experience of Steam.

You'd probably want to ensure that they never have any interaction with the directory structure, the command-line, configs or the console. That's basically how Steam functions, even if you're playing a game with mods. You just launch the game through the Steam UI, and if you want mods, you just double click stuff on the Workshop and it all installs automatically, never leaving the Steam interface.

So for Quake, you'd want the source port to come packaged in an installer (a single exe in a single exe sounds absurd, but as mh said, putting the engine in the right place isn't necessarily obvious to a newcomer to Quake) which the user just double clicks and it detects where Quake is and puts the exe in the right place, then creates a shortcut on the desktop. Maybe it could come packaged with Quake Injector too, as a means of ensuring that downloading and installing mods is all menu driven, rather than fiddling with rars and zips and the directory structure, with the Injector also creating its own desktop shortcut.

Afaik Quake Injector doesn't have any means to set up the correct command-line switches automatically though, so that would be an issue. I know some engines - FodQuake for sure - do away with the command-line entirely, so instead of having -heapsize etc, it just allocates memory correctly on the fly. That would probably solve a large percentage of command-lines required by mods.

Another interesting idea would be to actually get all that on to Steam through Greenlight. There are various old HL and HL2 mods up there now which you download directly through Steam servers, and Valve's long term plan is to allow basically any kind of software on Steam, so it'd be an interesting first to see if a source port could end up on there. =)

That way people who have Quake on Steam would likely find themselves directed through Steam's recommendation system to any custom Quake engine available on Steam, rather than being stuck with broken glQuake or having to trawl round the web searching for engines which they won't know how to install.

If something like that was in place, you could play Quake and any mod without ever touching anything other than desktop shortcuts/Steam UI and in-game menus, which would certainly make Quake future proof and more accessible to a wider audience. 

I see that some silence has returned to this thread. :P

Well, just dropped in to say that I am finished with my basic Mk V testing sessions.

I checked these:
- Quake + mission packs
- Nehahra
- Travail
- Shrak
- Malice
- Abyss of Pandemonium
- Beyond Belief
- Honey
- Rubicon Rumble Pack
- ne_ruins
- Rapture
- Soul of Evil
- Soul of Evil: Indian Summer
- In the Shadows
- Retro Jam 1-3
- Func Map Jam 1+2

Good news: No problems with any of these actually - besides the remaining issues with Shrak (white skin textures) and Malice (fov crash in map d15).

I will check some Quoth and Drake missions, but I am confident Mk V will do fine here, too. :) 

I'm glad to hear it!

Haven't had much to talk about because I've been working away on the to-do list and items in this thread.

But I'm only about 70% done, so late next week is likely when the next version will be out. 

How do I load from the autosave? I press F9 and it loads from the manual quicksave. 

Type load and the press a and then TAB.

You'll see a0.sav, a1.sav and a2.sav

(I need to give them better names but initially I didn't call them auto_save because some single player releases with autosave tend to use a name like auto_save.) 

a0 = newest, a1 a few minutes older, 2 a few minutes older than that. 

should probably load the latest autosave... Or the last autosave should show up in the load menu. Either/or will do. 

The last Quakespasm update at Quaddicted says Baker ported a MarkV feature into Quakespasm. I know he's involved in both projects. So, what are the differences between them? 

I am sure Baker can tell you all the differences instantly. For me, the most important difference is actually that Mk V can run Nehahra. And that's amazing.

Hoping that Baker eventually gets back to working on the new version. Still waiting for the Shrak/Malice fixes. ^^ 

Yah , Nehara is good.

MarkV is a windows project, with more experimental/fancy features. QS is multiplatform and, perhaps, more solid. 

Is the fog problem in Neh2m5 fixed? 

Is there any way to limit the game fps to 72 without syncing to the monitor refresh rate? My monitor only does 60 Hz. Also, with vsync on, there's some weird lag going on.

DirectQ has this feature, but unfortunately, it also has an annoying issue where the player will start sinking into the floor after some time of playing. 

Host_maxfps should do it 

Thanks, that's it! Still unplayable with it set to 72 though; quite jerky. I guess I won't be playing e3m2 with this engine. Everything else seems fine though! 

The software stuff is really exciting because it's the only software port besides super8 that can load big maps and it's much more faithful than super8. Do you plan on adding the interface scaling from regular Mark V/QuakeSpasm? The HUD is unreadable at 1920x1080.

Come to think of it, if you could implement colored lighting, interface scaling, and fog into the WinQuake Mark V executable, it would instantly make super8 obsolete and it would make me very happy indeed. 

Any news about a new build, btw? I am still waiting for those Shrak/Malice fixes (see #826 and #855). :P