MacOS 15.4 breaks v.2.3.1, 2.3.2

Comments

• olddoomer

  Apr 4, 17:47

  Having the same experience on a 2023 MacBook Pro that just got updated to Sequoia 15.4 (v2.3.1 was working fine on 15.3.x). Also tested 2.3.2 release candidate with the same result.
• TheOneTrueRobb

  Apr 4, 19:03

  We haven't received a response as of yet. Probably researching.
  
  Here's the message it gives me:

  Doom Crash Message.pdf 43.7K
• rarmelliin

  Apr 8, 20:01

  Same problem here... looking forward to hearing back from anyone with a solution for it!!!
• TheOneTrueRobb

  Apr 9, 02:06

  So, someone/anyone at Deng: Are you going to, at the very least, address this problem? Anything - an acknowledgement that there actually is a problem, and that someone is hopefully working on a fix?
  
  Too much to ask?
  
  
• rarmelliin

  Apr 9, 17:28

  TheOneTrueRobb wrote: »

  So, someone/anyone at Deng: Are you going to, at the very least, address this problem? Anything - an acknowledgement that there actually is a problem, and that someone is hopefully working on a fix?
  
  Too much to ask?
  

  
  I doubt it that they are doing anything... There hasn't been a new release of the engine since 2021. We are DOOMED!!! LOL
• skyjake

  Apr 12, 13:19 edited Apr 12, 13:20

  Hello there. Yes, I can confirm this crash is occurring, and also that the project is very much on hiatus currently so no quick fixes will be forthcoming, unfortunately.
  
  I suppose we've finally reached a point where the old Intel builds aren't going to work on modern systems. The solution is to try putting together a proper arm64 build, although that's not exactly a trivial task. I'll make a note to look into this if/when I manage to find a few hours of spare time (finding time is also not a trivial task :-| ).
• olddoomer

  Apr 12, 18:28

  skyjake wrote: »

  I'll make a note to look into this if/when I manage to find a few hours of spare time (finding time is also not a trivial task :-| ).

  
  Thank you, skyjake!
• TheOneTrueRobb

  Apr 13, 18:47

  skyjake wrote: »

  Hello there. Yes, I can confirm this crash is occurring, and also that the project is very much on hiatus currently so no quick fixes will be forthcoming, unfortunately.
  
  I suppose we've finally reached a point where the old Intel builds aren't going to work on modern systems. The solution is to try putting together a proper arm64 build, although that's not exactly a trivial task. I'll make a note to look into this if/when I manage to find a few hours of spare time (finding time is also not a trivial task :-| ).

  
  I would pay to get a copy of Doom 1-4 that works on my M2. Just a thought. Obviously, if that cost is prohibitive, that's probably not gonna happen. But if it costs similar to, say, Prodeus, around $25, I'd shell out for that.
• veirdo

  Apr 14, 06:55 edited Apr 14, 08:20

  I had a problem on MacOS after the update. The 2.3.2 build crashed, but I performed a clean-up and fresh install. Now, everything is working fine.
  
  
  upd. I haven't tried Sequoia 15.4 yet, but it helped me last time.
  upd2. I can confirm it's no longer working on 15.4. I'll have to dust off my older mac with an older OS.
• thesourcehim

  Apr 14, 07:06

  I suspect deleting application settings files (not sure where they are locatated in MacOS) may be enough. I had similar problem in Windows and Linux in the past after major updates, turned out some old settings were incompatile with new versions of Doomsday and OS.
• TheOneTrueRobb

  Aug 6, 20:21 edited Aug 6, 22:28

  Just checking: Any possible chance that Sequoia 15.6 fixes this? I suspect not, but one must ask...
  
  UPDATE: YESSSSSSSS!!!!!!!!!
  
  I Got Doom back! Halla-frickin'-Loo-Yahh!
  
  I won't be sleeping at all for a while...