Submit Feedback

[Update 1.190] Share inertia tensor missing with experimental enabled in Never Surrender scenario

GemHunter1 shared this bug ago

Solved

Hello There

I have some issues with shared inertia tensor option not being present on rotors and pistons in the Never Surrender scenario with experimental mode enabled in the game settings (and even in the .sbc file FYI).

Freshly created never surrender scenario world does not have the option too.

Files:

I have the same bug

Replies (19)

Ales Kozak ●

Hello, Engineer!

Thank you for your feedback! Your topic has been added between considered issues.

Please keep voting for the issue as it will help us to identify the most serious bugs.

We really appreciate your patience.

Kind Regards

Keen Software House: QA Department

Reply URL

StevieSkyHawk ●

I have the same issue since this update.

Have tried various never surrender scenario saves going back, and tried to disable/reenable experimental mode, but without success.

Reply URL

Jim Knight ●

This actually breaks my game, had to restart another cuz my pistons kept shooting off when I started/loaded a save

Reply URL

Sean Ferguson ●

Same problem, no checkbox for share tensor, makes Never Surrender unplayable :(

Reply URL

Ryan Hendry ●

Same here

Reply URL

Chris Marshall ●

Has share inertia tensor been inadvertently removed from the game, or was it intentional?

Reply URL

GemHunter1 ●

They fixed a bug where you were able to enable shared inertia tensor without having experimental mode enabled. After the update shared inertia tensor is still present and functional in any custom world. However there appears to be something funky with most of the scenarios where the option is just missing, leaving it off for all pistons/rotors. (tested on Never Surrender and Learning to Survive so far)

URL

beelzerob ●

I'm experiencing something like what you're saying.... I'm playing the Never Surrender scenario, using a local dedicated server. I have no problems checking the "Share inertial Tensor" box, and it works fine, on pistons and rotors.

My problem is actually that, whenever we have to stop and restart the server (for an update or whatever), all of those checkboxes get reset. So before we accidentally use the welding or mining rig that has lots of pistons and rotors, I have to go in and re-check all of their share tensor boxes to keep it all from exploding.

Is that the same as the problem you're seeing? It sounds like you're not seeing the box at all. I definitely am and it works fine...it just isn't persistent across server reboots.

Reply URL

GemHunter1 ●

It could be related to some degree. Since I am not playing on a dedicated server I didn't test that, but I will totally try it later when I have some more time (probably after Monday).

With locally (in-game) hosted world I don't even have the option, but the build vision mod has the option listed. Yet whenever I try to turn it on, it flips itself back to off immediately. I suppose I could try to ask a friend if he sees the box when he connects to my world, whether it behaves similarly.

I've also found another problem not just with the tensor. While in creative I cannot paste any blueprint nor copied grid (with ctrl+c) that has any experimental mode feature. For example while in the same world I can make a rotor with max torque (in the red) and it works fine. However when I try to copy and paste that grid I get greeted with "You cannot paste experimental grid" (or something along those lines). I think it might not register experimental mode for scenarios. Perhaps it's the same deal with torque as the patched tensor box (that it shouldn't be possible to go to red zone without experimental mode).

Once I have a bit more time I will definitely inspect the problem a bit more.

URL

GemHunter1 ●

So I have (finally) tested it more and found out some interesting information. I did try dedicated server with the same results. Additionally I got my friend to connect to my local world. I didn't even see the box as said before, however he was able to see the inertia box and even turn it on, which lasted until I reloaded the world after which it turned back off. Basically the same thing. This means the bug is more likely to be on the host side.

URL

Dareliisko ●

Meant to leave a new comment

URL

Jared W Boldon ●

It's missing in both experimental and vanilla for me at least. Tried enabling/un-enabling experimental... no dice.

Can't build much w/pistons without it :(

URL

Dareliisko ●

Any chance we can get a hotfix or an opt-in beta hotfix for this? Haven't played since clang visited me.

The option is missing on all 3 standard scenarios, and trying to change the property value using a script doesn't work and still returns false.

Not sure why its being forced even though the scenarios are in experimental mode

Reply URL

Sean Ferguson ●

I haven't played since that patch either (5mo), its like they made the feature then never tested it in single player (which i thought it was listed as a feature for?)

URL

Konrad Szymczak ●

Rotors and pistons ... never use them

Files:

Reply URL

Sean Ferguson ●

Haven't bothered playing since this first occurred, Reinstalled the game today (after 7 months) still no inertia tensor option in single player never surrender, RIP single player people

Reply URL

Valts Dārznieks ●

Have the same issue. Everything else from experimental works.

Reply URL

dalkgamler ●

any updates on this yet? or atleast a workround?

Reply URL

Guest ●

Still not able to tick it. Box doesn't exist.

Reply URL

Ryan Hendry ●

It's really frustrating this hasn't been fixed yet. I haven't come back to space engineers since I first encountered this bug 9 months ago.

Reply URL

Sean Ferguson ●

Same

URL

Sean Ferguson ●

How is this still broken?

Reply URL

Michael ●

Yep, experiencing this on Frostbite

Reply URL

Sean Ferguson ●

man its 2021 and this still broken? I havent played in 2 years, apparently i can stop looking, but hey, new aesthetic stuff right?

Reply URL

Dareliisko ●

I haven't tested (played at all) in-game since I encountered the issue and commented. And given this support ticket still hasn't been resolved I'll presume it's the case.

Definitely disappointing, scenarios can't be so different that it's impossible to fix..

Yet the Never Surrender scenario really gives a good practical and fun objective to aim for and we're forced to play it under the Clang overlord

URL

Laura K ●

Hello all!

I appreciate that this is an older thread, however, see that there are a few new comments. I have just double-checked this and it looks like it is visible in Never Surrender. Please see attached screenshot

Kind Regards,

Laura, QA Department

Files:

Reply URL

Sean Ferguson ●

Perhaps you guys could clear out your tickets then? there are /has been 8 open tickets for this. This is kinda ticket system 101, if you dont close your tickets, the issue isnt updated.

URL

Ondrej Borz ●

Hello, Engineers!

I´m happy to inform you that this issue will be fixed in upcoming game update v200.

Kind Regards

Keen Software House: QA Department

Reply URL