Boots to a black Screen on startup.

[blueinferno776]

On build QZDoom-q0.1alpha-220-g49e890f-x64.

Was working great until the later builds, I wiped the ini for a fresh one on startup and still got a black screen on windowed and fullscreen.

I do have a radeon r7 m360 in my laptop for some reason this is not in the dxdiag I have.

I really like were qzdoom is going and cant wait for the first stable release!

bluInfdxdiag.txt

My sys info

(109.08 KiB) Downloaded 246 times

[Rachael]

First, please try updating your video card driver, as the release you have may be buggy.

If that does not work, try booting with "+vid_used3d true" - it only has to be done once.

What is happening is QZDoom is using the same renderer canvas that GZDoom does for its software renderer, however for some users it appears to not be working, so "vid_used3d" was implemented as a fallback to use ZDoom's renderer canvas. Your card is more than recent enough that this should be a non-issue.

[blueinferno776]

Windows 10 has the most asinine auto updater I have ever seen. I Uninstalled my drivers for a clean install and rebooted when it was done. AND windows started to install display drivers in the middle of a reboot.

My laptop is being factory restored thanks to the auto installer that killed my windows os.

I can't do anything right now. I will test qzdoom when I get this fixed to see if I still get a black screen.

[blueinferno776]

Qzdoom started up with no problems! Runs smooth as it did before.

Gzdoom was working just fine before I fixed my laptop, the opengl render canvas should of worked for Qzdoom. Trying to make sense of it.

[dpJudas]

There were some bugs in the GLSL and the defines it used that may have have caused the black screen. OpenGL is a little bit fragile where tiny errors may work just fine on one vendor and totally breaks on another. The GL handling in GZDoom is 1000 times more tested for edge cases like this, which is probably why that runs just fine for you.

[blueinferno776]

Ok. It was something simple which is good. I thought is was the radeon software drivers or some obscure bug. Safe to say this is resolved.