View Issue Details

IDProjectCategoryView StatusLast Update
0000324FSSCPmultiplayerpublic2005-06-24 10:36
ReporterLightspeed Assigned ToGoober5000  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Summary0000324: fs2_open_T-20050212.exe breaks multiplayer.
DescriptionConnecting to the main server and refreshing take a long time (the game literally hangs for thirty or more seconds).

Much more critical however, is the fact that it fails to display half of the available servers, effectively preventing to join most games.

This has DEFINATELY been tracked down to a build issue, because when I revert to 3.6.5 the problems mentioned above disappear, and I can normally see all currently open games again.
TagsNo tags attached.

Activities

taylor

2005-02-19 22:09

administrator   ~0001666

Lightspeed, can you try anyone elses recent builds and see if the same problem exists. Anything in the past two weeks. I'm thinking that this is Linux merge related but haven't found an obvious problem yet. I just want to rule out a build issue with that one in particular if that's all it is. If WMCoolmon's build works then I'll chalk it up to a bad compile or something. If not then the code will have to be looked through again.

Lightspeed

2005-02-20 01:20

reporter   ~0001668

Sorry, but can you link me to WMC's build?

taylor

2005-02-20 02:02

administrator   ~0001669

http://fs2source.warpcore.org/exes/latest/C20050218.zip

I think it's the Linux merge but I'm just not 100% sure. My firewall won't let the traffic through like it needs, just because of how I have my network set up. It worked via LAN games during testing but I just never got FS2NetD tested. If that build has the same problem then we'll know what it is.

Lightspeed

2005-02-24 19:50

reporter   ~0001680

Okay, tested with that build. While the problem mentioned above did not occur, things indeed seem to have gone amiss somewhere.
WMC's build allowed me to normally join the game (and didn't hang on refresh) but led to weird problems as soon as the game actually started. The very instant the game started the sensors flickered off (as if they were damaged), same with weapons and all other systems. They were NOT damaged however (and I was still at 100%), but everything was disabled. I then self-destructed, and the game CTD'd.

I assume the build works in single player (right?) so this is definately something messy with the multi code.

This is what the errorlog said after the CTD: "Write to location 0d9231b8 caused an access violation."

kasperl

2005-03-20 10:53

developer   ~0002005

Reminder sent to Lightspeed

Lightspeed, is this fixed in later builds?

kasperl

2005-04-04 17:06

developer   ~0002093

Taking the bug, and will send reminder.

Goober5000

2005-05-25 02:00

administrator   ~0002482

Reminder sent to Lightspeed

Does this happen in recent builds, LS?

Goober5000

2005-06-24 10:36

administrator   ~0002683

Assume this particular bug was fixed. Works for me and no feedback in a month.

Issue History

Date Modified Username Field Change
2005-02-17 13:42 Lightspeed New Issue
2005-02-17 15:32 taylor Status new => assigned
2005-02-17 15:32 taylor Assigned To => taylor
2005-02-19 22:09 taylor Note Added: 0001666
2005-02-20 01:20 Lightspeed Note Added: 0001668
2005-02-20 02:02 taylor Note Added: 0001669
2005-02-24 19:50 Lightspeed Note Added: 0001680
2005-03-20 10:53 kasperl Note Added: 0002005
2005-04-04 17:06 kasperl Note Added: 0002093
2005-04-04 17:06 kasperl Assigned To taylor => kasperl
2005-04-04 17:06 kasperl Status assigned => feedback
2005-05-25 02:00 Goober5000 Note Added: 0002482
2005-06-24 10:36 Goober5000 Status feedback => resolved
2005-06-24 10:36 Goober5000 Resolution open => fixed
2005-06-24 10:36 Goober5000 Assigned To kasperl => Goober5000
2005-06-24 10:36 Goober5000 Note Added: 0002683