Widescreen Gaming Forum

I've tried larger until I get only one occurrence, Any advice for this in terms of wildcards?

C7 44 24 28 00 00 80 BF C7 44 24 2C 00 00 80 3F C7 44 24 30 00 00 80 BF F3 0F 5E AA 0C 01 00 00 C7 44 24 34 00 00 80 BF C7 44 24 38 00 00 80 3F C7 44 24 3C 00 00 80 3F F3 0F 5E F0 31 C0 0F 28 D6 0F 28 DD 0F 28 CF 48 83 C0 04 48 83 C3 10 F3 0F 59 54 04 2C F3 0F 59 5C 04 1C 0F 28 C7 0F 28 E3 F3 0F 59 D5 0F 14 E7 0F 14 D7 0F 14 E2 0F 28 D4 0F 28 C4 0F 28 CC 0F C6 D4 AA 0F C6 CC 55 0F C6 C4 FF 0F 59 52 50 0F 59 42 60 0F 59 4A 40 0F 58 D0 0F C6 E4 00 0F 59 62 30 0F 58 CC 0F 58 D1 0F 29 53 F0 48 83 F8 10 7C 94 0F

That's too much.
you should not need to look for such bytes count in your aobscan.
The original code to replace is only 8 bytes. Only few bytes before or after the orignal should be added to aobscan to expect a unique occurence.
Attaching Cheat Engine to the Metal Gear process, there is a shortcut you can use to execute aobscan to see if you're good or not.

Shortcut (CTRL+ALT+L)

Then type in the window

results = AOBScan('YYYYYYYYYYF3XX5EA9XXXXXXXX')
if results then print('results count: '..results.Count)
end
results.destroy()

Where XX are wildcards and YY are the bytes found before the original sequence.
eg : results = AOBScan('F3OF5EA9OFF3XX5EA9XXXXXXXX')

To see bytes before original code you have to do an array search and type F3 0F 5E A9 0C 01 00 00 (original sonar sequence).
Then browse for memory to see opcodes with bytes related.

For the wind effect using



I still get 2 results for that, where would I go from there? If I can't refine the search anymore without using too many bytes. It seems more than a few things are duplicated in memory.

Would it be advisable to make another script that executes after the first to scan and fix the second occurrence?

If you browse memory region for both results, the opcodes (machinge language) are the same before and after the sequence ?

Can you post the memory browse window screenshot here for both occurences ?

The addresses are 14357996E(the working one) and 14358ADEE (duplicate)

Edit: Changed the link to a download because the photo site was resizing the image to unreadable levels.

I didn't realise how close and large were these two functions.
It's more interesting to do an aobscan looking backward for wildcards and bytes.
But that won't be easy as looking for bytes backward will introduce other opcodes with offset and register that may change more or less in futur updates.

At that point i suggest asking how to perform and process an aobscan with two results and large opcodes similar in cheat engine forum.
This is beyond my skills.

Thank you so much, you did great i downloaded the fix as soon as possible and its working great ( the one you updated after your first file pg 84.). Do I need to update your FIX further ? or its safe to use 24/7 ?

_________________
Asus PG348Q-Asus STRIX GTX 1080-- Corsair Obsidian 900D-Core i7 6700k-Asus Z170 Sabertooth

It should work just fine on the current version of the game, no further updates at the moment. We're just discussing about how to make the fix more future proof, so that it won't need updating each time a new patch comes out.

If you're talking about leaving it open all the time, it shouldn't effect anything other than this game. I would say if you play multiplayer games at all, I wouldn't leave it running in the background, but that's just me being cautious.

Hi, how do I use the exe? Would be very nice to not have to start the game, start cheatengine, apply the fixes and then game every time I want to play. Thanks for your work non the less! I stopped playing the game when I noticed those annoying sections when weather effects or something were active. I can play again! Thanks!

The exe includes cheatengine and the cheat table all in one file. You just start it first and when you're in game press F1 to enable fixes, or F3 to disable fixes. The exe doesn't apply the fov fix though, because the value must be set manually in cheatengine and the exe has no way to input values.

The F1 and F3 keys should work in the regular cheatengine CT file version you're using now, but fov still must be enabled and set manually.

Either way you still have to start cheatengine or the standalone exe version before you start the game.