Okay... I started a server, GTR3 + all ADAC. Current tracks: Raceroom Raceway Grand Prix Portimao Grand Prix Nürburgring Grand Prix Red Bull Ring Grand Prix Zandvoort Grand Prix The server's name is Casual Race Club 78512 (The number does not mean anything, it's just for solving my problem losing servers with following unavailable server names)
Don't know why, but my server is gone... I have to set it up from scratch... the generic number will change when it's done. Can anyone tell me why my servers regularly are disappearing?
Now then, Was good to race with a few of you the other night...Was thinking maybe we could have a mini season if anyone is interested? 8pm Monday night or somthing.....just 15 mins qualy and a 15 mins race. Could run in maybe 4 week batches..American season, Asian and OZ, European....Would be easy enough to keep track. Anyone interested?
Yes... would be great... but as long as Andrew has these problems with lag on my server... this is a bit pointless for me hosting this. I don't know what the problem was, large grids where possible without lags, but Andrew always had this lag even with only three or so players connected.
Ah thats a bit annoying, we need Andrew to be able to connect. Lets try diagnose when you get a spare few mins: Andrew, first test your own pc - all the below is done in the CMD prompt: Run Ping Loopback test. The Ping loopback test will test your computer’s connection to verify that there are no local hardware problems causing the network or internet latency issue. Type “Ping 127.0.0.1 -n 20”. This IP address is the same for nearly all built in network connections, the “-n 20” extension will send 20 packets of data before terminating the test. If you forget to type “-n 20” you can cancel the test by entering Ctrl+C. View the statistics. The time it took for the packet of data to travel locally should be less than 5ms and there should be zero packet loss Now ping the server (Paradox will need to supply the IP address here) Type “Ping” followed by the IP address or site URL you wish to ping and hit enter. You may want to start with the URL of your internet service provider and proceed to other sites you commonly access. View the report. As the test pings the remote address, it will report back the results, the final number after the “time = “ is the time it took, in milliseconds, for the packet to travel to the remote site and back to your computer. Note: the “-n 20” extension works with this command, as does the “Ctrl+C” should you forget to enter it. Now try establish where the problem is: Run Traceroute test. The traceroute test will show the path that data travels from your computer to the remote server and any delay in that path. This can be helpful in determining the source of network or internet delays. Type “tracert” followed by the IP address or site URL you wish to route and hit enter. View the results. As the test traces the path it will display each address along the way and the time it took for a data packet to travel and acknowledge receipt for each “hop” along the path. The more “hops” or other devices the data packet needs to route through, the more delay you will experience. I might not know how to fix but I am sure we can get some geek help at this point.....
Don't know if Andrew's only currently, according to steam friends he is not. As my IP changes at least once a day, my current one does not help out here as long as he does not perform the test until my router's next restart. At my end, there was nothing running in the background consuming bandwith. Steam is not allowed to do updates when playing raceroom and I did not have any browser window opened when the lag occured. BTW: Andrew mentioned he had this lag on another server too.