This object is in archive! 

Merge block not releasing physics constraint

A G Systems shared this bug 2 years ago
Solved

Attaching a rotor, then trying to release with a merge block keeps the rotor physics constraint on both grids.

Steps to reproduce: Load up SBC linked below. Follow instructions on centre console.

https://steamcommunity.com/sharedfiles/filedetails/?id=274238039

Replies (4)

photo
1

Hello, A G Systems,

thanks for letting us know.

However... I do not quite follow what is the problem. Tried all sorts of things possible with rotors, merge blocks and it´s various combination. But all was working for me just fine.

I think that having a working Steam link might be awesome so I can see the world/blueprint on my own and try it there. Can you please check, why it´s not visible to me? Maybe restricted visibility? Anyway... can not access it :(

You can also send me full blueprint or save here:

You can access your blueprints files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers\Blueprints. Select the correct folder where your blueprint is saved (local or cloud), zip the file and attach it here.

Same method with saves.

Only thing regarding rotors (and hinges) that I can think of as currently broken and might be this (as I understand the text) is this. Can you please check it out and let me know if your issue is the same/similar to this, or completely different?

Thanks in advance for more information you can share and also for providing the blueprint/save.

Kind Regards

Keen Software House: QA Department

photo
1

Sorry, not sure where I messed up with that link, this one should work. (actually checked this time :/ )


https://steamcommunity.com/sharedfiles/filedetails/?id=2742375870


Here is also a video of what is reliably happening for me:

https://youtu.be/Wp2i-hsQBIw

photo
1

Hello, A G Systems,

thanks for coming back and for updating the Steam page, as well as providing the video.

With these information and BP, I was able to successfully reproduce this issue. It is now reported in our internal system.

Kind Regards

Keen Software House: QA Department

photo
1

Hello Engineer,


We’re pleased to inform you that this issue has been resolved in version 205.


As such, we’ll be closing this thread.


If you encounter any other issues with the game, please don’t hesitate to start a new thread here on the forum—we’re always happy to assist!


Happy engineering!


Kind regards,

Keen Software House - QA Department

Leave a Comment
 
Attach a file