Enable setting simulation speed in VSCode #12297
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
dagar
previously approved these changes
Jun 17, 2019
|
Awesome! I think the main problem with jmavsim right now is java compatibility. |
In order to be consistent between Gazebo and jMAVSim we should be using the env variable PX4_SIM_SPEED_FACTOR in the same way. This enables vscode to set the speed using the env variable.
This changes the VSCode debugging to use lockstep. For lockstep, the rate needs to be 250 Hz.
This env variable can be changed to adapt the simulation speed.
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.
This depends on PX4/jMAVSim#104.
For details, check commit messages.