О невидимых трассах в .ntrk в 1.22
На UBI прочитал:
Dear players,
We've decided to explain certain important features and fixes to you in case you have some questions regarding the 1.22 patch.
In order to address online cheating we've made the following changes:
- Improved protection against speed cheating programs like Speedhack;
- Preemptively increased checks on Unlimited Ammo use, as there was a theoretical possibility of such cheats.
Because of this, the NTRK tracks no longer display recording player's cannon and MG shots, even though the track does record these events, and their damage is correctly displayed. This was necessary because of the changes listed above.
We will attempt to rectify the NTRK situation in the Ace Expansion Pack, which will also contain an even higher anti-cheating protection ensuring continuously stable online play in the future.
Additional Information on checks against SpeedHack-like cheats.
- Speedhack protection has been included since the first version of Il-2. Il-2 and FB net code continuously synchronizes the time between the client and the server. The protection is activated when the time difference between the server and client is more than 20% and it continues for more than 17 seconds. This will cause the client to get disconnected from the server.
- After FB version 1.11 the conf.ini file contains two new parameters: checkServerTimeSpeed and checkClientTimeSpeed. They allow the server to turn off this protection for situations when smooth time progression cannot be maintained (see http://support.microsoft.com/default...b;en-us;274323).
- FB version 1.22 will have two new additional keys in conf.ini: checkTimeSpeedDifferense and checkTimeSpeedInterval. These will allow the server to set the maximum difference in time as well as the maximum allowed time period. The minimum value for the checkTimeSpeedDifferense parameter is 0.01 (1%), and for the checkTimeSpeedDifferense the minimum value is 1 (1 second). Default values are 0.2 (20%) and 17 (17 seconds). The preset values are sent to the chat window on all connected clients as the following message: checkTimeSpeed N sec K%.
Setting the new parameters to extremely low values may cause the cheat protection to kick in even when speedhacks are not used. This may especially happen when the connection quality is low and connectivity errors occur. This may also happen if the hardware malfunctions, such as overheating of the computer timer causing frequency changes.
