Macros/en - Revision history

FuzzyBot: Updating to match new version of source page

2015-09-30T13:06:37Z

Updating to match new version of source page

Show changes

FuzzyBot: Updating to match new version of source page

2014-09-03T08:33:07Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-08-23T09:13:49Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-07-16T16:00:08Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-07-16T15:47:33Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-07-14T19:44:18Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-07-08T20:26:32Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-03-08T08:31:35Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-02-06T13:46:06Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-07-12T07:56:23Z

Updating to match new version of source page

@@ Line 5: / Line 5: @@
 Macros have to be defined in files saved into:
 * 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.
@@ Line 46: / Line 50: @@
 * JAXIS: joystick axis moved
-ID: as in gimx-config<br />
+ID: the axis id as displayed in gimx-config<br />
-VALUE: in [-32768 .. 32767]
+VALUE: in [-32768 .. 32767] for centered axes, and in [0 .. 32767] for non-centered axes
 ==Example1: rapid_fire.txt==
@@ Line 67: / Line 71: @@
 ==Example2: recoil.txt==
-  MACRO KEYDOWN p
+  MACRO KEYDOWN o
   MAXIS 1 25
-  KEYDOWN p
+  KEYDOWN o
   MACRO MBUTTONDOWN BUTTON_LEFT
-  KEYDOWN p
+  KEYDOWN o
   MACRO MBUTTONUP BUTTON_LEFT
-  KEYDOWN p
+  KEYDOWN o
 ==Macro activation==
@@ Line 110: / Line 116: @@
   TRIGGER F5
   #content
-F1 remains active all the time as there is no trigger specified.
+With GIMX 1.12 and earlier, the above example works the following way:<br />
-F2 and F4 are default active. If F6 is pressed, F3 becomes active, F2 and F4 become inactive.
+F1 remains active all the time as there is no trigger specified.<br />
 ==Notes==
@@ Line 117: / Line 133: @@
 ===Delay precision===
-The delay precision depends on the controller update period.<br />
+The delay precision depends on the controller update period:
-Using bluetooth, the precision is 10ms. Using a USB adapter at 250Hz, the precision is 4ms.<br />
+* sixaxis/bluetooth = 11.25ms
 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.<br />
-For example, if the precision is 10ms and the delay is 11ms, the resulting delay will be 20ms.
+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===

@@ Line 98: / Line 98: @@
   MACRO F1
   #content
   MACRO F2
   TRIGGER F5
   #content
   MACRO F3
   TRIGGER F6
   #content
   MACRO F4
   TRIGGER F5

@@ Line 15: / Line 15: @@
   MACRO <DEVICE EVENT> <ID>
-  <DEVICE EVENT> <ID>
+  <DEVICE EVENT> <ID> <VALUE>
   DELAY <MS>
   #<COMMENT>
-  <DEVICE EVENT>: KEY, KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP
+  <DEVICE EVENT>: KEY, KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP, MAXIS, JAXIS
   <ID>: the event id (case sensitive) as displayed in gimx-config
   <MS>: integer value in milliseconds
   <COMMENT>: a comment, not interpreted
@@ Line 39: / Line 40: @@
 * DELAY: delay in milliseconds
 ==Example1: rapid_fire.txt==

@@ Line 40: / Line 40: @@
 * DELAY: delay in milliseconds
-==Example: rapid_fire.txt==
+==Example1: rapid_fire.txt==
   MACRO MBUTTONDOWN BUTTON_LEFT
@@ Line 55: / Line 55: @@
 'p' is bind to r1 in both hip fire and ADS profiles.<br />
 'BUTTON_LEFT' is NOT bind to r1 in both hip fire and ADS profiles.
 ==Macro activation==

@@ Line 63: / Line 63: @@
 This can be configured in a file named "configs.txt", located in the macros directory.<br />
 Example:
-  #If config1.xml is loaded, macros1.txt is read.
+  #If config1.xml is loaded, macro1.txt is read.
   config1.xml macro1.txt
-  #If config1.xml is loaded, macros2.txt is read.
+  #If config1.xml is loaded, macro2.txt is read.
   config1.xml macro2.txt
-  #If config2.xml is loaded, macros2.txt is read.
+  #If config2.xml is loaded, macro2.txt is read.
   config2.xml macro2.txt
 Lines beginning with a # are not interpreted.<br />

@@ Line 19: / Line 19: @@
   #<COMMENT>
-  <DEVICE EVENT>: KEYDOWN, KEYUP, MBUTTONDOWN, MBUTTONUP, JBUTTONDOWN, JBUTTONUP
+  <DEVICE EVENT>: KEY, KEYDOWN, KEYUP, MBUTTON, MBUTTONDOWN, MBUTTONUP, JBUTTON, JBUTTONDOWN, JBUTTONUP
   <ID>: the event id (case sensitive) as displayed in gimx-config
   <MS>: integer value in milliseconds
@@ Line 32: / Line 32: @@
 * MBUTTONDOWN: mouse button pressed
 * MBUTTONUP: mouse button released
 * JBUTTONDOWN: joystick button pressed
 * JBUTTONUP: joystick button released
 * DELAY: delay in milliseconds

← Older revision		Revision as of 13:46, 6 February 2013
Line 52:		Line 52:

	==Notes==		==Notes==
		+
		+	===Delay precision===
		+
		+	The delay precision depends on the controller update period.<br />
		+	Using bluetooth, the precision is 10ms. Using a USB adapter at 250Hz, the precision is 4ms.<br />
		+	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.<br />
		+	For example, if the precision is 10ms and the delay is 11ms, the resulting delay will be 20ms.

	===Macro loop===		===Macro loop===

@@ Line 48: / Line 48: @@
   MBUTTONDOWN BUTTON_LEFT
-'p' is bind to r1 in both hip fire and ADS profiles.<br/>
+'p' is bind to r1 in both hip fire and ADS profiles.<br />
 'BUTTON_LEFT' is NOT bind to r1 in both hip fire and ADS profiles.
@@ Line 55: / Line 55: @@
 ===Macro loop===
-To make a macro loop, just add a KEYDOWN or MBUTTONDOWN or JBUTTONDOWN command at the end of the macro definition.<br/>
+To make a macro loop, just add a KEYDOWN or MBUTTONDOWN or JBUTTONDOWN command at the end of the macro definition.<br />
 Example:
   MACRO MBUTTONDOWN BUTTON_LEFT
@@ Line 63: / Line 63: @@
   DELAY 50
   MBUTTONDOWN BUTTON_LEFT
-The macro is triggered by pressing 'BUTTON_LEFT'.<br/>
+The macro is triggered by pressing 'BUTTON_LEFT'.<br />
-The last command of the macro restarts the macro, creating a loop.<br/>
+The last command of the macro restarts the macro, creating a loop.<br />
 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.<br/>
+In case multiple keyboards or mice or joysticks are used, it's not possible to specify the device for which events are generated.<br />
 Events are generated for the first keyboard/mouse/joystick found in the configuration.