I've been playing the game for weeks with no problem. Now I am unable to save during a mission and the game crashes everytime I complete the mission or try to leave the game. I saw online this may be a GoG Galaxy issue. Anyone else having the same problem?

I been ahving this problem today also - started when GOG galaxy is having problem loading games adn even this board

Ok. Well at least it isn't just me. Hopefully they fix the issue soon.

I have the same problem. Autosaves are not working. I'm NOT using cloud storage. Probably some fuck up issue with gog galaxy or maybe achievments but I just lost a 4 hour fight because of gog buggy software.

I wish they would learn how to program. There is no freaking reason why the achievment crap can't be optional and just timeout or run in a sep thread async. We do not want to suffer game progress because they can't code worth crap.

Played through the same mission twice and lost both attempts. The game is long and slow enough already. Add in save bugs and that is not cool. Is it only an issue on Battletech or all their games?

While this is speculation I'm pretty sure it is a gog galaxy issue and likely related to achievements. Their server is obviously having some issue and the code is sloppy and just blocks. While speculation there is a high probability that is the issue. Folks really need to learn how to use threads and async socket programming.

Yup, same issue this side. Initially I thought it was the 1.0.3 timeline bug so rolled back to 1.0.2 but even that with my old saves were borked. After seeing it was running the GOG Galaxy Communication exe (even when Galaxy was closed), as an experiment, I added a firewall rule to block inbound and outbound communications to that exe and suddenly the saves started working again. It probably breaks Galaxy but Battletech works properly again.

Once I'd found it was that, I just uninstalled the Galaxy client entirely, I'd rather handle it manually myself than deal with that again.

Ok so it sounds like the solution is disable or unistall GOG Galaxy. Hopefully they get this fixed. I am sure they dont want to have bunch of people uninstal their program.

Well, it's definitely not the game itself. Both autosaves and mid-mission saves are working on my end, despite running 1.03 and Galaxy.

I had a rather similar issue with the galaxy client, however, a few months ago. I'd suggest trying a clean reinstall of the most recent installer, and if that doesn't help, contact support.
It took an actual update of the client to get it to work smoothly again on my end, so it turned out to be a proper bug (and not some shot configuration or driver file).

Check if the folder for saves have somehow become write protected.
Not had time to play yet myself so no idea if I'd have the same issue.

Just gave it a try and saving/loading works fine for me on updated game trough galaxy.

Definitely wasn't the save files being write-protected on my side, I was shunting a lot of files around when I was trying to resolve the issue so was checking them for that sort of thing whilst I was doing that (I take a lot of save file backups, paranoia given to me by a certain Fallout New Vegas early save corruption bug). Can't speak for others though of course.

The fact several people seem to get it simultaneously, and mine started doing it after working absolutely fine, suggests external influence. People saying the GOG site was screwy earlier today, combined with my experiment with the communication exe, does point to the GOG Galaxy connection being the trigger, although the root cause is probably problems in both the GOG Galaxy thing and Battletech itself (a game really shouldn't fall over whilst saving locally just because an entirely unrelated external server is throwing a bit of a wobbler).

Also probably means that once those GOG servers are working again, people who were having this problem should be alright again, it was a fair few hours ago so hopefully everything's been sorted for now and fingers cross you shouldn't see this (well, until the GOG servers fall over again).

The problem wasn't autosave but autosave at the end of a mission. It was fixed approx 4 hours ago and is now working fine but it was down for 2 or 3 hours. The reason autosaves (speculation) at end of mission fail is because it updates the stats for achievements.

Somebody in this forum, somewhere, said that you should delete the saves that you no longer needed. That having a huge number of these files caused a problem somehow.

That was a performance issue and not relevant to myself as I delete a lot of them anyways.

The behaviour on mine was all saving, manual, auto after financial reports, creating a new career, etc. After attempting to save, I'd check the options menu, the Save button would be red, time wouldn't progress in the strategy layer and after attempting that, the game had to be killed from task manager, it wouldn't quit normally. Same behaviour on both 1.0.2 (from using the rollback feature) and 1.0.3.

No idea when the fix happened, I removed Galaxy as soon as I worked out what bit was going nuts, had no problems after that.