| Author |
Posting |
|
The easiest way to check a file is to use the tool made by Scheddy
Aequitas Filechecker (Version 0.92c Beta)
----------
Aequitas File Checker (Executable)
Download executable
Aequitas File Checker (Installer) - incl. Framework (for those who don't have it)
Download installer
--
The dead know only one thing: it is better to be alive.
|
|
|
|
FAQ - Checking Aequitas files
----------
In order to check Aequitas files for manipulation you need to have the latest version of Aequitas. Only using the latest version ensures your results are correct.
After downloading the .zip file start Aequitas and enter the correct "Matchlink". This must be the complete URL to the match the file belongs to. The file checker only works with the correct match URL, otherwise it will show all files as manipulated.
Hint: If Aequitas shows all files being manipulated and you made sure the matchlink is correct you can try to extract the logfile from the archive in question and use the matchlink included there. If this doesn't change anything the file is most likely manipulated.
Now you can push the button "Check File" and browse your computer for the file to check.
Now the "ESL Aequitas Viewer" will be launched. Depending on your PC specs and the size of the file to be checked this may take a while. Now you can see the contents of the file (Screenshots, logfile and a config overview). In the upper left status bar you can see the following info:
- Ok! (this file is not manipulated)
- Old file! (this file was created using an old version of Aequitas. This can also be the case when checking older Aequitas files)
- Manipulated! (this file has been edited or overwritten after it has been created)
Browse the files using the buttons "next" or "prev" on the top of the window. Check the screenshots for possible wrong clientsettings or visible cheats. Please note, not every weird looking screenshot is a cheat. There are several known bugs causing them. This includes invisible parts of the HUD (money, time ammo) or weapon model. Also it is possible to see a player standing inside of a wall when the screenshot was taken between 2 frames or in spectator mode.
After checking the screenshots check the config.txt. Possible ways are either using the Aequitas Viewer or directly extracted from the archive. Now check it for forbidden settings.
Last but not least you should now check the logfile, again either using the Aequitas Viewer or extracted from the .zip archive. The logfile saves a few important things, but also a lot of stuff a player doesn't need. A few explanations what you should look for:
- Command Line Parameters found: (this is the command line used when starting the game, it can also be used to load extra configs or settings)
- Value has been changed: (the setting stated here has been modified during the game, if a forbidden one is shown there may be a rule violation)
- Game has been tabbed. No Screenshot taken. (the user was in windows and a possible screenshot was not made as screenshots of the desktop of a user is not needed)
- Customfiles: (all listed files are usually custom files and sounds from public servers)
- Servertime (GMT!): (the serverside time Aequitas was started at, this entry should be compared with other files of the same match, if a user uploaded his files later than others)
1st- Timings
No matter what timings there are listed. Noone has been banned for cheating because of his timings. There has been a cheat once increasing the timings, but this is ages ago and the cheats nowadays only increase the timings by maybe 10 ms, which is far not enough to catch someone with one.
2nd- Screenshots
In general there is one rule: If there is something on the screenshot not belonging to the game it is most likely a cheat. Also if there is less on the screenshot than usual this is no cheat. Missing weapon models, heaven, HUD, etc. are no cheats!
The amount of screenshots is completely random. Having only 2 screenshots in a file while the filecheck says everything is ok, there is nothing wrong with it.
3rd- Processes
Started and closed applications are not automatically cheats, not even if they appear along with every screenshot. Processes having a size of 0kb are no cheats. They appear when Aequitas has no permission to check the process or due to a bug. Also it is not possible to detect a cheat only by seeing its process name. Anyone can rename a file.
The only accurate way to detect a cheat is the following: If you think a launched application is a hack you got the MD5 checksum of it. Compare this checksum with any cheat you can find on the internet. THe MD5 is quite accurate, so if you find it elsewhere being a hack this is 99.999% sure the one you found.
Summary:
- A cheat can in most cases only be found by seeing something on a screenshot not belonging to the game
- Aequitas is best to check the configs for forbidden clientsettings
- Whenever Aequitas says there is nothing manipulated, there is nothing manipulated.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
INFO: systemcritical info
----------
Sometimes the message "THIS LOGFILE CONTAINS SYSTEMCRITICAL INFORMATIONS!" appears on top of a logfile. This means Aequitas was not able to contact the ESL server during and/or after a match. The file is still a valid one.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
INFO: 16/32bpp bug
----------
- Warning: Measured color depth while running the game was 16bpp!
When this message appears in your log and you surely used 32bpp make sure you set your windows color depth to 32bpp as well.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
INFO: Different Screenshots
----------
Sometimes Aequitas crashes while converting screenshots from bmp to jpg. In such a case the file is generated with different types of screenshots. A message checking this file would look like the following one: "Warning! There should be 10 Screenshots, but there are 9."
To make sure everything is correct open the logfile and count the screenshots being taken. and compare the amount with the one of the converted screenshots on the bottom of the logfile and with the screenshots in the .zip file.
The amount of taken screenshots must equal the amount of all images in the archive. The amount of converted screenshots must equal the amount of .jpg images in the archive.
Example:
- "Warning! There should be 10 Screenshots, but there are 9."
- 10 screenshots were taken
- 9 screenshots were converted to jpg
- The archive contains 9 .jpg images and one .bmp image
In this case everything is ok as long the file checker doesn't say any file is manipulated.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
BUG: No SteamID in the logfile
----------
- SteamID: (Note: this value might be not correct!)
This function doesn't work properly and can be ignored.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
INFO: wmiprvse.exe & wmiapsrv.exe & Wuauclt.exe
----------
Those files are windows system files.
The files starting with wmi belong to the "Windows Management Instrumentation (WMI)". The Wuauclt.exe is responsible for Windows updates.
--
The dead know only one thing: it is better to be alive.
|
|
|
|
INFO: Config files with *.rc extension
----------
Normal config files which are also being read and logged by Aequitas.
--
The dead know only one thing: it is better to be alive.
|
|
|
This Topic is closed.
English (en)
USA
>
Aequitas 
Counter-Strike
FIFA 09
Jedi Knight:Jedi Academ..
