Yes steam verifying said everything was okay. so who knows maybe it somehow curropted some file. I did crash my Reset my PC whilst playing prior to the problem happning whilst installing NVIDIAĬUDA stuff. Unless it was something on Ubi soft side, its come right yesterday and today :) Reinstalling the game appeared to fix it for me. Basically, if it messes with the game, it's a suspect. Anti virus, a trainer/cheat, recording software, stat software, overclocking software. TL DR Check for something that could be messing with the game's code. Anyway, what I'm guessing the game is complaining about is either an injected DLL Is manipulating an IAT (Import Address Table) address, EAT (Export Address Table) address, or something inside the. Completly seprate from FC64.dll, but Ubisoft isn't exactly known for making great decisions. However, this was stupid of them to use, since only cheaters would be abusing this particular part of injection, since pirates just create a wrapped version of uplay_r1_loader64.dll. This particular section you've posted, deals with the CRC32 check that VMProtect employs to try to prevent attackers from manipulating the DLL's integridy, presumably Ubisoft turned this on to stop pirates. That offset (FC64.dll+0x747786) lands you near the DLL's copy protection (VMProtect) section. I made a trainer for Far Cry 4, so I've reverse engineered the game's code quite extensively.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |