Oh yeah i was gonna suggest you do that, the reason i used the regionscan is because they put the code in a region of memory this year that can be very slow to scan if you scan the entire memory range, but obviously when they change the code alot, the functions will drop out of the scan range.York2016 wrote: ↑Thu Mar 14, 2019 4:56 amOkay i seemingly was able to figure out how to change over the codes to work for the free weekend/DRM-free version.
instead of aobScanRegion it should be aobscanmodule(like on the older tables) and then it works.
For example, for Tyre wear instead of:
aobScanRegion(TyreAOB, F1_2018_dx12.exe+D000000, F1_2018_dx12.exe+FFFFFFF, F3 0F 58 4F 70)
It should be:
aobscanmodule(TyreAOB,F1_2018.exe,F3 0F 58 4F 70)
It seems that on the Denuvo-less EXE, the AOB in question is before the address cited in aobScanRegion which is why it doesnt enable so just scanning everything will find it . This does work with the new scripts you put in as well such as Engine Performance script (only tested if it enables however)
I just stumbled across this when i compared scripts between the newer 1.16 tables with the older 1.06 tables lol
It does make sense that this works, considering the size difference between the Denuvo and Denuvo-free EXE (260mb vs 30mb respectively), the addresses were bound to have shifted quite a bit.
Will upload the modified tables (1.16 Denuvo-Free/Free Weekend version) if Acido allows it.
For contract script, I'm guessing the Reputation is the one that is broken, i usually need to update that one with every patch, if you take out Reputation the rest should work as a small workaround, for fuel consumption I'm not sure why that one doesn't work on that version, i would have to look at it.
I'm fine with you uploading the modified table, go ahead. I could also attach it in the first post with the others, but there is this annoying limitation of only being allowed to attach 10 files, every time i upload a new table i have to delete one of the old versions but yeah.