Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: almost constant crashes, unplayable #1342

    Oh, please don't be sorry! Regardless of the crashes that I'm having, you've basically developed the best game I've played since.. damn, probably since I discovered DF.
    I bought this on Humble for a reduced price (it was my game-i-can-buy-this-month for the next two months!), but as soon as you release it I'll be buying it again at full price 😀

    So, back to bug hunting!

    Copied the files into the game directory –
    Now runs again, possibly a bit better than before. Taking control of the Keeper and moving him around the map is WAY quicker & smoother now..

    That said, after about 10-15 minutes it quits same as before 🙁 stacktrace.out is now:

    Code:
    ?? ??:0
    ?? ??:0
    ?? ??:0
    in reply to: almost constant crashes, unplayable #1340

    Now it doesn't start up at all 🙁 The command prompt box comes up (though without any content), then I get a Windows error –

    Code:
    keeper.exe – Application Error
    [X] The application was unable to start correctly (0xc000007b). Click OK to
    close the application.

    No longer generates a stacktrace file in the game directory..

    in reply to: almost constant crashes, unplayable #1338

    got impatient, had any play around attempting to fix this..
    installed the MinGW collection on my Windows10 lappy, so that “addr2line” was in the environment paths.

    still crashes, at about the same time, but the error message in stacktrace.out is now:

    Code:
    ?? ??:0
    ?? ??:0
    ?? ??:0
    ?? ??:0
    ?? ??:0

    in reply to: almost constant crashes, unplayable #1337

    Deleted stacktrace.out, opened up a brand new game – just left it running (didn't dig or explore or anything).

    Still crashed – only thing in stacktrace.out now is :

    Code:
    'addr2line' is not recognized as an internal or external command,
    operable program or batch file.

    I played around with this over the weekend a fair bit (mostly because it's such a good game I wanted to play it regardless of the crashes..).

    This meant saving every 5 minutes or so, then copying that save file out somewhere so I could replace it when a crash occurred. I actually got about 30-45 minutes in this way – with absolutely no raids, whatsoever. I was thinking it's possible that this means the raids are what's making the game crash – or something associated with the raid popping up..?

    That's about as far as I got..

Viewing 4 posts - 1 through 4 (of 4 total)