[2.0.14] putting additional ammo in space platform turrets wrecks performance

[dnmr]

manually put some more ammo in a railgun and FPS/UPS got dunked to 40 (apparently even lower when getting this screenshotted), construction planner was in the 30's

20241103185724_1.jpg (921.21 KiB) Viewed 653 times

turns out a rocket turret was doing the same but only took up 6 ms or wahtever of construction planner so it was not noticeable

20241103185651_1.jpg (1.22 MiB) Viewed 653 times

big asteroid filter on railgun and medium on rocket, nothing else of note, platform parked

the save is actually from the previous patch but looks like the issue persisted after updating

[Rseding91]

Thanks for the report however when I try to reproduce this, it doesn't have any slowdown. Is there something extra i need to do? Can you provide a save file in the slowed-down state?

[rava]

This was happening in our multiplayer server.

The performance issue was reproducible in the linked save by all three of us on the mighty space platform TURBO CRUSHER by:

1. Adding ammo to existing turrets on space platforms with [Pipette -> Click]
2. Letting the turrets shoot some of it
3. Queuing more ammo in the turret with [Pipette -> Click] before the added ammo runs out
4. Construction Manager performance and UPS drops as long as there's queued ammo in the turret
5. [Right clicking] the queued ammo away makes Construction Manager and UPS rapidly return back to normal

Below are are a couple videos of it happening, with railgun seemingly being more affected than rocket turret.

Rocket Turret: https://i.imgur.com/ROkkNCE.mp4 (minor impact in total UPS, notable increase in Construction Manager)
Railgun: https://i.imgur.com/g6dMy6Y.mp4 (major impact in total UPS causing stuttering, huge increase in Construction Manager)

[dnmr]

Thanks for the report however when I try to reproduce this, it doesn't have any slowdown. Is there something extra i need to do? Can you provide a save file in the slowed-down state?

it's in the first post if you still need that, forgot to mention

[Rseding91]

Ok, I was able to reproduce it. I wasn't before because this was fixed in 2.0.15 which is what I was testing with.