UKGPL Season 20 (2010-2011) Graduates Cup (67) - Mosport - Oct 10

[Phil Thornton]

Just found the settings , forgot I had written 'em down at the time ......

Vosb   3/84   3/100

T7      3/84   3/132

I have no idea what these mean or how they effect the server , but would this explain why I could join T7 but not Vosb 3R   

If you want to try to understand it have a look through Bart Westra's pages.  This guy is seriously clever, in fact he wrote the bandwidth patch.

A detailed technical explanation of what 3/84 and 3/100 mean is on this page.  I'm not going to try to paraphrase Bart's explanations it will only confuse matters.

All a bit complicated but I think the simple answer is for everyone to always use the same settings (when starting the servers) then it shouldn't matter which server we join, the client settings will always be OK ( assuming the drivers don't change their settings between races.  My understanding is that the client should be set to be the same or faster than the server).  The recommended server settings for UKGPL are here under paragraph 5.  Easy to say in hindsight, I know only too well it can get very hectic on race night!!

[vosblod]

My understanding is that the client should be set to be the same or faster than the server).  The recommended server settings for UKGPL are here under paragraph 5.  Easy to say in hindsight, I know only too well it can get very hectic on race night!!

Yep that's my understanding too - my home one and UKGPL_6 are set at 100. If I recall we had a bit of debate when 6 was set up and 100 was the number reccomended. It's run many of our races since with no problems.

When you 'remote' host you can override clients so it doesn't matter what the drivers have set. When you host directly (ie from your own pc) you don't get that option so 100 is a good choice as no one should really be set below this figure.
The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

[Hristo Itchov]

The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I never knew or did this. I had always just tried connecting until it works or give up. 

[vosblod]

The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I never knew or did this. I had always just tried connecting until it works or give up. 

Well if you didn't know with your longevity then I guess it's not common knowledge. I must have spent too much time reading GPL forums

[EvilClive]

The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I never knew or did this. I had always just tried connecting until it works or give up. 

You cannot know how relieved I was to read this post, and know that I am not alone, and that my solution to such a problem is precisely the same ...........................

[Tom van Ostade]

Hi all,

I'm only a newbie here with one race under my belt, but I've been racing with the GPLRACER's for a long time.  If I understand it correctly the point of the token system is to be an equalizer so the fast guys have to take slow cars while the slow guys can take a fast car. Currently the chassis choice over at GPLRACER's is of a free choice, but when I first joined them they had a different rule with regards to the 1969 league.

The rule was very simple: Make sure no car is used more than once. If I understand correctly our UKGPL season 20 has more than 7 races, so you could change the rule into 'Make sure no car is used more than twice.'. This way you even have a free chassis choice of some sorts if there are less than 14 races.

For me it doesn't matter, it's more the guys I race with rather than the cars I race in .

Tom.

[maddog]

. . . season 20 has more than 7 races, so you could change the rule into 'Make sure no car is used more than twice.'. This way you even have a free chassis choice of some sorts if there are less than 14 races.

Hmmm . . .  an interesting system.  On the plus side, you'd have a more novel spread of car/driver combinations.  While a minus for some, would be the need to familiarise with more of the chassis.

[Hristo Itchov]

The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I never knew or did this. I had always just tried connecting until it works or give up. 

You cannot know how relieved I was to read this post, and know that I am not alone, and that my solution to such a problem is precisely the same ...........................

It is the Waza way! 

[bernie]

The first thing to do with a repeated time-out is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I wasn't getting timed out , though that's useful info for the future ( If I can remember)

My problem read ...

OPENING CHANNEL
OPENING NETWORK DEVICE
10054 : ERROR DETECTED ON NETWORK DEVICE
CLOSING ...... bla bla bla

My question is ....

How do I stop this error message from happening next time I want to race ?

 

[Hristo Itchov]

OPENING CHANNEL
OPENING NETWORK DEVICE
10054 : ERROR DETECTED ON NETWORK DEVICE
CLOSING ...... bla bla bla

I only get this message when there's a connection problem on my end, i.e. my ISP or something. But I guess it's different in this case since you could connect to other server. Very odd...

[Phil Thornton]

OPENING CHANNEL
OPENING NETWORK DEVICE
10054 : ERROR DETECTED ON NETWORK DEVICE
CLOSING ...... bla bla bla

My question is ....

How do I stop this error message from happening next time I want to race ?

Not sure so the only thing we can do is run a few tests.  I've set my server (UKGPL.4) up on IGOR with the same BW settings as UKGPL.6.  It's running 66 Mosport so it can be used as praccy for Historics Round 1.  The relevant lines in my client core.ini are:

Code:

net_mdm_client_send_every = 3 
net_mdm_client_send_size = 84 
net_mdm_server_send_every = 3 
net_mdm_server_send_size = 384 
net_use_mdm_bandwidth_for_tcp_ip=1 

The key thing is to set net_mdm_server_send_size to be bigger than the server (which in this case is set to 100). 

Try to connect and if you can't try changing net_mdm_server_send_size to 100.  Remember if you do that you will need to change it back before you try to joint T7_2 otherwise you will get the bandwidth mismatch error (because T7_2 will be set to net_mdm_server_send_size = 132).

My server is OK for praccy and testing but I wouldn't trust it for a league race.

[vosblod]

10054 : ERROR DETECTED ON NETWORK DEVICE

I've never had one of those.
Let's see what happens with Phil's test. A search around throws up a myriad of issues but no actual solutions and this is all I could find at SRMZ which seems to indicate we weren't shaking hands properly

You're not running McAfee are you? I found some references to that. Also, are you running IGOR v1.5 - there is reference to occasional errors in previous versions. Just a thought but maybe it was enforcing some kind of maximum latency even though I didn't set that.

Any IT experts out there?

[Ronniepeterson]

I'm no IT expert BUT McAfee security software is a disaster. If you are suffering any regular or random internet and/or network disconnections, chances are McAfee is your problem. At worst disable it and see if the problems go away. Better still use Add/Remove and get rid of it forever and use something like AVGfree. I have removed McAfee from more than one computer ton solve network/internet connection issues.

[FullMetalGasket]

For Gaming I'd reccomend Avast Ronnie, I tried AVG on my gaming rig (hadn't tried it before) and it had a noticable impact on modern games - since removing that and installing Avast the games rig has been perfect 

That said I agree with you 110% about Mcafee 

[bernie]

I binned AVG a few seasons ago because of continual connection problems , I do not have any AV running on my games machine though I was thinking of adding Avast on a trial basis 

Because of all the previous trouble I had, I did a complete re install of GPL using the latest installer prior to S19 

I have had no problems whatsoever connecting anyplace, day, date or time until the S20 grads thing on Vos's laptop server.

Phil I will try your connection though I dont think it will prove anything as the problem seems to be between me and Vos ( maybe its a personal thing "like poles" etc ) 

I'm hoping we dont really need to change settings for different servers , afraid I'm not to good at that sort of thing and tend to dig myself into a very deep hole when I start tweaking ini files etc .