Is Kaillera Confused or Something... .____.

[Korrupshen]

Ok....I've tried many clients, and they all give me some dumb result. First let me talk about "Kaillera P2P and Client". I'm able to connect Sonic Cage Dome which is in NY with pings like 13ms to 30ms, but I can't connect to Galaxy 64 which is also in NY which gives me pings in 300ms to 900ms. It has wondering is Galaxy64 really located in NY, because I can connect to a server in Rio de Janeiro with pings like 115ms to 130ms. I'm like WTF. I'm pretty sure I'm no where near Rio de Janeiro, yet I have a lower ping than Galaxy64.



Now lets talk about "Dolphin's kaillera client". Ok in this client I can Connect to a Server at WTF speed. In Galaxy 64 I get pings sometimes in to 30ms to 165ms, but I rarely get a 2 digit ping. In Sonic Cage Dome I once had 0ms, but I mostly get 13ms to 30ms. Just like the first client I spoke about. They this the client was stable, yet after a couple of trys I get a core core initialization error, which still pops up after I shut down the kaillera/program and start it up again.

Next lets talk about "Supraclient", sometimes days I connect really fast others it takes me a while to connect, but with Sonic Cage Dome I can connect automatic. The thing is nobody is hardly on Sonic Cage Dome. For galaxy 64 I have to connect to the server, which doesn't even let me connects and wait three min so I can actually connect to the dang thing, and sometimes if I relogin it doesn't connect right away it just says it connecting.

Finally I talk about the "Official Kaillera Client", which takes AGES or NEVER for it to connect. Galaxy 64 nor Sonic Cage Dome, niether of them I can connect to.

I've had about 3 routers, and they all do the same thing. I remember in the past when EGX was still up, and same **** happened.

So I don't really know whats the problem....

 

[Lordsmash]

First off, P2P has nothing to do with kaillera, P2P is its own thing, older p2p versions have kaillera support with servers though. Also what client you use has NO EFFECT whats so ever on how long it take to connect to a server unless you spoof your ping with the crash client. And when it keeps connecting thats for 2 reasons, The server is 1000+ ping for you, or no one is currently hosting the server and its just in history on raw server list. Just go to normal servers like galaxy64 and sonic cage demo. If your ping is high still like in 200 and stuff just p2p.

 

[KoRoBeNiKi]

are you trying to access Galaxy64 from the IP's from our thread or was it an old file? If it was an old file, try deleting the ip and re-entering it from the index thread.

 

[Korrupshen]

I would use p2p but its hard to find people who wanna p2p. I would go to Sonic Cage Dome , but no one plays ssb64 there. I will play with people offline, but you don't find a lot of people who play 64 or even have one anymore these days.

l'm using the newest Galaxy 64 IP, I pretty sure that isn't the problem. I was wondering does it have to do with the server version, listed on the master server next to the server's ping if I'm not mistaken,but its on supraclient.

Anymore solutions throw em at me :]

 

[StealthECartman]

Im down for p2p whenever, Korrupshen. Also anyone else that wants to play from the US/Canada

 

[firo]

It's possible that the route the signal takes to get to the server is causing high ping.

Go to start, run, type in "cmd" (no quotes) and then type

tracert 69.90.34.245

and note the highest jump in ms time (forget the time-outs if there are any). This should tell you if the ping is low before it gets to the server. (You should do this with the ip of sonic cage dome as well). If you are getting such drastic ping differences it's possible that your connection isn't too stable.

 

[Korrupshen]

Im down for p2p whenever, Korrupshen. Also anyone else that wants to play from the US/Canada

LMAO ur pro and I might get ***** though, it wouldn't hurt to try. I'll give it a shot, I have to use gc controller which kinda sucks. Anyways can you host 7:30 EST I'm kinda new to p2p, I just set it up yesterday.

It's possible that the route the signal takes to get to the server is causing high ping.

Go to start, run, type in "cmd" (no quotes) and then type

tracert 69.90.34.245

and note the highest jump in ms time (forget the time-outs if there are any). This should tell you if the ping is low before it gets to the server. (You should do this with the ip of sonic cage dome as well). If you are getting such drastic ping differences it's possible that your connection isn't too stable.

This is for Galaxy 64


Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.westell.com [192.168.1.1]
2 28 ms 25 ms 25 ms 10.32.177.1
3 26 ms 26 ms 26 ms P10-3.NYCMNY-LCR-09.verizon-gni.net [130.81.135.
64]
4 37 ms 26 ms 26 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.29.236]
5 27 ms 28 ms 28 ms 0.so-3-3-0.XL4.NYC4.ALTER.NET [152.63.10.25]
6 28 ms 28 ms 27 ms 0.xe-7-1-0.BR2.NYC4.ALTER.NET [152.63.3.170]
7 31 ms 28 ms 28 ms 192.205.34.49
8 30 ms 28 ms 29 ms cr2.n54ny.ip.att.net [12.122.86.10]
9 29 ms 28 ms 27 ms gar1.nyzny.ip.att.net [12.122.130.125]
10 29 ms 29 ms 28 ms 12.118.100.58
11 * * * Request timed out.
12 * * * Request timed out.
13 30 ms 30 ms 29 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

This is for Sonic Cage Dome


Tracing route to 69-90-34-38.ny.atlasservers.com [69.90.34.38]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.westell.com [192.168.1.1]
2 29 ms 26 ms 27 ms 10.32.177.1
3 26 ms 26 ms 29 ms P10-3.NYCMNY-LCR-09.verizon-gni.net [130.81.135.
64]
4 33 ms 26 ms 26 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.29.236]
5 27 ms 28 ms 29 ms 0.so-4-0-2.XL4.NYC4.ALTER.NET [152.63.1.57]
6 38 ms 30 ms 28 ms 0.xe-7-1-0.BR2.NYC4.ALTER.NET [152.63.3.170]
7 29 ms 28 ms 28 ms 192.205.34.49
8 29 ms 28 ms 27 ms cr2.n54ny.ip.att.net [12.122.86.10]
9 28 ms 29 ms 29 ms gar1.nyzny.ip.att.net [12.122.131.117]
10 28 ms 28 ms 33 ms 12.118.100.58
11 * * * Request timed out.
12 * * * Request timed out.
13 29 ms 29 ms 30 ms 69-90-34-38.ny.atlasservers.com [69.90.34.38]

Trace complete.


Is any of this normal

 

[Ownasaurus]

That looks fairly normal... but a touch slow for cable. Is this verizon DSL or FiOS? I'd say these are normal speeds for verizon DSL. As a cable use, I ping my provider's hardware (the first few hops) at about 10ms.

 

[Korrupshen]

That looks fairly normal... but a touch slow for cable. Is this verizon DSL or FiOS? I'd say these are normal speeds for verizon DSL. As a cable use, I ping my provider's hardware (the first few hops) at about 10ms.

Yup I'm using Verzion DSL

 

[Korrupshen]

bump bump bump

 

[Blue Yoshi]

avoid double posting if possible. People will respond, they just aren't at the computer yet (maybe at school or at work).

 

[firo]

Korrupshen I would try all possible troubleshooting solutions you can think of. Changing your router setup, trying a different computer in the house, changing kaillera files and emulators, making sure that no one else is using the internet when you are trying to log on....

If there are a lot of people on the server its possible that it is taking your connection a longer time to gather the users and their statuses - I would try logging when there is less people online to see if that makes a difference.

 

[Korrupshen]

Korrupshen I would try all possible troubleshooting solutions you can think of. Changing your router setup, trying a different computer in the house, changing kaillera files and emulators, making sure that no one else is using the internet when you are trying to log on....

If there are a lot of people on the server its possible that it is taking your connection a longer time to gather the users and their statuses - I would try logging when there is less people online to see if that makes a difference.

I tried all of those, kaillera just hates me. I'm trying it now, and I'm only one online. I used a different computer a month ago and still have this problem, and I tried every client known to man. The only client I can connect to a server with no problem is Dolphins client. My ping is stable at 156 on Galaxy 64 no matter how many times I connect. With Supraclient I can get lower pings for Galaxy 64. There was one time my ping was 31ms on Dolphins client. I never seem to get a ping lower on Galaxy, it effects my gamplay badly since its 9-11 frame delay. At Sonic Cage Dome I can get 31ms sometimes 15ms on Dolphins Client. I would be using that client if it wasn't for core initialization error I get time and time again, and the annoying frame delay. Each client seems to work different when I'm trying to connect to a server. Might as well give up. I've been trying to figure this out for months now and nothing. Also, the computer I'm using cost as much as an Alienware M15x, I didn't even have for a 4 months yet. So its still pretty new.