-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Physics update #480
Merged
Merged
Physics update #480
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
tcorbly
requested changes
Oct 6, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like cloning the fork instead of switching from the master branch worked. Here are a few of the things I've noticed so far:
- Objects in the world do not reset when the reset world button is clicked.
- Motor speeds appear to be around half the speed they were previously.
- When the robot stops the back of it flips up a little bit. This may be solved by changing the weight on some of the parts of the robot.
- The wheels tend to slide a bit during turns. This may be solved by changing friction on the wheels
- So far zero issues with the robot sliding over time!
- In JBC sandbox A, there is a second A mat overlaying the A mat that seems to be mirrored after switching between scenes. Not there after a page refresh
- In JBC Sandbox B, the A mat is overlaying the B mat, should just be B after switching between scenes. Not there after a page refresh
- The robot's starting rotation is labeled as -45 degrees. It should be 0 to start but still be in the same position
- Reflectance sensor are not picking up any readings and should be on port 1 instead of port 3
- When the robot is touching another object at the end of its run, both objects go flying as soon as the run finishes
- Hard to tell on my end but positions and things like that for challenges (6c would be the one to look at) don't seem to be the same or able to be reset
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.
Updated the physics engine to Havok. At this point I still plan on updating some of the moonbase assets to take advantage of the physics engine upgrade (making them more graspable).