X-Aim.cfg Explained

X-Aim.cfg is a configuration file that is stored on your computer that includes advanced 'under the hood' settings for the X-AIM plugin. This information isn't really for the casual user, however there may be some cases that advanced users may want to try and tune their settings a little further.
Here is an example of the contents of the file:
DirectInputDeviceName= XInput Controller (XBOX 360 For Windows)
; Don't change these settings unless you know what you are doing
The X-Aim.cfg is stored at the following location: C:\Users\<username>\AppData\Roaming\Cronus\Plugins or %APPDATA%\Cronus\Plugins

Explanation of each value:

ExitMode: This is a flag that says which exit mode you are using. This is related to Capture Mode.
0 - Ctrl + Esc (default)
1 - Esc
SelectedLayout: A numerical identifier that is linked to the list of X-AIM layouts so that the last selected on is recalled upon loading.
Dpi: This option sets the DPI Multiplier, internally this is how it's used:
multiplier = 800 / Dpi
x = x * multiplier
y = y * multiplier
It's applied prior to entering the math converting your mouse movements to stick input and essentially lowers/raises the value depending on your DPI since your mouse will be much more sensitive then a stick would normally be (if you have a gaming mouse).
DirectInputEnabled: A boolean flag stating if DirectInput should be enabled by default when you open X-AIM (it checks for the word "true", anything else is treated as false).
DirectInputGuid: This is a unique identifier for the connected controller. It's primarily there for X-AIM to remember what controller to use.
DirectInputIsXInput: A boolean flag stating if the selected controller should use the XInput interface (Xbox 360/Xbox One compatible controllers only), it works in a similar way to DirectInputEnabled.
DirectInputDeviceName: A string displayed when the GUID above can't be found and DI is enabled.
DirectInputRumble: A boolean flag stating if the selected controller should use enable Rumble (works in a similar way to DirectInputEnabled).
DirectInputDeadzone: A integer value ranging from 0 to 99 - What this value does is ignore any values below the specified limit on the sticks (Lx, Rx, Ly, Ry) for DirectInput/XInput.
IgnoreController: A boolean flag that decides if the inputs of the authorization controller are disabled.
DisableCMRumble: A boolean flag that decides if the rumble motors of the controller connected to the input port of the CronusMAX PLUS are disabled.
OverlayOpacity: This value sets the opacity of the monitor while X-AIM is in capture mode. You can set it to be completly black (100) or disabled (0). The default is 75.
Now we come to the somewhat 'dangerous' values:
SamplingCount: This value decides how many mouse state samples to keep in memory - The more you have, the more we can use for the math, the range of this value is 100 to 2 147 483 647, it only takes integer values (no decimals) - The higher this value is, the better... but, it also depends on your computer, you don't want it too high as it'll eat up your memory if you put it at maximum, if you put this value too low, when the mouse is polled for it's state the oldest entry will be removed and thus cannot be used to determine how much your mouse has moved since last operation.
SamplingTime: This value decides how far back in time mouse state samples should be taken into account when getting the current mouse state - Higher value means a higher output value as we're taking more values into account, as a result the sensitivity will be higher (faster movements etc). you can specify this with a decimal if you want, the unit used is milliseconds, but it's VERY high precision under the hood, so you can specify it VERY far down if you wanted to (pretty useless to go that deep, stick to something like 0.01 as a range, further then that and you're going into the extremes where you won't really see much of a difference.
SamplingDebugging: A boolean flag telling X-AIM to enable the debugging of sampling - Meaning display the number of samples used in the last mouse state poll - The information is placed in TRACE_1 and is limited to a maximum number of 32,767 which is quite a lot, NOTE: Scripts that write to TRACE_1 WILL overwrite this value regardless of what this flag is set to, the way this flag works is similar to DirectInputEnabled.
This flag is hidden by default (essentially, when you set it to it's default value - false, it will skip writing it to the HDD) it's hidden because we didn't want to clutter the config with flags that are highly unlikely to be used much. It's primarily in there to allow you see exactly how your sampling settings are used.
Setting this to true makes it output to TRACE_1, if you leave it set to false the count isn't displayed anywhere.
ScrollwheelTiming: This value is used to determine how long the scroll wheel should be considered "pressed" for when you scroll a single tick (it's used as a minimum timing so it will be held at least x milliseconds for a single notch on your scroll wheel this value is a integer type meaning it doesn't take into account decimals. The range of this is 10 to 2,147,483,647. Internally this is divided by 1000 as a small optimization.
MouseUpdateFrequency: This value is used to determine how long to wait between polling for new inputs to the mouse, it'll be at least x milliseconds between each poll, this value is a integer type meaning it doesn't take into account decimals. The range of this is 1 to 1000, internally it's divided by 1000 as a small optimization.
KeyboardUpdateFrequency: Same as MouseUpdateFrequency, except for the Keyboard.
DirectInputUpdateFrequency: Same as MouseUpdateFrequency, except for DirectInput/XInput.