Haha, you know what ... 1080 vs. 1024, that's a mere 56 pixels. A quick look and I dug up some Engoo/QBism/Makaqu threads and it appears that isn't going to explode anything. 

Beta 12 - Windows GL | WinQuake

1) mp3 status events don't print for developer 1
2) Increased the maximum vertical resolution for WinQuake to 1080 (in theory -- can't directly test).
3) ericw's lightmap precision changes + alloc block speed up from Quakespasm implemented.
4) Max edicts is gone. As a client it always uses 8192. As a server it uses 8192 if running FitzQuake protocol 666 (the usual) and standard Quake's limit of 600 if serving a protocol 15 game.

Later on, I'll upload the Mac version and updated source.

Thanks for all the help in testing all of this! 

Interesting , because protocol 15 can handle up to 8192 edicts correctly 

that's a subjective statement. while the protocol might be able to cope with up to 32k ents, the implementations of that protocol may only support 600.

seeing as vanilla nq will safely handle its limitation, I would personally say that the server should just use 8192 even with protocol 15, because its better to soft-crash outdated clients than the server.
fte filters entities over the assumed client's limit because invisible entities is probably better than soft-crashing anything. if the client supports the proquake 16bit angles thing, you can generally assume the limit is higher. heuristics can always be wrong, of course.
of course, fte is crazy, and filtering reliably is a whole load of work that I can understand not bothering with (svc_setview! oh noes!), in which case imho your server not crashing is more important than your clients not crashing. 

For protocol 15:

FitzQuake 0.80, if I recall bumped the max edicts from 600 to 1024. JoeQuake uses 2048 if I remember correctly. WinQuake and GLQuake use 600.

My thoughts were if someone was going to run in protocol 15 mode as a server, they would probably want to ensure anything original Quake could connect and play. 

No crash in "Nehahra's Den" any more with max_edicts limitation gone. So much for the good news.

Unfortunately, the game now crashes to desktop a bit later when entering the next/last map (nehend). This also happens when you directly try to go that level via menu or with +map nehend, so it's not related to the previous boss fight.

Nehahra savegames and autodemo (932 KB) to demonstrate the problem

At the end of that level (nehahra), mp3 music from id1 dir is played during the level statistics and the following episode ending screen. This interferes with the actual background music, maybe it can be fixed still even though it is a minimal issue? 

To be more precise, the following Nehahra levels now crash directly to desktop when loading them:

neh1m9 "To the Death"
neh2m6 "Your Last Cup of Sorrow"
nehend "Quintessence"

Also, ID1 music generally plays in all the levels, except for when the game searches for tracks 00 and 01, but cannot find them in the music folder within the id1 directory. 

Could you check a timerefresh command. I think it's broken. 

timerefresh is broken in pretty much any modern engine, isn't it? If not, it is completely useless on any modern hardware anyways. Use timedemo. 

@ NightFright ...

1) music + crashes

Nehahra isn't supposed to use the mp3 music or cdtracks, just the .xm tracks with fmod. I need to check the behavior there, but I bet if you temporarily remove your music tracks it won't crash. Clearly, I need to fix that so it doesn't try to play both.

2) Nehahra finale text --- interesting. Apparently Nehahra draws too many lines to display for the finale text (i.e. isn't backwards compatible to Quake minimum resolution of 320 x 200, which the menu is based on). I'll figure out how to address.

@spy ... I'll fix timerefresh. Thanks for finding that. There really is no reason why that shouldn't work. 

Really odd thing: I checked Nehahra again at home on my other PC, and neither do I have crashes there nor does it play MP3s and XM tracks at the same time. Hard to figure out the differences of the PC setups. Ofc the hardware isn't exactly the same. Hmmm... I am running the game in windowed mode in the other place. Will look into that. Still, it cannot hurt to make sure Nehahra will never use MP3 music from the ID1 folder.

So far, I have tested Mk V with:
- Quake + both mission packs (MP2 50% done) --> OK
- Travail --> OK
- Nehahra --> Intermission text length, missing fog
- ne_ruins --> Succubus resurrection crash

I also remember that the commercial TCs Shrak and Malice had some issues with Mk V at least one year ago (Shrak: crashed for me when using rocket launcher sometimes, Malice: crashes in pre-final level when killing Vasquez). Will look into those again as well, even though I am not sure you'd be willing to check this if I find anything. Those addons are not very common, and at least Shrak isn't the most popular, either. 

Does Succubus resurrection still crash ne_ruins? 

Succubus crash still happens, though not right after the first resurrection any more. Can take 2-3 now before you are going back to desktop.

I also still see quite some error messages, e.g.
302 models exceeds standard limit of 256
291 sounds exceeds standard limit of 256
111 lightmaps exceeds standard limit of 64
605 edicts exceeds standard limit of 600

Not sure if these still have any meaning, though. I play with -heapsize 524288 parameter. 

Demo and autosave please. Please, please. 

Here we go again:
ne_ruins autodemo/savegames (335 KB)

You can ignore the manual save(s). The quicksave will bring you straight to the situation with the succubus and the knights as seen in the short autodemo. God mode is activated.

Regarding the text length issue:
Actually, MP2 is also affected (e.g. at the end of episode 1). Maybe either use a second screen if texts are too long or simply make the game show all the text in any situation. I doubt that anybody still players in 320x200 these days, anyway. 

I've tried 15 ways to get it to crash, had tons of monsters resurrected, played your save game, watched your demo.

Also played ne_ruins for who knows how long (45 minutes?) couldn't get it to crash.

Does it just crash to desktop or does it say Host_Error or something? 

It's a straight crash to desktop without any error (besides the standard Windows thing "Program doesn't work any more"). Maybe it's again a hardware-specific issue (e.g. I have nvidia cards in both PCs I use).

In my autoexec.cfg, I have
gl_texturemode "gl_nearest_mipmap_linear"
r_shadows "1"
r_waterquality "32"

Here's the config.cfg from my ne_ruins folder.

I tried to more things which didn't change anything:
- Switch to fullscreen mode
- Move "ne_ruins" folder from "addons" subdir to Quake root dir (i.e. Quake/ne_ruins instead of Quake/addons/ne_ruins) and run it from there 

The good news: your config completely crashes me. 

The "exceeds standard limit" messages are warnings, not errors. I always get confused about that too. It means the engine warns you that engines without raised limits won't be able to load it or show errors. It's the "developers 1 for content creators output". 

It may be one of the settings applied through the config, then. But even with a default config file (wiping my customized one from ID1 folder and creating a new one from scratch when running ne_ruins afterwards), it doesn't fix the problem. 

@frightnight

I don't have an exact answer for why it is crashing for you. (It isn't for me, although I run out of memory without using a massive -heapsize 512000 because of your use of gl_subdivide_size which does look incredible with r_waterripple).

I think the use of several aggressive settings like gl_subdivide_size 16, a huge memory allocation, possibly mp3 music (and maybe model/sound replacements?) on the bunker-busting ne_ruins in aggregate is causing an unusual stress point somehow.

I notice you are using gl_texture_anisotropy 16.

gl_subdivide_size 16 is using ridiculous amounts of memory on ne_ruins.

Maybe you created the perfect storm and doing it with ne_ruins is piece of straw that breaks the camel's back. 

In my ID1 folder, I have the following additional PAKs:

- pak2.pak (.lit/.vis files for ID1 maps)
- pak3.pak (OriOn's fixed MDLs)
- pak4.pak (improved models by capnbubs/Lunaran)
- pak5.pak (E2M6.bsp with Romero's enhanced entrace included, .vis and .lit file)

Download the PAKs above here (11.3 MB) and put them into ID1 if you wish to try. However, since you said the config file is already enough for you to get the crashes as well, I hardly believe those files are to blame for it. 

But if you upload your id1 folder + your ne_ruins folder somewhere I'll try to see the nature of the problem. 

Ah, you just posted. I'll try your packs. 

Or nightfright could start from a clean installation himself and work step by step to find the culprit. Don't burn out, baker!