Version 0.92.0 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/2016/07/quakespasm-0920/ 

And thank you very much for your support in providing compatibility with oms3. I know its old news by now, but I appreciate all the steps you took to make it work. :) 

Couple of quick questions.

I'm trying to decide if I should add my IRC code to this version to release for QExpo rather than version 0.91.0.

Does it offer anything in the way of stability or bugfixes beyond what is stated in the notes?

Are you planning on releasing this for QExpo, and if so, do you want me to delay the official release of my code? 

The changelog is pretty much it: no other notable differences between 0.91.0 and 0.92.0. As for the qexpo thing, I have no interest in that. 

Hello, the latest quakespasm appears to be totally unresponsive to my controller.

Controller is a bog standard official "XBox 360 Controller for Windows", with up-to-date drivers. It also works fine on other games I use it for.

I have also done what it says in the readme and downloaded the gamecontrollerdb.txt file to the quake folder, but it does not help.

Any idea how I could troubleshoot this problem? 

@Kinn make sure to run quakespasm-sdl2.exe, only that .exe has controller support.

I have the same controller (wired version), tested it on Windows 10 and OS X so far.

Also, check for any "joystick missing controller mappings" or "failed to open controller" messages in the console. 

Cheers - that's it - mea culpa :}

Btw it's AWESOME - default sensitivities etc. are pretty much spot on - now I can sit back in a comfy chair and play quake and its the bestest thing in the world ever :D 

 

 

ur just jelli u don't have the gamepad skillz. 

>gamepad
>skills 

Doom was released not long after I got my first computer and it was one of the first PC games I played. Before it came out all I had on the PC was flight simulators and space combat game, so for the first year I played Doom I used a Thrustmaster joystick as the controller. 

Honestly, after 20+ years of playing console games I don't find controllers awkward to use in any way. I prefer them to mouse & keyboard because the level of comfort is incomparable. The only time I'd want to use a mouse & kb is for games that have complex controls like mmo games or rts or whatever. 

in QS and other engines has been lacking for quite a while. As superior as KB+M is there is still a problem with that setup for playing games on a couch in front of the telly box.

Also, wheres my splitscreen (yes, I am a pestering bastard but I fully intend on using this with my friends) 

 

Rip Kinn_sp3

you know when there's a band you like, and then they do nothing for over a decade, but then suddenly you hear they've got a new single coming out, and ur all like "omg holy shit that band i like is back" and everyones excited and then the single comes out and you buy it and you listen to it and first you're not sure what to think of it and you look at your friend and he also has the same "i'm not sure what to make of this" look on his face and you listen to it again, and you sort of pretend to like it this time but deep down you're kinda thinking "what the fuck is this".

Just sayin. 

 

I don't really have anything to add to that comment so instead here's a gif of a pig taking a cat for a walk: http://i.imgur.com/oneWY9J.gif 

I mean, I kinda enjoyed Kinn during my teenage rebellion phase. But nowadays it's just lost its appeal... 

I seem to 100% of the time get a black screen when I start up the sdl2 version. To fix it, I alt-tab to desktop, then alt-tab into the game again.

Doesn't happen with the non-sdl2 version.

Anyone else getting this?

Windows 10
NVIDIA GeForce GTX 765M 

Anyone else getting this?

I'm guessing that you have an Optimus laptop from the "M" in your GPU model number.

I was able to 100% reproduce this on a similar system, but only when running under the Intel graphics card. When running under the NVIDIA (either by right-clicking and selecting "Run with graphics processor" or by creating a profile in the NV control panel) it behaved properly. 

Holy shit - I had no idea I was running it all this time on my crappy intel card thing. Whoa. Cheers! 

On Windows the NvOptimusEnablement (there's an AMD equivalent too) export can be set to fix this: http://stackoverflow.com/questions/17458803/amd-equivalent-to-nvoptimusenablement

Only thing is, for some rendering workloads the Intel is actually the faster GPU in this kind of configuration - especially if it's a HD4000 or better. Quake falls into this category; what happens is that Optimus with the NV must transfer the framebuffer to the Intel for presenting, but Quake rendering is so lightweight that doing the transfer takes longer than just doing everything on the Intel. 

Not sure if this has already been requested, but it'd be a real time saver I think.

Predictive text for commands. Just like on swyftkey or similar, you type a letter and behind it the engine fills in, in grey, any possible command pertaining to that letter.

If you hit enter then it completes the command in text, if not then you carry on typing as normal.

Adding custom keybinds is all very well... but if prediction was a base feature then it'd remove a lot of this piddling about for most if not all users.

Just a thought. 

it exists, start typing something then press tab