-
Notifications
You must be signed in to change notification settings - Fork 91
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
Crash when launching a mission #733
Comments
I've reduced the active mods into just the XCOM2 LW2WOTC dependencies:
I also tried to purge configs, reinstall LW2WOTC and still I get the same crash. Have you tested this under Linux too? Might be Linux-specific issue (IIRC the original LW2 required some game fixes in order to work under Linux) |
I just load your save on Windows |
Must be Linux-specific then |
There should be a game log file, unless you're showing the game log file. It doesn't contain anything I recognise as such, though. The game log file might help. |
I've googled a bit about the other logs locations and found this:
|
I'm on Fedora 29 and could load your save file without problem. Regarding the several reports of breaks on Linux (Ubunut/Mint) I suspect more a Ubuntu specific problem. According to this reddit post the overlayrenderer.so segfault seems unrelated: https://www.reddit.com/r/archlinux/comments/48sahc/what_is_gameoverlayrendererso_and_why_does_it/ |
Disabling overlay in steam settings didn't help |
Tried upgrading the mod to the current version but it didn't help |
Adding recommended mods didn't help too |
I've tried loading this save/mission on my system and have encountered no issues. |
Sounds like an environmental issue. |
Hi guys, got a reproducible crash when starting certain mission:
OS: Linux Mint 19.2
Mod configuration:
All enabled mods are from steam workshop, except LW2 WOTC (beta1) and the custom highlander required by LW2 WOTC
Save:
save_Save 66.gz
Just try to start the mission. The game crashes on SIGSEGV afterwards.
Is that LW2WOTC related problem or this shall go to Feral?
The text was updated successfully, but these errors were encountered: