Closed BinarryCode closed 1 year ago
idk if its something with the pc specs but heres that
drop your sm64 rom on this site just in case and see what the output is http://emn178.github.io/online-tools/sha1_checksum.html
drop your sm64 rom on this site just in case and see what the output is http://emn178.github.io/online-tools/sha1_checksum.html
its 9bef1128717f958171a4afac3ed78ee2bb4e86ce
, seems like the intended result according to sm64 decomp github.
try downloading and running unmodded gzdoom, both 3.2.0 and latest version to make sure it's not this mod causing the crashing
I have 3.2.2, not sure if that's good enough but it runs fine (besides a rendering bug with opengl that fixed itself when I re-opened it)
also the latest version seems to run fine as well
i downloaded the latest debug build and it seems to run fine - i can't seem to pinpoint what's going on. are you able to use MSYS2 or the GDB debugger? if you have either of these installed, that is
I dont have either of them, at least not an updated version for the former
if it lets you, launch "MSYS2 MinGW x64" from your start menu and install gdb with pacman -S mingw-w64-x86_64-gdb
.
if you don't have MSYS2 MinGW x64, go get it from their site
download the mod again but this time pick "gzdoom-sm64-debug". extract it to an empty folder.
in MSYS2, write "cd" followed by a space, then drag that new folder into the MSYS2 window, then hit enter.
type gdb gzdoom.exe
, wait for GDB to load, then type "r" to run the game.
if GDB suddenly spits out "Segmentation fault", type bt
, then share with me what GDB spits out, either via a screenshot or copy-pasting the contents
Binar@DESKTOP UCRT64 /c/Users/Binar/Downloads/gzdoom-sm64-debug $ gdb gzdoom.exe -bash: gdb: command not found
I installed gdb
did you launch "MSYS2 MSYS" (purple icon) or "MSYS2 MinGW x64" (blue icon)? make sure you run gdb from within the latter.
also make sure you installed mingw-w64-x86_64-gdb
and not just gdb
same error
restart msys2 mingw x64 and try again, or try with msys2 msys
?
maximize and show me everything
?
check on the newest debug build on the actions tab and download the gzdoom-sm64-debug one again
if it doesn't work try launching the game from msys2 by typing ./gzdoom -iwad doom.wad
, replacing "doom.wad" with whatever WAD file you have
if that does nothing either, i'm gonna have to try and replicate this issue on another machine or a VM, but i have my doubts i can get this situation to happen because this is weird
Works perfectly now, thanks 👍
I have a PC that can actually run this, in theory.
But it crashes on startup now.
I'm pretty sure this applies to every version but I can't really test it too well