BATTLETECH - Game crashes to desktop near beginning of Three Years Later campaign mission

[huntercc]

One line summary of your issue
Game crashes to desktop near beginning of Three Years Later campaign mission

What platform are you running the game on?
Steam

What operating system do you use?
Ubuntu 22.04

Which version of the game are you running?
1.91-686R

What DLC do you have installed?
None

Please explain your issue is in as much detail as possible.
After launching the mission "Three Years Later", I begin moving my mechs around. Before I can finish my first turn, the game crashes to desktop.

Have you tried verifying your files?
Yes

Steps to reproduce the issue
Launch the mission "Three Years Later". Begin moving mechs. Game crashes before the first turn can be completed.

Attach DxDiag (PC), System Info log (Mac), or run sudo lshw -html > specs.html and uploaded specs.html (Linux)
File(s) attached

Attach Output Log
Windows: \Users\YourUserName\AppData\LocalLow\Harebrained Schemes\BATTLETECH\output_log.txt
Mac OS: Users >{name} > Library > Logs > Unity > Player.log
Linux: ~/.config/unity3d/Harebrained Schemes/BATTLETECH/Player.log
File(s) attached

If the game crashed, please attach the crash file with the time stamp closest to the crash.
Windows: [Steam library folder]\steamapps\common\BATTLETECH\DumpBox
For v.17 and beyond try here: C:\Users\[YourUserName]\AppData\LocalLow\Harebrained Schemes\BATTLETECH
OSX: Macintosh HD > Users > [username] > Library > Application Support > Steam > steamapps > common > BattleTech > DumpBox
Linux: [Steam library folder]/steamapps/common/BATTLETECH/DumpBox
File(s) attached

If a save game was loaded at the start of the game session, upload it. Please make sure to upload the save game with the timestamp closest to when you loaded it.
Windows:
Steam: [Steam installation folder]\userdata[SteamID]\637090\remote\C0\SGS1
GOG: 'C:\Users\USER_ID\AppData\Local\GOG.com\Galaxy\Applications\50593543263669699\Storage\Shared\Files\C#\SGS#'
Vanilla:'C:\Users\USER_ID\AppData\LocalLow\Harebrained Schemes\BattleTech\C#\SGS#'
OSX:
Steam: Macintosh HD > Users > [username] > Library > Application Support > Steam > userdata > [SteamID] > 637090 > remote > C#> SGS#
GOG: Macintosh HD > Users > [username] > Library > Application Support > GOG.com > Galaxy > Applications > 50593543263669699 > Storage > Shared > Files > C# > SGS#
Vanilla: Macintosh HD > Users > [username]> Library > Application Support > unity.Harebrained Schemes.BattleTech > C# > SGG#
Linux:
Steam: /home/.steam/steam/userdata/[steamID]/637090/remote/C#/SGS#
GOG: /home/[username]/.config/unity3d/Harebrained Schemes/BATTLETECH/remote/C#/SGS#/
Vanilla: /home/[username]/.config/unity3d/Harebrained Schemes/BATTLETECH/remote/C#/SGS#/
File(s) attached

Attach screenshot / video
File(s) attached

 

[huntercc]

Additional detail... it seems to be related somehow to how much I have zoomed out the camera. I haven't nailed it down exactly yet, but I did manage to play through half the mission before it crashed on me. This was done by only zooming out just a little bit at the beginning, rather than all the way. But then of course it crashed later on, at the start of the second phase of the mission.

 

[AndrewT]

Was that log taken just after one of these crashes? Because we don't see an actual crash in there.

What I do see is a bunch of video errors, that I'm not sure are cosmetic:

0:23(1): error: syntax error, unexpected '[', expecting end of file
Note: Creation of internal variant of shader 'Terrain/BT-TerrainTesselation' failed.

Are you on the very latest video driver?

https://www.amd.com/en/support/graphics/amd-radeon-rx-6000-series/amd-radeon-rx-6500-series/amd-radeon-rx-6500-xt

And you might consider updating the development Mesa version

Home — The Mesa 3D Graphics Library

www.mesa3d.org

Good luck!

 

[huntercc]

Was that log taken just after one of these crashes? Because we don't see an actual crash in there.

What I do see is a bunch of video errors, that I'm not sure are cosmetic:


Are you on the very latest video driver?


And you might consider updating the development Mesa version


Good luck!

I saved all of these logs right after a crash to the desktop. I can't promise they were all generated by the game at that time, but those were the latest files that were present at the time.

According to my system, my video driver is the latest.

I see on the mesa3d website you linked that there is a newer version of Mesa available, but it's not clear to me how to get the latest version installed on my system. It is insisting that I already have the newest version. Any chance you can offer some more links, with clear instructions?

Like I mentioned in my followup post the only workaround I've been able to discover is simply to *not* zoom in or out during the mission. This is not foolproof, it will still occasionally crash to desktop on me, but at least I'm able to advance through the campaign. When I do try to zoom, it will crash within a few seconds every time.

 

[AndrewT]

My Linux knowledge is years old I'm afraid! I think you'll need to get Linux distro help on how to update that driver and Mesa version.

I focus on this because from your symptoms, and the errors in that log, it seems like a video-related issue.

 

[huntercc]

My Linux knowledge is years old I'm afraid! I think you'll need to get Linux distro help on how to update that driver and Mesa version.

I focus on this because from your symptoms, and the errors in that log, it seems like a video-related issue.

It magically decided to find a whole bunch of updates shortly after I replied to you. I haven't had a chance to try it out yet, but I will update when I do.

 

[huntercc]

I lost a day trying to get the game to launch again. After the updates were applied to my system, the game refused to launch. I had to try several things, but what finally got it to launch again seems to be setting the compatibility to use Proton 8.0. That was last night; once I got it to run, I went to bed.

Tonight... that compatibility setting somehow got reverted to "none"... and now it just works. Go figure.

But the good news is, the original issue no longer seems to exist. I tried several different saved games in which I previously had issues, I zoomed the camera in and out every which way I could, but I could not replicate the original issue. I even managed to complete a couple of missions in the campaign.

Thank you for the suggestions!!