Namdrol on 16/2/2010 at 17:42
Since installing T2 on my new Win7 laptop I'm getting an odd error with my quicksaves.
Things were absolutely fine and then I loaded an fm beta for testing and quicksave didn't work. I added a new keybind to alt-s, which was k, used it and then alt-s worked. A bit later on alt-l stopped working so again I added a new keybind, j, and again things worked ok.
Later on in the same mission again both save and load stopped on alt-s and l so again I "added" the other keybinds and it worked ok.
Now this same mission had caused problems in its first beta and crashed every time I saved so I assumed it was just this mission.
I then loaded up another beta I'm testing and same thing happened halfway through.
It's irritating more than anything and I wonder if anyone's come across it before?
Searching, I see Larry G once had a problem with quick save but he deleted his post saying rebooting solved things for him.
Well it keeps happening for me.
theBlackman on 17/2/2010 at 21:24
Just off the top of my head, are you using the OPTIONS to LOAD your new key strokes every time you start the game or FM?
Namdrol on 17/2/2010 at 22:04
I have my own normal bindings always set up that I move from machine to machine.
I'm back to thinking it was one particular fm that caused the problem.
I've been testing a campaign all day with no trouble, then load up this other mission and there we are, same problem.
Yandros on 18/2/2010 at 00:03
Crashing on loading a savegame is sometimes caused by not having the dark mission description set properly in the .mis file.
