I read a bit further in the docs and I am right -- DP added stereo sound playback for mods. 

stuff like this is why I made QSS convert stereo to mono on load.

also, change sndspeed to anything other than 11025 and that will disable quakespasm's low-quality filter. 

To save myself the headache of changing precache file paths in the qc when merging in from mods, I kept the files in the same folders.

This had the drawbacks of not being able to tell which files came from which mods as well has name conflicts.

So...might be a while before I can tidy up and get a comprehensive list to find those again. 

Don't sweat it. I can peruse the files and check on my end if they are included in keep. 

Version 0.93.1 of QuakeSpasm is released.

http://quakespasm.sourceforge.net/download.htm
http://sourceforge.net/projects/quakespasm/files/

Changes since the previous version:
https://sf.net/p/quakespasm/news/2018/06/quakespasm-0931/ 

And what about that old quakespasm.pak that have date 1 march 2016, while the newest version (?) is 27 june 2017? 

It seems like the PNG screenshots that QS writes are larger than they have to be? If I resave them in Paint or Paint.NET the file size is halved with no apparent difference in quality.

Also, I would greatly appreciate an option to disable the "wrote xxx.png" message. 

Also, I would greatly appreciate an option to disable the "wrote xxx.png" message.

And why does that bother you? 

speaking for myself:

When taking multiple screen shots in a row to perhaps catch a monster in a specific position, for example, you have to wait for that message to go away or to use host_timescale to slow down monsters.

When I have r_drawviewmodel 0 and crosshair 0 for screenshots, itd be nice to have some sort of way to avoid all on screen prompts and such. 

You can freeze monsters at will. Mark V has the freezeall command and other engines have sv_freezenonclients 1 

The large PNG's are intentional to try to limit hitching. They're compressed in the main thread of the engine, and default settings of png libraries I tried caused unacceptably long freezes in the game (like 0.5 seconds - 1 second depending on the resolution.)

If we moved the PNG compression to a background thread, we could use good but slow compression settings - this is just more work to set up.

Agree with a cvar for hiding the "wrote" message. 

Sometimes I like to take multiple shots at once, but then the best "takes" have the message printed on them which isn't too good aesthetically. 

There is a cvar called "con_notifytime" or similar which controls how long the console text appears at top of screen. Try setting it to zero, maybe even make a alias that sets it to zero before your screenshot and then back to default after? 

Thanks, metl. That works. Doesnt show on screen but still shows in the console so one can confirm screenshots have been taken. 

What mukor said. I've never seen a screenshot with the message showing. Maybe an older version of QS? 

examples of prompt displaying in screenshots 

One way of handling this is, rather than taking the screenshot immediately, just flag an "scr_screenshot" qboolean to true, then run SCR_UpdateScreen and if scr_screenshot is true selectively suppress certain UI elements. Finally glReadPixels and capture the screen. 

hmmm... 

yes, taking one screenshot wont display the message in the screenshot.

spam the screenshot key and youll get the message in the screenshot.

some people implement real world photography concepts into screenshots and one of those concepts is to take a quick series of images to then pull the best one from.

Think of skateboarding where they use shutter speeds to capture the whole trick then pick one of the pictures to use on the cover. 

heres a GIF with this in action:

https://i.imgur.com/Xe2Jd1U.gifv 

http://www.quaketastic.com/files/screen_shots/rrp_start5.gif 

yup, now I see it 

are these last few posts just one big troll?

you know the "clear" command is a thing yeah? clears the console?

bind F12 "screenshot;clear"

does what you want I think? 

metlslimes suggestion of "con_notifytime" is better than using clear, imo. 

reading that back again sounds a bit patronising, but I think it's a valid solution for now.

Maybe the fact it clears the console history doesn't make it a perfect solution.