With -nostartup:
Without -nostartup:
Removing the call to ClearRect in FStartScreen::Render seems to prevent this breakage, so the issue has to lie there.
Start screens break some drawing functions in Vulkan
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
-
Marisa the Magician
-
- Posts: 3875
- Joined: Fri Feb 08, 2008 9:15 am
- Preferred Pronouns: She/Her
- Operating System Version (Optional): (btw I use) Arch
- Graphics Processor: nVidia with Vulkan support
- Location: Vigo, Galicia
Start screens break some drawing functions in Vulkan
This is something I've quickly taken note of since the code was merged. It appears that once a start screen finishes, calls to Screen.Dim, Screen.Clear, as well as Screen.DrawThickLine start behaving incorrectly, the first two become pretty much invisible, and thick lines become darker in some cases (not always). The quickest way for me to reproduce this bug was to launch Hexen and open any option menu containing color pickers. If I skip the start screen using -nostartup, this does not happen.
With -nostartup:
Without -nostartup:
Removing the call to ClearRect in FStartScreen::Render seems to prevent this breakage, so the issue has to lie there.
With -nostartup:
Without -nostartup:
Removing the call to ClearRect in FStartScreen::Render seems to prevent this breakage, so the issue has to lie there.
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 48514
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Start screens break some drawing functions in Vulkan
A workaround is in place, I ,have no idea yet what's really wrong with this, it must be some faulty assumption by the backend regarding the shader setup.