The above topic was a fix found by uPr0ph3tu. He deserves full credit for his finding the fix, I'm only posting in discussions so it does not get buried in comments as suggested by 「死の火」 Yamino Takamaru

Hi everyone,

There's a couple of issues that you might run into but both are quicky fixable !

First off if you're getting crashes or pure virtual function calls you need to uninstall .NET Framework and make sure you're using either version 4.5.1 or 4.5.2 (Both included with the game under the redistr. dirs but you can always just google and download it from MS if need be)

Next up make sure to go into the MOD's INIs in your workshop and change the shoot chance to 30.

Next up, I'm sure you're all using map packs at some point, VERY important: change your graphics to TILE-AO (Ambient occlusion I think ?), disable VSYNC. And that's about it you should be good to go.

Now if you're in a mission and you get that crash where you move your mouse over a tile and suddenly the game crashes ? That's the map pack. Can't do anything about that unfortunately so always make sure to save before srating a mission. Obviously that's not related to this mod but just mentioning it in case.

That's about it. You guys can msg me if you get stuck don't be shy but this will resolve 99% of your problems.

Figred I'd give a little more of an explanation plus my initial post doesn't sound very friendly lol sorry about that :P

uPr0ph3tu 님이 먼저 게시:

Hi everyone,

There's a couple of issues that you might run into but both are quicky fixable !

First off if you're getting crashes or pure virtual function calls you need to uninstall .NET Framework and make sure you're using either version 4.6.1 or 4.6.2 (Both included with the game under the redistr. dirs but you can always just google and download it from MS if need be)

Next up make sure to go into the MOD's INIs in your workshop and change the shoot chance to 30.

Next up, I'm sure you're all using map packs at some point, VERY important: change your graphics to TILE-AO (Ambient occlusion I think ?), disable VSYNC. And that's about it you should be good to go.

Now if you're in a mission and you get that crash where you move your mouse over a tile and suddenly the game crashes ? That's the map pack. Can't do anything about that unfortunately so always make sure to save before srating a mission. Obviously that's not related to this mod but just mentioning it in case.

That's about it. You guys can msg me if you get stuck don't be shy but this will resolve 99% of your problems.

Figred I'd give a little more of an explanation plus my initial post doesn't sound very friendly lol sorry about that :P

uhm to be clear your original post said .Net Framework 4.5.1 or 4.5.2, was there a change?

BigRowdy 님이 먼저 게시:

uPr0ph3tu 님이 먼저 게시:

Hi everyone,

There's a couple of issues that you might run into but both are quicky fixable !

First off if you're getting crashes or pure virtual function calls you need to uninstall .NET Framework and make sure you're using either version 4.6.1 or 4.6.2 (Both included with the game under the redistr. dirs but you can always just google and download it from MS if need be)

Next up make sure to go into the MOD's INIs in your workshop and change the shoot chance to 30.

Next up, I'm sure you're all using map packs at some point, VERY important: change your graphics to TILE-AO (Ambient occlusion I think ?), disable VSYNC. And that's about it you should be good to go.

Now if you're in a mission and you get that crash where you move your mouse over a tile and suddenly the game crashes ? That's the map pack. Can't do anything about that unfortunately so always make sure to save before srating a mission. Obviously that's not related to this mod but just mentioning it in case.

That's about it. You guys can msg me if you get stuck don't be shy but this will resolve 99% of your problems.

Figred I'd give a little more of an explanation plus my initial post doesn't sound very friendly lol sorry about that :P

uhm to be clear your original post said .Net Framework 4.5.1 or 4.5.2, was there a change?

♥♥♥♥ sorry, edited to make the correction. 4.5.1 and 4.5.2 are the correct versions.

uPr0ph3tu 님이 먼저 게시:

BigRowdy 님이 먼저 게시:

uhm to be clear your original post said .Net Framework 4.5.1 or 4.5.2, was there a change?

♥♥♥♥ sorry, edited to make the correction. 4.5.1 and 4.5.2 are the correct versions.

Thanks Bro.