The music code is probably attempting to detect and react to changes in the bgmvolume cvar. If it hasn't changed from it's default of 1 then it won't set things up properly.

A weird quirk of the .dem file format is that everything in it is binary, with the exception of the CD track number which is plain text. Carmack must have been eating funny burritos that day. 

You may have failed to embarass Microsoft and Google by not delivering whatever it was you wanted to do (never cared tbh), but there are a few bugs right here, waiting to be squished by you... 

I play MarkV Winquake (so the software version without z-buffering issues of the OpenGL branches) at 1920x1080 and runs perfectly smooth and fine with music etc.... The only issue I have is with TINY UI and fonts.
Would be great an update with UI zoom factor. 

Have you tried different settings for Autoscale in the preferences menu? 

You may have failed to embarass Microsoft and Google by not delivering whatever it was you wanted to do (never cared tbh), but there are a few bugs right here, waiting to be squished by you...

No, I totally have not failed to deliver this thing you don't care about.

I, Baker, am now the creator of a programming language and development environment that runs on everything and by my accounts better than everything. I had to level up about 200 times to do it, and if it is super hard -- I like it!

I have some interesting choices I need to make, and I think this beer is going to help me figure it out.

I will say that I am a bit touched that despite a couple of years of "developer inactivity" that this thread is still getting love and attention touches me. It makes me think I am right to care a lot about Quake --- which I do. 

But a lot has happened with Quake ports in the last few years. Any plans of bringing Mark V up to speed? TBH I am only using QSS these days because Mark V cannot run all maps any more. 

@Joel B
>Have you tried different settings for Autoscale in the preferences menu?

That option is for the OpenGL (MarkV, not MarkV Winquake version) only :(
That's the only "issue" with the amazing winquake software rendering version, which runs so smooth and without Z-Buffering issues etc. 

Do you have a Discord account, a Twitter, an e-mail address or something where we could stay in touch? 

if that's already all we read from Baker for the next 1-2 years again. Sadly. 

Is the WinQuake version of Mark V a true software rendered version or is it some shader type of thing? 

It's purely software rendered, no GPU required.

Its support for big maps is quite impressive, and I was hoping to ask him a few questions about that, but nevermind. 

thanks - this is helpful 

is mark V still being updated? Because I can't seem to find a build from later than 2017/2018 

nope 

In a few months maybe, for one post. That's it. He's not going to work on this any more. 

 

this is awesome! thanks Baker

> enhanced server capabilities
Could you elaborate a little bit? prediction? unlagged? 

also, does this build on linux? 

This hasn't been updated since 2018. 

I know this hasn't been updated since 2018, but recently the Winquake version of Mark V no longer launches for me since a year ago after a windows or graphics driver update I assume, as I haven't changed anything. It starts up then crashes immediately with a stopped working box. I tried updating NVIDIA drivers but it didn't help. I was wondering if anyone else had the same issue or is it just me? 

I think the Winquake version is DirectX right? They might have updated DX and borked it. Might be helpful to know the message on the error. 

There is no specific error message, all it says is 'mark_v_winquake.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.' 

Works perfectly fine for me. Windows 11, fully updated, Intel graphics.

I know that doesn't solve it, but by identifying that it can work it helps you to divide up the problem and reduce the list of possible causes.

Next step I'd suggest is that you try a clean install of Quake - just PAK0 and PAK1, empty config. Let's see if that works and we'll see what to do next.

(FYI - I am of course NOT the author of MarkV (although I did contribute code), I'm just doing this to be helpful.)