So yea... this guy has an MD3 version as well... I convert him to MDL afterwards.

I would love to include a more precise version for folks to use in Quake Spasm in the future. If that lovely tech gets added then I would just for joy.

https://media.giphy.com/media/Jjbb0HlG6KgGA/giphy.gif 

OK here is my wishlist:

What are the chances of sticking in a simple external file read/write ability, accessed via QuakeC?

Something a bit like this? http://www.quake-1.com/docs/quakesrc.org/144.html 

I posted it in the thread for the new Q1SP map, but whenever I try to start a game with this new updated client, the game exits to the desktop. Anybody know what's going on? 

Is this with the "Experimental build" in the oms3 thread (quakespasm-rf6d[...].exe)?

Argh, crash to desktop is the worst. No error message / dialog I assume?
Could be some dll conflicts.
If you don't mind trying a clean setup, this could help: create a empty directory. Extract all files in the QS zip. create an "id1" subdirectory in the same dir, and copy your pak0.pak/pak1.pak files to there. 

Haven't tried with the one in the oms3 thread, just the newest one in this thread and on the quakespasm site, 91 i believe. I'll try a clean install when I get the chance and report back. 

Alright so making a clean install didn't work either. To answer the previous question yep, no error message at all, just exits to desktop. 

Run it from a cmd window, might show something 

quakeisdead, ok, thanks.

Did a previous version of QS work for you?
There are 4 QS build to choose from for windows, 32/64-bit and SDL1/2 - which are you trying, or do all fail? the full download list is here: http://sourceforge.net/projects/quakespasm/files/Windows/

One thing to check is enter "gl_info" in the console. It'll print a bunch of GL extension info, but scroll up with PageUp and check the GL_VENDOR, GL_RENDERER, GL_VERSION.

Another idea is launch with the "-condebug" command line option (create a shortcut and put it in the end of the target field.) This creates a qconsole.log file that may have some info on the crash. 

If you're going to implement this, then I strongly recommend that you first implement a Sys_FileOpenAppend function in your sys_*.c rather than using the zone-memory nastiness in the original tutorial. I have no idea why the original authors didn't do this. 

Not a mapper or a programmer so I have absolutely no idea what any of that is. I guess I'll wait til the next stable release of Quakespasm to play again 

I just realized you can type in small or big.

Is this a feature for case-sensitive OSs?

In Windows versions it does not seem to be a very useful feature, because if you happen to use a capital letter in a console command it says 'unkown command'. 

Seems like it is not case-sensitive for commands, but it _is_ so for cvars. The behavior seems to be the same in the original quake source too. 

all quake engines do this. it's not very useful. 

I don't know the difference between command and cvar.

If you type 'mAp e1m1', it will load e1m1.

If you type map E1m1, it won't.

Is that what 'it is not case-sensitive for commands,
but it_is so for cvars' means? 

"map" is a command. What the engine not being case-sensitive for commands means is that "map", "Map", "mAp", etc will all work and will all change the map.

It's actually even worse because the engine is case-sensitive in some places for commands, but not in others. Cmd_AddCommand for example is case-sensitive, so it would in theory let you add "mAp" and "map" as separate commands. Cmd_ExecuteString is case-insensitive so which of the hypothetical two it actually executes depends on the order they're added in (or something else if you e.g sort commands for faster finding).

All of this is clearly buggy behaviour, but is it the kind of buggy behaviour that legacy content may have dependencies on? 

Are you thinking like cfgs and stuffcmd/localcmd? 

Not thinking anything in particular other than I've been in a "put the bugs back" scenario before, so caution seems merited. 

All of this is clearly buggy behaviour, but is it the kind of buggy behaviour that legacy content may have dependencies on?

Is Cmd_AddCommand used for alias commands? If not, then surely only the engine is going to be calling it. That should make it safe to fix in a given engine. 

i was thinking there may be some mod that executes commands from a config to set things up and maybe they typed the command with/without caps. 

Is fence texture support on .mdl planned? 

Is there a way to change water color? Underwater everything is beige and in dark corridors I can't see anything. 

try setting "gl_cshiftpercent 50" in the console (default is 100) 

Mark V has a cvar r_watercolor for the underwater cshift color. There is also r_lavacolor, r_slimecolor.

In the engine code itself, it is referred to as called r_watercshift as a more descriptive internal name. 

Thank you, ericw. Now underwater fights aren't a pain anymore.

PS. I'm planning to speedrun a forgotten map pack. 

Am I correct in understanding that, on OSX, there is no way to suppress the Quakespasm launch dialogue (which allows the selection of command line parameters and resolution)?

I am writing a shell script to compile my map and then launch it in the game and it would be great if I could pass an argument that tells Quakespasm to suppress the launch dialogue and go straight into the game engine.