|
|
I can't seem to reproduce this one. Give me some more specifics on this so that I can better try to replicate it: mission? ship type? full loadout? linked secondaries? |
|
|
Well I was hosting on the standalone playing m-02b by myself. Loaded out a turtle (Tauret?) with bank 1 Trebs (13 count) and bank 2 harps (40 count?) Secondaries were set to dual fire. Primaries were dual Kaysers of course. Occurred when 1 Treb was left in bank 1. It's not something that will happen every time. Never seen it on the host side except hosting on a standalone. Retail it would happen with just about any weapon/ship. Even saw it happen with Tornadoes when weapons subsystem was damaged and a whole bank didn't fire leaving only a partial swarm for the next shot. Most usual time would be a loadout of Trebs and Helios where the ship would hold 3 Helios in one bank (Ursa, Sekhmet, etc). When you got down to 1 Helios left and the next bank was a Treb it would only take the lock time of the Treb but still fire that one Helios. |
|
|
This might be something similar to Mantis 464. That's probably the one that was making me think this had already been fixed. |
|
|
Had a couple more occurrences of this but this time the bank still had 2 missiles left in it. Uploading screenshot from the first time. I was firing Trebs and the indictor changed to bank 2 with 2 Trebs left. It locked in the normal Treb lock time and fired Trebs. I was hosting on a standalone when this one happened. One time I tried firing the bombs and they fired instantly without locking. Apparently it assumed bank 2 was already locked. This was as a client. |
|
2008-11-02 02:39
|
screen0020.jpg (87,675 bytes) |
|
|
Is this still an issue? |
|
|
It still was last time I played multiplayer. |
|
|
The latest multiplayer beta builds no longer *seem* to have this issue, but I will ask testers to keep an eye out for it. |
|
|
I don't know what to say. Still not seeing this bug. Closing until it reappears. |
- Anonymous
