Extremely wacky problem in GZdoom.
Moderator: Graf Zahl
- Lucius Octavion
- Posts: 33
- Joined: Sun Mar 02, 2008 3:58
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
- Lucius Octavion
- Posts: 33
- Joined: Sun Mar 02, 2008 3:58
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
- Lucius Octavion
- Posts: 33
- Joined: Sun Mar 02, 2008 3:58
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
Ok, in that case I can definitely rule out anything in the code because Skulltag uses the exact same GL code. Something on your system must think that GZDoom needs special treatment and screws up. What happens if you rename GZDoom.exe to something else? Best try 'skulltag.exe' and see what results that might bring.
- Lucius Octavion
- Posts: 33
- Joined: Sun Mar 02, 2008 3:58
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
No direct idea. The program settings in the driver would have been my first guess.
So the only thing left would be looking through the Windows registry to see whether it contains anything related to gzdoom.exe. Unfortunately that's not that trivial and even experienced users might not be able to find something.
You can try it though. Start 'regedit' from the Windows 'Run' command and search for 'gzdoom'. Maybe something useful turns up.
So the only thing left would be looking through the Windows registry to see whether it contains anything related to gzdoom.exe. Unfortunately that's not that trivial and even experienced users might not be able to find something.
You can try it though. Start 'regedit' from the Windows 'Run' command and search for 'gzdoom'. Maybe something useful turns up.
- Lucius Octavion
- Posts: 33
- Joined: Sun Mar 02, 2008 3:58