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
While I can’t test (no Odyssey, duh), simply reading the last modified <preset>(\.(4\.0|3\.[08]))?\.binds file should break; upon writing the 4.0 (Odyssey) file it is copied over to Horizons by default, making the Horizons one the last modified; but loading into Horizons will strip the Odyssey-specific binds.
tl;dr: I’m actually going to have to go by file name. Load 4.0 if it exists, otherwise 3.8 if it exists, otherwise 3.0 if it exists, otherwise plain.
The text was updated successfully, but these errors were encountered:
So I’m not sure what the deal with these 3.8 files is or is not (see #16), but Horizons definitely reads them (or other arbitrary 3.x, 4.x files) then writes to 3.0.
So … until further notice I’m going to assume there’s 4.0.binds and 3.0.binds and plain binds.
While I can’t test (no Odyssey, duh), simply reading the last modified
<preset>(\.(4\.0|3\.[08]))?\.binds
file should break; upon writing the4.0
(Odyssey) file it is copied over to Horizons by default, making the Horizons one the last modified; but loading into Horizons will strip the Odyssey-specific binds.tl;dr: I’m actually going to have to go by file name. Load
4.0
if it exists, otherwise3.8
if it exists, otherwise3.0
if it exists, otherwise plain.The text was updated successfully, but these errors were encountered: