[BUG] RoveMax Model M1 Wheels Bug - Breaks Permanently Damaged When Motor Disabled

[DocMoriarty]

RoveMax Model M1 wheel's brakes get permanently damaged when the wheel's motor is disabled in the SPH or VAB. This can't be reversed except directly editing the craft file (which is not an option)! The reason why the motors must be disabled by default is that they suck power when the rover is mounted on a rocket for launch/transfer to mission site.

Reason: Bug in part description / generation

Reproduce: create rover and disable motors in SPH, then launch, enable motors drive and try to brake -> brakes aren't really working anymore

I made 2 rovers to verify the bug, 1 designed normally without disabling motors in SPH and the other one with disabled motors. Both use custom key 05 to toggle motors. The first one brakes normal as expected, the 2nd one doesn't brake at all (or only very very minimal according to craft file).

Then i compared the craft files in UltraCompare:

The brake torque in the bugged non braking model is set to 30 and in the model without disabled engines is set to 300, which by the way looks wrong too regarding the section brakeTorque_UIFlight which defines torque values between 0 and 30.

So there is something definitly wrong, either the torque must be 300 in both cases OR the applied force for 30 braking torque must be 10x higher than it is now. Also the part config file must match the desired/correct value, either 0-30 or 0-300 max torque value.

Here are links to the craft files for easy compare:

http://www.docmoriarty.com/ksp/mods/RN RoveMax M1 Test bugged.craft

http://www.docmoriarty.com/ksp/mods/RN RoveMax M1 Test Ok.craft

Image of testrover:

Edited August 11, 2015 by DocMoriarty

[sal_vager]

Yeah it's a known issue, there's lots of threads on this one

Claw has made a fix which you can find in his sticky at the top of this section which deals with this issue for now, and 1.1 will see completely replaced wheel code, but there are no plans for any interim patches.

Edited August 11, 2015 by sal_vager

[DocMoriarty]

Ok thanks, wasn't sure it has been reported already. My workaround was to fix it directly in the craft files.

[sal_vager]

Actually I think that's what Claws fix does as well, it's just automatic.