Scanning arm abort is too sensitive
Opened this issue · 1 comments
gotmachine commented
From forum user Krazy1 :
Maybe someone can come up with at least a partial fix here... super annoyed trying to scan a surface feature with a scanning arm: "vessel moved, scan aborted" or "arm hit object, scan aborted" The KSP sliding bug combined with extreme sensitivity to movement makes it almost impossible to finish the scan. My ship was moving 6 mm/s and it still failed. Is a workaround like giving science credit at the beginning of the scan possible? Or somehow disabling the check for movement?
Rodg88 commented
I've made this patch for my own game which helped, but there could be better solutions
@PART[RobotArmScanner_S*]:FINAL
{
@MODULE[ModuleRobotArmScanner]
{
@cancelScanDistance = 1
@emergencyStopDistanceFromSurface = 0.1
@firstJointRotationLimit = 95
}
}