How to fix memory the leak.

[Sqrly]

Apparently the current version of Oodle has some serious mem leak issues. This is the version included in this game.

Some resourceful people on another forum I shall not name here have discovered that if you replace 'oo2core_9_win64.dll' with a previous, stable version (v2.9.5) it cures the memory leak that is probably causing a lot of crashes.

I have done so on my version of the game and after the hour plus shader building the game has run great. The only issue I've had is sometimes I get stuck in 'listen' mode and have to tap the key again.

Also, the ingame VRAM usage display is wrong on my PC. It read 1.2GB too high. I reccomend you run a third party app like Afterburner to see correct VRAM usage.


Just FYI folks, and "DEVS!"

[Mexicola9302]

It's "2.9.5" and not "2.9.5.7".

[Wolves]

i have had zero crashes in a chunk of hours, crashes are because you overload vram on a console port which was for fixed hardware and it cant handle ram overloading well, my 2 cents anyway

[Sqrly]

Originally posted by Mexicola9302:

It's "2.9.5" and not "2.9.5.7".

You are correct. I accidentally added the 7 from 7z in the filename. I've edited my post.

[Sqrly]

Originally posted by Wolves:

i have had zero crashes in a chunk of hours, crashes are because you overload vram on a console port which was for fixed hardware and it cant handle ram overloading well, my 2 cents anyway

Perhaps the ingame VRAM useage is showing the opposite incorrect numbers for many others. Mine currently says I'm well over 100% but Afterburner shows I'm just under 100%.

[Revan]

Why need to create another topic? I dont understand these people..

[Ultradad]

Originally posted by Wolves:

i have had zero crashes in a chunk of hours, crashes are because you overload vram on a console port which was for fixed hardware and it cant handle ram overloading well, my 2 cents anyway

Same experience except that I had a few crashes and tweaked my texture detail settings to lower VRAM usage - worked fine after that.