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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Add comment