You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 …
The text was updated successfully, but these errors were encountered:
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:
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:
The text was updated successfully, but these errors were encountered: