I noticed after a while, the emulator then cleanly exists after code is run.
A simple code optimization driver u are u 4000b fingerprint reader so I do not just NOP the jump out (a NOP instruction in x86 is a no-op, basically wasting CPU cycles since its not doing anything).
I ended up executing the code and ended up at another ExitProcess call, so I did a similar process and found the jump leading to the ExitProcess call.Do not make clear calls to Winsock and other Windows APIs.So it is definately a product activation related hash.The two jumps found both lead to the ExitProcess call, which is bad.Or in my case, two jumps.Exe (for those that dont want to download the above package and just wanna use the uncracked.7.3d build running around on 4chan.You also need the n included to pass the n checks.Its altered by the code earlier so to change that pointer Now Mario Kart 8 boots.This will be used to backtrack to where the call to ExitProcess is made.Get the Cemu.7.0 Patreon build.This can be done with off the shelf code mutators to obfuscate the code flow and make it much more time consuming for people to reverse.Or in Bohemia Interactives games, weapons can even subtly perform worse over time, even to the point of constantly jamming.
I then trace the flow of the new jump I made.
And the call is only made once.