Ошибка при сканировании массива байт cheat engine

Is it related with this commit? c0534e3
Did you try to compile CE from source and above issue still exists?

I’m trying to compile the 64 bit but only the 32 app compiles :/ and that doesn’t scan at all.

lazarus-2.0.10-fpc-3.2.0-win64
lazarus-2.0.10-fpc-3.2.0-win32

lazarus-2.0.10-fpc-3.2.0-cross-x86_64-win64-win32
lazarus-2.0.10-fpc-3.2.0-cross-i386-win32-win64

What files should I install?

Does it find when you tick MEM_MAPPED option in «CE Settings->Scan settings»?

If not, you can try modify memscan.pas file, something like changing the lines with «size: dword» or «size: integer» to «size: qword»…

• yeah MEM_MAPPED is ticked
• Still the same changing line 5232: size: dword -> size: qword
• It’s weird because other scans work if they are early in memory (this one is 212629A0A50)
  Start 0000000000000000 Stop 7fffffffffffffff doesn’t find
  Start 21262900000 Stop 7fffffffffffffff does find…

I wrote «something like …».

You can try other places too. Maybe:

• «addressSize: dword» => «addressSize: qword»
• «memorySize: dword» => «memorySize: qword»
• «maxregionsize: dword» => «maxregionsize: qword»

If it still doesn’t work, then, I think there’s no an easy fix like this one c0534e3

Edit:
typo

I don’t know why but that worked, seems to be related to that 2GB, even if it’s not unknown initial value.
Also makes the lua scripts work.
Thank you so much for your help, I’m gonna keep making my cheat table 🙂

You can help and find the smallest possible change which fixes your issue.

Extract source files again. Then:

• do one change, build/compile
• check
• if problem exists, do next change, build/compile
• check

Note: while doing this, you should use Lazarus «Run=>Clean up and build project» (all options selected except «package output directories»).

Seems that
456: maxregionsize: qword; does the job
Normal Cheat Engine 7 doesn’t find anything, but extracting source files and changing that line finds the address.

OK. Thank you. This information should be useful. I’m adding permalink to this line:

what is your buffersize in scansettings?

1024 KB Currently working fine with my compiled CE.
I was changing between 512 and 1024 and more settings but always failed to scan the one that I not compiled.

i can’t see why maxregionsize would cause a difference as it’s size is limited by buffersize.
but i’ll check (tomorrow)

(did you do a full build or a compile after getting the latest source?)

I also have to sleep 🙂

I deleted the entire folder cheat-engine-master and unziped again before editing that one line.
I used «Run=>Clean up and build project»; now has 1130 files but when I tried before it was 0 since I deleted all.

How many bytes is the AOB you’re scanning for ? more than 2000?

If you compile in debug-nomt 64-bit. Does it still fail ?

The array is around 50.
I have others with 500 that work fine.
Complied in debug-nomt 64-bit with the original master folder? Without touching line 456?

Without touching line 456?

Do both, the more information the better.

Both find the address, but takes much more time scanning. Around 3 minutes instead of 15 sec.
I see that master memscan.pas 456 it’s now maxregionsize: qword; instead of maxregionsize: dword;

To be perfectly sure. You extracted source files from that zip file you downloaded earlier, right?

To summarize it. This?

or this?

Yep the first one, debug-nomt 64-bit slowly finds with dword and qword
release finds with qword only
(7.1 / 7.0 / 6.8.3 .exe from the github page don’t find either)