Mass Blocks placed prior to 1.190 are broken

Mike Dude shared this bug 16 months ago
Solved

Artificial Mass Blocks on ships placed before update 1.190 no longer function. They show 0kg, while new ones placed after show 50000kg. Grinding/hacking and re-welding does not fix it either.

ALSO: New mass blocks are unaffected by old gravity generators. Replacing all old gravity generators and all mass blocks is required to continue using gravity drives.

This seems to affect all blueprints contain mass blocks.

Attached is a new world created after 1.190 with a ship that contains a mass block from an old blueprint that is broken, and a new mass block that is functioning.

Comments (4)

photo
1

Attached is an updated world that has a ship that includes the gravity generator and mass block from an old blueprint, and a gravity generator and mass block that were freshly made. These "old" blocks were just cut out of an old blueprint and pasted onto the new grid. This allows you to turn each on and off and test different combinations.


mA2paKRh

photo
1

A friend took a look at the code differences between the old and new mass blocks on the ship and found a discrepancy below:


New mass blocks

<MyObjectBuilder_CubeBlock xsi:type="MyObjectBuilder_VirtualMass">
              <SubtypeName>VirtualMassLarge</SubtypeName>
              <EntityId>120424741354435268</EntityId>
              <Min x="0" y="1" z="0" />
              <ColorMaskHSV x="0.333333343" y="-0.329999983" z="-0.0500000045" />
              <Owner>144115188075855895</Owner>
              <BuiltBy>144115188075855895</BuiltBy>
              <ShareMode>Faction</ShareMode>
              <ComponentContainer>
                <Components>
                  <ComponentData>
                    <TypeId>MyModStorageComponent</TypeId>
                    <Component xsi:type="MyObjectBuilder_ModStorageComponent">
                      <Storage>
                        <dictionary>
                          <item>
                            <Key>74de02b3-27f9-4960-b1c4-27351f2b06d1</Key>
                            <Value />
                          </item>
                        </dictionary>
                      </Storage>
                    </Component>
                  </ComponentData>
                </Components>
              </ComponentContainer>
              <CustomName>New Artificial Mass</CustomName>
              <ShowOnHUD>false</ShowOnHUD>
              <ShowInTerminal>true</ShowInTerminal>
              <ShowInToolbarConfig>true</ShowInToolbarConfig>
              <ShowInInventory>true</ShowInInventory>
              <Enabled>false</Enabled>
            </MyObjectBuilder_CubeBlock>


Old mass blocks

<MyObjectBuilder_CubeBlock xsi:type="MyObjectBuilder_VirtualMass">
              <SubtypeName>VirtualMassLarge</SubtypeName>
              <EntityId>74606413639364958</EntityId>
              <Min x="1" y="2" z="0" />
              <BlockOrientation Forward="Up" Up="Left" />
              <ColorMaskHSV x="0" y="0" z="0.04999999" />
              <Owner>144115188075855895</Owner>
              <BuiltBy>144115188075855895</BuiltBy>
              <ShareMode>Faction</ShareMode>
              <CustomName>Old Artificial Mass</CustomName>
              <ShowOnHUD>false</ShowOnHUD>
              <ShowInTerminal>true</ShowInTerminal>
              <ShowInToolbarConfig>true</ShowInToolbarConfig>
              <ShowInInventory>true</ShowInInventory>
              <Enabled>true</Enabled>
            </MyObjectBuilder_CubeBlock>

photo
1

I think this bug report is closer to the root cause, whereas the one you linked is just a symptom. Still as long as old blueprint gravity drives get fixed then thats good.

photo
photo
1

Fixed in version 1.190.1.