andrei-drexler
commented
2 years ago Unfortunately this is most likely caused by a bug in Intel's graphics drivers and I don't think there's much I can do about it. If you also have a dedicated GPU in your system, no matter how weak, using it instead is a safer option. On Windows 10/11 you should be able to change the preferred GPU in the Settings app (System > Display > Graphics/Graphics settings). The next engine release will use the dedicated GPU by default, so this step won't be necessary. If the integrated GPU is the only one in your system a driver update might fix this, but most likely it won't. In that case, the only option at the moment is to switch to a different source port, like QuakeSpasm or QuakeSpasm-Spiked. Performance won't be as high or as consistent on complex maps, but their less sophisticated renderers don't trigger this issue.
In any case, it would still be helpful to get a bit more info about your system. Could you please check the console after starting the game and tell me what GL_VENDOR, GL_RENDERER and GL_VERSION values are reported? You might have to scroll up a bit to see them. Alternatively, you can use the condump command which will save a condump.txt file in your current mod folder (so in id1 by default).
I don't know if this is just my trash pc but anytime I try to play this it freezes.
I go into start map. It freezes. warp to e1m1 using commands. It freezes. sometimes even demo freeze! I have no idea whats causing this but I know it annoying. If anyone could help I would be thankful!