This page is a work in progress
MCE files are coded in xml. This language consists of elements delimited by tags and described by child elements.
Here i will describe an example MCE file that I am currently making for ArmA 2 Free. The file is cut in sections and the complete file will be available at the end of this page (when I am done with it). <hide>
Sixense recommends to use some version of Microsoft Visual Studio that handles xml (express versions are free). This is a good idea since Visual Studio handles autocompletion, making MCE creation a lot easier!
<?xml version="1.0" encoding="UTF-8"?> <game_list xmlns="http://www.sixense.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sixense.com http://www.sixense.com/sixense_mce.xsd">
Note that the <game_list> tag has to be closed, this line will be at the end of our file:
Game Description Edit
Game descriptions are placed inside a game_list, this is where you will put all your bindings for one game.
Configuration Filtering Edit
- <exe_name>: name of the focused process that activates this configuration
- <steam_appid>: a filter made for steam apps
- <full_name>: the name to display in Motion Creator 2 list of configurations (not a filter)
- <window_title_match>: not used in this example, can be used to filter games that share a same process name (think of all Source Engine games that use hl.exe)
<game> <version>1.0</version> <requires_schema_version>1.0</requires_schema_version> <exe_name>ArmA2Free.exe</exe_name> <steam_appid>33900</steam_appid> <full_name>*Arma 2: Free</full_name> <game_type>fps</game_type> <game_mode>hybrid</game_mode>
Once again, we will need to close <game>: