My UZDooM does not work.

[Relegard]

OS: Windows 11 (or higher) (NT 10.0) Build 26100

UZDoom version 4.14.3
W_Init: Init WADfiles.
adding D:/Games/UZDooM-4-14-3/uzdoom.pk3, 694 lumps
adding D:/Games/UZDooM-4-14-3/game_support.pk3, 3308 lumps
adding ./DOOM2.WAD, 2956 lumps
adding D:/Games/UZDooM-4-14-3/lights.pk3, 7 lumps
adding D:/Games/UZDooM-4-14-3/brightmaps.pk3, 499 lumps
adding D:/Games/UZDooM-4-14-3/game_widescreen_gfx.pk3, 214 lumps
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device IOpenAL Soft on Altavoces (USB PnP Sound Device)
EFX enabled
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick

Execution could not continue.
R_OPENGL: Unable to create an OpenGL render context. Insufficient driver support for context creation

This message is thrown in my face every time I try running my UZDooM, does not matter if I run DooM 1 or 2, it throws the same message. Any ideas why this might happen?

[drfrag]

Have you tried the GLES backend? But it still crashes on very old intel GL2 hardware, if that's the case you could try LZDoom and use the Softpoly backend.

[Relegard]

The thing is, I was playing the mod Countrycide before it crashed, and after it crashed, it now shows that message. But it worked good before the crash, so I'm wondering if perhaps I fucked something up or turned on an option that crashes the game or something.

[drfrag]

That's strange, then you could try deleting your ini. It's in Documents\My Games\UZDoom. But if it crashes the ini is not saved. Anyway LZDoom is a different build (VS 2019 and older CMake) and you could try that too just in case. BTW what's your hardware?

[Relegard]

A Lenovo IdeaPad S145 Intel Core i3. I will try LZDoom tomorrow and check if the problem no longer shows up. Thanks for helping. Its 3am and I need to sleep.

[drfrag]

I see there are several i3 configurations for those laptops and they are eight generation cpus using the uhd graphics 620 igpu supporting Vulkan and OpenGL 4.5. So you could first try selecting a different backend in the options tab of the UZDoom launcher.
If that doesn't work besides what i said earlier LZDoom uses the older interface and still has the Softpoly backend.

[Relegard]

OS: Windows 11 (or higher) (NT 10.0) Build 26100

LZDoom version l4.14.3a
W_Init: Init WADfiles.
adding D:/Games/DOOM PLEASE WORK I BEG OF YOU/lzdoom.pk3, 702 lumps
adding D:/Games/DOOM PLEASE WORK I BEG OF YOU/game_support.pk3, 3311 lumps
adding ./DOOM2.WAD, 2956 lumps
adding D:/Games/DOOM PLEASE WORK I BEG OF YOU/lights.pk3, 7 lumps
adding D:/Games/DOOM PLEASE WORK I BEG OF YOU/brightmaps.pk3, 500 lumps
adding D:/Games/DOOM PLEASE WORK I BEG OF YOU/game_widescreen_gfx.pk3, 214 lumps
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device OpenAL Soft on Altavoces (USB PnP Sound Device)
EFX enabled
I_Init: Setting up machine state.
CPU speed: 1190 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz
Family 6, Model 126, Stepping 5
Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 AVX512 F16C FMA3 BMI1 BMI2 HyperThreading
V_Init: allocate screen.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 796.81 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick
Selecting SoftPoly backend...
Changing the video backend requires a restart for LZDoom.

Execution could not continue.

R_OPENGL: OpenGL driver not accelerated!
Falling back to SoftPoly for next run.


running Doom 2 with Softpoly on LZDooM worked, though it ran atrociously compared to what I'm used to. OpenGL however, gave me this message on LZDooM. I'm gonna try to check the OpenGL on my PC to see if I can fix the problem.

[phantombeta]

As mentioned by drfrag, that laptop comes in multiple configurations: 3 different i3s, two with the Intel UHD Graphics 620, and one with the HD Graphics 620. Apparently it can even have an Nvidia GeForce MX110 with 2GB of GDDR5, according to this PDF from Lenovo.

I'd recommend checking if anything else works with OpenGL, or even Vulkan. The error means your drivers are reporting an error, or reporting they don't support something GZDoom needs, which means either something broke in the drivers, or something happened with the GPU that made Windows stop recognizing it.
I'd recommend checking if the GPU is still there and not showing any issues in the Device Manager, and if so, reinstalling your GPU drivers. It's possible Windows updated the drivers in the background and broke them.
And if it turns out you do have the GeForce MX110, it's worth checking what GPU Windows is trying to use (Windows Settings > System > Display > Graphics Settings (at the bottom)) and trying both.

[drfrag]

According to the log it's not one of those, it's the i3-1005G1 with the Intel® UHD Graphics for 10th Gen Intel® Processors but it should support OpenGL 4.5 and Vulkan 1.3 anyway. So it must be a gpu driver problem and you should download a driver from intel, i thought these problems were a thing of the past. And yeah UZDoom should run there.
Edit: apparently windows 11 uninstalled your drivers while you were playing causing the game to crash.

[phantombeta]

According to the log it's not one of those

That last post before mine wasn't there when I posted, only yours was. It must've been stuck in the admin queue

[zhd2]

Hello,

I had a similar problem, where UZDoom claimed, it could not load a shader. I found out that when I removed the config file and replaced it with the one from GZDoom + renaming it to UZD, it worked well.
Thus, I'd suggest removing the config file and see what happens.

Kind regards
zhd

[drfrag]

There's no need to delete the config file, it doesn't matter whether it's from gzdoom or uzdoom. You can simply select a different video backend on the launcher.