search

cmss13-devs / cmss13

Contains the code for CM-SS13
https://cm-ss13.com
GNU Affero General Public License v3.0
102 stars 569 forks source link

Normandy's starboard pylons suddenly disappear during setup time #6161

Open hminh2010 opened 7 months ago

hminh2010 commented 7 months ago

Testmerges

5401: 'M540-B Armored Recon Carrier' by Zonespace27 at commit 14fd730a63 #6103: 'Med Vendor Rebalance' by Drulikar at commit bfdc7f3309 #5957: 'OT CAS rocket' by iloveloopers at commit fb68496a9f #6114: 'dehardcodes client version warnings' by harryob at commit 653037e4a7 #6062: 'Stabilized metallic foam, a gimmick new flamer fuel' by iloveloopers at commit eb2a451306 #6039: 'Project ARES TM Holder (v5)' by realforest2001 at commit 0079ca12cb

Round ID

21804

Description of the bug

While I was setting up Normandy for CAS during the fueling period during pre-op, every weapon and engine point on the starboard side of the Normandy suddenly disappeared. Attempting to interact with the points, such as clicking on it with a powerloader to attempt to uninstall whatever was on there, or trying to install a new one, did nothing.

What's the difference with what should have happened?

Normandy's weapons should not have disappeared.

How do we reproduce this bug?

The DP was helping me install the components, so I am not sure of the exact order, but I installed the following components, in this rough order:

It is worth noting that the cooling system which I put on the port mount did not look like a normal one; rather then looking like this: image

It looked like this, but detached from the engine mount. image

I proceeded to install a Laser and Targeting Pod on the port side after this. When I viewed the computer at this time, the mounts were visible when setting up Fire Missions, though without ammo they couldn't be assigned to fire anything. image

image

image

The port side was completely unaffected, however. image

I Ahelped this, at which point the admin tries to fix it. They told me that they couldn't fix it, and that, "Be sure to say that VV'ing the STARBOARD WING ATTACH POINT shows whatever is in the PORT WING ATTACH POINT, and deleting it from the STARBOARD one deletes it from the PORT one. Nothing can be placed on the whole starboard side of the dropship."

At this point, I decided to swap out the port side Laser and Rocket Pod for more Guided Missile Racks and loaded them with a Dragon's Breath and a Widowmaker, hoping to do direct missions. However, after doing that and flying a flyby mission, the targeting computer completely removed all listed weapons in the FM, as well as listing no weapons to do directs with: image image At this same time I noticed that none of the equipment which requires a console worked either, e.g the Fulton I had on board. image However, I was able to do Medevacs just fine.

Issue Bingo

dadlips commented 7 months ago

dreamseeker_okhIGnEhqF I'm not really sure how this managed to happen. In this image you can see that I'm VV'ing the STARBOARD pylon, and it's showing me what is on the PORT pylon. If I were to delete the rocket pod, it would remove it from the PORT pylon, and the STARBOARD pylon will still be unusable.

a few runtimes fired for the weapons systems.

[2024-04-18 02:05:40.667] runtime error: Cannot read null.attach_id

hminh2010 commented 7 months ago

Haven't tested this out yet but I think this is related to another bug, https://github.com/cmss13-devs/cmss13/issues/5848. I'm pretty sure the DP who was helping me set up Normandy tried to grab the same missile rack as me, got the 'fake' missile rack, and placed it on the Normandy, breaking it.