Closed jadenquinn closed 2 years ago
The version used to make that config file is not the latest, but I have confirmed it still happens on v4.8.X. I just haven't bothered updating it on this Mac as it's a pain in the balls.
Okay the broad brush stroke over such a huge array of Macs is a bit misleading. I think you might've tested a narrow sampling of Macs that had a similar defect in the GPU drivers and possibly assumed.
So we need some much more specific information here about the actual Macs you did test with - their GPU, what specific system OS version they are running, and what backend you are using (Vulkan? OpenGL? OpenGLES?). The backend can be found in the menu under search for "API"
If you do not know what GPU they are running, simply let us know what Mac models and years they are - they're like cars, they can be looked up easy that way.
I can list the Macs I tested, iMac 20" (2007 - https://everymac.com/systems/apple/imac/specs/imac-core-2-duo-2.4-20-inch-aluminum-specs.html), MacBook Pro 15" (2010 - https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.8-aluminum-15-mid-2010-unibody-specs.html), MacBook Pro 15" (2012/Unibody - https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6-15-mid-2012-unibody-usb3-specs.html), MacBook Pro 16" (2019 - https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i9-2.4-eight-core-16-2019-scissor-specs.html), Mac mini (2009 - https://everymac.com/systems/apple/mac_mini/specs/mac-mini-core-2-duo-2.53-late-2009-specs.html), Mac mini (2018 - https://everymac.com/systems/apple/mac_mini/specs/mac-mini-core-i7-3.2-late-2018-specs.html), Mac Pro (2010 - https://everymac.com/systems/apple/mac_pro/specs/mac-pro-twelve-core-2.66-mid-2010-westmere-specs.html), MacBook Air 13" (2015 - https://everymac.com/systems/apple/macbook-air/specs/macbook-air-core-i5-1.6-13-early-2015-specs.html), MacBook Air 11" (2015 - https://everymac.com/systems/apple/macbook-air/specs/macbook-air-core-i5-1.6-11-early-2015-specs.html), MacBook Air 13" (2017 - https://everymac.com/systems/apple/macbook-air/specs/macbook-air-core-i5-1.8-13-2017-specs.html), MacBook Air 11" (2011 - https://everymac.com/systems/apple/macbook-air/specs/macbook-air-core-i5-1.6-11-mid-2011-specs.html). Wouldn't you call that a broad brush stroke sample of different Macs? I used OpenGL for pretty much every test, I don't usually change it and if I do, I change it to software rendering mode, but I don't think the issue occurs on that mode.
I also don't think it happens on the new ARM Macs, but I'm not totally sure yet.
I have never gotten this problem in ARM macs. Still - there's more than a huge number of Intel macs still in use today, I don't recall that many of them experiencing this kind of problem. Nobody who's been using one has made a complaint about this.
I didn't look at all the GPU's but it looks like most of them have either an AMD chipset or an Intel switchout. For the ones that have dual GPU's (NVidia/Intel) can you see if there's an option somewhere to use only the NVidia and see if the problem still happes?
Unfortunately the only Intel Mac that I have access to is a August 2008 Macbook, which has barely the minimum specs required to run GZDoom short of a supported operating system that can actually run it. I have no idea how high I can upgrade my Mac OS but I know it costs money to do so and that I am not willing to spend.
So I got myself a Mac Mini Late 2014 (2.6GHz model) - https://support.apple.com/kb/SP710?locale=en_US
I put in your exact GZDoom.ini and I cannot get this bug. I am using Mac OS Monterey 12.5.
I have never gotten this problem in ARM macs. Still - there's more than a huge number of Intel macs still in use today, I don't recall that many of them experiencing this kind of problem. Nobody who's been using one has made a complaint about this.
I didn't look at all the GPU's but it looks like most of them have either an AMD chipset or an Intel switchout. For the ones that have dual GPU's (NVidia/Intel) can you see if there's an option somewhere to use only the NVidia and see if the problem still happes?
None of them have AMD graphics. One has ATI graphics, as it's from 2007, and the brand hadn't officially changed yet by then. As for the others, none of them have AMD graphics.
So I got myself a Mac Mini Late 2014 (2.6GHz model) - https://support.apple.com/kb/SP710?locale=en_US
I put in your exact GZDoom.ini and I cannot get this bug. I am using Mac OS Monterey 12.5.
Yea I kinda guessed it's not on every model during the time period I specified, but it's across quite a few. I don't seem to be getting this issue EVER on the new ARM Macs though, I also didn't keep track of versions of GZDoom I used very well, so it's likely that this issue could have been fixed as of v4.8.0, as I never see the bug in v4.8.2, so I'm not totally sure if this issue even exists anymore. I do know for a fact that it did in v4.7.1 on an Intel MacBook Air 11" from 2015, as I used that MacBook every single day for almost everything other than production, as for the others, I only tested them on and off, but I know it happened on most of the machines I have/had.
I have two Macs for testing, a 2013 MacBook and a 2019 Mac Mini. Works fine on both.
I don't believe there was a 2019 Mac mini... I have a 2019 MacBook Pro though and it seems to be working fine now.
GZDoom version
GZDoom v4.X.X (Latest)
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Mac OS
Please describe your specific OS version
MacOS 10.7.X, 10.8.X, 10.9.X, 10.11.X, 10.13.X, 10.14.X, 10.15.X, 11.X.X, 12.X
Relevant hardware info
All Macs from 2007-2019
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
I had this issue about a year or two ago and it seemed to be fixed for a time, but it’s back now, and looks to be for good. When I have the graphics mode set to Hardware Accelerated, depending on the angle textures appear at, the wall textures will flicker with a checkerboard pattern. I can tell it depends on the angle, as it doesn’t happen when looking at the wall(s) in question at any other angle.
Steps to reproduce the behaviour.
Explain how to reproduce
Your configuration
Provide a Log
I don’t believe there is one…