GZDoom Very Fatal Error

[FreeThinker]

My hardware: AMD 7800 X3D CPU, AMD 6800 XT videocard

Made a fresh istall of Steam Doom1 + Doom2, unpacked GZdoom into new folder on C disk (Fast SSD). Stated gzdoom.exe, Got a message that its missing files, which directed me to rtgl-16.3. Unpacked them in the same folder

now I get the following error

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

GZDoom version g4.11pre-712-ge618865ce
W_Init: Init WADfiles.
adding C:/DoomRTX/gzdoom.pk3, 673 lumps
adding C:/DoomRTX/game_support.pk3, 3307 lumps
adding C:/Program Files (x86)/Steam/steamapps/common/ultimate doom/base/doom2/DOOM2.WAD, 2919 lumps
adding C:/DoomRTX/game_widescreen_gfx.pk3, 214 lumps
adding rt/wad, 117 lumps
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device OpenAL Soft on Luidsprekers (Realtek USB Audio)
EFX enabled
I_Init: Setting up machine state.
CPU speed: 4200 MHz
CPU Vendor ID: AuthenticAMD
Name: AMD Ryzen 7 7800X3D 8-Core Processor
Family 25 (25), Model 97, Stepping 2
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 272.50 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
Resolution: 3840 x 2160

How to get this functional

[Redneckerz]

Seems you are using a devbuild with the -pre moniker if that is any indication.

Also GZDoom doesn''t use rtgl-16.3, and considering i see RTX in there i assume you want to run the GZDoom-RT fork.

The above also doesn't show an error i can see, so if there is an error, please post a log. There is too little to go with here and too many assumptions that now take account.

[Graf Zahl]

There's no crash log and the listed commit doesn't exist, so it's very likely this is from a fork.

In short: not our business, especially without the crash log.

[Tamand33]

Having same problem what ido now

[Hellser]

This thread is considered closed. You're more than free to start a new one and post a detailed explanation as to what's going on. Your issue might be different than what was going on in this one.