Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
984493
Regression
No
"AddForceAtPosition" works only when an 'outside' force affects the Object first
Reproduction steps:
1. Open "MaschineKart.zip" project
2. In the Hierarchy window select "Kart"
3. In the Inspector window scroll down to "Kart Controller (Script)" -> "Suspension Force"
4. Enter Play mode
5. Increase the "Suspension Force" from '100' to '10000'
6. See that nothing happens
7. Revert the "Suspension Force" back to '100'
8. In the Game window click on the "Kart"
9. Increase the "Suspension Force" from '100' to '10000'
10. See that the "Kart" starts to move around from the force
Expected Result: The same that happens at step 10, should happen at step 5 (Both times the "Kart" should move around as the force is increased, but it only happens after an outside force first affects the "Kart")
Actual Result: Only after an outside force affects the "Kart", does the "AddForceAtPosition" actually affect the cart
Reproduced with: 2018.1.0b3, 2017.3.0p2, 2017.2.1p2, 2017.1.3f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment