Page 3 of 12
Posted: Mon Aug 28, 2006 12:27 am
by mdvalley
I can’t connect to the lobby, either. Maybe the lobby server crashed. Neither my home-built nor the distributed client crashes when it happens. When it tries to connect, it gets zilch for a reply. Pings do get responded to, though.
Spunky, the server app still needs to accept inbound connections. I believe it does it in 2302-2400.
TB, presuming you’re on with Admin access and you don’t have any programs that would block changes to the registry, best I can tell you is to hit Google for it.
Posted: Mon Aug 28, 2006 12:39 am
by Paradigm2
Now I am getting "failed to connect to lobby"
Posted: Mon Aug 28, 2006 1:54 am
by Spunkmeyer
Not the server app, I'm talking about the client.
Posted: Mon Aug 28, 2006 2:43 am
by Dogbones
Was messing around with the beta server this evening if you could not connect.
Get the latest client.
http://fazdev.alleg.net/FAZ/Allegiance_dplay8.zip
And see if you can actually play. Post your experiences (good or bad) here.
Posted: Mon Aug 28, 2006 3:11 am
by Paradigm2
Awsome, I can connect to the game now!!! this is amazing... i'm definately behind NAT and I can definately connect to a game... unfortunately no one else was online to play with...
Posted: Mon Aug 28, 2006 3:41 am
by DasSmiter
hot dog!
now i just need someone to play with!!!
p.s. although not technically a problem i noticed that when connecting to the game server itself it took about 10-15 seconds longer than it did for me to connect to the reg servers 6 months back ( could be connection limits on the server )
what core is that btw?
Posted: Mon Aug 28, 2006 3:56 am
by mdvalley
Connecting to the lobby or a server takes longer for me too. I figure it’s either a slower system on that end, or just a byproduct of the newer code. I played a small game vs dogbones where I showed off my total lack of anything resembling good commanding. His client crashed on an unrelated issue twice, but otherwise it worked as advertised. My end worked without a peep.
I went AFK in noat for an hour or so afterwards, and when I came back, I was looking at the lobby (DPlay session terminated). I dunno if it was a server hiccup or a legitimate error.
Posted: Mon Aug 28, 2006 1:39 pm
by TheBored
Devs and stuff: the new client still doesnt connect, same issue. I will try and fool around with DX9 later today...
TB
Posted: Mon Aug 28, 2006 3:50 pm
by Spunkmeyer
Yup, no go.
Posted: Mon Aug 28, 2006 4:00 pm
by mdvalley
_SRM_TheBored wrote:QUOTE (_SRM_TheBored @ Aug 28 2006, 06:39 AM) Devs and stuff: the new client still doesnt connect, same issue. I will try and fool around with DX9 later today...
I did some poking around online. Make sure you have the latest drivers for everything, including your network card or modem. If there’s a newer one, install it, then try reinstalling DirectX again.
If that don’t work, go to Start-Run and enter
regsvr32 dpnet.dll
Which should put in the right registry entries.
And I’m still able to get into the lobby. Anyone with problems, make sure you have the latest client (posted a little earlier in this thread) and that dxdiag is not complaining about anything.