Difference between revisions of "Help File:Scan settings"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:Help]] | |
| − | + | [[Category:Settings]] | |
For a lot of users, this will be the config screen that they are most accustomed to seeing and using, | For a lot of users, this will be the config screen that they are most accustomed to seeing and using, | ||
as it relates directly to the memory-searching process. Let's take a look.. | as it relates directly to the memory-searching process. Let's take a look.. | ||
Latest revision as of 02:46, 20 March 2017
For a lot of users, this will be the config screen that they are most accustomed to seeing and using, as it relates directly to the memory-searching process. Let's take a look..
Size of scanbuffer (KB): <type here>: This allows you to override the default buffer value used when
scanning memory. Raising this to 1024 or perhaps even 2048 is good for most modern systems,
and will speed up your scanning process a bit. Raising it too high though will yield a negative effect
(which is why it's low in the first place to accommodate for most users).
Fast scan on as default: You can check this box to make all of your memory searches aligned, unless you state otherwise in the main interface. This will cause all memory scans to only return addresses aligned to a 32-bit boundary (or ending in 0,4,8,C / divisible by 4). This will dramatically speed up memory scans, and is good for 99% of cases. Rarely though, you may miss key addresses with this turned on.
Don't scan memory that is protected with the No Cache option: Mainly a useful consideration if you are experience strange crashes/lockups while scanning memory. Checking this will prevent Cheat Engine from scanning memory regions which are protected with 'no cache'. Usually these areas are used by graphics and other hardware drivers, and I have never seen a case where games store variables here. Basically leave it off unless you have an issue, in which case give this a whirl.
Custom types will be included in the ALL scan variabletype: Custom scan scripts will be used along with other default variable types when you are using ALL as a variable type for scanning.
Don't store the temporary scanfiles in the windows tempdir: Specify a new location where cheat engine should store the temporary files.
MEM_PRIVATE: Will allow CE to scan 'private' memory. Leave it on in most cases.
MEM_IMAGE: ...scan memory that is mapped into the view of an image section. Leave it on also.
MEM_MAPPED: ...scan memory that is mapped into view of a section (file-mapping). Off by default. Slow!
Thread priority <Choose option>: Here you can assign a priority to the scan thread used by CE when
searching through memory. It is best left on it's default of Higher or one-down on Normal. Setting it too low can
cause scans to become very slow, and too high can cause the system to become unresponsive.
