Need to try twice to enter a game
I am having a slight problem the first time I get into the lobby. Whenever I try to enter a game, disk activity starts occuring and likeit takes forever. When the disk finally stops, I am still in the lobby. Second time I try to enter the same game, I get into the game as normal. After that, everything works OK in the lobby. Any ideas? Anyone having a similar issue?
Are you using HighRes textures?
On first launch the game has to load them and it takes "forever", 2nd time it uses the already loaded textures.
Have you tried to reproduce this without using high res textures (renaming textures folder in artwork)?
On first launch the game has to load them and it takes "forever", 2nd time it uses the already loaded textures.
Have you tried to reproduce this without using high res textures (renaming textures folder in artwork)?
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
No, I don't use high textures. I have texture pack turned off, and I don't have that enormous I-don't-remember-its-name texture file.
Have some mods added
: CortUI, thin gauge, icon pack (ammo, fuel, etc), custom targeting and target pointers. All of them are quite small files compared to hires textures, but maybe...
Strange thing is that it falls back to lobby (couild be some kind of timeout, but there is no error message. It just stays in the lobby). The problem becomes more notorious when trying to join crowded games (I particularly notice it when arriving late to squad games
). In small games it just takes longer the first time, but it joins OK.
Anyway, not a big deal for me, could be some trouble with my particular installation and the added mods. Just wondering if it was a more general problem, but probably not.
Thank you.
Have some mods added
: CortUI, thin gauge, icon pack (ammo, fuel, etc), custom targeting and target pointers. All of them are quite small files compared to hires textures, but maybe...Strange thing is that it falls back to lobby (couild be some kind of timeout, but there is no error message. It just stays in the lobby). The problem becomes more notorious when trying to join crowded games (I particularly notice it when arriving late to squad games
). In small games it just takes longer the first time, but it joins OK.Anyway, not a big deal for me, could be some trouble with my particular installation and the added mods. Just wondering if it was a more general problem, but probably not.
Thank you.
Happened many times, but it happened as well yesterday at squad game. Had to try twice to join the game (I remember clearly because each time I had to type the password, and I don't think I made a mistake). Maybe the server has some error message that could give a hint.MonAG wrote:QUOTE (MonAG @ Apr 29 2013, 01:40 PM) The problem becomes more notorious when trying to join crowded games (I particularly notice it when arriving late to squad games
Last edited by MonAG on Mon Apr 29, 2013 4:48 pm, edited 1 time in total.
I were talking about high res textures in general, not about that texture pack file.MonAG wrote:QUOTE (MonAG @ Apr 29 2013, 06:40 PM) No, I don't use high textures. I have texture pack turned off, and I don't have that enormous I-don't-remember-its-name texture file.
I've took a look into the server logs, but I still have no idea what happed.
CODE04/28 19:43:49.655 New connection ID: 2cb7f5e3 IP: x.x.x.x
04/28 19:43:49.815 New ship (player): Name=ManGO@NI(4), ShipID=421, PilotType=10
04/28 19:43:49.816 Player ManGO@NI(4) logon succeeded. Sent 1 msgs and 2398B to them in 0.001s, and 0 msgs and 0B to others in the process.
04/28 19:43:51.237 sending lobby our mission info for e866a0 listening on port 0
Unknown reason (client side?):
04/28 19:43:57.603 Logoff: ManGO@NI(4)(750253539), was on side=-1 mission=ffffffff.
04/28 19:43:57.603 Destroying ManGO@NI(4), id=421
04/28 19:43:59.587 New connection ID: 1227f5e2 IP: x.x.x.x
04/28 19:43:59.846 New ship (player): Name=ManGO@NI(4), ShipID=421, PilotType=10
04/28 19:43:59.847 Player ManGO@NI(4) logon succeeded. Sent 1 msgs and 2398B to them in 0.001s, and 0 msgs and 0B to others in the process.
04/28 19:43:59.847 Player ManGO@NI(4), ship=421 joined mission=e856d0
04/28 19:43:59.848 sending lobby our mission info for e856d0 listening on port 0
04/28 19:43:59.849 Sending PlayerInfo for ManGO@NI(4) to NI vs BS/SF/RT(2892494588)
DirectPlay error (Link dead):
04/28 19:45:03.013 Nuking ManGO@NI(4)(304608738) because they missed roll call, with messages (0) queued up to them.
04/28 19:45:03.013 DPlay's view of the link was: 0.0kbps, 0ms.
04/28 19:45:03.013 The last completion was 307401.06 seconds ago.
04/28 19:45:03.016 Player ManGO@NI(4), ship=421 quiting mission=e856d0, reason=9
04/28 19:45:03.018 sending lobby our mission info for e856d0 listening on port 0
04/28 19:45:03.021 Destroying ManGO@NI(4), id=421
04/28 19:45:25.054 New connection ID: 1d77f5dc IP: x.x.x.x
04/28 19:45:25.262 New ship (player): Name=ManGO@NI(4), ShipID=426, PilotType=10
04/28 19:45:25.263 Player ManGO@NI(4) logon succeeded. Sent 1 msgs and 2398B to them in 0.001s, and 0 msgs and 0B to others in the process.
Unknown reason (client side?):
04/28 19:45:33.250 Logoff: ManGO@NI(4)(494400988), was on side=-1 mission=ffffffff.
04/28 19:45:33.251 Destroying ManGO@NI(4), id=426
04/28 19:45:35.287 New connection ID: a7f5d8 IP: x.x.x.x
04/28 19:45:35.445 New ship (player): Name=ManGO@NI(4), ShipID=429, PilotType=10
04/28 19:45:35.445 Player ManGO@NI(4) logon succeeded. Sent 1 msgs and 2398B to them in 0.001s, and 0 msgs and 0B to others in the process.
04/28 19:45:35.445 Player ManGO@NI(4), ship=429 joined mission=e856d0
04/28 19:45:35.446 sending lobby our mission info for e856d0 listening on port 0
04/28 19:45:54.073 Player ManGO@NI(4), ship=429 joined side 0, mission=e856d0
04/28 20:00:51.486 Player ManGO@NI(4), ship=429 quitting side 0, mission=e856d0
Regular quiting mission:
04/28 20:07:50.121 Player ManGO@NI(4), ship=429 quiting mission=e856d0, reason=8
04/28 20:07:50.122 SetStage, stage=4, mission=e856d0
04/28 20:07:50.123 sending lobby our mission info for e856d0 listening on port 0
04/28 20:07:50.883 Logoff: ManGO@NI(4)(11007448), was on side=-1 mission=ffffffff.
04/28 20:07:50.883 Destroying ManGO@NI(4), id=429
04/28 20:08:02.972 New connection ID: a417f407 IP: x.x.x.x
04/28 20:08:03.133 New ship (player): Name=ManGO@NI(4), ShipID=491, PilotType=10
04/28 20:08:03.134 Player ManGO@NI(4) logon succeeded. Sent 1 msgs and 2398B to them in 0.001s, and 0 msgs and 0B to others in the process.
04/28 20:08:03.134 Player ManGO@NI(4), ship=491 joined mission=e75dc0
04/28 20:08:03.136 Sending PlayerInfo for ManGO@NI(4) to *AEnima@SysX's game(86504918)
04/28 20:08:11.157 sending lobby our mission info for e75dc0 listening on port 0
04/28 20:09:58.512 Player ManGO@NI(4), ship=491 joined side 0, mission=e75dc0
DirectPlay error (Link dead):
04/28 20:34:12.507 Player ManGO@NI(4), ship=491 quiting mission=e75dc0, reason=9
04/28 20:34:12.507 Player ManGO@NI(4), ship=491 quitting side 0, mission=e75dc0
04/28 20:34:12.510 Destroying ManGO@NI(4), id=491
Last edited by pkk on Mon Apr 29, 2013 5:17 pm, edited 1 time in total.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.