you do not need wows source code to run validation on it though. I’m not on mac that has that setup so I can’t post instructions off hand but hopefully that information is available online. I’ve not had time to do that with later alphas unfortunately, but it is something users CAN do, in fact you can do it and maybe see why your gpu is restarting too. Over a dozen reports (and all fixed too). In fact during Legion alpha when metal was first added, I make a fake project and then attached it to wow beta so I could run metal function validation on alpha while I played, and reported every validation error I found to blizzard for fixing. The level of validation that needs doing doesn’t often get done. Thing is developers like blizzard can’t be bothered to do this as much as apple wants…Apple kind of has this mentality that triple A studios should be approaching macOS with a macOS first mentality and that’s complete opposite of reality. It has a validation feature but it is a cpu hog and as such is only on when actually doing debug/function validation checking. Metal encourages doing validation through xcode. They leave function validation up to app developers and if we’re being honest I doubt blizzard does very much of it on mac side, and windows has more function validation than mac side so erratic code could run there without triggering an issue. This means if you tell driver to do something erratic, it actually does something erratic. From my understanding apple does very little function validation in their drivers. That said, wow is probably also in part to blame somewhere. I’m inclined to believe the drivers are definitely buggy and neglected. they’ve known they were transitioning away from both a lot longer than devs did and now we know why they’d kinda ignore bug reports regarding either. I know i’ve been told many times that intel and AMD metal drivers are both pretty buggy since apple has little reason to care about either for a while now. It’s definitely software but it can be anything between the driver, and the kernel. So I wanted to bring it up here in case there is some code in WoW that is triggering whatever is going on programmatically within an Intel Mac that causes this behavior. I reached out to my friend at Apple QA and asked if this were hardware or software, and their response was “logically, software.” I did see other people reporting this particular error in relation to WoW freezing, but mostly this seems to be a rare issue with no real, solid, solution. My search-fu failed me on what this means. The error is DumpGPURestart Sample output below: 10:11:54.530137-0400 DumpGPURestart : .gpuRestartĬom.2: UNBUNDLED ||| kernel ((null)) Today I found a string of errors happening in rapid succession around the time the behavior started. When this happens, I notice that my GPU load average is maxed out (iStats Menu FTW), but I could never find anything in the logs that corresponded to when the behavior happened. I notice that in times between the game (and computer) freezes and unfreezes it is possible to switch to windowed mode (if you spam Option-M), and from there you can, if lucky enough hit force quit to quit out of WoW. This usually happens in areas like Ardenweald and Revendreth (where there is fog overlay) especially where there are hidden zone changes. I would get cycling between the display, a bright red screen (contained within the WoW display) and heavily artifacted in-game renderings. For a number of years (since Big Sur) I have had instances where the game would freeze, and freeze the computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |