maxmanium Posted October 19, 2019 Hey folks, sorry if this has been posted before but I couldn't find anything about it. MAP22 of Scythe has this HOM, but it only happens on GZDoom (software renderer). I'm just curious if anyone knows why it happens. 0 Quote Share this post Link to post
hawkwind Posted October 19, 2019 (edited) Cause by sector 236 having the "wrong" floor/ceiling heights. Fix by having floor/ceiling heights of 120/121 respectively. Edited October 19, 2019 by hawkwind 0 Quote Share this post Link to post
maxmanium Posted October 19, 2019 3 minutes ago, hawkwind said: Cause by sector 236 having the wrong floor/ceiling heights. Fix by having floor/ceiling heights of 120/121 respectively. But why does it only happen in GZDoom? 0 Quote Share this post Link to post
seed Posted October 20, 2019 13 hours ago, maxmanium said: But why does it only happen in GZDoom? I don't think it does though, I think I've seen this in PrBoom when I went through Scythe. 0 Quote Share this post Link to post
maxmanium Posted October 20, 2019 1 hour ago, seed said: I don't think it does though, I think I've seen this in PrBoom when I went through Scythe. Seems fine to me 0 Quote Share this post Link to post
ReaperAA Posted October 20, 2019 Did u guys check compatibility settings for both GZdoom and PrBoom+. I don't remember seeing this in either port but the last time I played Scythe was many years ago. 0 Quote Share this post Link to post
hawkwind Posted October 20, 2019 (edited) 9 hours ago, seed said: I don't think it does though, I think I've seen this in PrBoom when I went through Scythe. PrBoom+ 2.5.1.5 at least is fine in software. Also using just zdoom 2.8.1 the area rendered fine. Could not see any compat settings for this issue. Would seem the software code has been modified since 2.8.1 ? Edited October 20, 2019 by hawkwind 0 Quote Share this post Link to post
3saster Posted October 21, 2019 (edited) Seems to be a problem unique to GZDoom, and only in software/softpoly renderers, with no compatibility setting to fix it. It does not occur in PrBoom+ or Chocolate Doom (But ZDoom 2.8.1 does cause the problem for me). This is easily fixed using level compatibility, so I made a pull request for GZDoom. Once this gets committed into the master, this visual glitch will be fixed in the next GZDoom Devbuild, and by extension, GZDoom 4.2.4 and later. As for why this occurs exclusively in GZDoom's software renderer, your guess is as good as mine... Edited November 3, 2019 by 3saster 0 Quote Share this post Link to post
Graf Zahl Posted October 21, 2019 The obvious answer would be that the renderer is not exactly the same, just like it swallows some map constructs others may choke on, the opposite can just as easily happen. It may be related to GL nodes. I remember the floating crate in Suspended in Dusk producing similar HOM in older ZDooms when the textured automap was on. GZDoom needs the GL nodes anyway so you can't switch them off and check, you'd have to do that in 2.8.1. 1 Quote Share this post Link to post
3saster Posted November 3, 2019 For what it's worth, this bug is fixed in GZDoom 4.2.4. 0 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.