-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wasn't able to get it to work #14
Comments
It uses key sends which should work both in windowed and full screen modes. It tries to detect your log files on startup - and as long as they are in the standard location (which I can’t remember off the top of my head but probably user data/frontier…. ) it uses those to detect game events. And it reads the primary display to try and detect images on the UI. I’ve not played E:D myself in 6 months or so. It’s possible a recent update may have changed the images on the hud or menus just enough to break the workflows. The last I I used it I did notice it had a hard time refueling - it seemed to be a timing issue.
In terms of key bindings it just needs the menu up/down/left/right, select, cancel/back. I thinks that’s WSAD enter/space escape and backspace.
You should see it trying to navigate the menus.
If you enable logging the log file will usually tell you what it thought it was trying to do and what it was looking for and failed. There is also a sub folder where it saves the screenshots it’s taken and you can usually use that to see what it found ha what it was expecting.
If you want to attach a log I’m happy to take a look at it. If I find a chance this weekend I will fire up E:D and see if it’s all gotten broken with a recent patch.
Good luck
On 2 Jun 2023 at 18:51 +0100, Preludeonlife ***@***.***>, wrote:
Not sure what I'm doing wrong. I'll get different errors each time I run. Some Clarification. Do you need to be looking at the game when you start? If I Alt-Tab back to fcmacros will it effect the process? If the Carrier is full will it try and fill it if the refuel on jump is selected? The various errors I've seen have been: destination invalid, finding net waypoint (hangs), it will Launch my ship, Elite dangerous does not have the focus, aborting. I confirmed I am in 1080p, and I reviewed my keybindings though I'm not sure which I changed and which this system needs to be defaulted.
Could you assist?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Thanks for the reply. I'd like to get it working. I probably won't be back
in front of my computer until next week. I'll def run the logs and do a
little troubleshooting. I'll reach back out and see what can be done.
…On Fri, Jun 2, 2023, 7:25 PM pilotso11 ***@***.***> wrote:
It uses key sends which should work both in windowed and full screen
modes. It tries to detect your log files on startup - and as long as
they are in the standard location (which I can’t remember off the top of my
head but probably user data/frontier…. ) it uses those to detect game
events. And it reads the primary display to try and detect images on the
UI. I’ve not played E:D myself in 6 months or so. It’s possible a recent
update may have changed the images on the hud or menus just enough to break
the workflows. The last I I used it I did notice it had a hard time
refueling - it seemed to be a timing issue.
In terms of key bindings it just needs the menu up/down/left/right,
select, cancel/back. I thinks that’s WSAD enter/space escape and
backspace.
You should see it trying to navigate the menus.
If you enable logging the log file will usually tell you what it thought
it was trying to do and what it was looking for and failed. There is also
a sub folder where it saves the screenshots it’s taken and you can usually
use that to see what it found ha what it was expecting.
If you want to attach a log I’m happy to take a look at it. If I find a
chance this weekend I will fire up E:D and see if it’s all gotten broken
with a recent patch.
Good luck
On 2 Jun 2023 at 18:51 +0100, Preludeonlife ***@***.***>, wrote:
Not sure what I'm doing wrong. I'll get different errors each time I run.
Some Clarification. Do you need to be looking at the game when you start?
If I Alt-Tab back to fcmacros will it effect the process? If the Carrier is
full will it try and fill it if the refuel on jump is selected? The various
errors I've seen have been: destination invalid, finding net waypoint
(hangs), it will Launch my ship, Elite dangerous does not have the focus,
aborting. I confirmed I am in 1080p, and I reviewed my keybindings though
I'm not sure which I changed and which this system needs to be defaulted.
Could you assist?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAIXSYZQ64BSH42SSNOKXHLXJJY57ANCNFSM6AAAAAAYYTSTJM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure what I'm doing wrong. I'll get different errors each time I run. Some Clarification. Do you need to be looking at the game when you start? If I Alt-Tab back to fcmacros will it effect the process? If the Carrier is full will it try and fill it if the refuel on jump is selected? The various errors I've seen have been: destination invalid, finding net waypoint (hangs), it will Launch my ship, Elite dangerous does not have the focus, aborting. I confirmed I am in 1080p, and I reviewed my keybindings though I'm not sure which I changed and which this system needs to be defaulted.
Could you assist?
The text was updated successfully, but these errors were encountered: