Weird Quakespasm bug... can anyone explain it?

I’ve had to basically give up playing Danzadan’s maps, because they cause Quakespasm (on Linux 64 bit, where I live) to blow up when I save the game. It’s only maps by Danzadan that do this. I’m assuming it has something to do with the toolchain they are using to build the maps, but I can’t figure out what it is. Darkplaces doesn’t run very well on my hardware, but Quakespasm runs fine and can play basically any other map just fine. It makes me sad, because so many of Danzadan’s maps are really nice…

I have no technical insight on the issue, but I faced that problem with one of the hwjam maps (I live in the same world as you, or close). Debian’s version of QuakeSpasm is 0.92.1, which crashed when saving games, but the problem disappeared with version 0.93.

Yeah, but I’m on 0.93 and I still have the bug…

Run it in gdb with debugging symbols included, get the crash, type “bt” and send that to the developers.

There’s a good chance it’s the “wad” key overflow, I posted about it in: https://www.quaddicted.com/reviews/xmasjam2018.html

Unfortunately I don’t have linux binaries of the latest SVN code to offer but if you can build Quakespasm SVN from source that would be worth a try, otherwise Spirit’s advice is good.

Thanks ericw, that’s helpful. I’ll do a little research and see if I can get that working.