-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running 'Doom 64: Unseen Evil' on the latest 14.3.0 Flatpak crashes GZDoom #78
Comments
Can you reproduce this issue with the non-flatpak version of GZDoom? |
I could try when I arrive home. EDIT: |
I just tested out the executable "gzdoom" from the Ubuntu 64bit package in the official GZDoom site. The executable is the one found within data.tar.xz (/opt/gzdoom/). I tested with the same files as with the Flatpak version, and with the executable the Unseen Evil mod does run without issues. |
Then it's likely related to this: Long story short, GZDoom plays fast-and-loose with some compiler-checks while the Flatpak app demands certain checks for security and reliability. |
I see, so it's some added checks that could be causing the issue. Should I wait for a plausible fix or should I continue with the EXE through Wine as I am at the moment? |
Report it upstream, and they can fix it. If they fix it, I can apply the patch so you can continue fighting demons. |
Sadly, not fixed with 4.13.1 |
The bug also seems present in 4.13.2. Where did you report the issue @Eonfge? I'd like to follow it up upstream. |
I didn't report it. I asked @ShadowOne333 to do it since he has the most concrete logging, experiencing the problem first hand. |
@ShadowOne333, I suppose you didn't experience the issue when working with wine and the .exe version, correct? |
Sorry I have been somewhat absent online as of late. I can make the report later today, but I am not certain on how to properly report this on GZDoom's issue tracker other than to mention the fast-and-loose compiler checks that Eonfge mentioned. Should I add something more in detail? |
If you give them the log from above, as well as a reference to the previous issue, they'll know what's up. |
Made the issue report on mainstream: |
I must sadly inform you all that the bug is not fixed with 14.4.0 |
This upstream change should fix things ZDoom/ZMusic#66. In the meantime, setting |
This should be fixed now. Keep in mind that if you see other Assertion related errors, you should report them here. |
Good day.
Yesterday, I tried playing the recently released "Doom 64: Unseen Evil" mod, which basically converts all the Doom and Doom II assets to play and behave like Doom 64, and I am getting a consistent crash whenever I tried to load any level of any game/episode.
I remember I tried running this on Friday and I was able to get it to run into the first level (E1M1) with the D64 assets, however, I didn't continue playing since I was modifying some controls options and left it there for the weekend. It wasn't until yesterday that I came back to it, and to my surprise, now I couldn't get it to run anymore.
I'm running GZDoom on a Steam Deck, with the Flatpak installed being up to date.
I ran the Flatpak through terminal with
flatpak run org.zdoom.GZDoom
, and at the very end I got the crash log, here's what I got:It mentions something about
stl_vector.h
and a wrong assertion.Not sure if something is missing in the latest Flatpak to get it to run properly, but I downloaded the latest Windows version, ran it through Wine/Proton and I can play the mod just fine, I went all the way from Episode 1 of Doom 1 up to the end of Episode 3 without any issues whatsoever, so it's something specifically with the Flatpak causing the issue.
The text was updated successfully, but these errors were encountered: