View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0001890 | FSSCP | multiplayer | public | 2009-03-04 18:19 | 2013-04-19 17:19 | ||||||||
Reporter | FUBAR-BDHR | ||||||||||||
Assigned To | karajorma | ||||||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||||||
Status | assigned | Resolution | open | ||||||||||
Product Version | 3.6.9 | ||||||||||||
Target Version | 3.7.0 | Fixed in Version | |||||||||||
Summary | 0001890: Fighter beams and lag = no respawn for client | ||||||||||||
Description | Best observed with the Vorlon Fighter in TBP. The best I can tell 3 things have to happen for you to get the problem. First you have to die by a beam. Second you must be firing a beam when you die, and third there needs to be lag. When this happens you never get the respawn prompt. There was a similar random problem in retail when you died by any beam but I haven't seen that in FS2 Open. | ||||||||||||
Additional Information | 3.6.10 r5078 and your Inferno-multi build both have the problem. I don't seem to get it in 3.6.9. Easiest way to get it to happen is run 2 copies of TBP (host regular build, client debug) on the same computer. That gives enough lag for the bug to show up and if using a joystick you will be firing when you kill yourself. I can not get it to reproduce across a LAN. I've also tried replacing the guns on the ships with 42mm which works and the Neutron gun which also exhibits the problem. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
![]() |
|
Goober5000 (administrator) 2012-11-11 00:21 |
Is this still a problem? |
FUBAR-BDHR (developer) 2012-11-11 11:31 |
Unless someone finally got around to rewriting the respawn code then probably yes. |
Goober5000 (administrator) 2012-11-11 13:06 |
It would be better if we had actual confirmation from a multiplayer game. The code has changed a lot since 2009; the problem may not in fact be in the spawn code. |
karajorma (administrator) 2012-12-30 05:24 |
Well I know I have made alterations to the respawn code since 2009 so it may already be fixed. |
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2009-03-04 18:19 | FUBAR-BDHR | New Issue | |
2009-03-04 18:19 | FUBAR-BDHR | File Added: custard.log | |
2009-03-04 18:20 | FUBAR-BDHR | File Added: fs2_open.vorlon | |
2009-03-04 18:44 | chief1983 | Status | new => assigned |
2009-03-04 18:44 | chief1983 | Assigned To | => karajorma |
2009-11-17 21:16 | chief1983 | Target Version | => 3.6.12 RC1 |
2009-11-17 21:16 | chief1983 | View Status | private => public |
2010-08-05 16:07 | chief1983 | Target Version | 3.6.12 RC1 => 3.7.2 |
2012-11-11 00:21 | Goober5000 | Note Added: 0014022 | |
2012-11-11 11:31 | FUBAR-BDHR | Note Added: 0014027 | |
2012-11-11 13:06 | Goober5000 | Note Added: 0014028 | |
2012-11-16 00:57 | Goober5000 | Target Version | 3.7.2 => 3.6.16 |
2012-12-30 05:24 | karajorma | Note Added: 0014589 | |
2013-04-19 17:19 | chief1983 | Target Version | 3.6.16 => 3.7.0 |