Bug #16364
physics bug version 1.3.1
100%
Description
There definitely seems to be some issues with physics in 1.3.1. Beside the ship jump as described in #16090 (https://bugs.kerbalspaceprogram.com/issues/16090), I noticed issues on EVA. Kerbal was carrying a container. Mobility changed accordingly with added mass of container, but when the container was no longer part of kerbal's inventory, her mobility became erratic, including violent uncontrolled spin. I was able to stop the spin by shutting off RCS and then turning it on again, but not consistently.
Secondly, container on the back of the kerbal seems to be an apparition, not a solid, as it passes through ship components while on the kerbal's back. As soon as the container was no longer in the inventory, it interacted normally with other solids. Quantum container?
History
#1 Updated by Technicalfool over 7 years ago
- Status changed from New to Need More Info
This could be a stock issue or it could be KIS/KAS. Without more information (a stock reproduction of wonky EVA physics would be ideal), it's difficult to fix the problem or know if there is a problem.
#2 Updated by unclejace about 7 years ago
Technicalfool wrote:
This could be a stock issue or it could be KIS/KAS. Without more information (a stock reproduction of wonky EVA physics would be ideal), it's difficult to fix the problem or know if there is a problem.
Will try to get video file when it next occurs
#3 Updated by Squelch about 7 years ago
- Severity changed from Critical to Low
We really need a reproduction in an unmodded game to be able to investigate this. Priority reduced.
Please see our wiki for details on how to report and what priorities mean.
#4 Updated by unclejace about 7 years ago
On most recent EVA I was unable to reproduce the issue. Secondly,I have KIS and KAS installed. I will retract my concerns on this issue until I can more substantiate it. Thanks for advice on reporting bugs.
#5 Updated by chris.fulton over 5 years ago
- Status changed from Need More Info to Resolved
- % Done changed from 0 to 100
#6 Updated by chris.fulton over 5 years ago
- Status changed from Resolved to Closed
Closed in efforts of database cleanup.