|
Post by scoops on Sept 19, 2014 21:43:36 GMT
I've now had 3 dropped connections in the last 2 Fridays and I noticed tonight that the internet was fine and it was just rFactor?
i'm thinking it might be the connection settings within rFactor? I seem to remember having to slow the connection down before so that the server can cope. Is there a possibility that my PC is sending too much too quickly and getting dumped off the server?
If anyone else has fibre optic can you let me have your connection settings to try, cheers
|
|
|
Post by brucey on Sept 19, 2014 22:18:12 GMT
The only time I kept loosing connection was when I didn't have my pc connected with an Ethernet cable, so it was relying on wireless.
I'm running fibre optic on standard (default?) settings. If you tell me how to find them, I will send you my setting info.
|
|
|
Post by Si on Sept 20, 2014 8:18:44 GMT
When I had fibre I found that setting the connection to Cable\DSL gave me a stuttery connection. So I dropped it to 256kbps. I doubt any of you should really have this setting on Cable\DSL as it just makes your PC ask a lot of your bandwidth and rFactor can run on less. However this may be a server issue since I moved and my broadband bandwidth up\down was reduced. From an ISI page I found this: Another way of limiting bandwidth is only available through editing the multiplayer configuration file (found by default at UserData/<your name>/multiplayer.ini). You can limit bandwidth on a per-client basis by changing the Max Data Per Client setting. For example, say you have some clients joining with cable connections (let's say 256kbit connections) and others joining using ISDN (64kbit). You may want everyone to experience the same connection type to your server, so you could change the Max Data Per Client to 64, which will limit even the cable clients' connection to be the same as the ISDN clients. Clearly, you can then easily calculate the maximum upload bandwidth you will be using. With 15 clients, you will be using no more than 15 * 64 = 960 kbits/sec. You might note that if this exceeds the Upload Speed you configured, bandwidth will be limited to the Upload Speed instead. Therfore, I'm adjusting Max Data Per Client today on the server. This by default was 9999, so it was dependent on each client getting what it asked. I'm going to drop it to 64. This is because I get just over 1Mbps up on my broadband. Now I need some for Teamspeak and the rest should be divided by our max driver count. 14 * 64 = 896kbps So I have some free for TS and if the wife or kids sneak on to check web etc, while we are racing. If this needs pushing up, then I'll gradually increase it. But we only have a max of around 1.07Mbps here until 2015 when I've been told that those on exchange only lines may get a chance of fibre.
|
|
|
Post by cageyh on Oct 11, 2016 7:42:43 GMT
Is this the same for rFactor2? This could be my issue...
|
|
|
Post by Si on Oct 11, 2016 8:19:39 GMT
That setting exists in rFactor2, but I was assuming it is a server based setting. The rFactor2 server is set at 64. By all means, you can change your local multiplayer file, but I don't think it will make much difference.
|
|