I_SignalHandler: Signal 11

[soup587]

No matter what WAD I use and where I place it, PrBoom always crashes before even loading the title screen with an "Exiting on signal: signal 11" error. Looking it up doesn't really give me any solutions (despite this being a thing in PrBoom for years)

[neekfenwick]

I also get this error message, and I have an AMD graphics card (RX6800). I note the home page of this repo has a Notes section which contains: "sadly, it works on Nvidia GPUs; it would be nice if someone will decide to add the AMD GPUs support :)" I do not know if this error is caused by not having an Nvidia GPU. Can anyone clarify? What kind of graphics card do you have?

[soup587]

A GTX 1080. Despite not being an RTX card it should still work as it supports all the RTX methods that the actual RTX cards have

[Wookie2600]

Created an account just to post. I was getting this error and once I installed the latest drivers from GeForce Experience app, it's working.

[arrowgent]

others have used non RTX cards on windows (nvidia atleast, not AMD)

this is only supported for doom 1 wad currently

[soup587]

Created an account just to post. I was getting this error and once I installed the latest drivers from GeForce Experience app, it's working.

Sadly I seem to be on the latest version, so not sure why it's not working

[BeermotorWB]

This is an annoying PRBoom bug/quirk/feature from way back, probably going on ten years or so now. It is a generic segfault error.

I'm getting an immediate segfault on the switch to full screen with both my RX 6800XT and my RTX 3090, both with the most recent drivers. Testing was performed using the original DOS Doom 1 1.9 release (timestamped May 24 1995 23:09) WAD file to ensure consistency.

[arrowgent]

does the latest prboom-plus 2.6.2 work? https://github.com/coelckers/prboom-plus/releases

the prboom-plus-RT is using 2.6.1 which is only slightly older

worth a test

[GalmFOx]

does the latest prboom-plus 2.6.2 work? https://github.com/coelckers/prboom-plus/releases

the prboom-plus-RT is using 2.6.1 which is only slightly older

worth a test

nope

[sultim-t]

There's a segfault somewhere... need to use address sanitizer as the starting point

[Rastommy77]

I am getting the same error. GTX 1080. Downloaded The Ultimate Doom on Steam and created a new folder within. Copied the prt folders contents in there and copied the doom.wad into it. Ran it, then it came up with signal handler error 11

[sultim-t]

Hmm.. I wonder if that signal 11 error related to MSI Afterburner / RivaTuner Statistics Server / etc being installed.

I remember I had a bad time making Serious Sam Ray Traced running while those programs were installed. After I uninstalled them, windowing system error was fixed magically there. There's a small chance that it's the solution

[lerouxm]

GTX 1060 / Latest Nvidia drivers : Same issue ! Got no additional software running like AfterBurner or Riva... :(

[AndrewMRX]

I have this issue too. I put the configuration file from another version of prboom and it worked. but when I select rt render, it crashes again. GTX 1060 6gb. Latest drivers.

[ferrellsl]

Same here. GTX 1080, latest drivers and tried various WAD files from ver. 1.1, 1.666 thru 1.9.

[Elizafur]

Same here on a GTX 1080 TI, tried using the included 2.6.1 prboom and then 2.6.2 but no luck.

[Herman-Sid]

I think it's worth releasing this on another engine, because PrBoom has problems that make it impossible to run.

[lafoxxx92]

I think it's worth releasing this on another engine, because PrBoom has problems that make it impossible to run.

Considering it works for them, why would they? It's usually easier to fix the issue than to start over in different port.

BTW, I also have this issue and can provide all info needed to resolve it (just tell me what's needed).

[sultim-t]

First thing is to understand if it's related to RT or to prboom itself: if the actual prboom v2.6.1 release works https://github.com/coelckers/prboom-plus/releases/tag/v2.6.1um without such error

[sultim-t]

Maybe try with -vidmode GL argument for the executable

[AndrewMRX]

Version 2.6.1 works well.

[lafoxxx92]

Maybe try with -vidmode GL argument for the executable

works, stops working with the above error after changing the renderer in options.

[BeermotorWB]

does the latest prboom-plus 2.6.2 work? https://github.com/coelckers/prboom-plus/releases

the prboom-plus-RT is using 2.6.1 which is only slightly older

worth a test

Thanks for the link to the new build. Ran without issue on my AMD and Nvidia GPUs. Worth noting that even though it didn't run on the 6800xt and 3090,

First thing is to understand if it's related to RT or to prboom itself: if the actual prboom v2.6.1 release works https://github.com/coelckers/prboom-plus/releases/tag/v2.6.1um without such error

This version also ran without the segfault.

If i can get time I'm planning on testing under Linux with the RADV driver to validate to see if the segfault issue is related to the issue identified in #8

Worth noting for completeness: I did get a successful run to E1M3 on my son's 3060 with Geforce driver v512.15.

[Herman-Sid]

Maybe try with -vidmode GL argument for the executable

The latest PrBoom works without problems. As well as the current PrBoom with the parameter "-vidmode GL" starts and works without RT. I don't understand what's wrong, the same Quake 2 RTX runs from steam in RTX mode.

[sultim-t]

Since original PrBoom works, then there's some bug in my changes in PrBoom or on RayTracedGL1 side :( It's tricky to find, would be nice to have some help. I will provide more info on how to build them, so more people can try to find the source of the segfault.

[planetarian]

I am also having this issue; playing on my desktop with a GTX 1080 gets a Signal 11 error unless I launch in GL mode. Switching to RT mode once in-game doesn't seem to do anything noticeable. A normal instance of PRBoom 2.6.1um works just fine.

[Herman-Sid]

I think, I wasn't completely honest. Quake 2 RTX works for me most likely because DXR is implemented there (software implementation of RTX). This explains why your project may not work for people with video cards based on Pascal architecture. Now, if you could add DXR to the port ...

[NadnerbD]

GTX 1080 user here, also seeing the same error. Runs without RT using -vidmode GL, subsequently selecting RT in options doesn't seem to change anything.

[ColonelPhantom]

I think, I wasn't completely honest. Quake 2 RTX works for me most likely because DXR is implemented there (software implementation of RTX). This explains why your project may not work for people with video cards based on Pascal architecture. Now, if you could add DXR to the port ...

Quake 2 RTX doesnt use DXR, it uses Vulkan ray-tracing in the form of VK_KHR_raytracing_pipeline or VK_KHR_ray_query. I'm quite certain the library from the author of this project also uses VK_KHR_raytracing_pipeline.

DXR is also not a software implementation of RTX. Rather, it's a generic API to interact with raytracing hardware, like DirectX (which DXR is an optional part of) is a generic API to interact with graphics hardware in general.

[arrowgent]

i have an nvidia 1070, and i can run Q2RTX at 8-10fps. i do NOT have an RTX capable card

[Civil]

I will provide more info on how to build them, so more people can try to find the source of the segfault.

Source of segfault is sort of simple to find.

You have a check that verifies if Vulkan was initialized. And the problem is that assert in non-debug built will be removed and check would be effectively removed from the code. If you don't have a proper Vulkan Surface next time you'll use it, your code will segfault.

I believe that Vulkan initialization logic need to have better error handling and provide verbose information on why it can't initialize vulkan.

[Orthestral]

It was working perfectly until today, after I updated my system and restarted. Now it's giving me the Signal 11

[xlen]

i have an nvidia 1070, and i can run Q2RTX at 8-10fps. i do NOT have an RTX capable card

RTX is not a feature... GTX 1060 6GB and above all support RTRT, the performance on Pascal isn't great and nVidia has put no effort into optimizing it in any way.

As for the issue at hand, GTX 1060 6GB here, signal 11 as well, I read in forums something about "textures in the PNG format instead of Doom format could be the problem." related to PRBooM Plus 🤷‍♂️

[xlen]

It was working perfectly until today, after I updated my system and restarted. Now it's giving me the Signal 11

What did you update? What GPU driver version you had and have now?

[VegaBiggs]

GTX 1060 6GB here, I have the signal 11 problem on prboom RT but the last vanilla prboom works fine. 512.15 Nvidia Driver.

[bubbleguuum]

Same issue:

• GTX 1080 TI
• Windows 11 (Beta)
• NVIDIA Drivers: 512.15

[NKO55]

Same issue here.

• GTX 1070 Ti 8 gb
• Windows 10 (10.0.19041 Build 19041)
• Drivers 512.15
• Using the GoG.com version of Ultimate Doom

Tried running with and without the dlss.dll.

[InFlamesHell]

Same here.. GTX 1080 seems like we all have a 10XX in here :P

[Orthestral]

What did you update? What GPU driver version you had and have now?

I didn't update any GPU driver. The most notable package updates were:

• libgcrypt
• X11 Display Server
• Lutris
• Pango
• shared-mime-info
• Wine Mono (.NET)
• zlib

All others are a standalone application or have to do networking or VMs

I use Void Linux and RTX 2070S. I run PRBoom through Lutris My driver version is 510.60.02

[xlen]

Same here.. GTX 1080 seems like we all have a 10XX in here :P

Most people here seems to have Pascal yes, but not everyone.

[BoomDoomTomb]

Same issue. Crash within seconds of starting up the .exe. I_SignalHandler: Exiting on signal: signal 11. I have GTX 1070 ti with latest drivers and Intel Core I7-3770K 16gb DDR3. Tried to Google this error code and it brought me here.

[CUTWEST]

At first I was getting the "can't initialize ray tracing engine" error....After I updated my drivers now im getting this error. Cant win for losing on this GTX 1080ti. Maybe its just not compatible with Pascal cards can anyone with a 10xx series card confirm this is even working for them? So far I see nothing but Pascal owners having this issue while no confirmation of this even working with pascal cards to begin with.

[xlen]

At first I was getting the "can't initialize ray tracing engine" error....After I updated my drivers now im getting this error. Cant win for losing on this GTX 1080ti. Maybe its just not compatible with Pascal cards can anyone with a 10xx series card confirm this is even working for them? So far I see nothing but Pascal owners having this issue while no confirmation of this even working with pascal cards to begin with.

People who have it working aren't looking at the issues section 😅

[RowanSkie]

At first I was getting the "can't initialize ray tracing engine" error....After I updated my drivers now im getting this error. Cant win for losing on this GTX 1080ti. Maybe its just not compatible with Pascal cards can anyone with a 10xx series card confirm this is even working for them? So far I see nothing but Pascal owners having this issue while no confirmation of this even working with pascal cards to begin with.

People who have it working aren't looking at the issues section 😅

Or probably is looking but is trying to find another solution to the problem (A GTX 1080ti here, trying to find a solution on other ways atm)

EDIT: My CPU is an AMD Ryzen Threadripper 2950x.

[Pablossjui]

I'll add that I also run into this error and I'm using a GTX 1080 Ti (with a Ryzen 5600x) I'm not sure it's anything related to Vulkan not being able to use the raytracing libraries. I can run this demo no problem https://www.geeks3d.com/dl/show/50110

[LittleGreenSpaceMan]

I am getting the same error with my GTX 1080ti, tried the possible solutions in this thread, they didn't work. I am the latest drivers for my card also.

[MissingNO57]

Same errorhere with Windows 11 and MSI GTX 1080ti, running NVIDIA drivers 512.15.

[gitsjd]

Same issue here on gtx1070. However, interestingly, when I copy the prboom-plus.cfg file from the latest (262) version of prboom plus, the game runs fine - but without ray tracing. Perhaps someone who got the RT working, can post their cfg file to see if using it would help us.

[Official-KEX]

At first I was getting the "can't initialize ray tracing engine" error....After I updated my drivers now im getting this error. Cant win for losing on this GTX 1080ti. Maybe its just not compatible with Pascal cards can anyone with a 10xx series card confirm this is even working for them? So far I see nothing but Pascal owners having this issue while no confirmation of this even working with pascal cards to begin with.

People who have it working aren't looking at the issues section 😅

I mean true, why would they hehe Im getting the same error here too (I_SignalHandler: Exiting on signal: signal 11), wasn't expecting to run well on a 1060 anyway, but i would have enjoyed seeing raytraced doom. Even if its only running at 2FPS :D

Also, for some reason Windows Defender was going crazy when i tried running it.

[sultim-t]

Not sure if related, but I've fixed a double-free bug on Linux in 1.0.4. Also, I wonder if SEGFAULT (i.e. signal 11) is related to upscaling techniques. prboom-rt-1.0.4-noupscalers.zip https://github.com/sultim-t/prboom-plus-rt/releases/tag/v2.6.1-rt1.0.4 doesn't have them, so maybe it's worth to check them

[VanillaDeath]

Not sure if related, but I've fixed a double-free bug on Linux in 1.0.4. Also, I wonder if SEGFAULT (i.e. signal 11) is related to upscaling techniques. prboom-rt-1.0.4-noupscalers.zip https://github.com/sultim-t/prboom-plus-rt/releases/tag/v2.6.1-rt1.0.4 doesn't have them, so maybe it's worth to check them

I'm also experiencing this issue (GTX 1080 on Win11, v512.15). Tried the noupscalers version too, same issue, sadly.