• Content Count

  • Joined

Community Reputation

495 Excellent

About fatheroctopus

  • Rank
    Senior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, I'm not surprised that it still crashes, as lowering resolution probably changes some timings and memory usage, but doesn't address the core problem. Since we can now repro this reliably, no more information is needed - thanks for your help, I'll update this thread when we learn more.
  2. Great! - and also very interesting. We have managed to reproduce this error on a machine on our end, so we'll keep plugging away at getting it working at native resolution.
  3. @Yozabroza There are a few tests that could provide some useful info: Assuming that continuing from a given save always crashes for you, does it crash... 1) ...when the steam overlay is disabled? (Right Click on Griftlands in library -> General -> Uncheck "Enabled the Steam Overlay while in-game") 2) ...in both full-screen and windowed mode? (Accessed via "Graphics" tab in the in-game settings) 3) ..at a different resolution from your default settings? Thanks!
  4. Hi @Yozabroza, just a quick update - the bug appears to be hardware dependent and I've had trouble reproducing on my own devices. This is substantiated by the bug report you attached, which shows the error occurring in a graphics driver library. We're currently relying on some static analysis tools to try to identify the bug - when a candidate fix is released I'll be sure to update this thread to see if it fixed things on your end. Thanks for your patience!
  5. Hi @Yozabroza and @baevar - does this occur every time for you, regardless of what save you're loading? If it's not every time, could you attach a copy of a .sav file that exhibits the crash? Instructions for finding your .sav are in the link below - thanks for the report! https://support.klei.com/hc/en-us/articles/360044520732-Logs-and-Useful-Information-for-Bug-Reports-for-Griftlands-Early-Access-
  6. Changed Status to Fixed
  7. It appears that the Steam client was hotfixed late yesterday with a fix for launching games on Mac. They don't call out Mojave though, so let us know if you're still unable to launch after updating steam.
  8. Hi, the latest build has some changes that might address this crash, let us know if you still encounter it after updating. Thanks!
  9. Changed Status to Known Issue Hi, just letting you know that we are looking at this. I'll update when we've deployed a hotfix. Since it's a pretty tricky repro, we may need to go back and forth a few times. Thanks for the report!
  10. Without going too deep into the details, basically the logs will flush -most- of the time when an error occurs, but in your case, a seg fault is happening in a manner that doesn't give the logs a chance to write. I'll follow up on that other bug report, but if it's what I think it is, the logs wouldn't be particularly helpful in this case.
  11. A heads-up for Linux users that started playing already, we just hot-fixed the build and you may have noticed your saves are gone! Don't worry - your saves are safe! They were just being copied to the wrong folder, and the new build is now looking in the correct location. To recover your old saves, follow these steps: 1) If it exists, move the directory ~/.local/share/Klei/Griftlands to somewhere else as a backup 2) Rename ~/.local/share/Klei/Griftlands_dev -> ~/.local/share/Klei/Griftlands 3) If steam cloud complains about a conflict, accept your local version Let us know here or on the bug forums if you encounter any issues. Thanks!
  12. We just deployed a potential fix, let me know if you still see the crash after updating to build 460578 I was unable to reproduce myself, but that's not surprising since the crash seems very dependent on specific hardware timings. If you still get it, the logs should at least have a different error message. Thanks for the report!