Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.26f1
2021.2
2022.1
2022.2
Issue ID
1396766
Regression
No
Description of the Surface Effector 2D "Use Contact Force" option contains a typo
How to reproduce:
1. Open the attached "case_1396766" project
2. Open the "SampleScene" Scene
3. Select the "Main Camera" GameObject in the Hierarchy
4. Hover with the mouse over the "Surface Effector 2D (Component) -> Options -> Use Contact Force" option in the Inspector
Expected result: A text box with the option description appears which the first sentence starts with "Should the force be applied..."
Actual result: The first sentence starts with "Should the force but applied..."
Reproducible with: 2019.4.35f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b5, 2022.2.0a2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.2):
Typo Fixed on Unity 2022.2.0a8 and above