Mandatory Connection Test - should give us an idea of what speeds everyone's running (thanks to Denilson for the suggestion).
As previously explained your bandwidth has very little impact on the overall quality of the connection when it comes to online gaming. You might be running a 56843565 megs connection and still get severely outperformed by someone on a 19 Euro, 1 meg/0.5 meg DSL.
2 megs up and 1 meg down is plenty to host any match in 95% of the online multiplayer games currently out there, fast paced ones and GT5 included, what truly makes or break the experience is latency/stability of the signal.
There is no point in running that test since each of you is targetting a different server whose distances may vary greatly (and that may or may not reside 2 blocks away from someone's place)...it'd be a hell of a lot more useful to pick 3 servers, one that sits in the middle of Europe, one in the US and one in Asia and run 3 separate "
Start>Run>cmd>ping -n 50 server IP address" tests on those, then whoever comes out with the best/more stable results gets picked as host.
Besides, from my experience as the Super GT Italian championship organizer (Nycrom's also in it), the lobby set-up's that will give you the best bang for your bucks is "Very High Quality/
UNfixed host", this way you'll be less likely to get desynchronizations (aka people not seeing each other on track, very annoying) and cars teleporting like crazy all over the track, there won't be mass-disconnections in the occurrance that the fixed host drops and you'll be able to drop the current host and move it to someone else (albeit it's not clear if it actually switches host or just "refreshes" the settings in a shared environment, it's most likely the latter tho) if there's a participant who can't seem to be able to join the lobby (happens a lot, cycling the host fixes it although it's a trial and error process).
It's also PIVOTAL that WIRELESS connection aren't used by anyone during the races: they must be avoided at all costs, regardless of whether you got 100% signal and the router sitting right next to the PS3 or not, they're bound to give you "lag spikes" that are going to ruin everyone else's smoothness as well and generate desynchs no matter what so just get a damn Ethernet cable, they're dirt cheap anyway.
Here's an example of the test mentioned above:
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Primo>ping -n 50 maya.ngi.it
Esecuzione di Ping maya.ngi.it [88.149.128.3] con 32 byte di dati:
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=92ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=19ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=19ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=15ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=19ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=16ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=14ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=18ms TTL=52
Risposta da 88.149.128.3: byte=32 durata=17ms TTL=52
Statistiche Ping per 88.149.128.3:
Pacchetti: Trasmessi = 50, Ricevuti = 50, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 14ms, Massimo = 92ms, Medio = 17ms
On a distinctly separate yet quite personally connected note:
chorda: bumper
KamyKaze1098: premium - cockpit / standart - bumper
johnkiller2: bumper
Nycrom: bumper
maSonn09 - Bumper
Paginas - Hood
cranky123 - hood
cranky456 - hood
GTP_african_kat - bumper
OwensRacing- Bumper for actual race (Cockpit for fun now that I got 3D, SICK)
C-Falcon - Bonnet, rarely Bumper
Centura: Bumper
Scanny_Flick: Bumper
RetriSearain: Cockpit
Sameone can help me? Thank u!
Think I´ll have to go to buy driving glasses...
