Default to MjViser - #1034
Merged
Merged
Conversation
jgueldenstein
approved these changes
Aug 18, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
As discussed in the meeting, this PR defaults the launch script(s) to use the viser frontend for MuJoCo by default.
From my personal testing running the simulator locally, the performance difference if it exists benefits Viser and not the native viewer. Since the native viewer also has a few limitations that Viser does not have default to the latter should not have any drawbacks. (ok, except that you manually need to open it up once)
Related issues
Checklist
pixi run buildTest on the robot