Merge Block problem for Inch Worm Drive

Alexandre Huppe shared this bug 3 months ago
Reported – Awaiting fix

Inspired by this tunel boring machine (https://steamcommunity.com/sharedfiles/filedetails/?id=2495892126), I'm tryin to desing my own.

1rst step (in my mind) is to have a working inch worm drive so I can fit a "track" inside a tunel blueprint.

Having some weird behaviors with my prototype, I tried creating a new world and making a over simplified version.


Am I doing something wrong here? (If it works in the liked blueprint, Why can't I make it work?)

World and videos can be downloaded here

(sorry for the english in the video, 2nd langage...)

Comments (2)

photo
1

I've done some more testing and prototyping and used a merge block on one end and a rotor on the other (preventing a merge of the 2 subgrids on each end of the piston). This worked.

This leads me to believe merging as one grid the 2 subgrids created by a piston is not possible (explaining the piston head detaching from the block on a merge).

Is this assumption correct? In brief, help me better understand this please ;)

(I tested this because I realized the linked workshop blueprint has many subgrids (at least 2) between merge blocks, so it never merges the 2 subgrids of a piston)

photo
2

Hello, Alexandre!

Thanks for letting is know about this one issue! With the information, videos and save that you provided, it was indeed easily reproducible. Thanks a lot for it! It is really making our lives and work easier when you provide all necessary information first handed :)

Keep it up!

If you will stumble across anything else, please don´t hesitate to contact us again.

Kind Regards

Keen Software House: QA Department

photo
1

Hi Ondrej,

Based on your response I guess my initial design (what I submitted in the videos) should have worked. Is this correct?

Thanks again

Alexandre

photo
2

Hello, Alexandre,

well, from what I saw and tried and upon communication with my colleague, we as QA decided that it MIGHT be an issue. So we pasted it to the devs in form of a bug, in order they decide whether it´s right or wrong.

So... we all will see, I guess :)

Sorry I have no better answer for you right now.

I will let you know once I have some more information on this.

Kind Regards

Keen Software House: QA Department

photo