Improve support for direct mission launching #649
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BrettMayson
requested changes
Feb 7, 2024
Co-authored-by: BrettMayson <brett@mayson.io>
BrettMayson
approved these changes
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve support for directly launching into 3DEN with an existing mission by allowing missions contained in the project to be used.
Adds a
missionconfiguration parameter that specifies whether a launch configuration loads directly into a mission. Can be specified as either:.hemtt/missions/(e.g.,mission = "test.VR"would launch.hemtt/missions/test.VR/mission.sqm).mission.sqmfile (or folder containing it).Tested all of the various cases and everything looks good. I am not too familiar with Rust and this is just the result of my messing around. So, the code could probably be improved.
Close #621