Elite Dangerous Fleet Carrier Macros There are 3 primary macros:
Route files are in CSV format from the spansh router. Only the first column matres and it must be titled "System Name". https://www.spansh.co.uk/fleet-carrier
Currently, this plugin uses default keybindings and mouse for input. The mouse is used to navigate the galmap. Because it uses the keyboard and mouse, it is unlikely to work with a joystick or HOTAS enabled.
Note: See keymaps.py to edit the keyboard mappings. (Only in source code version.)
The latest version no longer uses image matching, instead of uses known location on the screen and text recognition. It may now work with custom HUD colors. It is also hopefully insensitive to HUD Brightness options. It is also tested on both windowed and full screen modes, but only at 1008p full screen.
The tool is written attempting for safety in the UI.
If the macro cannot find the expected images or text it will abort for safety.
But I cannot guarantee it won't misbehave in some odd way. It is just sending keys and mouse
actions so if E:D loses focus while running it will start sending them to whatever application does have the focus.
If you use the refuel option, make sure your ship has enough room for a full jumps worth of Tritium, as much as 150 Tons if your carrier is fully loaded. This option will load the carrier and the ship before setting up a jump to minimize the carrier mass.
Option 1:
Option 2:
These are all included in the installation or are part of the pip install in setup.cmd.
The latest edition uses teseract for the text recognition.
A portable copy is provided in a zip file and is auto extracted at first runtime.
More about the teseract project can be found here.
The provided copy is the University of Manheim 64bit build.
There is heavy use of OpenCV.
The latest version uses much less of pyautogui But much homage is owed to this tool.
The UI theme is awthemes awdark by Brad Lanam. (Thank you.)
Summary of actions are written to "fcmacros.log" in the working directory. If you are experiencing issues, enable debug logging. The log file will contain details of every step the macro is taking - what keypresses it is making, the images or text it is searching for on the screen etc. Hopefully there will be enough information to troubleshoot. For now it saves many debug_*.png images in the debugimages/ folder. These are to also help troubleshoot problems. You might see something like debug_TRITIUM_threshold.png. If it doesn't contain the word "TRITIUM", that's a hint that it's not finding the text properly.
Likely causes:
If you have the source code version you can edit the keybindings in "keymaps.py".
The latest version has abandoned the pyautogui "find this image" technique and instead uses known offsets and text recognition. This should be less trouble free.
More work is needed to support non-1080p resolutions.
Copyright (c) 2022 Seth Osher. All Rights Reseved. Released under the MIT license.
Tags: Elite Dangerous Fleet Carrier autopilot auto jumper macros