GIMX - User contributions [en]

Config Index

2021-02-18T08:48:22Z

Matlo:

This page contains results of every game tested against compatibility with '''GIMX''' software. Tests are done on the latest available version of the game.

For most of games listed with here '''playable''' status on '''GIMX''', there should be a config available to download from the "Help > Get configs" menu in '''gimx-launcher'''. If you are unsure how to do it see the [[Quick_Start#How_to_download_a_config_file|following tutorial]]. For some alternative configs you will need to download them manually, just click the More Info link of the config you want to download.

If there is some info missing in particular config feel free to add it! We will be happy to submit it to the repository. Not only you will help other players but you can also became famous as for every config here the author name is displayed.

'''''Note''''': ''Most configs with "No Data" status were submitted before creating this index. Please add your opinion about the config playability to them''

'''''Note''''': ''If you are a config author please add it here using edit Wiki page feature''

==Playability==
{| class="wikitable" style=" border: 1px solid #a2a9b1; border-spacing:3px;padding: 5px; background-color: #f8f9fa;"
!colspan=2|Key
|-
|{{Template:ConfigIndex_Good}}
|style="padding-left: 8px;"|Playable on mouse with little to no acceleration and without input bugs
|-
|{{Template:ConfigIndex_Average}}
|style="padding-left: 8px;"|Playable on mouse but with some amounts of forced smoothing or acceleration
|-
|{{Template:ConfigIndex_Bad}}
|style="padding-left: 8px;"|Barely playable on mouse with massive amounts of smoothing, acceleration and/or input bugs
|-
|{{Template:ConfigIndex_Unplayable}}
|style="padding-left: 8px;"|Unplayable on mouse, mostly due to bad input mechanics implementation in the game engine
|-
|{{Template:ConfigIndex_NoData}}
|style="padding-left: 8px;"|No data about playability level available, feel free to add some!
|}

==Index==
{| class="wikitable sortable" style="text-align: center; min-width: 50%;"
|-
! Title
! Playability
! Date tested
! Tested on
! On repo
! Author
! More info
! Comment
|-
|  Anthem
|  {{Template:ConfigIndex_Unplayable}}
|  18/09/2019
|  PS4
|  {{No}}
|  GoDlike
|  N/A
|  Very odd deadzone shape
|-
|  Apex: Legends
|  {{Template:ConfigIndex_Good}}?
|  10/02/2019
|  Xbox One
|  {{No}}
|  lordaeron
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2909 Link]
|-
|  Army of Two
|  {{Template:ConfigIndex_Good}}
|  25/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3475 Link]
|-
|  Army of Two: The 40th Day
|  {{Template:ConfigIndex_Good}}
|  25/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3498 Link]
|-
|  Battlefield 1
|  {{Template:ConfigIndex_Good}}
|  17/02/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2479 Link]
|-
|  Battlefield 1
|  {{Template:ConfigIndex_Good}}?
|  02/02/2017
|  PS4
|  {{No}}
|  DoM__
|  [https://forum.gimx.fr/viewtopic.php?p=11195#p11195 Link]
|  Not longer compatible after BF1 update
|-
|  Battlefield 1943
|  {{Template:ConfigIndex_Good}}
|  13/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3425 Link]
|-
|  Battlefield 2: Modern Combat
|  {{Template:ConfigIndex_Good}}
|  28/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3549 Link]
|-
|  Battlefield 2: Modern Combat
|  {{Template:ConfigIndex_Average}}
|  30/09/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1814 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_Good}}
|  31/05/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3413 Link]
|  Correct Dead Zone shape. Tank/Jet/Heli config added.
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  29/09/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=288 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  06/12/2011
|  PS3
|  {{No}}
|  sp3c14list
|  [https://gimx.fr/forum/viewtopic.php?p=2154 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  15/02/2012
|  PS3
|  {{No}}
|  rizzlan
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=424&p=2478 Link]
|-
|  Battlefield 4
|  {{Template:ConfigIndex_Good}}
|  10/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3423 Link]
|-
|  Battlefield 4
|  {{Template:ConfigIndex_NoData}}
|  No Data
|  PS4
|  {{Yes}}
|  foxy
|  N/A
|-
|  Battlefield 4
|  {{Template:ConfigIndex_Good}}
|  11/02/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2911 Link]
|-
|  Battlefield Hardline
|  {{Template:ConfigIndex_Good}}
|  05/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3623 Link]
|-
|  Battlefield Hardline
|  {{Template:ConfigIndex_NoData}}
|  03/04/2015
|  PS3
|  {{No}}
|  shatterstar78
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1185 Link]
|-
|  Battlefield V
|  {{Template:ConfigIndex_Good}}
|  20/11/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2806 Link]
|-
|  Battlefield: Bad Company
|  {{Template:ConfigIndex_Average}}
|  06/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3418 Link]
|  Games dead zone shape is big and most likely diagonal
|-
|  Battlefield: Bad Company 2
|  {{Template:ConfigIndex_Good}}
|  31/05/2020
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3414 Link]
|-
|  Battlefield: Bad Company 2
|  {{Template:ConfigIndex_Average}}
|  No Data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|  Game has low max turning speed.
|-
|  Bioshock
|  {{Template:ConfigIndex_Bad}}
|  08/06/2020
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3422 Link]
| Input filtering and random acceleration, also bad on controller.
|-
|  Bioshock
|  {{Template:ConfigIndex_Unplayable}}
|  28/02/2020
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Input filtering and random acceleration, also bad on controller.
|-
|  Bioshock Infinite
|  {{Template:ConfigIndex_Unplayable}}
|  06/06/2020
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Weird deadzone, acceleration spikes
|-
|  Black
|  {{Template:ConfigIndex_Average}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3520 Link]
|-
|  Black
|  {{Template:ConfigIndex_Average}}
|  08/09/2017
|  <abbr title="Original Xbox emulator in X360">Xbox 360E</abbr>
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2208 Link]
|-
|  Blacklight: Retribution
|  {{Template:ConfigIndex_Unplayable}}?
|  29/07/2014
|  PS4
|  {{Yes}}
|  Kekskrümel
|  [https://gimx.fr/forum/viewtopic.php?f=3&t=1038&p=6073 Link]
|-
|  Borderlands
|  {{Template:ConfigIndex_Good}}
|  28/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3656 Link]
|-
|  Borderlands 2
|  {{Template:ConfigIndex_Good}}
|  11/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3663 Link]
|-
|  Borderlands 3
|  {{Template:ConfigIndex_Good}}
|  13/09/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3182 Link]
|-
|  Borderlands: The Handsome Collection
|  {{Template:ConfigIndex_Good}}
|  10/06/2019
|  PS4
|  {{No}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3064 Link]
|-
|  Brothers in Arms: Earned in Blood
|  {{Template:ConfigIndex_Average}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3540&p=19484#p19484 Link]
|  Wierd dead zone shape
|-
|  Brothers in Arms: Road to Hill 30
|  {{Template:ConfigIndex_Average}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3540&p=19484#p19484 Link]
|  Wierd dead zone shape
|-
|  Bulletstorm
|  {{Template:ConfigIndex_Good}}
|  17/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3671 Link]
|-
|  Call of Duty 2: Big Red One
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3522&p=19449#p19449 Link]
|-
|  Call of Duty 3
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3524 Link]
|-
|  Call of Duty: Black Ops
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Call of Duty: Black Ops
|  {{Template:ConfigIndex_NoData}}
|  11/07/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=38 Link]
|-
|  Call of Duty: Black Ops 4
|  {{Template:ConfigIndex_Good}}
|  12/10/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2772 Link]
|-
|  Call of Duty: Modern Warfare
|  {{Template:ConfigIndex_Good}}
|  12/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3666 Link]
|-
|  Call of Duty: Modern Warfare 2
|  {{Template:ConfigIndex_Good}}
|  04/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3660 Link]
|-
|  Call of Duty: Modern Warfare 3
|  {{Template:ConfigIndex_Good}}
|  11/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3664 Link]
|-
|  Call of Duty: Modern Warfare Remastered
|  {{Template:ConfigIndex_Good}}
|  20/01/2019
|  PS4
|  {{Yes}}
|  4773n0x
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2881 Link]
|-
|  Crysis 2
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Crysis 3
|  {{Template:ConfigIndex_Good}}
|  25/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3651 Link]
|-
|  Dark Souls 3
|  {{Template:ConfigIndex_NoData}}
|  23/04/2016
|  PS4
|  {{Yes}}
|  cajuil
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=1625&p=9952 Link]
|-
|  Dead Space
|  {{Template:ConfigIndex_Average}}
|  25/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3445 Link]
|  Game lacks ingame sensitivity change
|-
|  Destiny
|  {{Template:ConfigIndex_Good}}?
|  23/07/2014
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://gimx.fr/forum/viewtopic.php?t=1227 Link]
|-
|  Deus Ex: Human Revolution
|  {{Template:ConfigIndex_Good}}
|  07/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3420 Link]
|  Slow turnspeed
|-
|  Dishonored
|  {{Template:ConfigIndex_Average}}
|  22/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3444 Link]
|  Ingame sensitivity has to be under 10 or pixel skipping will occur
|-
|  Dishonored 2
|  {{Template:ConfigIndex_Unplayable}}
|  21/04/2018
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Extreme input lag by game engine
|-
|  DOOM
|  {{Template:ConfigIndex_Good}}
|  24/10/2017
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2268 Link]
|-
|  Doom 3
|  {{Template:ConfigIndex_Good}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3530 Link]
|-
|  Doom 3
|  {{Template:ConfigIndex_Good}}
|  26/01/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3297&p=18337#p18337 Link]
|-
|  DOOM Eternal
|  {{Template:ConfigIndex_Average}}
|  16/04/2020
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3361 Link]
|-
|  Fallout 4
|  {{Template:ConfigIndex_Bad}}
|  22/12/2016
|  PS4
|  {{No}}
|  Johny
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1949 Link]
|  Config lacks an ADS profile. High DPI needed.
|-
|  Fallout 4
|  {{Template:ConfigIndex_Average}}
|  18/02/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2476 Link]
|  Game input is not good. High DPI needed.
|-
|  Far Cry 2
|  {{Template:ConfigIndex_Unplayable}}
|  18/01/2021
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3640 Link]
|  Game has bad variable acceleration.
|-
|  Far Cry 3
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Far Cry 4
|  {{Template:ConfigIndex_Good}}
|  22/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3497 Link]
|-
|  Far Cry 5
|  {{Template:ConfigIndex_Average}}
|  02/04/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2537 Link]
|-
|  Far Cry Evolution
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3539&p=19483#p19483 Link]
|-
|  Far Cry Instincts
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3539&p=19483#p19483 Link]
|-
|  FEAR 3
|  {{Template:ConfigIndex_Good}}
|  21/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3647 Link]
|  Game has slower turn speed when aiming down sight.
|-
|  Gears of War 1
|  {{Template:ConfigIndex_Good}}
|  11/05/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1648 Link]
|-
|  Gears of War 2
|  {{Template:ConfigIndex_Average}}
|  16/05/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1661 Link]
|-
|  Gears of War 3
|  {{Template:ConfigIndex_Average}}
|  20/08/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1757 Link]
|-
|  Ghost Recon: Advanced Warfighter
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3523 Link]
|-
|  Ghost Recon: Future Soldier
|  {{Template:ConfigIndex_Good}}
|  12/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3519 Link]
|  No way to disable aim assist
|-
|  Ghost Recon: Wildlands
|  {{Template:ConfigIndex_Unplayable}}
|  20/09/2018
|  PS4
|  {{No}}
|  GoDlike
|  N/A
|  Bad input implementation
|-
|  GoldenEye 007:Reloaded
|  {{Template:ConfigIndex_Good}}?
|  18/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1772 Link]
|-
|  GoldenEye 007:Reloaded
|  {{Template:ConfigIndex_Good}}
|  28/03/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1772 Link]
|-
|  Grand Theft Auto V
|  {{Template:ConfigIndex_Good}}
|  26/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3500 Link]
|  More buffer needed on low DPI mouse to prevents the ingame acceleration to take over.
|-
|  Halo
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3526 Link]
|-
|  Halo 2
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3527 Link]
|-
|  Halo 3
|  {{Template:ConfigIndex_Good}}
|  07/07/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2661&p=14907#p14907 Link]
|-
|  Halo 4
|  {{Template:ConfigIndex_Good}}
|  02/08/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1734 Link]
|-
|  Halo 5: Guardians
|  {{Template:ConfigIndex_Good}}
|  30/01/2016
|  Xbox One
|  {{No}}
|  sephirotdnf
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1450 Link]
|  Config lacks an ADS profile.
|-
|  Halo: CEA
|  {{Template:ConfigIndex_Average}}
|  04/03/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2496 Link]
|-
|  Halo: Reach
|  {{Template:ConfigIndex_Average}}
|  19/07/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2674 Link]
|-
|  HAZE
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2698 Link]
|-
|  Hitman: Absolution
|  {{Template:ConfigIndex_Good}}
|  25/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3446 Link]
|-
|  Homefront
|  {{Template:ConfigIndex_Good}}
|  01/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3659 Link]
|-
|  Horizon: Zero Dawn
|  {{Template:ConfigIndex_Average}}
|  28/01/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2455 Link]
|-
|  Infamous
|  {{Template:ConfigIndex_Average}}
|  14/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3429 Link]
|  Unpredictable acceleration and only 3 sensitivity options ingame
|-
|  Infamous: Second Son
|  {{Template:ConfigIndex_Bad}}
|  03/02/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2459 Link]
| Severe input bugs in game engine
|-
|  Killzone 1 HD
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2699 Link]
|-
|  Killzone 2
|  {{Template:ConfigIndex_Bad}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2700 Link]
|  Genuine DS3 with Gyroscope is required
|-
|  Killzone 3
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2701 Link]
|-
|  Killzone 3
|  {{Template:ConfigIndex_Average}}
|  31/07/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=151 Link]
|-
|  Killzone: Shadow Fall
|  {{Template:ConfigIndex_Average}}
|  No Data
|  PS4
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Mass Effect 2
|  {{Template:ConfigIndex_Good}}
|  25/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3499 Link]
|-
|  Max Payne
|  {{Template:ConfigIndex_Good}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3531&p=19464#p19464 Link]
|-
|  Max Payne 2
|  {{Template:ConfigIndex_Average}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3533 Link]
|  Macro needed for faster turn speed.
|-
|  Max Payne 3
|  {{Template:ConfigIndex_Good}}
|  12/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3518 Link]
|  Vertical aim is slow in the game, so horizontal needs to be reduced to 7 in-game
|-
|  Medal of Honor 2010
|  {{Template:ConfigIndex_Good}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3491 Link]
|-
|  Medal of Honor: European Assault
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3541 Link]
|-
|  Medal of Honor: Frontline
|  {{Template:ConfigIndex_Unplayable}}
|  10/10/2017
|  PS3
|  {{No}}
|  GoDlike
|  N/A
|-
|  Medal of Honor: Warfighter
|  {{Template:ConfigIndex_Good}}
|  22/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3468 Link]
|-
|  Metro: Exodus
|  {{Template:ConfigIndex_Average}}
|  03/05/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2917 Link]
|  Install 1.03 patch
|-
|  Mirrors Edge
|  {{Template:ConfigIndex_Good}}
|  12/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3424 Link]
|-
|  Nioh: Complete Edition
|  {{Template:ConfigIndex_Good}}
|  13/02/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2473 Link]
|-
|  Overwatch
|  {{Template:ConfigIndex_Good}}
|  06/07/2018
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1685 Link]
|-
|  Paladins
|  {{Template:ConfigIndex_Average}}
|  24/10/2017
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2269 Link]
|-
|  Payday: The Heist
|  {{Template:ConfigIndex_NoData}}
|  18/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=390&p=2280 Link]
|-
|  Perfect Dark
|  {{Template:ConfigIndex_Bad}}
|  24/9/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1796 Link]
|-
|  PUBG
|  {{Template:ConfigIndex_Good}}
|  22/8/2018
|  Xbox One
|  {{Yes}}
|  lekken
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2717 Link]
|-
|  PUBG
|  {{Template:ConfigIndex_Good}}
|  07/12/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2820 Link]
|-
|  RAGE 2
|  {{Template:ConfigIndex_Good}}
|  16/05/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&p=17105#p17105 Link]
|-
|  Rainbow Six: Siege
|  {{Template:ConfigIndex_Good}}
|  10/11/2016
|  PS4
|  {{Yes}}
|  DiJu519
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1879 Link]
|-
|  Rainbow Six: Siege
|  {{Template:ConfigIndex_Good}}?
|  27/02/2019
|  Xbox One
|  {{No}}
|  Fluffywafflz
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2939 Link]
|-
|  Red Dead Redemption/ Undead Nightmare
|  {{Template:ConfigIndex_Average}}
|  25/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=3650 Link]
|  No way to disable aim assist
|-
|  Red Dead Redemption
|  {{Template:ConfigIndex_NoData}}
|  25/02/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=474&p=2830 Link]
|-
|  Red Dead Redemption 2
|  {{Template:ConfigIndex_Bad}}
|  28/10/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2792 Link]
|  Input filtering, bad controls
|-
|  Resistance 1
|  {{Template:ConfigIndex_Good}}
|  03/12/2016
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1916 Link]
|-
|  Resistance 2
|  {{Template:ConfigIndex_Average}}
|  11/12/2016
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1933 Link]
|-
|  Resistance 3
|  {{Template:ConfigIndex_Good}}
|  13/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=383 Link]
|-
|  Return to Castle Wolfenstein
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3528 Link]
|-
|  Sniper Elite
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3538 Link]
|-
|  Sniper Elite 3
|  {{Template:ConfigIndex_Good}}
|  07/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3626 Link]
|-
|  Sniper Elite 4
|  {{Template:ConfigIndex_Good}}
|  17/10/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3201 Link]
|-
|  Sniper Elite V2
|  {{Template:ConfigIndex_Good}}
|  14/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3636 Link]
|-
|  Sniper: Ghost Warrior
|  {{Template:ConfigIndex_Good}}
|  29/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3657 Link]
|  Very slow ads aiming while scoped.
|-
|  Sniper: Ghost Warrior 2
|  {{Template:ConfigIndex_Average}}
|  05/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3624 Link]
|  This game has bad micromovements with high ingame sensitivity.
|-
|  Splinter Cell: Blacklist
|  {{Template:ConfigIndex_Good}}
|  17/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3494 Link]
|-
|  Splinter Cell: Chaos Theory
|  {{Template:ConfigIndex_Good}}
|  17/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3534 Link]
|-
|  Star Wars: Republic Commando
|  {{Template:ConfigIndex_Good}}
|  08/03/2019
|  Xbox One
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3145 Link]
|-
|  StarHawk
|  {{Template:ConfigIndex_Good}}
|  25/11/2017
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2350&p=13125#p13125 Link]
|-
|  Syndicate
|  {{Template:ConfigIndex_Good}}
|  23/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3472 Link]
|-
|  The Chronicles of Riddick
|  {{Template:ConfigIndex_Average}}
|  19/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3536 Link]
|  Acceleration spikes when turning
|-
|  The Darkness
|  {{Template:ConfigIndex_Unplayable}}
|  09/09/2016
|  Xbox 360
|  {{No}}
|  GoDlike
|  N/A
|-
|  The Last of Us
|  {{Template:ConfigIndex_Average}}
|  01/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3658 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  The Last of Us
|  {{Template:ConfigIndex_NoData}}
|  19/03/2014
|  PS3
|  {{Yes}}
|  pawel
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=952&p=7898 Link]
|  Only Profile 1 is configured.
|-
|  Titanfall 2
|  {{Template:ConfigIndex_Good}}
|  28/08/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2686#p15014 Link]
|-
|  Tom Clancy's: The Division
|  {{Template:ConfigIndex_Good}}?
|  25/02/2016
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1507 Link]
|-
|  Tom Clancy's: The Division
|  {{Template:ConfigIndex_Good}}?
|  23/10/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2785 Link]
|-
|  Tom Clancy's: The Division 2
|  {{Template:ConfigIndex_Average}}
|  15/03/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2968 Link]
|-
|  Tomb Raider 2013
|  {{Template:ConfigIndex_Average}}
|  24/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3443 Link]
|  Input filtering
|-
|  Uncharted 1: Drake's Fortune
|  {{Template:ConfigIndex_Average}}
|  10/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3513 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Uncharted 1: Drake's Fortune
|  {{Template:ConfigIndex_NoData}}
|  19/03/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=506 Link]
|-
|  Uncharted 2: Among Thieves
|  {{Template:ConfigIndex_Average}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3493 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Uncharted 2: Among Thieves
|  {{Template:ConfigIndex_NoData}}
|  25/03/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=520 Link]
|-
|  Uncharted 3: Drake's Deception
|  {{Template:ConfigIndex_Average}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3492 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Warhammer 40K: Space Marine
|  {{Template:ConfigIndex_Good}}
|  07/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3421 Link]
|-
|  Watch Dogs
|  {{Template:ConfigIndex_NoData}}
|  No Data
|  PS4
|  {{Yes}}
|  foxy
|  N/A
|-
|  Wolfenstein: The New Order
|  {{Template:ConfigIndex_Good}}
|  26/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3652 Link]
|  Aiming system is "wonky"
|-
|  Wolfenstein 2: The New Colossus
|  {{Template:ConfigIndex_Good}}
|  08/12/2017
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2375 Link]
|  Slightly annoying input lag
|}

Config Index

2021-02-18T08:46:35Z

Matlo: Update ckaiycool's config status

This page contains results of every game tested against compatibility with '''GIMX''' software. Tests are done on the latest available version of the game.

For most of games listed with here '''playable''' status on '''GIMX''', there should be a config available to download from the "Help > Get configs" menu in '''gimx-launcher'''. If you are unsure how to do it see the [[Quick_Start#How_to_download_a_config_file|following tutorial]]. For some alternative configs you will need to download them manually, just click the More Info link of the config you want to download.

If there is some info missing in particular config feel free to add it! We will be happy to submit it to the repository. Not only you will help other players but you can also became famous as for every config here the author name is displayed.

'''''Note''''': ''Most configs with "No Data" status were submitted before creating this index. Please add your opinion about the config playability to them''

'''''Note''''': ''If you are a config author please add it here using edit Wiki page feature''

==Playability==
{| class="wikitable" style=" border: 1px solid #a2a9b1; border-spacing:3px;padding: 5px; background-color: #f8f9fa;"
!colspan=2|Key
|-
|{{Template:ConfigIndex_Good}}
|style="padding-left: 8px;"|Playable on mouse with little to no acceleration and without input bugs
|-
|{{Template:ConfigIndex_Average}}
|style="padding-left: 8px;"|Playable on mouse but with some amounts of forced smoothing or acceleration
|-
|{{Template:ConfigIndex_Bad}}
|style="padding-left: 8px;"|Barely playable on mouse with massive amounts of smoothing, acceleration and/or input bugs
|-
|{{Template:ConfigIndex_Unplayable}}
|style="padding-left: 8px;"|Unplayable on mouse, mostly due to bad input mechanics implementation in the game engine
|-
|{{Template:ConfigIndex_NoData}}
|style="padding-left: 8px;"|No data about playability level available, feel free to add some!
|}

==Index==
{| class="wikitable sortable" style="text-align: center; min-width: 50%;"
|-
! Title
! Playability
! Date tested
! Tested on
! On repo
! Author
! More info
! Comment
|-
|  Anthem
|  {{Template:ConfigIndex_Unplayable}}
|  18/09/2019
|  PS4
|  {{No}}
|  GoDlike
|  N/A
|  Very odd deadzone shape
|-
|  Apex: Legends
|  {{Template:ConfigIndex_Good}}?
|  10/02/2019
|  Xbox One
|  {{No}}
|  lordaeron
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2909 Link]
|-
|  Army of Two
|  {{Template:ConfigIndex_Good}}
|  25/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3475 Link]
|-
|  Army of Two: The 40th Day
|  {{Template:ConfigIndex_Good}}
|  25/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3498 Link]
|-
|  Battlefield 1
|  {{Template:ConfigIndex_Good}}
|  17/02/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2479 Link]
|-
|  Battlefield 1
|  {{Template:ConfigIndex_Good}}?
|  02/02/2017
|  PS4
|  {{No}}
|  DoM__
|  [https://forum.gimx.fr/viewtopic.php?p=11195#p11195 Link]
|  Not longer compatible after BF1 update
|-
|  Battlefield 1943
|  {{Template:ConfigIndex_Good}}
|  13/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3425 Link]
|-
|  Battlefield 2: Modern Combat
|  {{Template:ConfigIndex_Good}}
|  28/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3549 Link]
|-
|  Battlefield 2: Modern Combat
|  {{Template:ConfigIndex_Average}}
|  30/09/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1814 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_Good}}
|  31/05/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3413 Link]
|  Correct Dead Zone shape. Tank/Jet/Heli config added.
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  29/09/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=288 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  06/12/2011
|  PS3
|  {{No}}
|  sp3c14list
|  [https://gimx.fr/forum/viewtopic.php?p=2154 Link]
|-
|  Battlefield 3
|  {{Template:ConfigIndex_NoData}}
|  15/02/2012
|  PS3
|  {{No}}
|  rizzlan
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=424&p=2478 Link]
|-
|  Battlefield 4
|  {{Template:ConfigIndex_Good}}
|  10/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3423 Link]
|-
|  Battlefield 4
|  {{Template:ConfigIndex_NoData}}
|  No Data
|  PS4
|  {{Yes}}
|  foxy
|  N/A
|-
|  Battlefield 4
|  {{Template:ConfigIndex_Good}}
|  11/02/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2911 Link]
|-
|  Battlefield Hardline
|  {{Template:ConfigIndex_Good}}
|  05/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3623 Link]
|-
|  Battlefield Hardline
|  {{Template:ConfigIndex_NoData}}
|  03/04/2015
|  PS3
|  {{No}}
|  shatterstar78
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1185 Link]
|-
|  Battlefield V
|  {{Template:ConfigIndex_Good}}
|  20/11/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2806 Link]
|-
|  Battlefield: Bad Company
|  {{Template:ConfigIndex_Average}}
|  06/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3418 Link]
|  Games dead zone shape is big and most likely diagonal
|-
|  Battlefield: Bad Company 2
|  {{Template:ConfigIndex_Good}}
|  31/05/2020
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3414 Link]
|-
|  Battlefield: Bad Company 2
|  {{Template:ConfigIndex_Average}}
|  No Data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|  Game has low max turning speed.
|-
|  Bioshock
|  {{Template:ConfigIndex_Bad}}
|  08/06/2020
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3422 Link]
| Input filtering and random acceleration, also bad on controller.
|-
|  Bioshock
|  {{Template:ConfigIndex_Unplayable}}
|  28/02/2020
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Input filtering and random acceleration, also bad on controller.
|-
|  Bioshock Infinite
|  {{Template:ConfigIndex_Unplayable}}
|  06/06/2020
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Weird deadzone, acceleration spikes
|-
|  Black
|  {{Template:ConfigIndex_Average}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3520 Link]
|-
|  Black
|  {{Template:ConfigIndex_Average}}
|  08/09/2017
|  <abbr title="Original Xbox emulator in X360">Xbox 360E</abbr>
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2208 Link]
|-
|  Blacklight: Retribution
|  {{Template:ConfigIndex_Unplayable}}?
|  29/07/2014
|  PS4
|  {{Yes}}
|  Kekskrümel
|  [https://gimx.fr/forum/viewtopic.php?f=3&t=1038&p=6073 Link]
|-
|  Borderlands
|  {{Template:ConfigIndex_Good}}
|  28/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3656 Link]
|-
|  Borderlands 2
|  {{Template:ConfigIndex_Good}}
|  11/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3663 Link]
|-
|  Borderlands 3
|  {{Template:ConfigIndex_Good}}
|  13/09/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3182 Link]
|-
|  Borderlands: The Handsome Collection
|  {{Template:ConfigIndex_Good}}
|  10/06/2019
|  PS4
|  {{No}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3064 Link]
|-
|  Brothers in Arms: Earned in Blood
|  {{Template:ConfigIndex_Average}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3540&p=19484#p19484 Link]
|  Wierd dead zone shape
|-
|  Brothers in Arms: Road to Hill 30
|  {{Template:ConfigIndex_Average}}
|  20/09/2020
|  OG Xbox
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3540&p=19484#p19484 Link]
|  Wierd dead zone shape
|-
|  Bulletstorm
|  {{Template:ConfigIndex_Good}}
|  17/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3671 Link]
|-
|  Call of Duty 2: Big Red One
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3522&p=19449#p19449 Link]
|-
|  Call of Duty 3
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3524 Link]
|-
|  Call of Duty: Black Ops
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Call of Duty: Black Ops
|  {{Template:ConfigIndex_NoData}}
|  11/07/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=38 Link]
|-
|  Call of Duty: Black Ops 4
|  {{Template:ConfigIndex_Good}}
|  12/10/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2772 Link]
|-
|  Call of Duty: Modern Warfare
|  {{Template:ConfigIndex_Good}}
|  12/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3666 Link]
|-
|  Call of Duty: Modern Warfare 2
|  {{Template:ConfigIndex_Good}}
|  04/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3660 Link]
|-
|  Call of Duty: Modern Warfare 3
|  {{Template:ConfigIndex_Good}}
|  11/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3664 Link]
|-
|  Call of Duty: Modern Warfare Remastered
|  {{Template:ConfigIndex_Good}}
|  20/01/2019
|  PS4
|  {{Yes}}
|  4773n0x
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2881 Link]
|-
|  Crysis 2
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Crysis 3
|  {{Template:ConfigIndex_Good}}
|  25/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3651 Link]
|-
|  Dark Souls 3
|  {{Template:ConfigIndex_NoData}}
|  23/04/2016
|  PS4
|  {{Yes}}
|  cajuil
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=1625&p=9952 Link]
|-
|  Dead Space
|  {{Template:ConfigIndex_Average}}
|  25/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3445 Link]
|  Game lacks ingame sensitivity change
|-
|  Destiny
|  {{Template:ConfigIndex_Good}}?
|  23/07/2014
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://gimx.fr/forum/viewtopic.php?t=1227 Link]
|-
|  Deus Ex: Human Revolution
|  {{Template:ConfigIndex_Good}}
|  07/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3420 Link]
|  Slow turnspeed
|-
|  Dishonored
|  {{Template:ConfigIndex_Average}}
|  22/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3444 Link]
|  Ingame sensitivity has to be under 10 or pixel skipping will occur
|-
|  Dishonored 2
|  {{Template:ConfigIndex_Unplayable}}
|  21/04/2018
|  PS4
|  {{No}}
|  GoDlike
|  N/A
| Extreme input lag by game engine
|-
|  DOOM
|  {{Template:ConfigIndex_Good}}
|  24/10/2017
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2268 Link]
|-
|  Doom 3
|  {{Template:ConfigIndex_Good}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3530 Link]
|-
|  Doom 3
|  {{Template:ConfigIndex_Good}}
|  26/01/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3297&p=18337#p18337 Link]
|-
|  DOOM Eternal
|  {{Template:ConfigIndex_Average}}
|  16/04/2020
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3361 Link]
|-
|  Fallout 4
|  {{Template:ConfigIndex_Bad}}
|  22/12/2016
|  PS4
|  {{No}}
|  Johny
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1949 Link]
|  Config lacks an ADS profile. High DPI needed.
|-
|  Fallout 4
|  {{Template:ConfigIndex_Average}}
|  18/02/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2476 Link]
|  Game input is not good. High DPI needed.
|-
|  Far Cry 2
|  {{Template:ConfigIndex_Unplayable}}
|  18/01/2021
|  PS3
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3640 Link]
|  Game has bad variable acceleration.
|-
|  Far Cry 3
|  {{Template:ConfigIndex_Good}}
|  No data
|  PS3
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Far Cry 4
|  {{Template:ConfigIndex_Good}}
|  22/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3497 Link]
|-
|  Far Cry 5
|  {{Template:ConfigIndex_Average}}
|  02/04/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2537 Link]
|-
|  Far Cry Evolution
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3539&p=19483#p19483 Link]
|-
|  Far Cry Instincts
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{No}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3539&p=19483#p19483 Link]
|-
|  FEAR 3
|  {{Template:ConfigIndex_Good}}
|  21/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3647 Link]
|  Game has slower turn speed when aiming down sight.
|-
|  Gears of War 1
|  {{Template:ConfigIndex_Good}}
|  11/05/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1648 Link]
|-
|  Gears of War 2
|  {{Template:ConfigIndex_Average}}
|  16/05/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1661 Link]
|-
|  Gears of War 3
|  {{Template:ConfigIndex_Average}}
|  20/08/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1757 Link]
|-
|  Ghost Recon: Advanced Warfighter
|  {{Template:ConfigIndex_Good}}
|  13/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3523 Link]
|-
|  Ghost Recon: Future Soldier
|  {{Template:ConfigIndex_Good}}
|  12/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3519 Link]
|  No way to disable aim assist
|-
|  Ghost Recon: Wildlands
|  {{Template:ConfigIndex_Unplayable}}
|  20/09/2018
|  PS4
|  {{No}}
|  GoDlike
|  N/A
|  Bad input implementation
|-
|  GoldenEye 007:Reloaded
|  {{Template:ConfigIndex_Good}}?
|  18/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1772 Link]
|-
|  GoldenEye 007:Reloaded
|  {{Template:ConfigIndex_Good}}
|  28/03/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1772 Link]
|-
|  Grand Theft Auto V
|  {{Template:ConfigIndex_Good}}
|  26/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3500 Link]
|  More buffer needed on low DPI mouse to prevents the ingame acceleration to take over.
|-
|  Halo
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3526 Link]
|-
|  Halo 2
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3527 Link]
|-
|  Halo 3
|  {{Template:ConfigIndex_Good}}
|  07/07/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2661&p=14907#p14907 Link]
|-
|  Halo 4
|  {{Template:ConfigIndex_Good}}
|  02/08/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1734 Link]
|-
|  Halo 5: Guardians
|  {{Template:ConfigIndex_Good}}
|  30/01/2016
|  Xbox One
|  {{No}}
|  sephirotdnf
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1450 Link]
|  Config lacks an ADS profile.
|-
|  Halo: CEA
|  {{Template:ConfigIndex_Average}}
|  04/03/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2496 Link]
|-
|  Halo: Reach
|  {{Template:ConfigIndex_Average}}
|  19/07/2018
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2674 Link]
|-
|  HAZE
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2698 Link]
|-
|  Hitman: Absolution
|  {{Template:ConfigIndex_Good}}
|  25/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3446 Link]
|-
|  Homefront
|  {{Template:ConfigIndex_Good}}
|  01/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3659 Link]
|-
|  Horizon: Zero Dawn
|  {{Template:ConfigIndex_Average}}
|  28/01/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2455 Link]
|-
|  Infamous
|  {{Template:ConfigIndex_Average}}
|  14/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3429 Link]
|  Unpredictable acceleration and only 3 sensitivity options ingame
|-
|  Infamous: Second Son
|  {{Template:ConfigIndex_Bad}}
|  03/02/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2459 Link]
| Severe input bugs in game engine
|-
|  Killzone 1 HD
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2699 Link]
|-
|  Killzone 2
|  {{Template:ConfigIndex_Bad}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2700 Link]
|  Genuine DS3 with Gyroscope is required
|-
|  Killzone 3
|  {{Template:ConfigIndex_Average}}
|  05/08/2018
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2701 Link]
|-
|  Killzone 3
|  {{Template:ConfigIndex_Average}}
|  31/07/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=151 Link]
|-
|  Killzone: Shadow Fall
|  {{Template:ConfigIndex_Average}}
|  No Data
|  PS4
|  {{Yes}}
|  Matlo
|  N/A
|-
|  Mass Effect 2
|  {{Template:ConfigIndex_Good}}
|  25/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3499 Link]
|-
|  Max Payne
|  {{Template:ConfigIndex_Good}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3531&p=19464#p19464 Link]
|-
|  Max Payne 2
|  {{Template:ConfigIndex_Average}}
|  16/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3533 Link]
|  Macro needed for faster turn speed.
|-
|  Max Payne 3
|  {{Template:ConfigIndex_Good}}
|  12/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3518 Link]
|  Vertical aim is slow in the game, so horizontal needs to be reduced to 7 in-game
|-
|  Medal of Honor 2010
|  {{Template:ConfigIndex_Good}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3491 Link]
|-
|  Medal of Honor: European Assault
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3541 Link]
|-
|  Medal of Honor: Frontline
|  {{Template:ConfigIndex_Unplayable}}
|  10/10/2017
|  PS3
|  {{No}}
|  GoDlike
|  N/A
|-
|  Medal of Honor: Warfighter
|  {{Template:ConfigIndex_Good}}
|  22/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3468 Link]
|-
|  Metro: Exodus
|  {{Template:ConfigIndex_Average}}
|  03/05/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2917 Link]
|  Install 1.03 patch
|-
|  Mirrors Edge
|  {{Template:ConfigIndex_Good}}
|  12/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3424 Link]
|-
|  Nioh: Complete Edition
|  {{Template:ConfigIndex_Good}}
|  13/02/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2473 Link]
|-
|  Overwatch
|  {{Template:ConfigIndex_Good}}
|  06/07/2018
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1685 Link]
|-
|  Paladins
|  {{Template:ConfigIndex_Average}}
|  24/10/2017
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2269 Link]
|-
|  Payday: The Heist
|  {{Template:ConfigIndex_NoData}}
|  18/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=390&p=2280 Link]
|-
|  Perfect Dark
|  {{Template:ConfigIndex_Bad}}
|  24/9/2016
|  Xbox 360
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1796 Link]
|-
|  PUBG
|  {{Template:ConfigIndex_Good}}
|  22/8/2018
|  Xbox One
|  {{Yes}}
|  lekken
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2717 Link]
|-
|  PUBG
|  {{Template:ConfigIndex_Good}}
|  07/12/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2820 Link]
|-
|  RAGE 2
|  {{Template:ConfigIndex_Good}}
|  16/05/2019
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&p=17105#p17105 Link]
|-
|  Rainbow Six: Siege
|  {{Template:ConfigIndex_Good}}
|  10/11/2016
|  PS4
|  {{Yes}}
|  DiJu519
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1879 Link]
|-
|  Rainbow Six: Siege
|  {{Template:ConfigIndex_Good}}?
|  27/02/2019
|  Xbox One
|  {{No}}
|  Fluffywafflz
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2939 Link]
|-
|  Red Dead Redemption/ Undead Nightmare
|  {{Template:ConfigIndex_Average}}
|  25/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=3650 Link]
|  No way to disable aim assist
|-
|  Red Dead Redemption
|  {{Template:ConfigIndex_NoData}}
|  25/02/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=474&p=2830 Link]
|-
|  Red Dead Redemption 2
|  {{Template:ConfigIndex_Bad}}
|  28/10/2018
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2792 Link]
|  Input filtering, bad controls
|-
|  Resistance 1
|  {{Template:ConfigIndex_Good}}
|  03/12/2016
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1916 Link]
|-
|  Resistance 2
|  {{Template:ConfigIndex_Average}}
|  11/12/2016
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1933 Link]
|-
|  Resistance 3
|  {{Template:ConfigIndex_Good}}
|  13/12/2011
|  PS3
|  {{Yes}}
|  McKack
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=383 Link]
|-
|  Return to Castle Wolfenstein
|  {{Template:ConfigIndex_Good}}
|  15/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3528 Link]
|-
|  Sniper Elite
|  {{Template:ConfigIndex_Good}}
|  20/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3538 Link]
|-
|  Sniper Elite 3
|  {{Template:ConfigIndex_Good}}
|  07/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3626 Link]
|-
|  Sniper Elite 4
|  {{Template:ConfigIndex_Good}}
|  17/10/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3201 Link]
|-
|  Sniper Elite V2
|  {{Template:ConfigIndex_Good}}
|  14/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3636 Link]
|-
|  Sniper: Ghost Warrior
|  {{Template:ConfigIndex_Good}}
|  29/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3657 Link]
|  Very slow ads aiming while scoped.
|-
|  Sniper: Ghost Warrior 2
|  {{Template:ConfigIndex_Average}}
|  05/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3624 Link]
|  This game has bad micromovements with high ingame sensitivity.
|-
|  Splinter Cell: Blacklist
|  {{Template:ConfigIndex_Good}}
|  17/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3494 Link]
|-
|  Splinter Cell: Chaos Theory
|  {{Template:ConfigIndex_Good}}
|  17/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3534 Link]
|-
|  Star Wars: Republic Commando
|  {{Template:ConfigIndex_Good}}
|  08/03/2019
|  Xbox One
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3145 Link]
|-
|  StarHawk
|  {{Template:ConfigIndex_Good}}
|  25/11/2017
|  PS3
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2350&p=13125#p13125 Link]
|-
|  Syndicate
|  {{Template:ConfigIndex_Good}}
|  23/07/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3472 Link]
|-
|  The Chronicles of Riddick
|  {{Template:ConfigIndex_Average}}
|  19/09/2020
|  OG Xbox
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3536 Link]
|  Acceleration spikes when turning
|-
|  The Darkness
|  {{Template:ConfigIndex_Unplayable}}
|  09/09/2016
|  Xbox 360
|  {{No}}
|  GoDlike
|  N/A
|-
|  The Last of Us
|  {{Template:ConfigIndex_Average}}
|  01/02/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3658 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  The Last of Us
|  {{Template:ConfigIndex_NoData}}
|  19/03/2014
|  PS3
|  {{Yes}}
|  pawel
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=952&p=7898 Link]
|  Only Profile 1 is configured.
|-
|  Titanfall 2
|  {{Template:ConfigIndex_Good}}
|  28/08/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2686#p15014 Link]
|-
|  Tom Clancy's: The Division
|  {{Template:ConfigIndex_Good}}?
|  25/02/2016
|  PS4
|  {{Yes}}
|  Cybereu
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=1507 Link]
|-
|  Tom Clancy's: The Division
|  {{Template:ConfigIndex_Good}}?
|  23/10/2018
|  PS4
|  {{Yes}}
|  kaiba_seto2004
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2785 Link]
|-
|  Tom Clancy's: The Division 2
|  {{Template:ConfigIndex_Average}}
|  15/03/2019
|  PS4
|  {{No}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2968 Link]
|-
|  Tomb Raider 2013
|  {{Template:ConfigIndex_Average}}
|  24/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3443 Link]
|  Input filtering
|-
|  Uncharted 1: Drake's Fortune
|  {{Template:ConfigIndex_Average}}
|  10/09/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3513 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Uncharted 1: Drake's Fortune
|  {{Template:ConfigIndex_NoData}}
|  19/03/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=506 Link]
|-
|  Uncharted 2: Among Thieves
|  {{Template:ConfigIndex_Average}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3493 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Uncharted 2: Among Thieves
|  {{Template:ConfigIndex_NoData}}
|  25/03/2012
|  PS3
|  {{Yes}}
|  yeicob
|  [https://gimx.fr/forum/viewtopic.php?f=9&t=520 Link]
|-
|  Uncharted 3: Drake's Deception
|  {{Template:ConfigIndex_Average}}
|  16/08/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3492 Link]
|  Game has slow turnspeed and unpredictable acceleration
|-
|  Warhammer 40K: Space Marine
|  {{Template:ConfigIndex_Good}}
|  07/06/2020
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3421 Link]
|-
|  Watch Dogs
|  {{Template:ConfigIndex_NoData}}
|  No Data
|  PS4
|  {{Yes}}
|  foxy
|  N/A
|-
|  Wolfenstein: The New Order
|  {{Template:ConfigIndex_Good}}
|  26/01/2021
|  PS3
|  {{Yes}}
|  ckaiycool
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=3652 Link]
|  Aiming system is "wonky"
|-
|  Wolfenstein 2: The New Colossus
|  {{Template:ConfigIndex_Good}}
|  08/12/2017
|  PS4
|  {{Yes}}
|  GoDlike
|  [https://forum.gimx.fr/viewtopic.php?f=9&t=2375 Link]
|  Slightly annoying input lag
|}

Development on Windows

2021-01-07T11:52:36Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run "MSYS2 MSYS" from Start menu, and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run "MSYS MinGW 64-bit" from Start menu, and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run Run "MSYS2 MinGW 32-bit" from Start menu instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run "MSYS2 MinGW 64-bit" from Start menu, and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run Run "MSYS2 MinGW 32-bit" from Start menu instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command" (replace 4 with your number of CPU cores)
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Development on Windows

2021-01-07T11:52:23Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run "MSYS2 MSYS" from Start menu, and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run "MSYS MinGW 64-bit" from Start menu, and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run "MSYS2 MinGW 64-bit" from Start menu, and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run Run "MSYS2 MinGW 32-bit" from Start menu instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command" (replace 4 with your number of CPU cores)
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Development on Windows

2021-01-07T11:50:27Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run "MSYS2 MSYS" from Start menu, and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run "MSYS MinGW 64-bit" from Start menu, and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command" (replace 4 with your number of CPU cores)
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Development on Windows

2021-01-07T11:49:52Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run "MSYS2 MSYS" from Start menu, and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command" (replace 4 with your number of CPU cores)
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Template:Firmwares

2020-11-27T08:30:10Z

Matlo:

<translate>

:* EMUJOYSTICK: HID joystick emulation, with 16bit stick axes, for PS3 and PC
:* EMUPS3: Sixaxis emulation, for PS3
:* EMU360: 360 pad emulation, for Xbox 360 and PC
:* EMUPS4: Hori Pad FPS Plus emulation, for PS4 and PC
:* EMUXONE: Xbox One pad emulation, for Xbox One
:* EMUG29PS4: Logitech G29 gaming wheel emulation, for PS4
:* EMUG27: Logitech G27 gaming wheel emulation, for PS3 and PC
:* EMUGTF: Logitech GT Force emulation, for PS2 and PC
:* EMUDF: Logitech Driving Force emulation, for PS2 and PC
:* EMUDFP: Logitech Driving Force Pro emulation, for PS2 and PC
</translate>

Development on Linux

2020-11-25T21:25:16Z

Matlo:

<languages />
<translate>
This wiki explains how to compile GIMX from a Linux terminal.

==Install development packages== 


On Ubuntu 20.04: 
<code>
sudo apt-get install build-essential pkg-config git g++ libwxgtk3.0-gtk3-dev libbluetooth-dev libxml2-dev libusb-1.0-0-dev libncursesw5-dev gettext xterm xdg-utils libmhash-dev libcurl4-gnutls-dev libxi-dev libx11-dev</code>


On Ubuntu 18.04 / Raspbian Stretch: 
<code>
sudo apt-get install build-essential pkg-config git g++ libwxgtk3.0-dev libbluetooth-dev libxml2-dev libusb-1.0-0-dev libncursesw5-dev gettext xterm xdg-utils libmhash-dev libcurl4-gnutls-dev libxi-dev libx11-dev</code>


On Ubuntu 14.04: 
<code>
sudo apt-get install git g++ libwxgtk2.8-dev libbluetooth-dev libxml2-dev libusb-1.0-0-dev libncursesw5-dev gettext xterm xdg-utils libmhash-dev libcurl4-gnutls-dev libxi-dev libx11-dev</code>


On Raspbian Jessie: 
<code>
sudo apt-get install build-essential pkg-config git g++ libwxgtk2.8-dev libbluetooth-dev libxml2-dev libusb-1.0-0-dev libncursesw5-dev gettext xterm xdg-utils libmhash-dev libcurl4-gnutls-dev libxi-dev libx11-dev</code>


On Fedora: 
<code>
yum -y install wxGTK-devel bluez-libs-devel glib2-devel libxml2-devel libXi-devel libusb-devel (to be completed)</code>

==Download GIMX sources== 


<code>
git clone -b master --single-branch --depth 1 --recursive -j8 <nowiki>https://github.com/matlo/GIMX.git</nowiki></code>

==Compile== 


<code>
cd GIMX 
make -j 2</code>


Replace "2" with your number of CPU cores.

==Install== 


<code>
sudo make install</code>

==Set the setuid== 


A few gimx binaries need root priviledges.


<code>
sudo chmod u+s /usr/bin/gimx /usr/bin/sixaddr /usr/bin/bdaddr /usr/bin/hcirevision</code>

==Set Input Device Permissions== 


One way to give read permissions to GIMX is to create a special group, change /dev/input/event* group ownership to that group, and then make the gimx binaries setgid to that group.


<code>
sudo su 


groupadd -f input 


echo "KERNEL==\"event*\", NAME=\"input/%k\", MODE:=\"660\", GROUP=\"input\"" > /etc/udev/rules.d/99-gimx-input.rules 
echo "KERNEL==\"js*\", NAME=\"input/%k\", MODE:=\"664\", GROUP=\"input\"" >> /etc/udev/rules.d/99-gimx-input.rules 
chgrp -f input /dev/input/event* /dev/input/js* 
chmod -f g+rw /dev/input/event* /dev/input/js* 


chgrp input /usr/bin/gimx-config /usr/bin/gimx-fpsconfig /usr/bin/gimx-launcher 
chmod g+s /usr/bin/gimx-config /usr/bin/gimx-fpsconfig /usr/bin/gimx-launcher 


exit</code>
</translate>

Template:FirmwaresNext/USB

2020-05-06T09:35:04Z

Matlo:

This part explains how to load the right firmware into the adapter.

{{#ifeq:{{{platform|}}}|ps4|{{#ifeq:{{{device|}}}|SteeringWheel|'''If you have a brand new official GIMX adapter you can skip this part (it has the right firmware preloaded).'''|}}|}}

===Preparation for flash===

Connect both ends of the adapter to the computer, as shown in the picture below.

[[File:Schemeflash.png]]

===Flashing firmware for official GIMX adapter===
# Run gimx-launcher.
# Click on "Help > Update firmware".
# Select '''{{#switch:{{{platform|}}}
| ps4 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG29PS4
| Mouse = EMUPS4
| Pad = EMUPS4
}}
| xboxone = {{#switch:{{{device|}}}
| Mouse = EMUXONE
| Pad = EMUXONE
}}
| ps3 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27
| Mouse = EMUPS3
| Pad = EMUPS3
}}
| xbox360 = {{#switch:{{{device|}}}
| Mouse = EMU360
| Pad = EMU360
}}
| ps2 = {{#switch:{{{device|}}}
| SteeringWheel = EMUGTF, EMUDF, or EMUDFP
}}
| pc = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27, EMUDFP, EMUDF, or EMUGTF
| Pad = EMUXBOX, EMU360, EMUXONE, EMUPS3, EMUPS4, or EMUJOYSTICK
}}
| originalxbox = {{#switch:{{{device|}}}
| Mouse = EMUXBOX
| Pad = EMUXBOX
}}
| #default = default
}}''', click on "Load", and follow the instructions. Upon success a "Firmware loaded successfully!" message should be displayed.

===Flashing firmware for other adapters===

<div class="mw-collapsible mw-collapsed">

'''Firmwares'''

[http://gimx.fr/download/gimx-firmwares Download link] 

{{FirmwareLoading}}

</div>

Template:FirmwaresNext/USB

2020-05-06T09:34:25Z

Matlo: /* Flashing firmware for official GIMX adapter */

This part explains how to load the right firmware into the adapter.

{{#ifeq:{{{platform|}}}|ps4|{{#ifeq:{{{device|}}}|SteeringWheel|'''If you have a brand new official GIMX adapter you can skip this part (it has the right firmware preloaded).'''|}}|}}

===Preparation for flash===

Connect both ends of the adapter to the computer, as shown in the picture below.

[[File:Schemeflash.png]]

===Flashing firmware for official GIMX adapter===
# Run gimx-launcher.
# Click on "Help > Update firmware".
# Select '''{{#switch:{{{platform|}}}
| ps4 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG29PS4
| Mouse = EMUPS4
| Pad = EMUPS4
}}
| xboxone = {{#switch:{{{device|}}}
| Mouse = EMUXONE
| Pad = EMUXONE
}}
| ps3 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27
| Mouse = EMUPS3
| Pad = EMUPS3
}}
| xbox360 = {{#switch:{{{device|}}}
| Mouse = EMU360
| Pad = EMU360
}}
| ps2 = {{#switch:{{{device|}}}
| SteeringWheel = EMUGTF, EMUDF, or EMUDFP
}}
| pc = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27, EMUDFP, EMUDF, or EMUGTF
| Pad = EMUXBOX, EMU360, EMUXONE, EMUPS3, EMUPS4, EMUJOYSTICK
}}
| originalxbox = {{#switch:{{{device|}}}
| Mouse = EMUXBOX
| Pad = EMUXBOX
}}
| #default = default
}}''', click on "Load", and follow the instructions. Upon success a "Firmware loaded successfully!" message should be displayed.

===Flashing firmware for other adapters===

<div class="mw-collapsible mw-collapsed">

'''Firmwares'''

[http://gimx.fr/download/gimx-firmwares Download link] 

{{FirmwareLoading}}

</div>

Template:Capabilities

2020-05-06T09:31:17Z

Matlo:

==Capabilities and limitations==

{{#switch:{{{platform|}}}
| ps4 = {{#switch:{{{device|}}}
| SteeringWheel = GIMX allows to emulate a G29 for PS4. All controls are working: wheel and pedals axes, wheel buttons, shifter buttons. Combining multiple devices (wheel, pedals, shifter, ...) is possible. {{#switch:{{{ostype|}}}
| windows = Force feedback is supported for all Windows-compatible force feedback wheels.
| linux = Force feedback only works for Logitech wheels older than the G29/G920, and for the G29/G920 starting from Linux kernel 4.6.
}} Auto-adjustment of the wheel range is only supported for Logitech wheels older than the G29/G920, and rpm led control is only supported for the G27.
| Mouse = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a HORI Pad FPS Plus. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working including touchpad. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Motion sensing controls are not supported due to limitations of the emulated device. Audio is not supported as well (but it is possible to use another Dualshock 4).
| linux = {{#switch:{{{connectionType|}}}
| USB = GIMX allows to emulate a HORI Pad FPS Plus. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working including touchpad. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Motion sensing controls are not supported due to limitations of the emulated device. Audio is not supported as well (but it is possible to use another Dualshock 4).
| BT = GIMX allows to emulate a Dualshock 4. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls (except motion sensing) are working including touchpad. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported (but it is possible to use another Dualshock 4).
}}
}}
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a HORI Pad FPS Plus. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working including touchpad. Motion sensing controls are not supported. Audio is not supported as well (but it is possible to use another Dualshock 4).
| linux = {{#switch:{{{connectionType|}}}
| USB = GIMX allows to emulate a HORI Pad FPS Plus. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working including touchpad. Motion sensing controls are not supported. Audio is not supported as well (but it is possible to use another Dualshock 4).controller.
| BT = GIMX allows to emulate a Dualshock 4. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working including touchpad. Motion sensing controls are not supported. Audio is not supported as well (but it is possible to use another Dualshock 4).
}}
}}
}}
| xboxone = {{#switch:{{{device|}}}
| Mouse = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate an Xbox One controller. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
| linux = GIMX allows to emulate an Xbox One controller. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
}}
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate an Xbox One controller. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
| linux = GIMX allows to emulate an Xbox One controller. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
}}
}}
| ps3 = {{#switch:{{{device|}}}
| SteeringWheel = GIMX allows to emulate a G27 for PS3. All controls are working: wheel and pedals axes, wheel buttons, shifter buttons. Combining multiple devices (wheel, pedals, shifter, ...) is possible. {{#switch:{{{ostype|}}}
| windows = Force feedback is supported for all Windows-compatible force feedback wheels.
| linux = Force feedback only works for Logitech wheels older than the G29/G920, and for the G29/G920 starting from Linux kernel 4.6.
}} Auto-adjustment of the wheel range is only supported for Logitech wheels older than the G29/G920, and rpm led control is only supported for the G27. A current limitation is that the controls do not work correctly in the XMB (PS3 menus). To work-around this issue, start the game with a Dualshock 3, and then [https://support.us.playstation.com/articles/en_US/KC_Article/PS3-Pair-and-Assign-Controllers reassign controllers].

| Mouse = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a Dualshock 3. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles.
| linux = {{#switch:{{{connectionType|}}}
| USB = GIMX allows to emulate a Dualshock 3. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles.
| BT = GIMX allows to emulate a Dualshock 3. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles.
}}
}}
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a Dualshock 3. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing.
| linux = {{#switch:{{{connectionType|}}}
| USB = GIMX allows to emulate a Dualshock 3. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing.
| BT = GIMX allows to emulate a Dualshock 3. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working, except motion sensing.
}}
}}
}}
| xbox360 = {{#switch:{{{device|}}}
| Mouse = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate an Xbox 360 controller. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
| linux = GIMX allows to emulate an Xbox 360 controller. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
}}
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate an Xbox One controller. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
| linux = GIMX allows to emulate an Xbox One controller. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
}}
}}
| ps2 = {{#switch:{{{device|}}}
| SteeringWheel = GIMX allows to emulate either a GT Force, a Driving Force, or a Driving Force Pro, for PS2. It is recommended to use the most recent wheel emulation supported by the game (GT Force < Driving Force < Driving Force Pro). All controls are working: wheel and pedals axes, wheel buttons, shifter buttons. Combining multiple devices (wheel, pedals, shifter, ...) is possible. {{#switch:{{{ostype|}}}
| windows = Force feedback is supported for all Windows-compatible force feedback wheels.
| linux = Force feedback only works for Logitech wheels older than the G29/G920, and for the G29/G920 starting from Linux kernel 4.6.
}}
}}
| pc = {{#switch:{{{device|}}}
| SteeringWheel = GIMX allows to emulate any of the following Logitech wheels: G27, Driving Force Pro, Driving Force, GT Force. It is possible to run GIMX on the target PC. All controls are working: wheel and pedals axes, wheel buttons, shifter buttons. Combining multiple devices (wheel, pedals, shifter, ...) is possible. {{#switch:{{{ostype|}}}
| windows = Force feedback is supported for all Windows-compatible force feedback wheels.
| linux = Force feedback only works for Logitech wheels older than the G29/G920, and for the G29/G920 starting from Linux kernel 4.6.
}} Auto-adjustment of the wheel range is only supported for Logitech wheels older than the G29/G920, and rpm led control is only supported for the G27.
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate the following controllers: Xbox 360 controller, Dualshock 4. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
| linux = GIMX allows to emulate the following controllers: original Xbox controller, Xbox 360 controller, Xbox One controller, Dualshock 3, Dualshock 4, HID joystick. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported. Rumble is not supported for the HID joystick emulation.
}}
}}
| originalxbox = {{#switch:{{{device|}}}
| Mouse = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a controller for the original Xbox. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
| linux = GIMX allows to emulate a controller for the original Xbox. Any mouse, keyboard or game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Adjusting ADS (aiming down the sight) sensitivity is possible using a second profile triggered by the mouse right click. It is also possible to use additional profiles for controlling vehicles. Audio is not supported.
}}
| Pad = {{#switch:{{{ostype|}}}
| windows = GIMX allows to emulate a controller for the original Xbox. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
| linux = GIMX allows to emulate a controller for the original Xbox. Any game controller (gamepad, joystick, fightstick...) can be used. All controls are working. Audio is not supported.
}}
}}
| #default = default
}}

{{#switch:{{{device|}}}
|Pad = Rumble should work with any controller that has rumble support at driver level. Rumble commands are either directed to the controller defined in the FFB tweaks, or to the first controller found in the configuration that has a binding to the left stick x axis.
|}}

{{#switch:{{{device|}}}
|Mouse = {{#switch:{{{platform|}}}
|ps3 = [[File:schememouse.png]]
|ps4
|xboxone
|xbox360 = [[File:schememouseauth.png]]
|}}
|SteeringWheel = {{#switch:{{{platform|}}}
|ps2
|ps3 = [[File:schemewheel.png]]
|ps4 = [[File:schemewheelauth.png]]
|pc = '''In the diagram below, the computer is represented by the console. It is possible to have the game and GIMX run on the same computer. In this case both ends of the adapter are plugged to the same computer.''' [[File:schemewheel.png]]
|}}
|Pad = {{#switch:{{{platform|}}}
|ps3 = [[File:schemegamepad.png]]
|ps4
|xboxone
|xbox360 = [[File:schemegamepadauth.png]]
|}}
|}}

Template:FirmwaresNext/USB

2020-05-06T09:17:30Z

Matlo:

This part explains how to load the right firmware into the adapter.

{{#ifeq:{{{platform|}}}|ps4|{{#ifeq:{{{device|}}}|SteeringWheel|'''If you have a brand new official GIMX adapter you can skip this part (it has the right firmware preloaded).'''|}}|}}

===Preparation for flash===

Connect both ends of the adapter to the computer, as shown in the picture below.

[[File:Schemeflash.png]]

===Flashing firmware for official GIMX adapter===
# Run gimx-launcher.
# Click on "Help > Update firmware".
# Select '''{{#switch:{{{platform|}}}
| ps4 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG29PS4
| Mouse = EMUPS4
| Pad = EMUPS4
}}
| xboxone = {{#switch:{{{device|}}}
| Mouse = EMUXONE
| Pad = EMUXONE
}}
| ps3 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27
| Mouse = EMUPS3
| Pad = EMUPS3
}}
| xbox360 = {{#switch:{{{device|}}}
| Mouse = EMU360
| Pad = EMU360
}}
| ps2 = {{#switch:{{{device|}}}
| SteeringWheel = EMUGTF, EMUDF, or EMUDFP
}}
| pc = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27, EMUDFP, EMUDF, or EMUGTF
}}
| originalxbox = {{#switch:{{{device|}}}
| Mouse = EMUXBOX
| Pad = EMUXBOX
}}
| #default = default
}}''', click on "Load", and follow the instructions. Upon success a "Firmware loaded successfully!" message should be displayed.

===Flashing firmware for other adapters===

<div class="mw-collapsible mw-collapsed">

'''Firmwares'''

[http://gimx.fr/download/gimx-firmwares Download link] 

{{FirmwareLoading}}

</div>

Template:FirmwaresNext/USB

2020-05-06T09:16:41Z

Matlo:

This part explains how to load the right firmware into the adapter.

{{#ifeq:{{{platform|}}}|ps4|{{#ifeq:{{{device|}}}|SteeringWheel|'''If you have a brand new official GIMX adapter you can skip this part (it has the right firmware preloaded).'''|}}|}}

===Preparation for flash===

Connect both ends of the adapter to the computer, as shown in the picture below.

[[File:Schemeflash.png]]

===Flashing firmware for official GIMX adapter===
# Run gimx-launcher.
# Click on "Help > Update firmware".
# Select '''{{#switch:{{{platform|}}}
| ps4 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG29PS4
| Mouse = EMUPS4
| Pad = EMUPS4
}}
| xboxone = {{#switch:{{{device|}}}
| Mouse = EMUXONE
| Pad = EMUXONE
}}
| ps3 = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27
| Mouse = EMUPS3
| Pad = EMUPS3
}}
| xbox360 = {{#switch:{{{device|}}}
| Mouse = EMU360
| Pad = EMU360
}}
| ps2 = {{#switch:{{{device|}}}
| SteeringWheel = EMUGTF, EMUDF, EMUDFP
}}
| pc = {{#switch:{{{device|}}}
| SteeringWheel = EMUG27, EMUDFP, EMUDF, EMUGTF
}}
| originalxbox = {{#switch:{{{device|}}}
| Mouse = EMUXBOX
| Pad = EMUXBOX
}}
| #default = default
}}''', click on "Load", and follow the instructions. Upon success a "Firmware loaded successfully!" message should be displayed.

===Flashing firmware for other adapters===

<div class="mw-collapsible mw-collapsed">

'''Firmwares'''

[http://gimx.fr/download/gimx-firmwares Download link] 

{{FirmwareLoading}}

</div>

Axis translation parameters

2020-01-26T13:53:26Z

Matlo:

TODO: Give simple use cases such as: how to bind a joystick axis to an axis

<languages />
<translate>


This page explains the purpose of each axis translation parameter.

=Dead zone= 


[[File:DZShapeCircle.gif|left|frame|Visual Demonstration]] '''The dead zone parameter allows to shift the stick positions away from the stick center. Higher the DZ (Dead zone) is, larger mouse moves need to be done in order to aim.'''

This allows to skip all the stick positions around the stick center that do not generate in-game movement (these positions are called the dead zone of the stick).

If lowest input motion do not generate enough movement, increase the dead zone parameter.

When you calibrate the dead zone you want the aim to move as slowly and smoothly as possible (no jitters or random jumps)
The aim should start moving by itself when you increase the dead zone using the mouse wheel, so all you need to do is fine tune it until the speed of the aim is slow and fluid.

Remember to go out of dead zone calibration to test the results of your adjustments. If the aim lags in calibration mode you'll need to save your configuration and run the emulator in normal Grab mode to test any changes you've made.

'''''Tip''''': ''To get rid of potential jerky aim when aiming slowly you need to increase DZ slightly above the game setting. So if you find through dead zone calibration that the aim starts moving by itself at '''22''', increase it to '''25'''-'''30''' instead.''
 

=Dead zone shape= 


The dead zone shape can be set to:

<div style="margin-top: 10px; "><ul style="margin-left:0px;">
<li style="display: inline-block;"> [[File:DZShapeCircle.gif|frame|none|Circle]] </li>
<li style="margin-left: 10px;display: inline-block;"> [[File:DZShapeRectangle.gif|frame|none|Rectangle]] </li>
</ul></div>


More shapes will be added in a future version.

=Sensitivity= 


[[File:mpanim.gif|left|frame|Visual Demonstration]]'''The sensitivity parameter is nothing more than a multiplier: input motion is multiplied so as to scale to the output motion range.'''

Increase it if the movement is too slow and decrease it if the movement is too fast.

It can be a negative value, so as to reverse the motion direction.

Remember that the output motion range is limited (the stick has a max position).


To map a joystick axis to a stick axis, use a value of 128/32768 (about 0.004).

To map a joystick axis to a button axis, use a value of 256/32768 (about 0.008).

=X/Y ratio= 


'''The x/y ratio allows to change the vertical sensitivity independently from the horizontal sensitivity''' i.e. it determines how much faster your vertical (Y axis) aim is in relation to your horizontal (X axis) aim.

A value of 3.0 would make you aim up and down incredibly fast, whereas 0.1 would make it almost impossible to move it up or down at all.

Some games require higher or lower value. It all depends on developers implementation of controls in the game engine.

Vertical sensitivity formula is as follows:
vertical_sens = sens * xy_ratio

=Acceleration= 


[[File:expanim.gif|left|frame|Visual Demonstration]] '''The acceleration parameter allows to change the in-game acceleration.'''

Values higher than '''1''' increase the effective acceleration, whereas values lower that '''1''' decrease it.

FPS games generally have a positive acceleration, which means there is a value in the '''0..1''' range that will cancel it (at least for games that use simple look mechanics).

Acceleration value required for good aiming experience may vary from game to game as it depends on developers implementation of controls in the game engine.

After having played around with these settings and you've learned what does what and how they work together, you can start fine tuning configurations to fit your personal preference or make your very own ones that we hope you'd like to share with us on the [https://forum.gimx.fr/viewforum.php?f=9 forums!].

'''''Tip''''': ''In the Call of Duty series (since Call of Duty 4) for example, a value of 0.39 will give you a 1:1-like aim (meaning there is little to no acceleration when moving the mouse) Having a higher exponent will make the aim accelerate but you won't need a high multiplier (the higher the multiplier is the bigger the gaps are between each "step" in the speed curve)
''

=Buffer size and filter= 


These parameters are specific to the mouse smoothing, which is detailed on the [[Mouse_Calibration|Mouse calibration]] page.

</translate>

Macros

2020-01-24T19:03:48Z

Matlo:

<languages />
<translate>
It's possible to configure keyboard/mouse/joystick macros: a key or button press can trigger a series of keyboard/mouse/joystick events, with timing conditions.

==File format==

File format is plain text UTF-8. Recommended text editors are [https://notepad-plus-plus.org/ Notepad++] on Windows and gedit on Ubuntu.

==Directory== 


To open the directory where to put macro files, open gimx-launcher and click on "File > Open Macro Directory".

==Syntax== 


<pre>MACRO <DEVICE EVENT> <ID> <RANGE>
<DEVICE EVENT> <ID> <VALUE>
DELAY <MS>
#<COMMENT></pre>


*<DEVICE EVENT>: KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP, MAXIS, JAXIS
*<ID>: the event id (case sensitive) as displayed in gimx-config
*<VALUE>: the axis value (only for MAXIS and JAXIS)
*<RANGE>: the axis range (only for MAXIS and JAXIS); the syntax is [min,max] with min and max in [-32768,32767]; example: [8192,16384]
*<MS>: integer value in milliseconds
*<COMMENT>: a comment, not interpreted ('#' is the first character of the line)

==Commands== 


* KEYDOWN: keyboard key pressed
* KEYUP: keyboard key released
* KEY: KEYDOWN + DELAY 50 + KEYUP


* MBUTTONDOWN: mouse button pressed
* MBUTTONUP: mouse button released
* MBUTTON: MBUTTONDOWN + DELAY 50 + MBUTTONUP


* JBUTTONDOWN: joystick button pressed
* JBUTTONUP: joystick button released
* JBUTTON: JBUTTONDOWN + DELAY 50 + JBUTTONUP


* DELAY: delay in milliseconds


* MAXIS: mouse axis moved; ID: 0 for x axis, and 1 for y axis; VALUE: positive values for right and down


* JAXIS: joystick axis moved; ID: the axis id as displayed in gimx-config; VALUE: in [-32768 .. 32767] for centered axes, and in [0 .. 32767] for non-centered axes

==Macro activation== 


* '''It is possible to specify the macro files to be read for each configuration file.'''
This can be configured in a file named "configs.txt", located in the macros directory. 
Example:
<pre>#If config1.xml is loaded, macro1.txt is read.
config1.xml/macro1.txt
#If config1.xml is loaded, macro2.txt is read.
config1.xml/macro2.txt
#If config2.xml is loaded, macro2.txt is read.
config2.xml/macro2.txt</pre>
Lines beginning with a # are not interpreted. 
Since GIMX 4.0 the separator is a slash so as to allow using file names containing spaces. 


* '''It is also possible to define activation triggers within the macro definition.'''
The syntax is:
<pre>TRIGGER <event></pre>
Example:
<pre>MACRO F1
#content


MACRO F2
TRIGGER F5
#content


MACRO F3
TRIGGER F6
#content


MACRO F4
TRIGGER F5
#content</pre>
The above example works the following way: F1 is default active, F2, F3, F4 are default inactive. When F5 is pressed, F2 and F4 become active, and F3 becomes inactive. When F6 is pressed, F3 becomes active, and F2 and F4 become inactive. 
Macros with a trigger are default inactive. To make a macro with trigger default active, add a line containing "INIT ON" after the "TRIGGER <event>" line. 
Macros with a trigger can work with a toggle mode, which allows to activate and deactivate a macro autonomously: activating a togglable macro has no impact on other macros, and activating another macro has no impact on a togglable macro. This can be configured adding a line containing "TOGGLE YES" after the "TRIGGER <event>" line. 
Example:
<pre>MACRO F1
TRIGGER 1
INIT ON
TOGGLE YES
#content</pre>

==Notes== 

===Delay precision=== 


The delay precision depends on the controller update period:
* ds3/bluetooth = 11.25ms
* ds3/usb = 10ms
* ds4/bluetooth = 10ms
* ds4/usb = 10ms
* 360 pad = 8ms
* XOne pad = 4ms
If you specify a delay that is not a multiple of the precision, the resulting delay will be the lowest multiple of the precision higher than the specified delay. 
For example, if the precision is 11.25ms and the delay is 12ms, the resulting delay will be 22.50ms (=2*11.25ms).

===Macro loop=== 


To make a macro loop, just add a matching KEYDOWN, MBUTTONDOWN or JBUTTONDOWN command at the end of the macro. 
Example:
<pre>MACRO MBUTTONDOWN BUTTON_LEFT
#content
MBUTTONDOWN BUTTON_LEFT</pre>


The macro is triggered by pressing 'BUTTON_LEFT'. 
The last command of the macro restarts the macro, creating a loop. 
To stop a macro loop, just press the trigger again. The macro is stopped immediately, and the state of the controller is unchanged.

===Multiple keyboards/mice/joysticks=== 


In case multiple keyboards or mice or joysticks are used, it's not possible to specify the device for which events are generated. 
Events are generated for the first keyboard/mouse/joystick found in the configuration.

==Examples== 

===Rapid fire macro=== 


<pre>MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN p
#Set delay no less than the maximum rate of fire
#10 rounds per second (600 rpm)
DELAY 100
KEYUP p
#~Do not set delay after keyup or it will negatively impact automatic weapons
MBUTTONDOWN BUTTON_LEFT

MACRO MBUTTONUP BUTTON_LEFT
MBUTTONDOWN BUTTON_LEFT
#Sometimes the fire key can be stuck down after the macro ends this releases it after the macro has been terminated
KEYUP p</pre>


In gimx-config, bind 'p' to r1 in both hip fire and ADS profiles (profiles 1 and 2). 
DO NOT bind 'BUTTON_LEFT' to r1 in both hip fire and ADS profiles.


The macro is triggered by pressing the left mouse button. 
The last command of the first macro restarts the macro, creating a loop. 
Upon the release of the left mouse button the second macro ends the loop of the first macro.

===Recoil macro=== 


<pre>MACRO KEYDOWN o
MAXIS 1 25
KEYDOWN o


MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN o


MACRO MBUTTONUP BUTTON_LEFT
KEYDOWN o</pre>


Change '25' with the value that cancels the recoil.

===Custom button press duration===

Using gimx-config, replace your current binding with an unused key, for example 'p', and define the following macro:
<pre>MACRO JBUTTONDOWN X
KEYDOWN p
DELAY Y
KEYUP p</pre>
Replace X with the button id, and Y with the delay value in ms (should be at least 1 report period = 1 / frequency).

</translate>

Macros

2020-01-24T18:57:03Z

Matlo:

<languages />
<translate>
It's possible to configure keyboard/mouse/joystick macros: a key or button press can trigger a series of keyboard/mouse/joystick events, with timing conditions.

==File format==

File format is plain text UTF-8. Recommended text editors are [https://notepad-plus-plus.org/ Notepad++] on Windows and gedit on Ubuntu.

==Directory== 


To open the directory where to put macro files, open gimx-launcher and click on "File > Open Macro Directory".

==Syntax== 


<pre>MACRO <DEVICE EVENT> <ID> <RANGE>
<DEVICE EVENT> <ID> <VALUE>
DELAY <MS>
#<COMMENT></pre>


*<DEVICE EVENT>: KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP, MAXIS, JAXIS
*<ID>: the event id (case sensitive) as displayed in gimx-config
*<VALUE>: the axis value (only for MAXIS and JAXIS)
*<RANGE>: the axis range (only for MAXIS and JAXIS); the syntax is [min,max] with min and max in [-32768,32767]; example: [8192,16384]
*<MS>: integer value in milliseconds
*<COMMENT>: a comment, not interpreted ('#' is the first character of the line)

==Commands== 


* KEYDOWN: keyboard key pressed
* KEYUP: keyboard key released
* KEY: KEYDOWN + DELAY 50 + KEYUP


* MBUTTONDOWN: mouse button pressed
* MBUTTONUP: mouse button released
* MBUTTON: MBUTTONDOWN + DELAY 50 + MBUTTONUP


* JBUTTONDOWN: joystick button pressed
* JBUTTONUP: joystick button released
* JBUTTON: JBUTTONDOWN + DELAY 50 + JBUTTONUP


* DELAY: delay in milliseconds


* MAXIS: mouse axis moved; ID: 0 for x axis, and 1 for y axis; VALUE: positive values for right and down


* JAXIS: joystick axis moved; ID: the axis id as displayed in gimx-config; VALUE: in [-32768 .. 32767] for centered axes, and in [0 .. 32767] for non-centered axes

==Macro activation== 


* '''It is possible to specify the macro files to be read for each configuration file.'''
This can be configured in a file named "configs.txt", located in the macros directory. 
Example:
<pre>#If config1.xml is loaded, macro1.txt is read.
config1.xml/macro1.txt
#If config1.xml is loaded, macro2.txt is read.
config1.xml/macro2.txt
#If config2.xml is loaded, macro2.txt is read.
config2.xml/macro2.txt</pre>
Lines beginning with a # are not interpreted. 
Since GIMX 4.0 the separator is a slash so as to allow using file names containing spaces. 


* '''It is also possible to define activation triggers within the macro definition.'''
The syntax is:
<pre>TRIGGER <event></pre>
Example:
<pre>MACRO F1
#content


MACRO F2
TRIGGER F5
#content


MACRO F3
TRIGGER F6
#content


MACRO F4
TRIGGER F5
#content</pre>
The above example works the following way: 
Macros with a trigger are default inactive. To make a macro with trigger default active, add a line containing "INIT ON" after the "TRIGGER <event>" line. 
Macros with a trigger can work with a toggle mode, which allows to activate and deactivate a macro autonomously: activating a togglable macro has no impact on other macros, and activating another macro has no impact on a togglable macro. This can be configured adding a line containing "TOGGLE YES" after the "TRIGGER <event>" line. 
Example:
<pre>MACRO F1
TRIGGER 1
INIT ON
TOGGLE YES
#content</pre>

==Notes== 

===Delay precision=== 


The delay precision depends on the controller update period:
* ds3/bluetooth = 11.25ms
* ds3/usb = 10ms
* ds4/bluetooth = 10ms
* ds4/usb = 10ms
* 360 pad = 8ms
* XOne pad = 4ms
If you specify a delay that is not a multiple of the precision, the resulting delay will be the lowest multiple of the precision higher than the specified delay. 
For example, if the precision is 11.25ms and the delay is 12ms, the resulting delay will be 22.50ms (=2*11.25ms).

===Macro loop=== 


To make a macro loop, just add a matching KEYDOWN, MBUTTONDOWN or JBUTTONDOWN command at the end of the macro. 
Example:
<pre>MACRO MBUTTONDOWN BUTTON_LEFT
#content
MBUTTONDOWN BUTTON_LEFT</pre>


The macro is triggered by pressing 'BUTTON_LEFT'. 
The last command of the macro restarts the macro, creating a loop. 
To stop a macro loop, just press the trigger again. The macro is stopped immediately, and the state of the controller is unchanged.

===Multiple keyboards/mice/joysticks=== 


In case multiple keyboards or mice or joysticks are used, it's not possible to specify the device for which events are generated. 
Events are generated for the first keyboard/mouse/joystick found in the configuration.

==Examples== 

===Rapid fire macro=== 


<pre>MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN p
#Set delay no less than the maximum rate of fire
#10 rounds per second (600 rpm)
DELAY 100
KEYUP p
#~Do not set delay after keyup or it will negatively impact automatic weapons
MBUTTONDOWN BUTTON_LEFT

MACRO MBUTTONUP BUTTON_LEFT
MBUTTONDOWN BUTTON_LEFT
#Sometimes the fire key can be stuck down after the macro ends this releases it after the macro has been terminated
KEYUP p</pre>


In gimx-config, bind 'p' to r1 in both hip fire and ADS profiles (profiles 1 and 2). 
DO NOT bind 'BUTTON_LEFT' to r1 in both hip fire and ADS profiles.


The macro is triggered by pressing the left mouse button. 
The last command of the first macro restarts the macro, creating a loop. 
Upon the release of the left mouse button the second macro ends the loop of the first macro.

===Recoil macro=== 


<pre>MACRO KEYDOWN o
MAXIS 1 25
KEYDOWN o


MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN o


MACRO MBUTTONUP BUTTON_LEFT
KEYDOWN o</pre>


Change '25' with the value that cancels the recoil.

===Custom button press duration===

Using gimx-config, replace your current binding with an unused key, for example 'p', and define the following macro:
<pre>MACRO JBUTTONDOWN X
KEYDOWN p
DELAY Y
KEYUP p</pre>
Replace X with the button id, and Y with the delay value in ms (should be at least 1 report period = 1 / frequency).

</translate>

Macros

2020-01-24T18:55:11Z

Matlo:

<languages />
<translate>
It's possible to configure keyboard/mouse/joystick macros: a key or button press can trigger a series of keyboard/mouse/joystick events, with timing conditions.

==File format==

File format is plain text UTF-8. Recommended text editors are [https://notepad-plus-plus.org/ Notepad++] on Windows and gedit on Ubuntu.

==Directory== 


To open the directory where to put macro files, open gimx-launcher and click on "File > Open Macro Directory".


GIMX 1.12 and older
<div class="mw-collapsible mw-collapsed">
* Ubuntu: the ~/.emuclient/macros directory. ~ is the home directory, and .emuclient folder is hidden (in the file manager, press ctrl+h to display hidden folders).
* Windows: the C:\Users\<username>\AppData\Roaming\emuclient\macros directory.</div>


GIMX 0.51 and older
<div class="mw-collapsible mw-collapsed">
* Windows 32bits: the C:\Program Files\GIMX\macros directory.
* Windows 64bits: the C:\Program Files (x86)\GIMX\macros directory.</div>

==Syntax== 


<pre>MACRO <DEVICE EVENT> <ID> <RANGE>
<DEVICE EVENT> <ID> <VALUE>
DELAY <MS>
#<COMMENT></pre>


*<DEVICE EVENT>: KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP, MAXIS, JAXIS
*<ID>: the event id (case sensitive) as displayed in gimx-config
*<VALUE>: the axis value (only for MAXIS and JAXIS)
*<RANGE>: the axis range (only for MAXIS and JAXIS); the syntax is [min,max] with min and max in [-32768,32767]; example: [8192,16384]
*<MS>: integer value in milliseconds
*<COMMENT>: a comment, not interpreted ('#' is the first character of the line)

==Commands== 


* KEYDOWN: keyboard key pressed
* KEYUP: keyboard key released
* KEY: KEYDOWN + DELAY 50 + KEYUP


* MBUTTONDOWN: mouse button pressed
* MBUTTONUP: mouse button released
* MBUTTON: MBUTTONDOWN + DELAY 50 + MBUTTONUP


* JBUTTONDOWN: joystick button pressed
* JBUTTONUP: joystick button released
* JBUTTON: JBUTTONDOWN + DELAY 50 + JBUTTONUP


* DELAY: delay in milliseconds


* MAXIS: mouse axis moved; ID: 0 for x axis, and 1 for y axis; VALUE: positive values for right and down


* JAXIS: joystick axis moved; ID: the axis id as displayed in gimx-config; VALUE: in [-32768 .. 32767] for centered axes, and in [0 .. 32767] for non-centered axes

==Macro activation== 


* '''It is possible to specify the macro files to be read for each configuration file.'''
This can be configured in a file named "configs.txt", located in the macros directory. 
Example:
<pre>#If config1.xml is loaded, macro1.txt is read.
config1.xml/macro1.txt
#If config1.xml is loaded, macro2.txt is read.
config1.xml/macro2.txt
#If config2.xml is loaded, macro2.txt is read.
config2.xml/macro2.txt</pre>
Lines beginning with a # are not interpreted. 
Since GIMX 4.0 the separator is a slash so as to allow using file names containing spaces. 


* '''It is also possible to define activation triggers within the macro definition.'''
The syntax is:
<pre>TRIGGER <event></pre>
Example:
<pre>MACRO F1
#content


MACRO F2
TRIGGER F5
#content


MACRO F3
TRIGGER F6
#content


MACRO F4
TRIGGER F5
#content</pre>
The above example works the following way: 
Macros with a trigger are default inactive. To make a macro with trigger default active, add a line containing "INIT ON" after the "TRIGGER <event>" line. 
Macros with a trigger can work with a toggle mode, which allows to activate and deactivate a macro autonomously: activating a togglable macro has no impact on other macros, and activating another macro has no impact on a togglable macro. This can be configured adding a line containing "TOGGLE YES" after the "TRIGGER <event>" line. 
Example:
<pre>MACRO F1
TRIGGER 1
INIT ON
TOGGLE YES
#content</pre>

==Notes== 

===Delay precision=== 


The delay precision depends on the controller update period:
* ds3/bluetooth = 11.25ms
* ds3/usb = 10ms
* ds4/bluetooth = 10ms
* ds4/usb = 10ms
* 360 pad = 8ms
* XOne pad = 4ms
If you specify a delay that is not a multiple of the precision, the resulting delay will be the lowest multiple of the precision higher than the specified delay. 
For example, if the precision is 11.25ms and the delay is 12ms, the resulting delay will be 22.50ms (=2*11.25ms).

===Macro loop=== 


To make a macro loop, just add a matching KEYDOWN, MBUTTONDOWN or JBUTTONDOWN command at the end of the macro. 
Example:
<pre>MACRO MBUTTONDOWN BUTTON_LEFT
#content
MBUTTONDOWN BUTTON_LEFT</pre>


The macro is triggered by pressing 'BUTTON_LEFT'. 
The last command of the macro restarts the macro, creating a loop. 
To stop a macro loop, just press the trigger again. The macro is stopped immediately, and the state of the controller is unchanged.

===Multiple keyboards/mice/joysticks=== 


In case multiple keyboards or mice or joysticks are used, it's not possible to specify the device for which events are generated. 
Events are generated for the first keyboard/mouse/joystick found in the configuration.

==Examples== 

===Rapid fire macro=== 


<pre>MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN p
#Set delay no less than the maximum rate of fire
#10 rounds per second (600 rpm)
DELAY 100
KEYUP p
#~Do not set delay after keyup or it will negatively impact automatic weapons
MBUTTONDOWN BUTTON_LEFT

MACRO MBUTTONUP BUTTON_LEFT
MBUTTONDOWN BUTTON_LEFT
#Sometimes the fire key can be stuck down after the macro ends this releases it after the macro has been terminated
KEYUP p</pre>


In gimx-config, bind 'p' to r1 in both hip fire and ADS profiles (profiles 1 and 2). 
DO NOT bind 'BUTTON_LEFT' to r1 in both hip fire and ADS profiles.


The macro is triggered by pressing the left mouse button. 
The last command of the first macro restarts the macro, creating a loop. 
Upon the release of the left mouse button the second macro ends the loop of the first macro.

===Recoil macro=== 


<pre>MACRO KEYDOWN o
MAXIS 1 25
KEYDOWN o


MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN o


MACRO MBUTTONUP BUTTON_LEFT
KEYDOWN o</pre>


Change '25' with the value that cancels the recoil.

===Custom button press duration===

Using gimx-config, replace your current binding with an unused key, for example 'p', and define the following macro:
<pre>MACRO JBUTTONDOWN X
KEYDOWN p
DELAY Y
KEYUP p</pre>
Replace X with the button id, and Y with the delay value in ms (should be at least 1 report period = 1 / frequency).

</translate>

RPi

2019-12-28T11:27:32Z

Matlo:

<languages />
<translate>

'''Warning: RPi support should be considered as experimental. The USB controller has been unstable since the first version. Be prepared to face issues if you try GIMX on the RPi.'''

GIMX can run on many Linux targets, and the [http://www.raspberrypi.org/ the Raspberry Pi] is one of them!

== Setup using pre-made image == 


The simplest way to set up GIMX on a Raspberry Pi is by flashing a pre-made image. See forum user steel_3d's instructions on getting up and running: [http://www.steve-marton.com/gimx/?p=462 Build your own Plug n Play GIMX emulator using Raspberry Pi]

== Hardware considerations == 


Use a USB HUB only if there are no ports available on the RPi. 
It is highly recommended to use a HUB with an external power supply.

== USB adapter using the on-board UART interface == 

=== Hardware requirements === 


The on-board UART runs at 0V/3.3V levels, and the AVR USB board has to run at 5V to operate at 16MHz (running at 3.3V would only allow to operate at 8MHz). 
Connecting the RPi and the AVR USB board directly may damage the hardware! 
One cheap solution is to use a voltage divider: 
* Connect both GNDs
* It's safe to connect the TXD pin of the RPi to the Rx pin of the AVR USB board (the GIMX firmwares configure the Rx pin as an input)
* To connect the Tx pin of the AVR USB board to the RXD pin of the RPi, you'll need to convert the voltage level from 0..5V to 0..3.3V. 
This can be done with a simple voltage divider:
<div class="image200px">[https://gimx.fr/img/wiki/Resistive_divider.png https://gimx.fr/img/wiki/Resistive_divider.png]</div>
Vin is the Tx pin of the AVR USB board, Vout is the RXD pin of the RPi, R1=2.2kΩ , R2=3.3kΩ
* Do not connect any other pin!

=== Sotware adjustments === 


By default, the RPi UART is configured as a serial console. 
Disable this serial console using raspi-config:
<pre>
sudo raspi-config
</pre>
Then select:
<pre>
"Advanced Options", "Serial", "No", "Finish"
</pre>
The default configuration does not allow high baudrates. 
Enable high baudrates editing /boot/config.txt:
<pre>
sudo nano /boot/config.txt
</pre>
Add the following line at the end of the file:
<pre>
init_uart_clock=8000000
</pre>
Reboot to apply the changes:
<pre>
sudo reboot
</pre>

== GIMX installation == 
<pre>wget https://gimx.fr/download/gimx-raspbian -O gimx.deb
sudo dpkg -i gimx.deb
sudo apt-get update && sudo apt-get -f install</pre>


If you get a "Dependency is not satisfiable: ..." error message, upgrade Raspbian:
<pre>sudo apt-get update && sudo apt-get upgrade
sudo apt-get -f install</pre>

== Stop/disable triggerhappy service == 
[https://github.com/wertarbyte/triggerhappy/blob/master/README Triggerhappy] is a daemon that opens every input device for reading, and that consumes a few percent of the CPU time.


It seems a good idea to stop it while running GIMX.


To stop triggerhappy:
sudo service triggerhappy stop
To disable triggerhappy:
sudo update-rc.d triggerhappy disable

== Run GIMX == 
Read the [[Quick_Start|Quick start page]] to learn how to run GIMX through the GUI. 

A good idea is to run GIMX directly from a terminal, without starting a graphical session, which can be done over the network, using a ssh client, or you can [[#Autostart GIMX at boot without GUI]] 

Ideally, GIMX should be launched without using the Ethernet port (because it is connected on the USB bus). However, this doesn't seem to cause any issues generally. 

More details on command line options on [[Command_line|this page]]. 

The GUI will help you download the config xmls. If you never run the GUI, you MUST grab the Linux config xmls from here: https://github.com/matlo/GIMX-configurations/tree/master/Linux The Windows xmls are NOT compatible! 

== Autostart GIMX at boot without GUI == 
Simply create a file /etc/systemd/system/gimx.service (as root):

<pre>
sudo nano /etc/systemd/system/gimx.service
</pre>

With the following contents:


<pre>
[Unit]
Description=GIMX
After=syslog.target network.target


[Service]
User=pi
Type=simple
# Replace /dev/ttyUSB0 with /dev/ttyAMA0 when using the on-board UART interface
ExecStart=/usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
Restart=always
RestartSec=5


[Install]
WantedBy=multi-user.target
</pre>


Replace ttyUSB0 with your device (/dev/ttyAMA0 when using the on-board UART interface) and LogitechDrivingForceGT_G29.xml with your mapping file (which should be available in the pi home directory as /home/pi/.gimx/config/LogitechDrivingForceGT_G29.xml)


Run <pre>sudo systemctl daemon-reload</pre> to notify systemd about the new file and <pre>sudo systemctl enable gimx && sudo systemctl start gimx</pre> to enable the gimx service start at boot and start it in the same line.

== Notify when GIMX is running using a led == 
In order to have a proper confirmation about if the gimx service is up and running, you can add a simple python script that turns a led on if the gimx service is running.


The file will be located at /home/pi/blink.py:

<pre>sudo nano blink.py</pre>

With the following contents:


<pre>
#!/usr/bin/python
import os
import time
import RPi.GPIO as GPIO


led = 23
button = 18
GPIO.setmode(GPIO.BCM)
GPIO.setup(led, GPIO.OUT)
GPIO.setup(button, GPIO.IN, pull_up_down = GPIO.PUD_UP)


def Shutdown(channel):
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
time.sleep(0.2)
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
os.system("sudo shutdown -h now")


GPIO.add_event_detect(18, GPIO.FALLING, callback = Shutdown, bouncetime = 2000)


while True:
found = False
time.sleep(5)
pids = [pid for pid in os.listdir('/proc') if pid.isdigit()]
for pid in pids:
try:
cmd = open(os.path.join('/proc', pid, 'cmdline'), 'rb').read()
if "gimx" in cmd:
found = True
except IOError: # proc has already terminated
continue
if found == True:
GPIO.output(led, True)
else:
GPIO.output(led, False)
</pre>


As a bonus, you can add a button so when it is pressed, there is a little blink effect, and the pi is shutted down.


<div class="image200px">[https://gimx.fr/img/wiki/PiButtonLed.png https://gimx.fr/img/wiki/PiButtonLed.png]</div>


To start at boot, simply add it to the pi user crontab (crontab -e) as <pre>@reboot python /home/pi/blink.py &</pre>

== Powering on AVR and RPi simultaneously using the on-board UART interface == 
In case you want to power up AVR (Tested on Pro Micro ATmega32u4) and RPi at once (i.e. using PS4 USB port and a USB Y Splitter) using the on-board UART interface, you will need the adjust shown below in order to reset the AVR board from RPi once started.


It is planned to solve this issue on GIMX 8 version [https://github.com/matlo/GIMX/issues/426]


More details on support forum thread [https://gimx.fr/forum/viewtopic.php?f=5&t=1672]


'''Physically'''
* RPi's PIN40 / GPIO21 connected to ATmega32u4 RST pin directly. (Any RPi GPIO pin should works)


'''Logically'''
* New bash script created /home/pi/resetArduino.sh with content shown below:
<pre>
#!/bin/bash

echo 21 > /sys/class/gpio/export
sleep 1
echo out > /sys/class/gpio/gpio21/direction
sleep 1
echo 1 > /sys/class/gpio/gpio21/value
sleep 1
echo 0 > /sys/class/gpio/gpio21/value
sleep 1
echo 1 > /sys/class/gpio/gpio21/value

exit 0
</pre>
* Grant execution permissions
<pre>chmod +x /home/pi/resetArduino.sh</pre>
* Add the new script to boot sequence (like we do with blink.py program)
<pre>
pi@raspberrypi:~ $ crontab -l
@reboot /home/pi/resetArduino.sh && python /home/pi/blink.py &
</pre>

Using this configuration, GIMX is able to start correctly on its first attempt when RPi and ATmega32u4 are powered on from PS4 simultaneously using GPIO instead of CP2102 USB UART.

</translate>

Axis translation parameters

2019-10-24T05:51:19Z

Matlo:

Give simple use cases such as: how to bind a joystick axis to an axis

<languages />
<translate>


This page explains the purpose of each axis translation parameter.

=Dead zone= 


[[File:DZShapeCircle.gif|left|frame|Visual Demonstration]] '''The dead zone parameter allows to shift the stick positions away from the stick center. Higher the DZ (Dead zone) is, larger mouse moves need to be done in order to aim.'''

This allows to skip all the stick positions around the stick center that do not generate in-game movement (these positions are called the dead zone of the stick).

If lowest input motion do not generate enough movement, increase the dead zone parameter.

When you calibrate the dead zone you want the aim to move as slowly and smoothly as possible (no jitters or random jumps)
The aim should start moving by itself when you increase the dead zone using the mouse wheel, so all you need to do is fine tune it until the speed of the aim is slow and fluid.

Remember to go out of dead zone calibration to test the results of your adjustments. If the aim lags in calibration mode you'll need to save your configuration and run the emulator in normal Grab mode to test any changes you've made.

'''''Tip''''': ''To get rid of potential jerky aim when aiming slowly you need to increase DZ slightly above the game setting. So if you find through dead zone calibration that the aim starts moving by itself at '''22''', increase it to '''25'''-'''30''' instead.''
 

=Dead zone shape= 


The dead zone shape can be set to:

<div style="margin-top: 10px; "><ul style="margin-left:0px;">
<li style="display: inline-block;"> [[File:DZShapeCircle.gif|frame|none|Circle]] </li>
<li style="margin-left: 10px;display: inline-block;"> [[File:DZShapeRectangle.gif|frame|none|Rectangle]] </li>
</ul></div>


More shapes will be added in a future version.

=Sensitivity= 


[[File:mpanim.gif|left|frame|Visual Demonstration]]'''The sensitivity parameter is nothing more than a multiplier: input motion is multiplied so as to scale to the output motion range.'''

Increase it if the movement is too slow and decrease it if the movement is too fast.

It can be a negative value, so as to reverse the motion direction.

Remember that the output motion range is limited (the stick has a max position).


To map a joystick axis to a stick axis, use a value of 128/32768 (about 0.004).

To map a joystick axis to a button axis, use a value of 256/32768 (about 0.008).

=X/Y ratio= 


'''The x/y ratio allows to change the vertical sensitivity independently from the horizontal sensitivity''' i.e. it determines how much faster your vertical (Y axis) aim is in relation to your horizontal (X axis) aim.

A value of 3.0 would make you aim up and down incredibly fast, whereas 0.1 would make it almost impossible to move it up or down at all.

Some games require higher or lower value. It all depends on developers implementation of controls in the game engine.

Vertical sensitivity formula is as follows:
vertical_sens = sens * xy_ratio

=Acceleration= 


[[File:expanim.gif|left|frame|Visual Demonstration]] '''The acceleration parameter allows to change the in-game acceleration.'''

Values higher than '''1''' increase the effective acceleration, whereas values lower that '''1''' decrease it.

FPS games generally have a positive acceleration, which means there is a value in the '''0..1''' range that will cancel it (at least for games that use simple look mechanics).

Acceleration value required for good aiming experience may vary from game to game as it depends on developers implementation of controls in the game engine.

After having played around with these settings and you've learned what does what and how they work together, you can start fine tuning configurations to fit your personal preference or make your very own ones that we hope you'd like to share with us on the [https://forum.gimx.fr/viewforum.php?f=9 forums!].

'''''Tip''''': ''In the Call of Duty series (since Call of Duty 4) for example, a value of 0.39 will give you a 1:1-like aim (meaning there is little to no acceleration when moving the mouse) Having a higher exponent will make the aim accelerate but you won't need a high multiplier (the higher the multiplier is the bigger the gaps are between each "step" in the speed curve)
''

=Buffer size and filter= 


These parameters are specific to the mouse smoothing, which is detailed on the [[Mouse_Calibration|Mouse calibration]] page.

</translate>

Template:PrerequisitesNext

2019-10-04T14:06:19Z

Matlo: /* Hardware requirements */

==Hardware requirements==
# '''Computer''' {{#switch:{{{ostype|}}}
|windows = PC running Windows 7 or later
|linux = #:PC running Ubuntu 18.04 or derivatives such as Linux Mint 19 '''OR''' Raspberry Pi running Raspbian Stretch (experimental)
|}}{{#switch:{{{device|}}}
| Mouse = # '''Mouse''' Forget about using a mouse with anything less than 2000DPI and 250Hz. A gaming mouse with 5000+ DPI and running at 500Hz is highly recommended. Whereas a gaming mouse with more than 1600 DPI doesn't really make a difference on a computer, it's not the case with GIMX. GIMX can decelerate mouse movements so as to counteract the in-game acceleration. A high DPI mouse results in smoother movements in this specific case.|}}
{{#switch:{{{connectionType|}}}
|BT = # '''Bluetooth adapter''' Using a bluetooth dongle or an internal bluetooth module, GIMX can disguise itself as a controller to your console. While all bluetooth dongles/modules can't work with GIMX, working dongles are quite common. Check the [[Bluetooth_dongle|compatibility list]]. {{#ifeq:{{{platform|}}}|ps4|
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the PS4.
# '''An AVR USB board such as the Teensy 2.0''' It is required for the bluetooth pairing procedure.|}}
|USB = # '''USB adapter''' This is an adapter that you can either buy from the GIMX shop or build yourself:
#* [https://blog.gimx.fr/product/gimx-adapter/ Buy a ready to use GIMX adapter from the official GIMX shop.]
#* [[DIY_USB_adapter|Build yourself a GIMX adapter]]
#: Forget about using any other USB to USB cable (like file transfer cables, or direct cables), they are not suited to this use.
{{#switch:{{{platform|}}}
| ps4 =
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the console.
| xboxone =
# '''Genuine Xbox One controller''' It is required because GIMX has to authenticate to the console. Controllers with the 3.5mm jack are supported since GIMX 7.13.
| xbox360 =
# '''Genuine wired 360 controller''' It is required because the USB adapter has to authenticate to the console. A wireless 360 controller with a play and charge kit will NOT work.
}}|}}

Template:PrerequisitesNext

2019-10-04T14:05:36Z

Matlo: /* Hardware requirements */

==Hardware requirements==
# '''Computer''' {{#switch:{{{ostype|}}}
|windows = PC running Windows 7 or later
|linux = #:PC running Ubuntu 18.04 or derivatives such as Linux Mint 19 '''OR''' Raspberry Pi running Raspbian Stretch (experimental)
|}}{{#switch:{{{device|}}}
| Mouse = # '''Mouse''' Forget about using a mouse with anything less than 2000DPI and 250Hz. A gaming mouse with 5000+ DPI and running at 500Hz is highly recommended. Whereas a gaming mouse with more than 1600 DPI doesn't really make a difference on a computer, it's not the case with GIMX. GIMX can decelerate mouse movements so as to counteract the in-game acceleration. A high DPI mouse gives a smoother movement in this specific case.|}}
{{#switch:{{{connectionType|}}}
|BT = # '''Bluetooth adapter''' Using a bluetooth dongle or an internal bluetooth module, GIMX can disguise itself as a controller to your console. While all bluetooth dongles/modules can't work with GIMX, working dongles are quite common. Check the [[Bluetooth_dongle|compatibility list]]. {{#ifeq:{{{platform|}}}|ps4|
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the PS4.
# '''An AVR USB board such as the Teensy 2.0''' It is required for the bluetooth pairing procedure.|}}
|USB = # '''USB adapter''' This is an adapter that you can either buy from the GIMX shop or build yourself:
#* [https://blog.gimx.fr/product/gimx-adapter/ Buy a ready to use GIMX adapter from the official GIMX shop.]
#* [[DIY_USB_adapter|Build yourself a GIMX adapter]]
#: Forget about using any other USB to USB cable (like file transfer cables, or direct cables), they are not suited to this use.
{{#switch:{{{platform|}}}
| ps4 =
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the console.
| xboxone =
# '''Genuine Xbox One controller''' It is required because GIMX has to authenticate to the console. Controllers with the 3.5mm jack are supported since GIMX 7.13.
| xbox360 =
# '''Genuine wired 360 controller''' It is required because the USB adapter has to authenticate to the console. A wireless 360 controller with a play and charge kit will NOT work.
}}|}}

Development on Windows

2019-09-20T12:43:16Z

Matlo: /* Debug build */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command" (replace 4 with your number of CPU cores)
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Development on Windows

2019-09-20T12:42:14Z

Matlo: /* Building project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

===Debug build===

* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* in "C/C++ Build", uncheck "Use default build command"
* enter "make -j 4 DEBUG=1 VERBOSE=1" without quotes as "Build command"
* in the "Project Explorer" view, right-click on the project, and click on "Clean project"
* in the "Project Explorer" view, right-click on the project, and click on "Build project"

===Notes===

The build system does not detect changes in headers. Clean and rebuild project after modifying a header.

</translate>

Development on Windows

2019-09-20T12:34:59Z

Matlo: /* Building project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin
** it is not a good idea to change PATH at the system level, as this could lead to other apps malfunctioning

</translate>

Mouse Calibration

2019-08-30T14:54:59Z

Matlo:

<languages />
<translate>=Before calibrating the mouse= 


Set the in-game sensitivity to the highest, and set the mouse dpi to the highest value. 
If game allows adjusting the dead zone, set it to the lowest value.

'''''Note''''': ''In rare cases some games may require leaving sensitivity at default value due to input bugs introduced at higher speeds.''
=Start calibration= 


<div class="image200px">[https://gimx.fr/wiki/images/a/ae/Mousecalibration.png https://gimx.fr/wiki/images/a/ae/Mousecalibration.png]</div> 
Select Messages>curses in gimx-launcher. Then click on Start.


<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_2.png https://gimx.fr/img/screenshots/Calibration_2.png]</div>


Current mouse calibration values appear in the "Mouse calibration" part of the gui. 
This calibration mode reads values from the loaded configuration. 
If you use multiple mice, it lets you calibrate each mouse independently.

=General instructions= 


Press ctrl+F1 to enable the calibration.
<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_3.png https://gimx.fr/img/screenshots/Calibration_3.png]</div>
Press F1 ... F12 to select the parameter, and use the mouse wheel to change the value.
Press ctrl+F1 to leave the calibration and save the parameters.

=Step-by-step instructions= 

Make sure to perform the steps in order, and don't skip any step or you'll get it wrong.


# Press ctrl+F1. If you use multiple mice, select the mouse to calibrate with the mouse wheel.
# Press F2 and select the profile to calibrate with the mouse wheel (generally, profile 1 is for hip fire, and profile 2 is for aiming down the sight).
# Press F3. If the sight moves, decrease the x dead zone value with the mouse wheel until the sight does not move. Once the sight does not move, increase the x dead zone until the first moving position.
# Press F4. Set the same value as the x dead zone value.
# Press F5. Set the dead zone shape value to "rectangle". If the sight moves, set the dead zone shape to "circle", and let it set to "rectangle" otherwise.
# Press F6 to start a translation test. The sight will move horizontally at different speeds in both left and right directions. A 1:1 translation means the sight should come back near the start point. If it doesn't, use F7 and the mouse wheel to change the x acceleration value. Note that it's not always possible to get a 1:1 translation (this depends on the game).
# Press F8. Set the same value as the x acceleration value.
# Press F9. Adjust the x sensitivity to your liking.
# Press F10 to start a circle test. Adjust the circle radius and speed (F10/F11 + mouse wheel) if necessary. The x/y ratio is properly set if the sight moves in a perfect circle. If it doesn't, adjust the x/y ratio using F12 and the mouse wheel.
# Press ctrl+F1 to save.

Note: if the mouse has low DPI and if the acceleration value is well below 1, your sensitivity will probably be so high that it will result in low movements to be jerky. This is because a mouse movement of 1 dot results in a stick position far away from the dead zone. To compensate this you may subtract the sensitivity from your dead zone. For example with a dead zone of 32 and a sensitivity of 10, set the dead zone to 22. Using smoothing may also help with a low DPI mouse.

=Smoothing= 


The mouse motion can be smoothed using previous mouse motion reports. 
This is useful for lowering jerkiness, especially with a low DPI mouse (below 2000 DPI). 
It is configurable with two parameters: a buffer size and a filter. 
A deeper description of the smoothing technique used by GIMX is available [http://www.flipcode.com/archives/Smooth_Mouse_Filtering.shtml there].

==Note== 


Before adding smoothing, you should have properly set the other parameters.

==Buffer size== 


The buffer size (in the 0..30 range) is the number of mouse motion reports that are used to smooth the mouse motion. 
The smoothing window is the buffer size multiplied by the GIMX update period (inverse of the frequency). 
Examples:
GIMX frequency = 250Hz, buffer size = 10
1000/250 * 10 = 40ms


GIMX frequency = 100Hz, buffer size = 10
1000/100 * 10 = 100ms


Keep in mind that increasing the buffer size makes motion smoother but increases the latency.

==Filter== 


The filter (in the 0..1 range) defines how much the previous motion reports will count in the final motion. 
Value 1 means that the final motion is an average of the buffered motion reports. 
Value 0.5 means that the current motion report counts for 1, the previous one for 0.5, the next oldest one for 0.25 (=0.5x0.5), and so on. 
Value 0 means that only the current motion report counts (resulting in an unfiltered motion). 
So as to preserve a low latency, high filters (1) should only be used with low buffer sizes (2), and high buffer sizes (>10) should only be used with low filters (<0.75).

=Pitfalls= 


This summarizes all common errors you should avoid, and what you should do instead.


* Don't change the mouse dpi to adjust your aiming speed. Always let the mouse dpi setting to the max value. Adjust the GIMX sensitivity instead.
* Don't change the in-game sensitivity to adjust your aiming speed. Always let the in-game sensitivity to the max value. Adjust the GIMX sensitivity instead.
* Don't change the mouse parameters of the OS (Linux/Windows) to adjust your aiming speed. GIMX uses raw (unmodified) events from the mouse!
* Prefer editing the sensitivity with the calibration mode. The calibration mode keeps the x/y ratio.
</translate>

Mouse Calibration

2019-08-30T14:43:20Z

Matlo:

<languages />
<translate>=Before calibrating the mouse= 


Set the in-game sensitivity to the highest, and set the mouse dpi to the highest value. 
If game allows adjusting the dead zone, set it to the lowest value.

'''''Note''''': ''In rare cases some games may require leaving sensitivity at default value due to input bugs introduced introduced at higher speeds.''
=Start calibration= 


<div class="image200px">[https://gimx.fr/wiki/images/a/ae/Mousecalibration.png https://gimx.fr/wiki/images/a/ae/Mousecalibration.png]</div> 
Select Messages>curses in gimx-launcher. Then click on Start.


<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_2.png https://gimx.fr/img/screenshots/Calibration_2.png]</div>


Current mouse calibration values appear in the "Mouse calibration" part of the gui. 
This calibration mode reads values from the loaded configuration. 
If you use multiple mice, it lets you calibrate each mouse independently.

=General instructions= 


Press ctrl+F1 to enable the calibration.
<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_3.png https://gimx.fr/img/screenshots/Calibration_3.png]</div>
Press F1 ... F12 to select the parameter, and use the mouse wheel to change the value.
Press ctrl+F1 to leave the calibration and save the parameters.

=Step-by-step instructions= 

Make sure to perform the steps in order, and don't skip any step or you'll get it wrong.


# Press ctrl+F1. If you use multiple mice, select the mouse to calibrate with the mouse wheel.
# Press F2 and select the profile to calibrate with the mouse wheel (generally, profile 1 is for hip fire, and profile 2 is for aiming down the sight).
# Press F3. If the sight moves, decrease the x dead zone value with the mouse wheel until the sight does not move. Once the sight does not move, increase the x dead zone until the first moving position.
# Press F4. Set the same value as the x dead zone value.
# Press F5. Set the dead zone shape value to "rectangle". If the sight moves, set the dead zone shape to "circle", and let it set to "rectangle" otherwise.
# Press F6 to start a translation test. The sight will move horizontally at different speeds in both left and right directions. A 1:1 translation means the sight should come back near the start point. If it doesn't, use F7 and the mouse wheel to change the x acceleration value. Note that it's not always possible to get a 1:1 translation (this depends on the game).
# Press F8. Set the same value as the x acceleration value.
# Press F9. Adjust the x sensitivity to your liking.
# Press F10 to start a circle test. Adjust the circle radius and speed (F10/F11 + mouse wheel) if necessary. The x/y ratio is properly set if the sight moves in a perfect circle. If it doesn't, adjust the x/y ratio using F12 and the mouse wheel.
# Press ctrl+F1 to save.

Note: if the mouse has low DPI and if the acceleration value is well below 1, your sensitivity will probably be so high that it will result in low movements to be jerky. This is because a mouse movement of 1 dot results in a stick position far away from the dead zone. To compensate this you may subtract the sensitivity from your dead zone. For example with a dead zone of 32 and a sensitivity of 10, set the dead zone to 22. Using smoothing may also help with a low DPI mouse.

=Smoothing= 


The mouse motion can be smoothed using previous mouse motion reports. 
This is useful for lowering jerkiness, especially with a low DPI mouse (below 2000 DPI). 
It is configurable with two parameters: a buffer size and a filter. 
A deeper description of the smoothing technique used by GIMX is available [http://www.flipcode.com/archives/Smooth_Mouse_Filtering.shtml there].

==Note== 


Before adding smoothing, you should have properly set the other parameters.

==Buffer size== 


The buffer size (in the 0..30 range) is the number of mouse motion reports that are used to smooth the mouse motion. 
The smoothing window is the buffer size multiplied by the GIMX update period (inverse of the frequency). 
Examples:
GIMX frequency = 250Hz, buffer size = 10
1000/250 * 10 = 40ms


GIMX frequency = 100Hz, buffer size = 10
1000/100 * 10 = 100ms


Keep in mind that increasing the buffer size makes motion smoother but increases the latency.

==Filter== 


The filter (in the 0..1 range) defines how much the previous motion reports will count in the final motion. 
Value 1 means that the final motion is an average of the buffered motion reports. 
Value 0.5 means that the current motion report counts for 1, the previous one for 0.5, the next oldest one for 0.25 (=0.5x0.5), and so on. 
Value 0 means that only the current motion report counts (resulting in an unfiltered motion). 
So as to preserve a low latency, high filters (1) should only be used with low buffer sizes (2), and high buffer sizes (>10) should only be used with low filters (<0.75).

=Pitfalls= 


This summarizes all common errors you should avoid, and what you should do instead.


* Don't change the mouse dpi to adjust your aiming speed. Always let the mouse dpi setting to the max value. Adjust the GIMX sensitivity instead.
* Don't change the in-game sensitivity to adjust your aiming speed. Always let the in-game sensitivity to the max value. Adjust the GIMX sensitivity instead.
* Don't change the mouse parameters of the OS (Linux/Windows) to adjust your aiming speed. GIMX uses raw (unmodified) events from the mouse!
* Prefer editing the sensitivity with the calibration mode. The calibration mode keeps the x/y ratio.
</translate>

Network API

2019-08-28T19:49:27Z

Matlo:

This page describes how to talk to a GIMX instance that is listening for UDP packets on a specific port. 
See the "--src IP:port" argument on the [[Command_line#General_gimx_options|Command line page]] to learn how to start such a GIMX instance.

=Protocol starting from version 7.1=

One problem with the earlier protocol was that backward compatibility was broken each time a new axis was added to the controller map. 
The new protocol allows to send any number of axis values.

==Get controller type==

Use this request for getting the controller type of the remote GIMX instance.

{| class="wikitable" style="text-align: center;"
|+Request
| byte || value
|-
|
|-
| 0 || 0x00
|-
| 1 || 0x00
|}

{| class="wikitable" style="text-align: center;"
|+Answer
| byte || value
|-
|
|-
| 0 || 0x00
|-
| 1 || 0x01
|-
| 2 || value
|}

{| class="wikitable" style="text-align: center;"
|value || type
|-
|
|-
| 0x00 || JOYSTICK
|-
| 0x01 || 360 PAD
|-
| 0x02 || SIXAXIS
|-
| 0x05 || DS4
|-
| 0x06 || Xbox One PAD
|-
| 0x07 || T300RS PS4
|-
| 0x08 || G27 PS3
|-
| 0x09 || G29 PS4
|-
| 0x0A || DF PS2 (Driving Force)
|-
| 0x0B || DFP PS2 (Driving Force Pro)
|-
| 0x0C || GTF PS2 (GT Force)
|}

==Send report==

Use this request to update the axes of the remote GIMX instance. 
The [[Controller_Maps|Controller Maps]] page describes the axes and the value ranges corresponding to each controller type.

{| class="wikitable" style="text-align: center;"
|+Report
| byte || value
|-
|
|-
| 0 || 0x01
|-
| 1 || number of axes to follow
|-
| 2 ||
{| class="wikitable" style="text-align: center;"
|bit 7
|bit 6
|bit 5
|bit 4
|bit 3
|bit 2
|bit 1
|bit 0
|-
|0 for rel_axis 
1 for abs_axis
|colspan="7"|axis index X for abs_axis_X or rel_axis_X
|}
|-
| 3-6 || axis value (network byte order, see below)
|-
| ... || repeat 2 and 3-6 for each axis to update
|-
|}

To compute the axis value, take the int value stored as two's complement, and store it using the network byte order, which is big endian. 
Examples:
* -32767 = 0xffff8001 => value = 0xff, 0xff, 0x80, 0x01
* -127 = 0xffffff81 => value = 0xff, 0xff, 0xff, 0x81
* -1 = 0xffffffff => value = 0xff, 0xff, 0xff, 0xff
* 0 = 0x00000000 => value = 0x00, 0x00, 0x00, 0x00
* 1 = 0x00000001 => value = 0x00, 0x00, 0x00, 0x01
* 127 = 0x0000007f => value = 0x00, 0x00, 0x00, 0x7f
* 32767 = 0x00007fff => value = 0x00, 0x00, 0x7f, 0xff

=Python source code example=

A python source code example is available here: https://github.com/matlo/gimx-network-client

=Protocol for versions up to 6.11=

<div class="mw-collapsible mw-collapsed">

==Get controller type==

It's possible to send a packet to get the controller type from the remote GIMX.

{| class="wikitable" style="text-align: center;"
|+Request
| byte || value
|-
|
|-
| 0 || 0x11
|-
| 1 || 0x00
|}

{| class="wikitable" style="text-align: center;"
|+Answer
| byte || value
|-
|
|-
| 0 || 0x11
|-
| 1 || 0x01
|-
| 2 || value
|}

{| class="wikitable" style="text-align: center;"
|value || type
|-
|
|-
| 0x00 || JOYSTICK
|-
| 0x01 || 360 PAD
|-
| 0x02 || SIXAXIS
|-
| 0x05 || DS4
|-
| 0x07 || T300RS PS4
|-
| 0x08 || G27 PS3
|-
| 0x09 || G29 PS4
|}

==Send report==

All axes are signed integers.

The [[Controller_Maps|Controller Maps]] page describes the axes and the value ranges corresponding to each controller type.

{| class="wikitable" style="text-align: center;"
|+Report
| byte || value
|-
|
|-
| 0 || 0xff
|-
| 1 || 0x9C = 156
|-
| 2-5 || axis 0
|-
| 6-9 || axis 1
|-
| ... ||
|-
| 158-161 || axis 39 (changed in GIMX 6.10)
|}

</div>

Force Feedback

2019-07-03T21:26:24Z

Matlo:

<languages />
<translate>

Force feedback support is available for all Logitech wheel emulations:
* EMUG29PS4: G29, for PS4 (does not work with PC as target)
* EMUG27PS3: G27, for PS3 (does not work with PC as target)
* EMUGTFPS2: GT Force, for PS2 (may work with PC as target)
* EMUDFPS2: Driving Force, for PS2 (may work with PC as target)
* EMUDFPPS2: Driving Force Pro, for PS2 (may work with PC as target)
* EMUG27PC: G27, for PC


There are two force feedback conversion methods: direct translation and OS translation.

=Notes= 

==Compatibility mode== 


This concerns at least the EMUG27PS3 firmware. 
The G27 is supposed to switch to compatibility mode (behaving as a Driving Force) when in the XMB. GIMX does not do this. As a consequence the controls do not work correctly in the XMB. 
To work-around this issue, start the game with a Dualshock 3, and then [https://support.us.playstation.com/articles/en_US/KC_Article/PS3-Pair-and-Assign-Controllers reassign controllers].

==Device selection strategy== 


GIMX considers the first joystick device controlling the wheel axis as the target for force feedback effects. 
Starting from GIMX '''6.7''', any device set in the "Overall>Force Feeback tweaks" panel gets selected as the target. 
If the target has no force feedback capabilities, then no device receives the force feedback effects.


--todo: add screenshot

=Direct translation= 
It works for the following Logitech wheels:
* Formula Force GP
* Driving Force
* Driving Force Ex
* Momo Force
* Momo Racing Force
* Driving Force Pro
* G25
* Driving Force GT
* G27
* G29
It also should work for all wheels that have a Logitech compatibility mode. Many Fanatec wheel have such compatibility mode.

=OS translation= 
* Windows: any wheel supporting force feedback over DirectInput should work
:All PC/Windows-compatible force feedback wheels should work.
* GNU/Linux: any wheel with force feedback support at driver level should work
:Currently only the G29/G920 wheels have good support at driver level on GNU/Linux, with Linux kernel 4.6+.
:The G29 has direct translation, and the G920 will have OS translation from GIMX 6.3 (with Linux kernel 4.6+ only).

=Pedal axis correction= 


From version '''6.8''' gimx-config includes a calibration tool for pedal axes. It is triggered when adding or editing a pedal axis mapping in the Axis tab. It automatically adds the right settings in the "Overall>Joystick corrections" tab.

=Direct Input= 


Direct Input is a very tricky interface, and some wheels may require adjustments to have force feedback working. 
Use the instructions below to provide useful information to the GIMX devs.

==API monitor== 
This tools allows to observe how an application uses the Windows APIs. 
Download: http://www.rohitab.com/download/api-monitor-v2r13-x86-x64.zip 
Make sure to extract the whole archive.

==fedit== 
This tool was provided by Microsoft in the DirectX 8 SDK. 
Download: https://gimx.fr/download/b882e209a0ac023d03abbf560dfc3f25fe6367ca/fedit.zip 
API capture instructions:
* run the '''x86''' version of API monitor (fedit is a 32-bit application)
* in the "API filter" area on the left, unfold "Graphics and Gaming" and "DirectX Graphics and Gaming", and select "DirectX Input"
* in the near "Monitored Processes" area, click on "Monitor New Process", and select fedit.exe
* in fedit, select the wheel: File>Select Device
* insert the desired effect: Effect>Insert>...
* play the effect: click on the play button
* quit fedit
* save the capture
Make a capture for each of the following effects: constant, spring and damper.

==ffb_x== 
This tool mimics the GIMX interactions with the Direct Input API. 
Download: https://gimx.fr/download/4777c33d5c1b29f40605b3f898b6ed92d9a6eead/ffb_3.zip 
In the following instructions, replace ffb_x with ffb_3. 
Getting the tool text output:
* open a command window (run cmd.exe)
* click on the icon in the top left corner
* click on Properties
* click on the Layout tab
* set the width of the Window Size to 240
* go to the ffb_x.exe directory (cd C:\Users\<username>\Downloads\ffb_x)
* run ffb_x.exe
* select the device matching your wheel
* let the test finish
* right-click on the command window
* click on Select all
* press enter (this will copy the window contents)
* paste in a text editor and save in a file
API capture instructions:
* run the '''x64''' version of API monitor (ffb_x is a 64-bit application)
* in the "API filter" area on the left, unfold "Graphics and Gaming" and "DirectX Graphics and Gaming", and select "DirectX Input"
* in the near "Monitored Processes" area, click on "Monitor New Process", and select ffb_x.exe
* select the device matching your wheel
* let the test finish
* save the capture

==Report== 


Make sure that your report contains all the following details:
* fedit API capture, constant force
* fedit API capture, spring force
* fedit API capture, damper force
* ffb_x command output as text
* ffb_x spring force result OK/KO (move the wheel during the test)
* ffb_x damper force result OK/KO (move the wheel during the test)
* ffb_x API capture

</translate>

Template:PrerequisitesNext

2019-04-18T21:09:21Z

Matlo: /* Hardware requirements */

==Hardware requirements==
# '''Computer''' {{#switch:{{{ostype|}}}
|windows = PC running Windows 7 or later
|linux = #:PC running Ubuntu 18.04 or derivatives such as Linux Mint 19 '''OR''' Raspberry Pi running Raspbian Stretch (experimental)
|}}{{#switch:{{{device|}}}
| Mouse = # '''Mouse''' Forget about using a mouse with anything less than 2000DPI and 250Hz. A gaming mouse with 5000+ DPI and running at 500Hz is highly recommended. Whereas a gaming mouse with more than 1600 DPI doesn't really make a difference on a computer, it's not the case with GIMX. GIMX can decelerate mouse movements so as to counteract the in-game acceleration. A high DPI mouse gives a better linearity (i.e. smoother movements) in this specific case.|}}
{{#switch:{{{connectionType|}}}
|BT = # '''Bluetooth adapter''' Using a bluetooth dongle or an internal bluetooth module, GIMX can disguise itself as a controller to your console. While all bluetooth dongles/modules can't work with GIMX, working dongles are quite common. Check the [[Bluetooth_dongle|compatibility list]]. {{#ifeq:{{{platform|}}}|ps4|
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the PS4.
# '''An AVR USB board such as the Teensy 2.0''' It is required for the bluetooth pairing procedure.|}}
|USB = # '''USB adapter''' This is an adapter that you can either buy from the GIMX shop or build yourself:
#* [https://blog.gimx.fr/product/gimx-adapter/ Buy a ready to use GIMX adapter from the official GIMX shop.]
#* [[DIY_USB_adapter|Build yourself a GIMX adapter]]
#: Forget about using any other USB to USB cable (like file transfer cables, or direct cables), they are not suited to this use.
{{#switch:{{{platform|}}}
| ps4 =
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the console.
| xboxone =
# '''Genuine Xbox One controller''' It is required because GIMX has to authenticate to the console. Controllers with the 3.5mm jack are supported since GIMX 7.13.
| xbox360 =
# '''Genuine wired 360 controller''' It is required because the USB adapter has to authenticate to the console. A wireless 360 controller with a play and charge kit will NOT work.
}}|}}

Template:PrerequisitesNext

2019-04-18T21:08:57Z

Matlo: /* Hardware requirements */

==Hardware requirements==
# '''Computer''' {{#switch:{{{ostype|}}}
|windows = PC running Windows 7 or later
|linux = #:PC running Ubuntu 18.04 or derivatives such as Linux Mint 19 '''OR''' Raspberry Pi running Raspbian Stretch (experimental)
|}}{{#switch:{{{device|}}}
| Mouse = # '''Mouse''' Forget about using a mouse with anything less than 2000DPI and 250Hz. A gaming mouse with 5000+ DPI and running at 500Hz is highly recommended. Whereas a gaming mouse with more than 1600 DPI doesn't really make a difference on a computer, it's not the case with GIMX. GIMX can decelerate mouse movements so as to counteract the in-game acceleration. A high DPI mouse gives a better linearity (i.e. smoother movements) in this specific case.|}}
{{#switch:{{{connectionType|}}}
|BT = # '''Bluetooth adapter''' Using a bluetooth dongle or an internal bluetooth module, GIMX can disguise itself as a controller to your console. While all bluetooth dongles/modules can't work with GIMX, working dongles are quite common. Check the [[Bluetooth_dongle|compatibility list]]. {{#ifeq:{{{platform|}}}|ps4|
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the PS4.
# '''An AVR USB board such as the Teensy 2.0''' It is required for the bluetooth pairing procedure.|}}
|USB = # '''USB adapter''' This is an adapter that you can either buy from the GIMX shop or build yourself:
#* [https://blog.gimx.fr/product/gimx-adapter/ Buy a ready to use GIMX adapter from the official GIMX shop.]
#* [[DIY_USB_adapter|Build yourself a GIMX adapter]]
#: Forget about using any other USB to USB cable (like file transfer cables, or direct cables), they are not suited to this use.
{{#switch:{{{platform|}}}
| ps4 =
# '''Genuine Dualshock 4 controller''' It is required because GIMX has to authenticate to the console.
| xboxone =
# '''Genuine Xbox One controller''' It is required because GIMX has to authenticate to the console. '''Controllers with the 3.5mm jack are supported since GIMX 7.13'''.
| xbox360 =
# '''Genuine wired 360 controller''' It is required because the USB adapter has to authenticate to the console. A wireless 360 controller with a play and charge kit will NOT work.
}}|}}

Mouse Calibration

2019-03-19T19:06:47Z

Matlo:

<languages />
<translate>=Before calibrating the mouse= 


Set the in-game sensitivity to the highest, and set the mouse dpi to the highest value.

'''''Note''''': ''In rare cases some games may require leaving sensitivity at default value due to input bugs introduced introduced at higher speeds.''
=Start calibration= 


<div class="image200px">[https://gimx.fr/wiki/images/a/ae/Mousecalibration.png https://gimx.fr/wiki/images/a/ae/Mousecalibration.png]</div> 
Select Messages>curses in gimx-launcher. Then click on Start.


<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_2.png https://gimx.fr/img/screenshots/Calibration_2.png]</div>


Current mouse calibration values appear in the "Mouse calibration" part of the gui. 
This calibration mode reads values from the loaded configuration. 
If you use multiple mice, it lets you calibrate each mouse independently.

=General instructions= 


Press ctrl+F1 to enable the calibration.
<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_3.png https://gimx.fr/img/screenshots/Calibration_3.png]</div>
Press F1 ... F12 to select the parameter, and use the mouse wheel to change the value.
Press ctrl+F1 to leave the calibration and save the parameters.

=Step-by-step instructions= 

Make sure to perform the steps in order, and don't skip any step or you'll get it wrong.


# Press ctrl+F1. If you use multiple mice, select the mouse to calibrate with the mouse wheel.
# Press F2 and select the profile to calibrate with the mouse wheel (generally, profile 1 is for hip fire, and profile 2 is for aiming down the sight).
# Press F3. If the sight moves, decrease the x dead zone value with the mouse wheel until the sight does not move. Once the sight does not move, increase the x dead zone until the first moving position.
# Press F4. Set the same value as the x dead zone value.
# Press F5. Set the dead zone shape value to "rectangle". If the sight moves, set the dead zone shape to "circle", and let it set to "rectangle" otherwise.
# Press F6 to start a translation test. The sight will move horizontally at different speeds in both left and right directions. A 1:1 translation means the sight should come back near the start point. If it doesn't, use F7 and the mouse wheel to change the x acceleration value. Note that it's not always possible to get a 1:1 translation (this depends on the game).
# Press F8. Set the same value as the x acceleration value.
# Press F9. Adjust the x sensitivity to your liking.
# Press F10 to start a circle test. Adjust the circle radius and speed (F10/F11 + mouse wheel) if necessary. The x/y ratio is properly set if the sight moves in a perfect circle. If it doesn't, adjust the x/y ratio using F12 and the mouse wheel.
# Press ctrl+F1 to save.

Note: if the mouse has low DPI and if the acceleration value is well below 1, your sensitivity will probably be so high that it will result in low movements to be jerky. This is because a mouse movement of 1 dot results in a stick position far away from the dead zone. To compensate this you may subtract the sensitivity from your dead zone. For example with a dead zone of 32 and a sensitivity of 10, set the dead zone to 22. Using smoothing may also help with a low DPI mouse.

=Smoothing= 


The mouse motion can be smoothed using previous mouse motion reports. 
This is useful for lowering jerkiness, especially with a low DPI mouse (below 2000 DPI). 
It is configurable with two parameters: a buffer size and a filter. 
A deeper description of the smoothing technique used by GIMX is available [http://www.flipcode.com/archives/Smooth_Mouse_Filtering.shtml there].

==Note== 


Before adding smoothing, you should have properly set the other parameters.

==Buffer size== 


The buffer size (in the 0..30 range) is the number of mouse motion reports that are used to smooth the mouse motion. 
The smoothing window is the buffer size multiplied by the GIMX update period (inverse of the frequency). 
Examples:
GIMX frequency = 250Hz, buffer size = 10
1000/250 * 10 = 40ms


GIMX frequency = 100Hz, buffer size = 10
1000/100 * 10 = 100ms


Keep in mind that increasing the buffer size makes motion smoother but increases the latency.

==Filter== 


The filter (in the 0..1 range) defines how much the previous motion reports will count in the final motion. 
Value 1 means that the final motion is an average of the buffered motion reports. 
Value 0.5 means that the current motion report counts for 1, the previous one for 0.5, the next oldest one for 0.25 (=0.5x0.5), and so on. 
Value 0 means that only the current motion report counts (resulting in an unfiltered motion). 
So as to preserve a low latency, high filters (1) should only be used with low buffer sizes (2), and high buffer sizes (>10) should only be used with low filters (<0.75).

=Pitfalls= 


This summarizes all common errors you should avoid, and what you should do instead.


* Don't change the mouse dpi to adjust your aiming speed. Always let the mouse dpi setting to the max value. Adjust the GIMX sensitivity instead.
* Don't change the in-game sensitivity to adjust your aiming speed. Always let the in-game sensitivity to the max value. Adjust the GIMX sensitivity instead.
* Don't change the mouse parameters of the OS (Linux/Windows) to adjust your aiming speed. GIMX uses raw (unmodified) events from the mouse!
* Prefer editing the sensitivity with the calibration mode. The calibration mode keeps the x/y ratio.
</translate>

Mouse Calibration

2019-03-19T19:05:40Z

Matlo:

<languages />
<translate>=Before calibrating the mouse= 


Set the in-game sensitivity to the highest, and set the mouse dpi to the highest value.

'''''Note''''': ''In rare cases some games may require leaving sensitivity at default value due to input bugs introduced introduced at higher speeds.''
=Start calibration= 


<div class="image200px">[https://gimx.fr/wiki/images/a/ae/Mousecalibration.png https://gimx.fr/wiki/images/a/ae/Mousecalibration.png]</div> 
Select Messages>curses in gimx-launcher. Then click on Start.


<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_2.png https://gimx.fr/img/screenshots/Calibration_2.png]</div>


Current mouse calibration values appear in the "Mouse calibration" part of the gui. 
This calibration mode reads values from the loaded configuration. 
If you use multiple mice, it lets you calibrate each mouse independently.

=General instructions= 


Press ctrl+F1 to enable the calibration.
<div class="image200px">[https://gimx.fr/img/screenshots/Calibration_3.png https://gimx.fr/img/screenshots/Calibration_3.png]</div>
Press F1 ... F12 to select the parameter, and use the mouse wheel to change the value.
Press ctrl+F1 to leave the calibration and save the parameters.

=Step-by-step instructions= 

Make sure to perform the steps '''in order''', and '''don't skip any step''' or you'll get it wrong.


# Press ctrl+F1. If you use multiple mice, select the mouse to calibrate with the mouse wheel.
# Press F2 and select the profile to calibrate with the mouse wheel (generally, profile 1 is for hip fire, and profile 2 is for aiming down the sight).
# Press F3. If the sight moves, decrease the x dead zone value with the mouse wheel until the sight does not move. Once the sight does not move, increase the x dead zone until the first moving position.
# Press F4. Set the same value as the x dead zone value.
# Press F5. Set the dead zone shape value to "rectangle". If the sight moves, set the dead zone shape to "circle", and let it set to "rectangle" otherwise.
# Press F6 to start a translation test. The sight will move horizontally at different speeds in both left and right directions. A 1:1 translation means the sight should come back near the start point. If it doesn't, use F7 and the mouse wheel to change the x acceleration value. Note that it's not always possible to get a 1:1 translation (this depends on the game).
# Press F8. Set the same value as the x acceleration value.
# Press F9. Adjust the x sensitivity to your liking.
# Press F10 to start a circle test. Adjust the circle radius and speed (F10/F11 + mouse wheel) if necessary. The x/y ratio is properly set if the sight moves in a perfect circle. If it doesn't, adjust the x/y ratio using F12 and the mouse wheel.
# Press ctrl+F1 to save.

Note: if the mouse has low DPI and if the acceleration value is well below 1, your sensitivity will probably be so high that it will result in low movements to be jerky. This is because a mouse movement of 1 dot results in a stick position far away from the dead zone. To compensate this you may subtract the sensitivity from your dead zone. For example with a dead zone of 32 and a sensitivity of 10, set the dead zone to 22. Using smoothing may also help with a low DPI mouse.

=Smoothing= 


The mouse motion can be smoothed using previous mouse motion reports. 
This is useful for lowering jerkiness, especially with a low DPI mouse (below 2000 DPI). 
It is configurable with two parameters: a buffer size and a filter. 
A deeper description of the smoothing technique used by GIMX is available [http://www.flipcode.com/archives/Smooth_Mouse_Filtering.shtml there].

==Note== 


Before adding smoothing, you should have properly set the other parameters.

==Buffer size== 


The buffer size (in the 0..30 range) is the number of mouse motion reports that are used to smooth the mouse motion. 
The smoothing window is the buffer size multiplied by the GIMX update period (inverse of the frequency). 
Examples:
GIMX frequency = 250Hz, buffer size = 10
1000/250 * 10 = 40ms


GIMX frequency = 100Hz, buffer size = 10
1000/100 * 10 = 100ms


Keep in mind that increasing the buffer size makes motion smoother but increases the latency.

==Filter== 


The filter (in the 0..1 range) defines how much the previous motion reports will count in the final motion. 
Value 1 means that the final motion is an average of the buffered motion reports. 
Value 0.5 means that the current motion report counts for 1, the previous one for 0.5, the next oldest one for 0.25 (=0.5x0.5), and so on. 
Value 0 means that only the current motion report counts (resulting in an unfiltered motion). 
So as to preserve a low latency, high filters (1) should only be used with low buffer sizes (2), and high buffer sizes (>10) should only be used with low filters (<0.75).

=Pitfalls= 


This summarizes all common errors you should avoid, and what you should do instead.


* Don't change the mouse dpi to adjust your aiming speed. Always let the mouse dpi setting to the max value. Adjust the GIMX sensitivity instead.
* Don't change the in-game sensitivity to adjust your aiming speed. Always let the in-game sensitivity to the max value. Adjust the GIMX sensitivity instead.
* Don't change the mouse parameters of the OS (Linux/Windows) to adjust your aiming speed. GIMX uses raw (unmodified) events from the mouse!
* Prefer editing the sensitivity with the calibration mode. The calibration mode keeps the x/y ratio.
</translate>

Macros

2019-03-17T19:59:46Z

Matlo:

<languages />
<translate>
It's possible to configure keyboard/mouse/joystick macros: a key or button press can trigger a series of keyboard/mouse/joystick events, with timing conditions.

==File format==

File format is plain text UTF-8. Recommended text editors are [https://notepad-plus-plus.org/ Notepad++] on Windows and gedit on Ubuntu.

==Directory== 


To open the directory where to put macro files, open gimx-launcher and click on "File > Open Macro Directory".


GIMX 1.12 and older
<div class="mw-collapsible mw-collapsed">
* Ubuntu: the ~/.emuclient/macros directory. ~ is the home directory, and .emuclient folder is hidden (in the file manager, press ctrl+h to display hidden folders).
* Windows: the C:\Users\<username>\AppData\Roaming\emuclient\macros directory.</div>


GIMX 0.51 and older
<div class="mw-collapsible mw-collapsed">
* Windows 32bits: the C:\Program Files\GIMX\macros directory.
* Windows 64bits: the C:\Program Files (x86)\GIMX\macros directory.</div>

==Syntax== 


<pre>MACRO <DEVICE EVENT> <ID> <RANGE>
<DEVICE EVENT> <ID> <VALUE>
DELAY <MS>
#<COMMENT></pre>


*<DEVICE EVENT>: KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP, MAXIS, JAXIS
*<ID>: the event id (case sensitive) as displayed in gimx-config
*<VALUE>: the axis value (only for MAXIS and JAXIS)
*<RANGE>: the axis range (only for MAXIS and JAXIS); the syntax is [min,max] with min and max in [-32768,32767]; example: [8192,16384]
*<MS>: integer value in milliseconds
*<COMMENT>: a comment, not interpreted ('#' is the first character of the line)

==Commands== 


* KEYDOWN: keyboard key pressed
* KEYUP: keyboard key released
* KEY: KEYDOWN + DELAY 50 + KEYUP


* MBUTTONDOWN: mouse button pressed
* MBUTTONUP: mouse button released
* MBUTTON: MBUTTONDOWN + DELAY 50 + MBUTTONUP


* JBUTTONDOWN: joystick button pressed
* JBUTTONUP: joystick button released
* JBUTTON: JBUTTONDOWN + DELAY 50 + JBUTTONUP


* DELAY: delay in milliseconds


* MAXIS: mouse axis moved; ID: 0 for x axis, and 1 for y axis; VALUE: positive values for right and down


* JAXIS: joystick axis moved; ID: the axis id as displayed in gimx-config; VALUE: in [-32768 .. 32767] for centered axes, and in [0 .. 32767] for non-centered axes

==Macro activation== 


This section is only applicable since GIMX 1.00.


* '''It is possible to specify the macro files to be read for each configuration file.'''
This can be configured in a file named "configs.txt", located in the macros directory. 
Example:
<pre>#If config1.xml is loaded, macro1.txt is read.
config1.xml/macro1.txt
#If config1.xml is loaded, macro2.txt is read.
config1.xml/macro2.txt
#If config2.xml is loaded, macro2.txt is read.
config2.xml/macro2.txt</pre>
Lines beginning with a # are not interpreted. 
Since GIMX 4.0 the separator is a slash so as to allow using file names containing spaces. 


* '''It is also possible to define activation triggers within the macro definition.'''
The syntax is:
<pre>TRIGGER <event></pre>
Example:
<pre>MACRO F1
#content


MACRO F2
TRIGGER F5
#content


MACRO F3
TRIGGER F6
#content


MACRO F4
TRIGGER F5
#content</pre>
With GIMX 1.12 and earlier, the above example works the following way: 
F1 remains active all the time as there is no trigger specified. 
F2 and F4 are default active. If F6 is pressed, F3 becomes active, F2 and F4 become inactive. 
With GIMX 2.00: 
Macros with a trigger are default inactive. To make a macro with trigger default active, add a line containing "INIT ON" after the "TRIGGER <event>" line. 
Macros with a trigger can work with a toggle mode, which allows to activate and deactivate a macro autonomously: activating a togglable macro has no impact on other macros, and activating another macro has no impact on a togglable macro. This can be configured adding a line containing "TOGGLE YES" after the "TRIGGER <event>" line. 
Example:
<pre>MACRO F1
TRIGGER 1
INIT ON
TOGGLE YES
#content</pre>

==Notes== 

===Delay precision=== 


The delay precision depends on the controller update period:
* ds3/bluetooth = 11.25ms
* ds3/usb = 10ms
* ds4/bluetooth = 10ms
* ds4/usb = 10ms
* 360 pad = 8ms
* XOne pad = 4ms
If you specify a delay that is not a multiple of the precision, the resulting delay will be the lowest multiple of the precision higher than the specified delay. 
For example, if the precision is 11.25ms and the delay is 12ms, the resulting delay will be 22.50ms (=2*11.25ms).

===Macro loop=== 


To make a macro loop, just add a matching KEYDOWN, MBUTTONDOWN or JBUTTONDOWN command at the end of the macro. 
Example:
<pre>MACRO MBUTTONDOWN BUTTON_LEFT
#content
MBUTTONDOWN BUTTON_LEFT</pre>


The macro is triggered by pressing 'BUTTON_LEFT'. 
The last command of the macro restarts the macro, creating a loop. 
To stop a macro loop, just press the trigger again. The macro is stopped immediately, and the state of the controller is unchanged.

===Multiple keyboards/mice/joysticks=== 


In case multiple keyboards or mice or joysticks are used, it's not possible to specify the device for which events are generated. 
Events are generated for the first keyboard/mouse/joystick found in the configuration.

==Examples== 

===Rapid fire macro=== 


<pre>MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN p
#Set delay no less than the maximum rate of fire
#10 rounds per second (600 rpm)
DELAY 100
KEYUP p
#~Do not set delay after keyup or it will negatively impact automatic weapons
MBUTTONDOWN BUTTON_LEFT

MACRO MBUTTONUP BUTTON_LEFT
MBUTTONDOWN BUTTON_LEFT
#Sometimes the fire key can be stuck down after the macro ends this releases it after the macro has been terminated
KEYUP p</pre>


In gimx-config, bind 'p' to r1 in both hip fire and ADS profiles (profiles 1 and 2). 
DO NOT bind 'BUTTON_LEFT' to r1 in both hip fire and ADS profiles.


The macro is triggered by pressing the left mouse button. 
The last command of the first macro restarts the macro, creating a loop. 
Upon the release of the left mouse button the second macro ends the loop of the first macro.

===Recoil macro=== 


<pre>MACRO KEYDOWN o
MAXIS 1 25
KEYDOWN o


MACRO MBUTTONDOWN BUTTON_LEFT
KEYDOWN o


MACRO MBUTTONUP BUTTON_LEFT
KEYDOWN o</pre>


Change '25' with the value that cancels the recoil.

===Custom button press duration===

Using gimx-config, replace your current binding with an unused key, for example 'p', and define the following macro:
<pre>MACRO JBUTTONDOWN X
KEYDOWN p
DELAY Y
KEYUP p</pre>
Replace X with the button id, and Y with the delay value in ms (should be at least 1 report period = 1 / frequency).

</translate>

Development on Windows

2019-03-17T13:09:09Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

On 32-bit Windows run mingw32.exe instead.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-03-17T13:08:44Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe and type:'''


cd GIMX-build/windows
./install.sh

On 32-bit Windows run mingw32.exe instead.

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-03-17T13:07:40Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''Run msys2.exe and type:'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-03-17T13:04:29Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''This has to be run into msys2.exe.'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-03-17T13:04:19Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''This has to be run into msys2.exe.'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


'''Run mingw64.exe (or mingw32.exe if you want to build 32bit binaries) and type:'''


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-03-17T13:03:23Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 

'''This has to be run into msys2.exe.'''


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

RPi

2019-03-16T09:30:58Z

Matlo:

<languages />
<translate>

'''Warning: RPi support should be considered as experimental. The USB controller has been unstable since the first version. Be prepared to face issues if you try GIMX on the RPi.'''

GIMX can run on many Linux targets, and the [http://www.raspberrypi.org/ the Raspberry Pi] is one of them!

== Setup using pre-made image == 


The simplest way to set up GIMX on a Raspberry Pi is by flashing a pre-made image. See forum user steel_3d's instructions on getting up and running: [http://www.steve-marton.com/gimx/?p=462 Build your own Plug n Play GIMX emulator using Raspberry Pi]

== Hardware considerations == 


Use a USB HUB only if there are no ports available on the RPi. 
It is highly recommended to use a HUB with an external power supply.

== USB adapter using the on-board UART interface == 

=== Hardware requirements === 


The on-board UART runs at 0V/3.3V levels, and the AVR USB board has to run at 5V to operate at 16MHz (running at 3.3V would only allow to operate at 8MHz). 
Connecting the RPi and the AVR USB board directly may damage the hardware! 
One cheap solution is to use a voltage divider: 
* Connect both GNDs
* It's safe to connect the TXD pin of the RPi to the Rx pin of the AVR USB board (the GIMX firmwares configure the Rx pin as an input)
* To connect the Tx pin of the AVR USB board to the RXD pin of the RPi, you'll need to convert the voltage level from 0..5V to 0..3.3V. 
This can be done with a simple resistive divider:
<div class="image200px">[https://gimx.fr/img/wiki/Resistive_divider.png https://gimx.fr/img/wiki/Resistive_divider.png]</div>
Vin is the Tx pin of the AVR USB board, Vout is the RXD pin of the RPi, R1=2.2kΩ , R2=3.3kΩ
* Do not connect any other pin!

=== Sotware adjustments === 


By default, the RPi UART is configured as a serial console. 
Disable this serial console using raspi-config:
<pre>
sudo raspi-config
</pre>
Then select:
<pre>
"Advanced Options", "Serial", "No", "Finish"
</pre>
The default configuration does not allow high baudrates. 
Enable high baudrates editing /boot/config.txt:
<pre>
sudo nano /boot/config.txt
</pre>
Add the following line at the end of the file:
<pre>
init_uart_clock=8000000
</pre>
Reboot to apply the changes:
<pre>
sudo reboot
</pre>

== GIMX installation == 
<pre>wget https://gimx.fr/download/gimx-raspbian -O gimx.deb
sudo dpkg -i gimx.deb
sudo apt-get update && sudo apt-get -f install</pre>


If you get a "Dependency is not satisfiable: ..." error message, upgrade Raspbian:
<pre>sudo apt-get update && sudo apt-get upgrade
sudo apt-get -f install</pre>

== Stop/disable triggerhappy service == 
[https://github.com/wertarbyte/triggerhappy/blob/master/README Triggerhappy] is a daemon that opens every input device for reading, and that consumes a few percent of the CPU time.


It seems a good idea to stop it while running GIMX.


To stop triggerhappy:
sudo service triggerhappy stop
To disable triggerhappy:
sudo update-rc.d triggerhappy disable

== Run GIMX == 
Read the [[Quick_Start|Quick start page]] to learn how to run GIMX through the GUI. 

A good idea is to run GIMX directly from a terminal, without starting a graphical session, which can be done over the network, using a ssh client, or you can [[#Autostart GIMX at boot without GUI]] 

Ideally, GIMX should be launched without using the Ethernet port (because it is connected on the USB bus). However, this doesn't seem to cause any issues generally. 

More details on command line options on [[Command_line|this page]]. 

The GUI will help you download the config xmls. If you never run the GUI, you MUST grab the Linux config xmls from here: https://github.com/matlo/GIMX-configurations/tree/master/Linux The Windows xmls are NOT compatible! 

== Autostart GIMX at boot without GUI == 
Simply create a file /etc/systemd/system/gimx.service (as root):

<pre>
sudo nano /etc/systemd/system/gimx.service
</pre>

With the following contents:


<pre>
[Unit]
Description=GIMX
After=syslog.target network.target


[Service]
User=pi
Type=simple
# Replace /dev/ttyUSB0 with /dev/ttyAMA0 when using the on-board UART interface
ExecStart=/usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
Restart=always
RestartSec=5


[Install]
WantedBy=multi-user.target
</pre>


Replace ttyUSB0 with your device (/dev/ttyAMA0 when using the on-board UART interface) and LogitechDrivingForceGT_G29.xml with your mapping file (which should be available in the pi home directory as /home/pi/.gimx/config/LogitechDrivingForceGT_G29.xml)


Run <pre>sudo systemctl daemon-reload</pre> to notify systemd about the new file and <pre>sudo systemctl enable gimx && sudo systemctl start gimx</pre> to enable the gimx service start at boot and start it in the same line.

== Notify when GIMX is running using a led == 
In order to have a proper confirmation about if the gimx service is up and running, you can add a simple python script that turns a led on if the gimx service is running.


The file will be located at /home/pi/blink.py:

<pre>sudo nano blink.py</pre>

With the following contents:


<pre>
#!/usr/bin/python
import os
import time
import RPi.GPIO as GPIO


led = 23
button = 18
GPIO.setmode(GPIO.BCM)
GPIO.setup(led, GPIO.OUT)
GPIO.setup(button, GPIO.IN, pull_up_down = GPIO.PUD_UP)


def Shutdown(channel):
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
time.sleep(0.2)
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
os.system("sudo shutdown -h now")


GPIO.add_event_detect(18, GPIO.FALLING, callback = Shutdown, bouncetime = 2000)


while True:
found = False
time.sleep(5)
pids = [pid for pid in os.listdir('/proc') if pid.isdigit()]
for pid in pids:
try:
cmd = open(os.path.join('/proc', pid, 'cmdline'), 'rb').read()
if "gimx" in cmd:
found = True
except IOError: # proc has already terminated
continue
if found == True:
GPIO.output(led, True)
else:
GPIO.output(led, False)
</pre>


As a bonus, you can add a button so when it is pressed, there is a little blink effect, and the pi is shutted down.


<div class="image200px">[https://gimx.fr/img/wiki/PiButtonLed.png https://gimx.fr/img/wiki/PiButtonLed.png]</div>


To start at boot, simply add it to the pi user crontab (crontab -e) as <pre>@reboot python /home/pi/blink.py &</pre>

== Powering on AVR and RPi simultaneously using the on-board UART interface == 
In case you want to power up AVR (Tested on Pro Micro ATmega32u4) and RPi at once (i.e. using PS4 USB port and a USB Y Splitter) using the on-board UART interface, you will need the adjust shown below in order to reset the AVR board from RPi once started.


It is planned to solve this issue on GIMX 8 version [https://github.com/matlo/GIMX/issues/426]


More details on support forum thread [https://gimx.fr/forum/viewtopic.php?f=5&t=1672]


'''Physically'''
* RPi's PIN40 / GPIO21 connected to ATmega32u4 RST pin directly. (Any RPi GPIO pin should works)


'''Logically'''
* New bash script created /home/pi/resetArduino.sh with content shown below:
<pre>
#!/bin/bash

echo 21 > /sys/class/gpio/export
sleep 1
echo out > /sys/class/gpio/gpio21/direction
sleep 1
echo 1 > /sys/class/gpio/gpio21/value
sleep 1
echo 0 > /sys/class/gpio/gpio21/value
sleep 1
echo 1 > /sys/class/gpio/gpio21/value

exit 0
</pre>
* Grant execution permissions
<pre>chmod +x /home/pi/resetArduino.sh</pre>
* Add the new script to boot sequence (like we do with blink.py program)
<pre>
pi@raspberrypi:~ $ crontab -l
@reboot /home/pi/resetArduino.sh && python /home/pi/blink.py &
</pre>

Using this configuration, GIMX is able to start correctly on its first attempt when RPi and ATmega32u4 are powered on from PS4 simultaneously using GPIO instead of CP2102 USB UART.

</translate>

Gimx-config

2019-03-08T14:20:43Z

Matlo:

<languages />
<translate>

'''gimx-config''' is the general purpose config editor, and the most complete of the [[Config_Editors|editors]]. It can edit configs produced by other editors.

==gimx-config== 

===Start=== 
[[File:gimx-config.png|none|thumb|600px]]

===Button tab=== 
Bind controls (button or axis, from any device) to controller buttons (cross, select, etc.).
[[File:gimx-config-buttons.png|none|thumb|600px]]

===Axis tab=== 
Bind controls (button or axis, from any device) to controller axes (left stick x, left stick y, pressure sensitive buttons, etc.).
[[File:gimx-config-axis.png|none|thumb|600px]]

===Overall tab=== 
====profile trigger====
Profile trigger is the button that activates the profile.
[[File:gimx-config-overall.png|none|thumb|600px]]
:The profile activation can be delayed (for ex. 100ms). 
:If the switch back checkbox is enabled, GIMX will switch back to the previous profile when the button is released. 
:Typical use cases that allow to tweak the ADS mouse parameters in FPS games:
:# second profile with right mouse button as trigger, and switch back enabled; right mouse button is bind to the ADS button (for ex. l1) in both profiles 
:# first and second profiles with right mouse button as trigger, and switch back disabled; right mouse button is bind to the ADS button (for ex. l1) in the first profile only ("toggle mode") 
====mouse options====
[[File:gimx-config-mouseoptions.png|none|thumb|600px]]
[[Mouse_Calibration#Smoothing|Mouse smoothing]] can be configured there if needed. 
The mouse mode can be either "aiming" or "driving/flying".
====axis intensities====
[[File:gimx-config-axisintensity.png|none|thumb|600px]]
:This can be used to have a precise control over a stick with buttons, or over a pressure-sensitive button with buttons. 
:Typical use case for FPS games: 
:* WASD is bind to the left stick 
:* mouse wheel down and up resp. decrease and increase the left stick intensity 
:* dead zone = 20 (lowest stick position along each axis) 
:* steps = 3 (number of stick positions along each axis)

===Controllers=== 
This part is only applicable for bluetooth. 
Up to 7 sixaxis controllers, each using a different bluetooth dongle, can be emulated by GIMX. 
Each controller can be configured independently.


[[File:gimx-config-controller.png|none|thumb|600px]]

===Profiles=== 
There are up to 8 profiles per controller. 
For example, it's possible to define a profile for aiming: copy-paste the profile #1 to profile #2, define the right mouse click as profile #2 trigger with switch back (Overall tab), and adjust the mouse sensitivity & acceleration (Axis tab).


[[File:gimx-config-profile.png|none|thumb|600px]]

===Config conversion=== 
Items of the "Edit" menu that allow to convert a configuration:


[[File:gimx-config-edit.png|none|thumb|600px]]


* The "Replace Mouse" item allows to change the mouse name and id. 
* The "Convert mouse sensitivity" item allows to adjust the mouse sensitivity according to source/destination DPI values. 
* The "Replace Keyboard" item allows to change the keyboard name and id.

===Advanced=== 


* Multiple mice and keyboards: check this box if you want two mice or two keyboards to be independent.
:Use case: use the mouse wheel of a keypad (such as the n52te) independently from the mouse wheel.
* Link controls: updates bindings in all controller profiles.
:Use case: a same binding is defined in profiles 1 & 2; modify the binding in profile 1: the binding in profile 2 is updated.
* Auto-bind controls: remap bindings according to the labels; the configuration to modify and the reference configuration should have labels configured (column 'Label' in Button and Axis tabs).

</translate>

Development on Windows

2019-02-25T21:35:06Z

Matlo: /* Building project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2 (C:\msys64), you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-02-25T21:34:43Z

Matlo: /* Building project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
** for example, if you used default installation folder for msys2, you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-02-25T21:34:03Z

Matlo: /* Building project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails at finding make or gcc :
* in the "Project Explorer" view, right-click on the project, and click on "Properties"
* unfold "C/C++ Build", and click on "Environment"
* make sure msys2 and mingw64 bin folders are present in the PATH variable
* if you used default installation folder for msys2, you should have this at the end of the PATH variable: C:\msys64\usr\bin;C:\msys64\mingw64\bin

</translate>

Development on Windows

2019-02-23T16:38:50Z

Matlo: /* Building project= */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

===Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails, make sure that the "Linux Tools Path" matches your Msys2/Mingw64 installation. In the "Project Explorer" view, right-click on the project, and click on "Properties". Click on "Linux Tools Path" and check configuration.

</translate>

Development on Windows

2019-02-23T16:10:55Z

Matlo:

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe. 
Use default workspace folder. 

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

==Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails, make sure that the "Linux Tools Path" matches your Msys2/Mingw64 installation. In the "Project Explorer" view, right-click on the project, and click on "Properties". Click on "Linux Tools Path" and check check configuration.

</translate>

Development on Windows

2019-02-23T16:00:29Z

Matlo: /* Importing project */

<languages />
<translate>
This wiki explains how to install a compilation environment (based on Msys2/mingw64) to build GIMX. 
It also explains how to install Eclipse CDT and perform a checkout. 
Unless otherwise specified, perform a default installation (default directories, etc).

==Msys2/MinGW64== 


Download and install [https://msys2.github.io/ Msys2]. 
Make sure to follow the instructions from the Msys2 wiki.


If you are running a 32-bit Windows, install the i686 version. 
If you are running a 64-bit Windows, install the x84_64 version.

==Checkout installation and build tools== 


pacman --noconfirm -S git
git clone <nowiki>https://github.com/matlo/GIMX-build.git</nowiki>

==Development tools== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./install.sh

==Inno setup== 


Download and install [http://www.jrsoftware.org/isdl.php Inno setup].

==Automated command-line build== 


Run mingwXY.exe (XY=32 or 64) and type:


cd GIMX-build/windows
./build.sh


All binaries are copied into <path to msys>\home\<username>\GIMX\setup, e.g. C:\msys32\home\matlo\GIMX\setup. 
A setup file is also created.

==Eclipse IDE== 


This part is only useful in case you intend to modify the source code. If you only want to build GIMX, you can skip it. 
Eclipse is an IDE that can be stacked onto the Msys2/MinGW64 compilation toolchain. 
Be sure to have a [http://www.oracle.com/technetwork/java/javase/downloads/index.html java JRE] installed on your system. 
Download [https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-12/R/eclipse-cpp-2018-12-R-win32-x86_64.zip Eclipse CDT 2018-12]. Unzip it to wherever you want. 
Run eclipse.exe.

===Cloning project===

Copy the following URL: <nowiki>https://github.com/matlo/GIMX.git</nowiki> 
Click on "Window > Show View > Other...", select "Git repositories", and click on "Open". 
Type Ctrl+V. A "Clone Git Repository" window should appear. 
First step defines the repository to import. Click on "Next". 
Second step defines the branch selection. Select the branches you are interested in. "master" branch contains latest stable source code. Click on "Next". 
Third step defines local destination. A standard value for "Directory" is "C:\Users\<username>\git\GIMX". Make sure to select "Clone submodules". Click on "Finish".

===Importing project===

In the "Git Repositories" view, right click on the cloned git repository, and click on "Import Projects...". Select the project folder (for example "GIMX") and click on "Finish". 

==Building project===

In the "Project Explorer" view, right-click on the project, and click on "Build Project". 
If the build fails, make sure that the "Linux Tools Path" matches your Msys2/Mingw64 installation. In the "Project Explorer" view, right-click on the project, and click on "Properties". Click on "Linux Tools Path" and check check configuration.

</translate>

Development on Windows

2019-02-23T15:52:08Z

Matlo: /* Cloning project */

Development on Windows

2019-02-23T15:51:51Z

Matlo: /* Cloning project */

Development on Windows

2019-02-23T15:51:20Z

Matlo: /* Cloning project */