In the meantime, I'd like to hear others' experiences with win32 and win64 builds.

(FWIW, I re-tested both win32 and win64 builds on my win8.1/x64 laptop with on-board intel graphics and nvidia graphics, both still run ok with both intel and nvidia chosen as the 3d accelerator.) 

couple ideas for mfx:

- just for a sanity check, could you try extracting the zip into an empty directory, and just add id1/pak0,1.pak, to rule out any issues with DLL interference
- try launching with "-notexturenpot"
- does the win64 one szo posted also give a red screen? http://quakespasm.sf.net/devel/quakespasm-0.85.10-r944_win64.zip 

tried suggested clean folder setup, won�t work:( stdout.txt says this:

Warning: multitexture not supported (extension not found)
Warning: texture_env_combine not supported
Warning: texture_env_add not supported
Warning: vertical sync not supported (SDL_GL_GetAttribute failed)
Warning: texture_filter_anisotropic not supported
Warning: texture_non_power_of_two not supported 

Won�t change the red output.. 

Running on 32-bit win7. 64bit build won�t start. 

Try launching with "-bpp 16", this will disable requesting a 24-bit depth buffer which was changed recently.

So in the clean folder setup you still get the red screen, or does it fail to start at all? The messages in stdout.txt suggest it's using software OpenGL :-/

Looks like that build I sent you for trying to fix the console key was from april 30. not much has changed since then besides the depth buffer thing, and the non-power-of-two support. 

still red, 16 bit request too. 

Here's another one to try: http://quakespasm.ericwa.com/job/quakespasm/23/artifact/quakespasm-r944.zip

this is r944 with a different SDL.dll, the one from "SDL-devel-1.2.15-mingw32.tar.gz"

Just to confirm, this is the one I sent in april, it still works?
https://www.dropbox.com/s/hkha9wl897wg7oq/quakespasm-germanlayoutfix.zip 

tried suggested clean folder setup, won�t work:( stdout.txt says this:

Warning: multitexture not supported (extension not found)
Warning: texture_env_combine not supported
Warning: texture_env_add not supported
Warning: vertical sync not supported (SDL_GL_GetAttribute failed)
Warning: texture_filter_anisotropic not supported
Warning: texture_non_power_of_two not supported

Are you sure that you have hardware accelerated opengl??? 

layoutfix works, still, r944 doesn�t.

szo: Are you sure that you have hardware accelerated opengl???

How can i check this? 

This is starting to sound like a joke...


layoutfix works, still, r944 doesn�t.

That 'layout fix' build seems to be from r913. Thas hasn't been any commits since r913 that would affect video. Eric, can you see arything otherwise?


szo: Are you sure that you have hardware accelerated opengl???

How can i check this?

If you can run any opengl games properly, then you have hw accelerated ogl.

What hardware and what driver is this anyway? 

This happens only on the Lenovo thinkpad, all other HW i use makes no problem.

Onboard Gfx: Mobile Intel(R) 4 Series Express Chipset Family

Driver Version: 8.15.10.1872

DirectX10

Oh, btw, this laptop has also problems with Fitz, FMKV, and DirectQ.
Darkplaces, requiem, Qbism, tyrquake and QuakeSpasm do work. 

gl_clear 0? 

OK then. Try and run quakespasm (r944, mine or Eric's, doesn't matter, and doesn't matter it gives a red screen) using a command line like
"quakespasm +gl_info"
... then exit, and see the generated stdout.txt file. What does it say about GL_VENDOR, GL_RENDERER and GL_EXTENSIONS? 

GL_VENDOR: Microsoft Corporation
GL_RENDERER: GDI Generic
GL_VERSION: 1.1.0
GL_EXTENSIONS:
GL_WIN_swap_hint
GL_EXT_bgra
GL_EXT_paletted_texture 

is the problem, right? 

GDI Generic is the problem, right?

Correct: there is no hw-accelerated opengl driver.

Is your driver from micro$haft (I think it is, they usually don't provide ogl, but only dx), or from intel? I suggest you download from intel, who should provide proper ogl drivers. 

OpenGL version 2.1.0 - Build 8.15.10.1872 is supported, but its software emulated or..? I don�t get tbh.

Ok then, i�m checking out intels ogl drivers then. 

Looks like its solved, though i had intel drivers already. Updated them and no red screen anymore.
Thanks for your patience szo and eric! 

Next time test everything on the same system, you dummerle. 

no. 

On windows, what opengl driver to use is a registry entry (or at least it used to be) which possibly got deleted or whatever.. Anyways, glad to hear that it works now. 

good to hear it's fixed :-)

I wonder why that layoutfix build worked. The only difference I can think of is that I compiled the layoutfix build with mingw32 on windows, and the ones that gave a red screen were all compiled on linux. 

what, micro$shaft is detecting our build machines and sabotaging us now? 

joke aside, he said that 0.85.9 works too, and looking at it the 0.85.9-win32 version is compiled on the same linux machine using the same toolchain against the same crt and headers. baffled...