Skip to content
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

Modifying a shipped preset causes a confusing error message #31

Open
alterNERDtive opened this issue Feb 3, 2022 · 1 comment
Open
Labels
bug Something isn't working

Comments

@alterNERDtive
Copy link
Owner

So if you use a preset the game is shipped with (stored in the installation folder), bindED doesn’t work. By design.

Once you change anything in such a preset, Elite switches to the default “Custom” preset. Unfortunately the preset change is reflected immediately in StartPreset.start while the actual binds file is only written after hitting “Apply”.

So the first time you “create” the “Custom” preset by modifying any bind in a shipped preset, you will get:

4:37:41.313 ERROR | bindED: No bindings file found for preset 'Custom'. If this is a default preset, please change anything in Elite’s controls options.

This is technically correct, but a little confusing. I’m not quite sure how to deal with this in a way that doesn’t cause even more confusion.

NB: binds will still load correctly once you hit “Apply” and the actual binds file is written to disk, and will tell you so in the log:

4:37:59.303 INFO | bindED: Bindings file 'Custom.3.0.binds' has changed, reloading …
@alterNERDtive alterNERDtive added the bug Something isn't working label Feb 3, 2022
@alterNERDtive
Copy link
Owner Author

Still don’t really have an idea on this apart from making the error message more explain-y … which possibly only leads to more confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant