Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.2.0a4
2017.2.0f3
Issue ID
969743
Regression
Yes
Auto Sync Transforms does not sync correctly when using AddRelativeForce
To reproduce:
1. Open users attached project "AddRelativeForceBug.zip"
2. Open "Test.unity" scene
3. Enter play mode
4. Press space and observe the arrows fly direction
Expected result: arrow flies to its pointing direction
Actual result: arrow flies to its first frame rotation direction
Reproduced on: 2017.2.0b1 2017.2.0b6 2017.2.0f3 2017.3.0b10 2018.1.0a5
Not reproduced on: 2017.1.2f1 2017.2.0a1 2017.2.0a2 2017.2.0a3
workaround: call Physics.SyncTransforms(); right before using AddRelativeForce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment