Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scanning arm abort is too sensitive #225

Open
gotmachine opened this issue May 5, 2024 · 1 comment
Open

Scanning arm abort is too sensitive #225

gotmachine opened this issue May 5, 2024 · 1 comment
Labels
kspBug Identified KSP issue

Comments

@gotmachine
Copy link
Contributor

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?

@gotmachine gotmachine added the kspBug Identified KSP issue label May 5, 2024
@Rodg88
Copy link

Rodg88 commented May 5, 2024

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
    }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kspBug Identified KSP issue
Development

No branches or pull requests

2 participants