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
Currently, the path on which the program looks for settings.json is hard coded in relation to the user's home directory, which tends to cause confusion and is in general a bad practice. In the original AirSim repo this was fixed to allow looking for the settings.json in
the executable's folder
the current directory from which the executable is being launched
a path specified by the --settings command line argument
or optionally passing the full content of the settings.json file as a string argument (e.g. --settings "{\"SettingsVersion\": 1.0, \"SimMode\": \"Car\"}" )
Currently, the path on which the program looks for
settings.json
is hard coded in relation to the user's home directory, which tends to cause confusion and is in general a bad practice. In the original AirSim repo this was fixed to allow looking for the settings.json in--settings
command line argumentor optionally passing the full content of the settings.json file as a string argument (e.g.
--settings "{\"SettingsVersion\": 1.0, \"SimMode\": \"Car\"}"
)Those changes were introduced in microsoft/AirSim#715 and microsoft/AirSim#2668,
and we can make the same changes here with little effort.
The text was updated successfully, but these errors were encountered: