Hi Graeme, firstly let me reassure you that the points Yunus gave were not some prefab reply or attempt to ignore your concerns. We really did investigate your case, the whole team, because this is exactly the sort of thing we're trying to stop at the moment. Darren (viewer/sim developer) was looking at the history of your connection to the race and saw you coming and going a lot. He had a theory that we could perhaps increase the timeout duration on some settings to prevent this, but in the grand scheme of things it was isolated to you or your race. That's why Yunus said nobody else was experiencing it at the time.
Graeme
Well for stater's it was nothing to do with the router or internet here as i tried it on both laptops and it was the same.
It's not so much which laptop as which internet connection is being used. If they were both connecting to the same router then this won't make any difference. Were they on the same network / router or different ones?
Graeme
To say also that it didnt affect anyone else is wrong as i told you in my initial post that even the host or our league who was watching the race with us said he had problems also. We in our championship usually have 4 of us there watching every race and sometimes more but the chat was like a yoyo with people in and out all over the place.
Are you all based in Australia? Or with the same ISP? Or even in the same location/network? This would be another clue.
Graeme
Every time you tried to adjust your drivers settings or chat and you were gone and booted.
Did it always happen right after you interacted with the interface? That's another interesting clue. It could be coincidence, but it may have been an issue with communication between your device and the server. It could even be a latency issue or timeout happening on these interactions (much as Darren hypothesized).
Of course we understand your frustration. Overall, we've seen huge improvements in the service since moving to the new servers (once we ironed out initial config issues). This may just be another configuration issue that happens to be hitting your region in this manner, and something we need to tweak, because I can tell you that the service is running pretty comfortably since the switch. I realise this is no consolation to you, but it should at least be reassuring to know that this isn't a service-wide issue and we're doing our best to find out what is happening to your league.