Project

General

Profile

Bug #24242

Unmotorized pistons reset their position to the last deployed value when locked.

Added by dok_377 over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Severity:
Low
Assignee:
Technicalfool
Category:
Parts
Target version:
1.12.0
Start date:
10/30/2019
% Done:

100%

Version:
1.8.1
Platform:
Linux, Windows
Expansion:
Breaking Ground, Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

It's fairly hard to explain in text, by I'll try anyway. Here's the steps to reproduce this:

1. Take any sized piston. Make sure the "On Power Loss" flag is set to free.
2. Launch it and deploy it to any value.
3. Unmotorize it.
4. Lock it.

It will reset to the last value it was previously set to instead of keeping its position.

5. Now motorize it again and change the deployment value.
6. Try to unmotorize it again.

For some reason this button refuses to work after the first unmotorization. If you try to unmotorize the piston again, it will do so for a split second and then will immediately reset to motorized. I don't know why this is happening. It can be fixed by switching scene.

7. When you switch scene, unmotorize the piston again.
8. Lock it again.

It will reset to this new value that you just set it to instead of keeping its position. It will happen even against the force of gravity. Also, this whole thing is happening even when you unmotorize the piston in the editor and then try to lock it.

Video #1: https://youtu.be/13a61mAlZaw
Video #2: https://youtu.be/qgMNO4nCius

You can't see my cursor (thanks nvidia), but when the PAW is flashing - I'm trying to press the motorization button (explanation after the step 6).

Piston Behavior 2.craft (15.8 KB) Piston Behavior 2.craft dok_377, 10/30/2019 09:47 AM
Piston Behavior.craft (30.2 KB) Piston Behavior.craft dok_377, 10/30/2019 09:47 AM

History

#1 Updated by dok_377 over 4 years ago

  • Description updated (diff)

#3 Updated by Technicalfool over 4 years ago

  • Status changed from New to Confirmed
  • Assignee set to Technicalfool
  • % Done changed from 0 to 10
  • Platform Linux added

Confirmed with some caveats: The piston does not extend to its previous value here, but it does jiggle rather disconcertingly. In any case, I don't think this should be happening.

#5 Updated by victorr almost 3 years ago

  • Status changed from Confirmed to Ready to Test
  • Target version set to 1.12.0
  • % Done changed from 10 to 80

We have made some changes in this last 1.12.0 release and would like some feedback on this issue. Thanks.

#6 Updated by Technicalfool over 2 years ago

  • Status changed from Ready to Test to Resolved
  • % Done changed from 80 to 100

This should now be fixed. Please continue to report robotics bugs as you find them.

Also available in: Atom PDF