Fatal Error When Launching Doom II Raytraced and Selaco
Moderator: GZDoom Developers
Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
-
A_Zombie1223
- Posts: 1
- Joined: Sat Aug 17, 2024 9:00 am
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD (Modern GZDoom)
Fatal Error When Launching Doom II Raytraced and Selaco
I've been having issues with launching Selaco and Doom II Raytraced. Both are stating very fatal errors with access violations. My AMD drivers for my GPU is up to date.
You do not have the required permissions to view the files attached to this post.
-
Rachael
- Posts: 13717
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
Re: Fatal Error When Launching Doom II Raytraced and Selaco
These are not issues that we can help with since they come from forks of the engine.
Try switching to the OpenGL backend to see if it helps. But otherwise you will have to contact the fork authors, or AMD themselves. There's nothing we can do here.
Try switching to the OpenGL backend to see if it helps. But otherwise you will have to contact the fork authors, or AMD themselves. There's nothing we can do here.