Posted April 25, 2018
Apologies for cross posting this information in a couple of places - I'm just so happy I'm getting somewhere with this and want to share! V. much looking forward to playing the rest of this game...
Did quite a bit of application monitoring and tried a few things at once, and one of them worked... Not sure which one of these did these did the trick, and can't go back and try them one by one to narrow it down just now due to real-world commitments, but these might help you if you are having the memory leak followed by Access Violation error in the combat sections and are desperate to play Battletech like I was. I'll do some further testing tomorrow.
I finally managed to complete 2nd mission - physical memory usage staying at a stable 6.5GB. Page file wasn't getting hit at all - this had a massive boost fixing the lag when switching to the cinematic camera whilst sprinting. (FYI loading times are still loooooooooong though).
1. I updated NVidia drivers to today's release, 397.31. Initially after upgrade, the memory leak and crash remained, so not sure this is what helped. It may be a couple of reboots after installing the drivers did though.
2. Monitoring TCP/IP connections I noticed Battletech.exe was making some TCP/IP connections during play. Some of these are to AWS, but a couple of IPs didn't respond to ping. So completely disabled all network connections/adapters be they wired, Virtual Box adapter and Wi-Fi
3. With all network adapters disabled, I completely shut off Anti-Virus software (Webroot). Sadly, Webroot doesn't have an exclusions whitelist (say whaaaaa) so I hope this isn't what fixed things!
4. Crash in 2nd mission usually happened around time music / sound effects were playing, so disabled my SoundBlaster X-fi, and switched to NVidia audio.
Did quite a bit of application monitoring and tried a few things at once, and one of them worked... Not sure which one of these did these did the trick, and can't go back and try them one by one to narrow it down just now due to real-world commitments, but these might help you if you are having the memory leak followed by Access Violation error in the combat sections and are desperate to play Battletech like I was. I'll do some further testing tomorrow.
I finally managed to complete 2nd mission - physical memory usage staying at a stable 6.5GB. Page file wasn't getting hit at all - this had a massive boost fixing the lag when switching to the cinematic camera whilst sprinting. (FYI loading times are still loooooooooong though).
1. I updated NVidia drivers to today's release, 397.31. Initially after upgrade, the memory leak and crash remained, so not sure this is what helped. It may be a couple of reboots after installing the drivers did though.
2. Monitoring TCP/IP connections I noticed Battletech.exe was making some TCP/IP connections during play. Some of these are to AWS, but a couple of IPs didn't respond to ping. So completely disabled all network connections/adapters be they wired, Virtual Box adapter and Wi-Fi
3. With all network adapters disabled, I completely shut off Anti-Virus software (Webroot). Sadly, Webroot doesn't have an exclusions whitelist (say whaaaaa) so I hope this isn't what fixed things!
4. Crash in 2nd mission usually happened around time music / sound effects were playing, so disabled my SoundBlaster X-fi, and switched to NVidia audio.