Skip to content

Commit

Permalink
Read control bindings from Odyssey file
Browse files Browse the repository at this point in the history
  • Loading branch information
andrewdsmith committed May 20, 2021
1 parent 76c4aa7 commit f77de35
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 10 deletions.
1 change: 1 addition & 0 deletions Changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

## Version 1.6

- Reads control bindings from Odyssey `Custom.4.0.binds` file
- Reads configuration from `edxlc.toml` file in the current working directory
- Writes default `edxlc.toml` configuration file if missing
- Shows alert state for landing gear if not deployed while docking
Expand Down
17 changes: 8 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Elite Dangerous X52 Pro LED Control - EDXLC

The aim of this small companion app is to automatically control the button LEDs
on your Saitek X52 Pro joystick using the state of your ship or SRV in the game
Elite Dangerous.
This small companion app to the game Elite Dangerous automatically controls the
button LEDs on your Saitek X52 Pro joystick so that they reflect the current
state of your ship or SRV in the game.

Currently the app detects if you activate any of the following:

Expand All @@ -20,18 +20,17 @@ For example when mass-locked, all buttons relating to hyperdrive and supercruise
turn red.

Buttons that may require immediate activation alert by flashing red and yellow.
For example when overheating, the heat sink button flashes.
For example when docking the landing gear button flashes and when overheating
the heat sink button flashes.

The app reads the control bindings from the custom bindings file (Horizons not
Odyssey) so if you're using any other pre-defined set of bindings it won't work.
The app reads the control bindings from the custom bindings file (Odyssey only)
so if you're using any other pre-defined set of bindings it won't work (yet).

The colours used by the app can be configured by editing the `edxlc.toml` file.
This file is created automatically when the app is first run if it does not
exist. You must restart the app to pick up changes in configuration.

The intent is that over time more buttons, controls and states will be
supported. Additionally, the app will become configurable to set the desired
colours for conditions such as active, in use and alert.
Over time more buttons, controls and states will be supported.

The app runs in a console window and can be exited with Ctrl+C.

Expand Down
2 changes: 1 addition & 1 deletion src/game/file.rs
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ use std::path::PathBuf;
pub fn bindings_file_path() -> PathBuf {
dirs::data_local_dir()
.expect("Can't find user app data directory")
.join(r#"Frontier Developments\Elite Dangerous\Options\Bindings\Custom.3.0.binds"#)
.join(r#"Frontier Developments\Elite Dangerous\Options\Bindings\Custom.4.0.binds"#)
}

/// Returns a `PathBuf` for the directory containing the game's journal files.
Expand Down

0 comments on commit f77de35

Please sign in to comment.