Sensor doc cleanup #5309
Merged
Sensor doc cleanup #5309
Conversation
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
dongruoping
approved these changes
Apr 22, 2021
vincentpierre
pushed a commit
that referenced
this pull request
Apr 27, 2021
vincentpierre
pushed a commit
that referenced
this pull request
Apr 27, 2021
vincentpierre
pushed a commit
that referenced
this pull request
Apr 27, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposed change(s)
Doc cleanup (prompted by forum post below). The main thing was fix the "ISensor SensorComponent" line, but added Match3 and Grid to the component list too.
Useful links (Github issues, JIRA tickets, ML-Agents forum threads etc.)
https://forum.unity.com/threads/some-advice-and-suggestions-python-status-maxstep-vs-maxenvironmentsteps-and-ray-sensor-useage.1097416/
Types of change(s)