The turrets of a capital ship does not reflect a weapon change until you enter (one of?) them.

Steps to reproduce:
1) Be piloting a capital ship equipped with capital cannons (for example).
2) Procced an in-space turret swap. Remove all the capital cannons replacing them with repair turrets.
3) Wait 5 minutes for the turrets to become active again.
4) Without actually entering any of the turrets, try to repair someone.
5) Poor "someone" is probably dead by now as the turrets, now equipped with repair guns, still fire capital cannons. (Yes, I learnt this the hard way.)
6) Enter a turret and exit it.
7) Turrets will now accept the change and fire repair guns.

It is probably reproducible with all possible loadouts.

This bug can be abused in the way that you can be using one loadout while having the second one ready for immediate use without disabling the turrets and losing the shields.

We have been unable to reproduce this issue so far. Has anyone else been able to?
Or better yet, please let us know a precise time that this happened so we can check the logs.

I experienced this bug for the first time when I nearly killed a friend of mine with freshly swapped repair turrets while capital cannons were still active. Since then, I replicated the bug twice to confirm it. As I believe, once with the same setup and then interchanging swarms and cannons. I am 100% sure it was working that way but I do not know the exact date as I am being a bit late with my report. I will try again, report the results and exact date/time.

I have to admit that I cannot reproduce this bug anymore. It is my fault that I did not check it once again right before posting but I really had repeatedly confirmed its existence earlier. All I have at hand are old logs and I am not sure when exactly I was testing this. It returns a lot of turret swaps when I try to grep the logs. Anyway, I see some possible testing done in Dau L-10 on November 4 between 15:01 and 15:14 UTC. I see many consecutive turret swaps there and I remember shooting roids for the confirmation test.

Generally, with the game as actively developed as it is, bug reports that are two months old are likely to be pretty out of date.

This may have been fixed as a result of some other problem, that created a different symptom that we knew about. We didn't "intentionally" fix this particular symptom, but we may have fixed the underlying cause previously.

Anyway, we appreciate the reporting, but as you said, please do confirm bugs still exist immediately before reporting.

I perfectly understand what you mean, and I feel really sorry.