Patch / Update 350.1 about gta5fov HOT 3 CLOSED

I don't know whether these functions detect the FoV mod, I haven't analysed them.

The mod still works with the newest patch, though, and ScriptHook breaking has nothing to do with them.

from gta5fov.

I saw a thread on reddit about this, not talking about any other type of loaders.
https://www.reddit.com/r/GrandTheftAutoV_PC/comments/347nxq/uninstall_your_fov_mods/

And as if we are to talk about the "anti"-functions that prevent us from doing what we want, CheckDllName doesn't care about what is being loaded, it's for how it's being loaded.

And dsound is being exploited with every other mod so theres a real possibility that FoV mod could catch aswell.

But this is just a note, not saying anything needs to be done whilst this is unconfirmed. As per reddit comments as a source.

Also these anti-functions were on a reverse forum here are the decompiled functions in pseudo C https://www.unknowncheats.me/forum/1215235-post8.html

I'm sorry if this issue sounded aggregating. This is by no means a personal attack or a standpoint of other modding.

from gta5fov.

I'm sorry if this issue sounded aggregating. This is by no means a personal attack or a standpoint of other modding.

No worries, thanks for informing me, actually.

The Reddit thread you linked was posted before the update, which makes it look pretty dubious in retrospect.

I looked up the the UnknownCheats thread before, and the decompilate posted doesn't really say too much, I'd have to disassemble the game and analyse those functions in context to know more.

Based purely on the function names, I'd speculate that MemoryRegionCheckDllName is used to check loaded modules by name and MemoryRegionCheckMemoryHash is used to check for signatures of known cheats.

"dsound.dll" being the name of the original DirectX DLL as well, it wouldn't look too suspicious (unlike things like GTALua's lua.dll), but they could totally have a signature of the FoV mod in there. Or they could not, I just don't know.

from gta5fov.