Notes |
|
|
|
|
|
Not sure. I've only had this problem with Zandronum itself. |
|
|
|
Please download GZDoom 1.8.6 and test. |
|
|
|
I was going to once I had access to the computer again. It's my mom's (I've had to borrow it because my own computer's video card went kaput) & she kinda has to use it for some Social Security stuff at the moment. I'll check if GZDOOM 1.8.6 has this problem once she's done & I have access to it again. |
|
|
|
I just checked. I also had this problem with GZDoom 1.8.6. |
|
|
|
Thanks for checking! Can you see if this happens also in latest gzdoom git build here? |
|
|
|
Judging by the fact that the bug in question was fixed by version 2.0.0.5, I think it's safe to assume that it's just a side effect of the GZDoom code base-derived portion of Zandronum's code using an outdated version of GZDoom. |
|
|
|
This is a GZDoom bug that was is fixed in newer GZDoom versions then. If somebody finds when this was fixed in GZDoom, we can talk about backporting the fix. |
|
|
(0018176)
|
Dusk
|
2017-08-13 10:42
|
|
Without knowing what GZDoom version fixed this and being unable to reproduce the bug in question there's not much we can do. Please reopen if you have new information to add. |
|