View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002139 | FSSCP | gameplay | public | 2010-02-24 00:42 | 2021-01-09 09:37 |
| Reporter | FUBAR-BDHR | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | open | ||
| Product Version | 3.6.11 | ||||
| Summary | 0002139: AI will fire secondaries at start when mission is restarted | ||||
| Description | Reminds me of the old multiplayer lag bug that would cause secondaries attempting to be fired before respawn to fire after respawn. This is in single though. I've reproduced it 2 ways. First was dying and hitting replay. Second was just hitting escape and doing a replay mission. The weapons fired were aspect seekers and just flew straight. If I restarted immediately before any enemy fighters were within range it did not seem to happen. | ||||
| Additional Information | 3.6.11 r5919. This was in Diaspora but nothing really out of the ordinary. Fighters, aspect seekers (corkscrew but single fire) some new AI features, etc but nothing that should cause a missile to fire after restart. I'm going to keep an eye out for it in other places. | ||||
| Tags | No tags attached. | ||||
|
|
If the cause is what I think it is, I doubt the cause is exactly the same (the multiplayer bug appears to be caused by the control info not being wiped properly, this shouldn't affect an AI ship). That said, it does sound very similar. |
|
|
This does not seem to be happening in recent builds. I restarted after my wingmen were in range of enemy fighters and no firing happened. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-02-24 00:42 | FUBAR-BDHR | New Issue | |
| 2012-12-30 15:42 | karajorma | Relationship added | related to 0001262 |
| 2012-12-30 15:44 | karajorma | Note Added: 0014592 | |
| 2021-01-09 09:37 | FSCyborg | Status | new => closed |
| 2021-01-09 09:37 | FSCyborg | Note Added: 0017056 |
