GTP_WRS Week 4: Official Results

  • Thread starter Vaxen
  • 96 comments
  • 7,100 views
Sorry to ask such a noobie question, but what’s the handicap thing & how does it work?

It may be just because I’ve been at work since 9 this morning but I can’t get my head around it, could someone please explain it to me or share a link to a thread that does (I had a quick look but couldn’t find anything)
Later this week, we'll have an initial registry posted, and that should help make things a bit clearer.

This is the old registry (GT6 registry). https://www.gtplanet.net/forum/threads/official-gtp_registry-gt6.297257/

You can see that each driver has a handicap listed next to them.

Some have two numbers.

GTP_Twissy / Twissy / U.K (0.536 / 0.646)

The first number above is the current handicap, while the second is the original handicap for that driver.

In the case of GT6, we ran a qualifier to determine initial placement. But partway through the game, we abandoned it and moved to a system in which 3 event results would determine your division placement.

Each week, we use the overall results for the event to determine a handicap placement for each driver.

In turn, we compare that to your existing handicap. Your existing handicap will be the average of your already completed events (until you have three completed events).

Once you have 3 completed events, we continue to average your performance over a larger cross section of events, to assure we have you placed based on consistent performance.

Using myself as an example, my result this week was a 2.103 handciap, which is good for D2 gold. That was 0.192 better than my current handicap, meaning my current handicap is 2.295.

11--1'22.955---GTP_EDK r=2.103 (d2/-0.192)

Using you as an example, you have a 4.277 this week, which is good for D4 gold. This is 0.042 worse than your current handicap, which means that is at 4.235.

47--1'26.165---Nerazzurri_Outla r=4.277 (d4/0.042)

This stuff at the end is just showing a ranking of drivers and how they compare to their current handicap, in order. This will only show up for drivers who completed 3 events, which is why only 20 of 53 drivers are there.

1---1'23.094---(-0.62332)---routergod24
2---1'23.873---(-0.19157)---GTP_EDK
3---1'23.903---(-0.17482)---Never2fast1
4---1'24.067---(-0.08387)---iMires
5---1'24.096---(-0.06786)---racer_xis
6---1'24.187---(-0.01730)---Espial_
7---1'24.205---(-0.00732)---GTP_Argon
8---1'24.217---(-0.00091)---GTP_NielsG2
9---1'24.289---(0.03917)---GTP_Mini_Stiggy
10--1'24.294---(0.04177)---Nerazzurri_Outla
11--1'24.442---(0.12412)---Need4Speed685
12--1'24.546---(0.18128)---GTP_REMO
13--1'24.660---(0.24488)---GTP_RikWrx
14--1'24.683---(0.25722)---nolucktoday
15--1'24.746---(0.29224)---GTP_Sjaak
16--1'24.896---(0.37581)---GTP_Speedy6543
17--1'25.104---(0.49113)---shoenboggie
18--1'25.353---(0.62907)---mtbmik50
19--1'25.487---(0.70294)---Dougill
20--1'25.504---(0.71277)---crft555
 
I am a rookie so I would like another member to look at your replay but it looks like you are off the track just after turn three.

Having checked the replay I can confirm that it is a dirty lap, sorry @DGiant2000 you went all 4 off at time marker 17.938

GTP_DGiant2000
redflag-gif.152574

You’re quite right guys, I’ve just had another look and you’re spot on. Thanks for checking and apologies for missing it when I looked myself

Ren
Jeeez, quite a few things going wrong this time around :guilty:
DGiant, how could that happen to you buddy, really sorry.

To add my bit to typos and other mishaps: I put typo in when I shared my lap (tagged it gtpwr004 instead of gtpwrS004, droppped the s.)
So I have shared again now, tag gtpwrs004 this time spelled out correctly.
gtpwrs004
branding
exercise

No excuse really mate, submitting in a hurry due to the psn outage and not taking enough care basically. First time it’s ever happened to me but a good wake up call!
 
EDK
Later this week, we'll have an initial registry posted, and that should help make things a bit clearer.

This is the old registry (GT6 registry). https://www.gtplanet.net/forum/threads/official-gtp_registry-gt6.297257/

You can see that each driver has a handicap listed next to them.

Some have two numbers.

GTP_Twissy / Twissy / U.K (0.536 / 0.646)

The first number above is the current handicap, while the second is the original handicap for that driver.

In the case of GT6, we ran a qualifier to determine initial placement. But partway through the game, we abandoned it and moved to a system in which 3 event results would determine your division placement.

Each week, we use the overall results for the event to determine a handicap placement for each driver.

In turn, we compare that to your existing handicap. Your existing handicap will be the average of your already completed events (until you have three completed events).

Once you have 3 completed events, we continue to average your performance over a larger cross section of events, to assure we have you placed based on consistent performance.

Using myself as an example, my result this week was a 2.103 handciap, which is good for D2 gold. That was 0.192 better than my current handicap, meaning my current handicap is 2.295.

11--1'22.955---GTP_EDK r=2.103 (d2/-0.192)

Using you as an example, you have a 4.277 this week, which is good for D4 gold. This is 0.042 worse than your current handicap, which means that is at 4.235.

47--1'26.165---Nerazzurri_Outla r=4.277 (d4/0.042)

This stuff at the end is just showing a ranking of drivers and how they compare to their current handicap, in order. This will only show up for drivers who completed 3 events, which is why only 20 of 53 drivers are there.

1---1'23.094---(-0.62332)---routergod24
2---1'23.873---(-0.19157)---GTP_EDK
3---1'23.903---(-0.17482)---Never2fast1
4---1'24.067---(-0.08387)---iMires
5---1'24.096---(-0.06786)---racer_xis
6---1'24.187---(-0.01730)---Espial_
7---1'24.205---(-0.00732)---GTP_Argon
8---1'24.217---(-0.00091)---GTP_NielsG2
9---1'24.289---(0.03917)---GTP_Mini_Stiggy
10--1'24.294---(0.04177)---Nerazzurri_Outla
11--1'24.442---(0.12412)---Need4Speed685
12--1'24.546---(0.18128)---GTP_REMO
13--1'24.660---(0.24488)---GTP_RikWrx
14--1'24.683---(0.25722)---nolucktoday
15--1'24.746---(0.29224)---GTP_Sjaak
16--1'24.896---(0.37581)---GTP_Speedy6543
17--1'25.104---(0.49113)---shoenboggie
18--1'25.353---(0.62907)---mtbmik50
19--1'25.487---(0.70294)---Dougill
20--1'25.504---(0.71277)---crft555
Cheers @EDK that makes sense now :cheers:
 
Ren
Jeeez, quite a few things going wrong this time around :guilty:
DGiant, how could that happen to you buddy, really sorry.

To add my bit to typos and other mishaps: I put typo in when I shared my lap (tagged it gtpwr004 instead of gtpwrS004, droppped the s.)
So I have shared again now, tag gtpwrs004 this time spelled out correctly.
gtpwrs004
branding
exercise

GTP_Ren
greenflag-gif.152575
 
Replay previously shared with the gtpwrs004 tag.

Pulling flags of required replays from the other thread so Fetchy can see them:

Special_K_2181
greenflag-gif.701695

GTP_RikWrx
greenflag-gif.701695

giznav
greenflag-gif.701695

(checks courtesy @Sjaak)
GTP_GTRacer22
greenflag-gif.152575

(check courtesy @Rikson, who also checked mine)
jfrod52
greenflag-gif.701695

(check courtesy @DeuxMilles)
Bassaddition
greenflag-gif.701695

(check courtesy @Ren)

There were more green-flagged laps, but replays weren't required of those drivers.
 
Don't know why Fetchy didn't catch your green-flag of The_Boss69, but for JamCar0ne, that's a zero, not an 'O', in his PSN. That will throw him off.
 
Let's try Ren's green flag again...

GTP_Ren
greenflag-gif.152575


There seems to be a problem with some best-lap replays cutting out before displaying the lap time on-screen. Turnupdaheat's video did that, but on the Timing Monitor screen, I was able to verify that the lap time was valid as that was fading out. Good thing too, because it allows me to give him a green flag.

turnupdaheat
greenflag-gif.152575


Unfortunately, I couldn't do the same for NaveekDarkroom's lap - that cut out too early.
 
Last edited:
Let's try Ren's green flag again...

GTP_Ren
greenflag-gif.152575


There seems to be a problem with some best-lap replays cutting out before displaying the lap time on-screen. Turnupdaheat's video did that, but on the Timing Monitor screen, I was able to verify that the lap time was valid as that was fading out. Good thing too, because it allows me to give him a green flag.

turnupdaheat
greenflag-gif.152575

Thanks for that :cheers: (and yip Fetchly does not like me at times... Kevin had to put extra effort in just to get him to accept me on the registry...:lol:)

And the replay cutting out too early has happened to me as well, in fact "lost" my best lap with the AMG due to that.... Someone had pointed out to habitually run into the next lap (after the hot one) to the next sector...wise words!
 
Last edited:
Let's try Ren's green flag again...

GTP_Ren
greenflag-gif.152575


There seems to be a problem with some best-lap replays cutting out before displaying the lap time on-screen. Turnupdaheat's video did that, but on the Timing Monitor screen, I was able to verify that the lap time was valid as that was fading out. Good thing too, because it allows me to give him a green flag.

turnupdaheat
greenflag-gif.152575


Unfortunately, I couldn't do the same for NaveekDarkroom's lap - that cut out too early.

Thank you @Eggstor

Hmm, I was pretty sure I had run well into the next lap before stopping so I must check that.
 
  • Like
Reactions: Ren
@EDK, @Vaxen , @monoha

Sorry, but there seems to be some name confusion about monoha. The replay I just checked (very clean and easy to check 👍) was driven by user "monoha" and name in result is "GTP_monoha".

Seems like a trivial **** up, but not sure if the green flag is strictly correct before this is cleared. :confused:
 
@EDK, @Vaxen , @monoha

Sorry, but there seems to be some name confusion about monoha. The replay I just checked (very clean and easy to check 👍) was driven by user "monoha" and name in result is "GTP_monoha".

Seems like a trivial **** up, but not sure if the green flag is strictly correct before this is cleared. :confused:
He's good. We have not posted the updated registry, so we have some guys with pending name changes. We told them they could begin participating with their old registry PSN ID's.

There's also a few guys with [] around their names, those are essentially typos with pending name changes.

Short version: name changes are a pain the 🤬 and we try to batch them together in one shot.
 
@EDK, @Vaxen , @monoha

Sorry, but there seems to be some name confusion about monoha. The replay I just checked (very clean and easy to check 👍) was driven by user "monoha" and name in result is "GTP_monoha".

Seems like a trivial **** up, but not sure if the green flag is strictly correct before this is cleared. :confused:

No different than mine, my replays are remo_of_oz, registry is GTP_REMO just waiting on name changes to go through.

It will be a bigger mess when Sony allows for PSN: name changes lol
 
Mine got shared awhile back then. Still need someone to check whenever I'm going to check any remaining ones if needed.
 
Once Fetchy catches up with the green flag for Ph1sh (Vaxen has fixed the time), that leaves two to go, plus a third where the final time cannot be verified because the replay cuts out too early:

[PSDazmaniac]
nail-27
NaveekDarkroom (replay is clean, and the first 3 splits match what is on the board, but the replay cuts out before the final time is displayed anywhere)
 
Once Fetchy catches up with the green flag for Ph1sh (Vaxen has fixed the time), that leaves two to go, plus a third where the final time cannot be verified because the replay cuts out too early:

[PSDazmaniac]
nail-27
NaveekDarkroom (replay is clean, and the first 3 splits match what is on the board, but the replay cuts out before the final time is displayed anywhere)

nail-27 is in the same position all splits match but replay freezes before the line - have asked for guidance :)
 
Back