This is due to a bug in the GZDoom 3.7 series; GZDoom 4.0 was just released and does not exhibit this issue, give that a shot: https://forum.zdoom.org/viewtopic.php?f=1&t=64188