Search Issue Tracker
By Design
Votes
0
Found in
6000.0.22f1
Issue ID
UUM-83636
Regression
No
Incorrect vehicle rotation when using ForceMode.VelocityChange
Reproduction steps:
1. Open the attached “2022_IN-84796“ project
2. Open the “Assets/DogsSimcadePhysics/Demo/Scenes/Simcade_DemoScene.unity“ Scene
3. Enter the Play Mode
4. Notice the feeling of the controls when rotating the vehicle
5. Close the project and open the attached “6000_IN-84796” project
6. Open the “Assets/DogsSimcadePhysics/Demo/Scenes/Simcade_DemoScene.unity“ Scene
7. Enter the Play Mode
8. Notice the feeling of the controls when rotating the vehicle
Expected result: The feeling of the vehicle rotation control is the same or very similar in both 2022.3.50f1 and 6000.2.22f1 versions
Actual result: In 6000.2.22f1, the vehicle rotates much faster than in 2022.3.50f1, and the grip is significantly different - overall handling of the vehicle is not the same between the two versions
Reproducible with: 2023.2.0a12, 6000.0.22f1
Not reproducible with: 2022.3.50f1, 2023.2.0a11
Reproducible on: Windows 10 (22H2), Windows 11 (10.0.22631) (user’s)
Not reproducible on: No other environments tested
Note: Reproducible in Player
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Heya! This change is by design, previously the resulting angular impulse would be incorrect as it was mass based rather than taking into account the inertia tensor matrix. This means that some setups need to be re-tweaked due to this fix.
Cheers,
AlexRvn