Layout Configuration

Configuring a layout begins with the assigning of keyboard and mouse inputs (keys, buttons, mouse movements, etc) to the buttons on the controller. You can start by looking up the settings info on the PC version of the game, and try to use the same keys in your X-AIM layout. The second step is to adjust the X-AIM mouse parameters to achieve a PC like movement between your mouse movement and the in-game reticule movement. Optionally you can also develop a GPC script for advanced customization, one button press macros, automation of commands, event reaction and more. You can find help in the support forums on how to achieve this.
When running X-AIM and Capture Mode, make sure you have any other programs closed down, especially web browsers such as Firefox, as this may cause lag. You want the signal between your Keyboard and Mouse to your console to be as clean as possible.

Layout Configuration
Layout Options
 Set of tools and operations for configuration of the active X-AIM layout, as described below:
Lock Editing: Checkable menu item for lock/unlock the layout editing, useful to prevent unintended changes on a finished layout. The lock operation can also be performed through keyboard shortcut (Ctrl+L).
Layout Summary: Opens the Layout Summary dialog window. It shows the layout name, controller type, GPC script information, all buttons assignments and mouse settings.
Controller: Selection menu to choose the background controller image. This setting is merely visual and has no effect on the layout operation. e.g. You can perfectly use a X-AIM layout with an Xbox One controller background on a PS3 console.
Rename: Shows a dialog box to rename the active layout.
Mouse Settings: Opens the Mouse Settings window where the mouse parameters can be adjusted through intuitive controls and a graphical visualization of transformation curves. The circle test can help to find out the optimal settings for every game.
Load GPC Script: Compiles the GPC script currently active on Cronus PRO's code editor. If the compilation succeed the bytecode of the script is loaded into the X-AIM layout. The information about the loaded GPC script (bytecode) is shown on the status bar.
Unload GPC Script: Unload any GPC Script (bytecode) of the active layout.
Button Mapping
Mapping the keyboard and mouse to a X-AIM layout is easy, as well as binding a Direct Input entry. Simply right click on any layout button and pick an option from the popup menu. The layout can be highly customized, meaning you can link any keyboard, mouse or DI input to any controller entry. For example you can assign a mouse movement to the motion sensor or to a regular controller button, so when you push your mouse up it will be translated to the CROSS button.
The popup menu will not open if the layout editing is locked in the Layout Options menu.

 • Keystroke: Assign a keyboard key to the selected controller entry. By choosing this item a dialog box will open to read the input key. X-AIM can recognize virtually any key available in your keyboard. International keyboards may show different key symbols on the layout buttons.
Mouse Button: Assign a mouse button to the selected controller entry. By choosing this item a dialog box will open to read the mouse button. X-AIM supports a mouse with up to 5 buttons.
Mouse Wheel: Assign the mouse wheel up or the mouse wheel down events to the selected controller entry.
Mouse Movement: Assign a mouse movement (up, down, left or right) to the selected controller entry. The mouse movement is usually assigned to the right analog stick, but you can assign this input to any button entry.
Direct Input Catch: Bind a DI input to the selected controller entry. By choosing this item a dialog box will open to read the DI input button from the controller.
Direct Input List: Bind a DI input to the selected controller entry. Choose a DI input from a list.
Clear: This option will clean all assignments on the selected controller entry.
More: Assign up to 10 inputs to the selected controller entry, check out the next subject (Additional Mappings) for more details in this regard.

Binding a DI input to the selected controller entry

By clicking on the [Direct Input Catch], a dialog box will open and wait for the user to press a button or an analog direction on the controller.
Alternatively, clicking on the [Direct Input List] a dialog window will popup with all available game controller inputs. Select the appropriate input and hit the OK button to save your selection, or click on the Cancel button to close the window without any changes. The user can check which inputs are active for the currently connected game controller on the DI Settings window.
 • Analog Inputs (lX, lY, lZ, lRX, lRY, lRZ, Slider1 and Slider2)
Each analog input is split in two, by its signal, representing one specific direction (up, down, left, right, forward or back). The meaning of the direction is dependent on the Direct Input entry and of the controller model.
D-Pad Inputs (POV1, POV2, POV3 and POV4)
The POV members contains the D-Pad position in degrees clockwise from north. Where 0 means UP, 90 means RIGHT, 180 mean DOWN and 270 means LEFT.
Up to 4 D-Pads are supported, however only the POV1 is commonly found in game controllers.
Button Inputs (Button 1 to 32)
The Buttons are grouped in an array of entries, one for each of 32 buttons. The meaning of each button is dependent on the controller in use. You can check the button actuations on the DI Settings window.
Additional Mappings
The Additional Mappings dialog box allows you to assign up to 10 inputs to a single controller entry. The first one (1) is the main entry and corresponds to the one in the main window. The assigning procedure is the same described in the Button Mapping subject.
    A green line on the bottom of a given button entry indicates that it has multiple assignments.
Extra Inputs
The extra inputs are available mainly to be used in conjunction with GPC scripts, where you can have, for example, a shortcut key to start a macro or set certain configurations in your script.
GPC identifiers for extra inputs:
The first 4 extra inputs correspond to the motion sensors of DualShock 3 controllers (Accelerometer X, Accelerometer Y, Accelerometer Z and Gyroscope respectively), any assignments to theses entries will be translated to the sensors when using CronusMAX PLUS on PS3 systems. The same is also true for DualShock 4 and PS4 systems, but all extra inputs are used (Accelerometer X, Accelerometer Y, Accelerometer Z, Gyroscope X, Gyroscope Y, Gyroscope Z, Touch, Touch X, Touch Y). Very few games makes use of these sensors, so you are free to use them for other purposes.