Quarterly cost: 0
 
November 25, 2017, 09:19:26 AM +0000 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
Series
S3255F1
S3267GT
S3267P
S3267W
S32His
Recent
S3267P Salzburgring
S3267W Salzburgring
S3267GT Monza (10km 19…
S32His Zandvoort (1939…
S3255F1 Zandvoort (194…
Forthcoming
S3267W Monza (GP 1955-…
S3267P Monza (GP 1955-…
S3267GT Targa Florio
S32His Aintree
S3255F1 Aintree
 
   Home   Help Search Calendar Login Register     LM2 Replays Rules Links Circuits Teams  
Linked Events
  • S31His Hockenheim: June 18, 2017
June 18, 2017, 09:36:53 PM +0100 - Hockenheim (1965-2001) - UKGPL Season 31 (2017) Historic Trophy (66)
Driver
 Team
Nat. Make Model Class Qualifying Race
Tyres Pos Time/Gap Pos Time/Gap Laps Stops Best Retirement
reason
Ballast
Samb
 Black Night Racing
Eagle T1F (Climax) F1 1966 2 +1.803
127.492mph
1 50:36.735
125.500mph
25 1:59.282
127.801mph
Goodyear  
AndyL
 
BRM P261 (1966) F1 1966 8 +2.838
126.398mph
2 +2.071
125.414mph
25 1:59.233
127.854mph
Goodyear  
Doni Yourth
 Blue Moose Racing
Lotus 33 (BRM) F1 1966 7 +2.788
126.451mph
3 +8.758
125.139mph
25 1:59.234
127.853mph
Firestone  
bagrupp
 Team Groundhog
Brabham BT11 (Climax 2.7) F1 1966 9 +3.532
125.675mph
4 +9.818
125.095mph
25 1:59.417
127.657mph
Goodyear  
AnGex
 Black Night Racing
Ferrari 246 F1 1966 4 +2.144
127.130mph
5 +11.589
125.023mph
25 2:00.035
126.999mph
Firestone  
Phil Thornton
 Antipasti Racing
BRM P261 (1966) F1 1966 11 +4.699
124.477mph
6 +1:12.652
122.567mph
25 2:01.151
125.830mph
Goodyear  
francesco
 Antipasti Racing
BRM P261 (1966) F1 1966 5 +2.272
126.994mph
7 +6L
122.210mph
19 2:01.058
125.926mph
accident
Goodyear  
MagicArsouille
 
Eagle T1F (Climax) F1 1966 3 +2.098
127.179mph
8 +13L
124.383mph
12 1:59.520
127.547mph
Disco
Goodyear  
EvilClive
 Blue Moose Racing
Brabham BT11 (Climax 2.5) F1 1966 10 +3.532
125.675mph
9 +0.677
124.325mph
12 2:00.203
126.822mph
Disco
Goodyear  
Cookie
 Antipasti Racing
BRM P261 (1966) F1 1966 1 1:57.768
129.444mph
10 +17L
126.535mph
8 1:58.963
128.144mph
Disco
Goodyear  
DLogan
 
Brabham BT11 (Climax 2.7) F1 1966 6 +2.708
126.535mph
11 +25L
---
0 ---
---
Disco
Goodyear  
Rainier
 Black Night Racing
Lotus 33 (BRM) F1 1966 12 +7.884
121.322mph
12
---
0 ---
---
Disco
Firestone  
4 UKGPL
 
BRM P261 (1966) F1 1966 13 14 DNS ---
---
Goodyear  

Moderator's Report

Summary

A couple of drivers suffered from laggy connections but overall it was a clean race with no reported incidents. Sam ended up on the top spot to secure the championship in style. Well done Sam, just reward for clean and consistent driving all season. Second place went to Andy Livingston who dropped to the back of the field in the early stages but gradually worked his way to the front. Another couple of laps and he might have been able to challenge for the win. Doni secured third place on the podium with a spirited determined drive.

The Hockenheim circuit produced some great racing for the 66 cars, the generous slipstream modelling ensuring that the bunch stayed together. Congratulations to everyone on clean competitive racing.

SimRacing.org.uk Lap Records
Grand Prix Legends
F1 1966
1:57.768
129.444mph
Cookie
Qualifying
BRM P261 (1966)June 18, 2017, 09:36:53 PM +0100
S31His
Grand Prix Legends
F1 1966
1:58.963
128.144mph
Cookie
Race
BRM P261 (1966)June 18, 2017, 09:36:53 PM +0100
S31His
Pages: 1 2 [3]
  Print  
Author Topic: UKGPL Season 31 (2017) Historic Trophy (66) - Hockenheim - Jun 18  (Read 1179 times)
0 Members and 1 Guest are viewing this topic.
Cookie
UKGPL Divisional Moderator
UKGPL Moderators
Sr. Member
****
Posts: 3626


Chris Amon fan


View Profile
« Reply #30 on: June 22, 2017, 02:26:20 PM +0100 »

The GPL Multiplayer engine was built in 1997-98, so the connections were via 56K modems or better when you had ISDN.
The paquet size is 84 bit for the client -> server and 384 from server to client!

So we should have lots of reserve to have a good race....

BUT

The providers want to maximize their profits and fill their cables with as much traffic as possible,
so I learned that it depends a lot of the recent traffic in the net
and how good anyone conected to the next net main knot.

Warping and partially absent clients stress the servers ability to give the position of such drivers to their opponents.
Logged

Axel "Cookie"

Poor man, not seeing the stars without being hit in the face.
My translation of an aphorism of  Stanislaus Jercy Lec
EvilClive
UKGPL Senior Consultant
UKGPL Moderators
Hero Member
****
Posts: 5038


I always play by the rules.... they are MY rules!


View Profile
« Reply #31 on: June 22, 2017, 03:23:11 PM +0100 »


"So does that mean a laggy connection is simply down to luck?  Once the packets are out on the internet the switches can route them anywhere."

I know that I am a simple soul when it comes to computer stuff but....

 If the above statement is true, then would that not result in latency being a random event and not a regular predictable lag that I was getting? I am assuming that the route and therefore the hops would vary throughout the race as each packet is sent/received? or is it a case that once the connection and route are established at log-on to the server, everything goes that way until the connection is lost?
Logged

Evil Waza, now a completely reformed character!

Rank   Only when I sweat
dave curtis
Full Member
***
Posts: 640



View Profile
« Reply #32 on: June 22, 2017, 07:00:01 PM +0100 »


Just a suggestion & mileage may vary...

If you have another PC available on the same network as the client machine [surely everyone has a couple of old spares floating around/hidden in the loft?!] - then you could maybe try running a tool such as PingPlotter & point it at the GPL server address as indicated in iGOR race list.  There is a free version available at https://www.pingplotter.com/products/free.html.

Granted, this is not sending 'proper' race traffic,  but may give an indication of potential issues & whether it's a local network or somewhere in the middle.

If the GPL server is not replying to ping requests [most likely if the firewall feature set on the remote side is doing its job too well & silently dropping them] then the endpoint will show as non-responsive/100% loss,  but the details from the previous hop may still give an indication of overall health.


Cheers,
Dave.
Logged
Pages: 1 2 [3]
  Print  
 
Jump to:  

Hosted by DaveGymer.com
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.71 seconds with 52 queries.
anything