17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Moderator: Paul Skingley

Benutzeravatar
MLGathome
Moderator
Moderator
Beiträge: 465
Registriert: Mi Dez 12, 2018 4:56 pm

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von MLGathome » Do Nov 19, 2020 6:53 am

ErikHeijden hat geschrieben:
Mi Nov 18, 2020 2:57 pm
MLGathome hat geschrieben:
Mi Nov 18, 2020 10:52 am
The lapping driver should adjust his speed and wait for an opportunity to make a save pass.
Wait for the next straight and don't hit me from behind on the exit of the corner. Thanks for the understanding.

Greetings, Marcel
I did not hit you from behind, Pete steered into me and that put me on your trajectory
You came out of the hay bales and were rejoining the track. I'm sorry for the end result but I don't see how I was in the wrong here.
Hi Erik,

I wasn't refering to this incident. As Peter said, race incident. I already moved on the next morning.
It was a general remark for drivers who overlap another driver. You have to adjust your corner speed or you run into the rear of the slower car.
An avoiding maneuver is necessary where an easy overtake on the next straight is possible. I see that a lot.
The save overtake is the responsibility of the faster driver. The slower driver should only help him to do so.

Greetings, Marcel
Übung macht den Meister, aber mir macht es nur spaß. :)

Benutzeravatar
Stefan Roess
Site Admin
Site Admin
Beiträge: 983
Registriert: Fr Dez 07, 2018 1:24 pm
Wohnort: Germany
Kontaktdaten:

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Stefan Roess » Do Nov 19, 2020 8:47 am

Speaking of overtaking I may point to this guide again.
Even after many years of Sim Racing, it doesn't hurt to take a look now and then.

GPL Recommended Driver Behaviour
http://www.gplworld.de/en/grand-prix-le ... -behaviour

Original English text "Recommended Driver Behaviour" by Phillip McNelley © 1999
Homepage: http://wiki.grandprixlegends.info/index ... _Behaviour

German translation by Stefan Roess © 2004 and 2019
Homepage: http://www.gplworld.de/grand-prix-legen ... -verhalten


This is the part about overtaking:
Overtaking

The Non Contested Pass
A non contested pass is simply a pass where you're happy, for whatever reason, to let an overtaking driver go past with the least hindrance to them as possible. Your reasons may be that you don't want to risk an incident due to an overtaking battle, the overtaking driver may be known to you as a notorious accident causer, or you may be being lapped - in which case race etiquette requires you to do what you can to expedite a clean quick safe pass for the lapping driver. Whatever the reason, there may be times when you want to let someone past.

To let someone past uncontested, drive against one side of the track and maintain that position until they’ve passed. You need to use clear body language here. Moving from side to side trying to stay off the racing line, for the sake of the passing car, is the worse thing you can do. What’s important is not weather you’re on the racing line or not, but whether you’re driving a predictable line. Pick a side of the road to move to, usually the one you’re nearest to at the time, then religiously stay against that side until the car has passed. You might even try slowing a little to expedite the pass, as sometimes a quick pass can benefit you as much as it does the passer. But don’t slow down too abruptly of course.

In GPL during the race, if you're being lapped by another car you'll be shown blue flags by the marshals. These are advisory flags to let you know your about to be lapped and you're expected to do the gentlemanly thing and move out of the way.

Bild
In GPL, you may not always see all the cars behind you in your mirrors at a particular time. There may be several unseen cars close by around your tail. You may only ever see whichever one happens to be in your mirror's field of vision at the moment. This has special significance when you're being passed - with or without blue flags being waved.

If you're being lapped, perhaps with blue flags but whenever, be aware there could be any number of lapping cars right on your gearbox even though you don't see them. What can happen is this ... You see a car coming up in your mirrors, maybe you also see blue flags, you think " there's a car lapping me I'll move over to let him pass", you move to one side of the road and let him through, you then move back onto the racing line and BAM, you've hit someone. It turns out there was more than one car lapping you. When you moved over to let the first one through the others tried to go through too, as you'd expect. But while you were on the other side of the road, they were out of you mirrors, you simply never got to see them.

This can really take you by surprise, and them too. All you can do here is be as careful as possible, look around if you're able too, try to shy a glimpse, listen for more engine sounds, toggle the arcade view for a moment. They can help by trying to show themselves in your mirrors before going through. Be aware that just because you see one car go past that may not be the end of them. Whether after a blue flag or whenever, as the same limitations always apply.

The drivers doing the lapping / passing should also bear in mind these limitations. You ( passing drivers ) be aware that the car you're lapping may have absolutely no knowledge of your presence what-so-ever. Be careful. You should always try to show yourself in the mirrors of an ahead car before trying a pass.


The Contested Pass
The contested pass, or the pass done in anger, whatever you want to call it, is arguably one of the most difficult things to do cleanly without incident in GPL. Battling for position, passing and counter passing, wheel to wheel racing, is also the most fun thing to do.

The problem with close racing of any sort, contested passing included, is largely one of what each driver in the situation can see of the other. Most people I've raced with are fair and don't mean to cause accidents. Most aren't reckless. Its just that there's a lot of guessing going on about exactly where and how close you are to another driver. The GPL range of vision is much less than real life. There are huge blind spots to contend with. In fact the restricted visual range in GPL is so much a factor in close racing situations it warrants a detailed discussion in itself. The contested pass then is all about what you can and can't see.

Bastian Grupp
Chef-Fahrer
Chef-Fahrer
Beiträge: 120
Registriert: Mi Jan 16, 2019 8:50 am

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Bastian Grupp » Do Nov 19, 2020 11:16 am

Difficult but satisfying race for me. I had a online meeting and was short to prepare the track. (as most of times)
So i was very cautious in practice not to stand in the way and to learn the track at the same time.

Fortunately the track was not so difficult and it went well, even found a setup thats ok.

Good start, won some places In Lap 3 my race was nearly over when hitting the hayballs quite hard.
You see it a little bit in Youtube on 3:12. It took me 45 Seconds to rev myself free with danger of losing the engine.
Race was in danger two more times when i missed a corner and spun.

In the end i was quite surprised keeping Pauls speed after lapping, i thougt he need to save fuel or anything.
I must have been very lucky with my setup, this is often roulette for me.


I wanted to see also the incident Erik/Marcel but i think the Race video does not capture all incidents ?
There is also no focus on me in Lap 3. Just as a question.

Benutzeravatar
Stefan Roess
Site Admin
Site Admin
Beiträge: 983
Registriert: Fr Dez 07, 2018 1:24 pm
Wohnort: Germany
Kontaktdaten:

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Stefan Roess » Do Nov 19, 2020 6:59 pm

pmercal hat geschrieben:
Mi Nov 18, 2020 9:04 pm
I reviewed the race on Youtube and I wanted to give 2 thanks.
1 Thanks Stefan, it's really great to put on your slippers and have fun 45 min. on the sofa. :handgestures-thumbup:
It's nice to see the many duels that have taken place, maybe the real races were so exciting. :o
Nice that you (and others) like it and that I do not waste my time on this. :clap:
I also like to review the race(s) on YouTube. :)
Bastian Grupp hat geschrieben:
Do Nov 19, 2020 11:16 am
I wanted to see also the incident Erik/Marcel but i think the Race video does not capture all incidents ?
There is also no focus on me in Lap 3. Just as a question.
I also noticed in the race videos that not all race incidents are focused by the Replaydirector patch.
I persume that there is some other action going on in the same moment with a smaller distance between the drivers than that of the incident. And Olaf has adjusted the patch so that the camera does not change quickly from one car to another car within a very short time. Which would make it very confusing to watch. You can see that quick switching at our first GPLRACER race video of the 65 race at Firebird.

This should be the reasons that it does not display all incidents that happen.

Here is a part of the Replaydirector readme_rd.txt:
http://srmz.net/index.php?showtopic=12427
...
The focus will be set at the drivers with the smallest distance and the type of camera will be changed between TV1, Onboard and TV2 view. When then smallest distance increases to more than 150 metres the focus will be set to the leader.
...

But it is possible to adjust the settings of the patch. Atm I am using the default settings because I didn`t have the passion and time yet to take a deeper look into this. But the GPLRACER winter break is coming to have a closer look into this and see if it can be optimized. :)

Here is the Replaydirector readme_rd_forspecialists.txt of the patch zip (it also gives more insight how the patch works):
You are specialist, YOU can change the cameratypes and adjust the distance for switching on near- and farcamera and adjust the distance at which the focus will be seted at the leader in replaydirector.

To adjust something you have to open replaydirector with editor.

At the beginning of the file you find this:

<BinaryPatch>
<VirtualAddress>0x00474331</VirtualAddress>
<Data>6681FA 1040 7906C700 11 000000EB54</Data>
</BinaryPatch>

Such an part of the file I call a sequence. So this is the first sequence. The important part is the line started with <Data>.
The separated values are the values you need, in the first sequence 1040 and 11.
11 is the number of near-camera type.
In the second sequence is 01 the number of middle-distance-camera,
and in the third sequence is 12 the number of far-camera type.

These are the numbers for the cameras:
01 = Onboard view
06 = camera from behind the car (F10 view)
0E = rear suspention
11 = tv1
12 = tv2

In exemple: If you would change the far distance camera to tv1 change in the third sequence number 12 to number 11.

1040 in the first sequence means the camera will be set to the near-distance camera when the nearest distance is smaller than the value.

This values are (parts of) floating point values (type float). Think about it: The most significant byte is the last byte, in this case 40 and not 10.

Some values in decimal translation:
803F = 1
0040 = 2
1040 = 2.25
0041 = 8
0042 = 32
8042 = 64
0043 = 128
1843 = 152
4843 = 200
0044 = 512

So you see in the table the near distance camera type will be set if the smallest distance of all drivers is 2.25 metres (1040=2.25m)

In the second sequence you find the value to adjust the distance for middle distance camera.
The value for middle distance camera type works different to the other camera values. 42 means middle distance camera will be set when the distance of the nearest drivers is between 32m and 128m. When you would set this value to 41 it would be between 8m and 32m.
In the third sequence you find the middle distance camera type.

4843 (200m) in the forth sequence is the comparision value for far distance camera. So...if the nearest distance is more than 200m the far distance camera will be set.

With standard values the camera type stays where it was before when the nearest distance between drivers is between 2.25m and 32m or between 128m and 200m.


In fifth and sixth sequence you find values that determinates at which distance the focus will be set at the leader.
1843 in fifth sequence is the value at which the focus will be set at the leader: Is the distance between the nearest drivers more than 152metres the focus will be set at the leader.
8042 in sixth sequences determinates when the focus will be switched back from leader to the drivers with the nearest distance.
If the distance is between the values in fifth and sixth sequence the focus stays at the leader or at nearest distance drivers - where it was before. So think about it: If you set the values in the firth and sixth sequence with too less difference the focus will be switch very often between leader and nearest drivers.




With the seventh sequence you can force near distance camera type (normally: tv1) in generally at determinated laps (default is 06):
06 = tv1 view in the first, second, 9th, 10th, 17th, 18th...and so on...and in the last lap
07 = tv1 view in the first, 9th, 17th ...and so on...and in the last lap
03 = tv1 view in the first, 5th, 9th, 13th, 17th, 21th...and so on...and in the last lap
01 = tv1 view in the first, 3th, 5th, 7th, 9th, 11th, 13th, 15th...and so on...and in the last lap
FF = tv1 view only in first and last lap
In the other laps the automatic camera switching determinated by values in the first four sequences works.

That's it. I hope it's understandable.


ONLY IF YOU WOULD UNDERSTAND THE FLOAT VALUE SYSTEM BETTER READ THIS:
Float values have 4 Bytes. Every byte have two digits in hexadecimal number system.
Decimalvalue 2 is really not 0040, but 00000040.
Replaydirector compares only the both most significant bytes. So I cut out the both least significant bytes.

If the high value byte increases by 1 the decimal value will be multipliesed with 4, i.E.:
0040 is decimal 2
0041 is decimal 4 * 2 = 8
0042 is decimal 4 * 8 = 32
and so on.

If the least of the both high significant bytes is 80 the decimal value will be twice as much as the byte would be 00, i.E.:
0040 is decimal 2
8040 is decimal 2 * 2 = 4
0041 is decimal 8
8041 is decimal 2 * 8 = 16
and so on.


If the least of the both high significant bytes is C0 the decimal value will be be multipliesed with 3, i.E.:
0040 is decimal 2
C040 is decimal 3 * 2 = 6
0041 is decimal 8
C041 is decimal 3 * 8 = 24
and so on.

The other values are consistent between 00xx and 80xx or between 80xx and 0Cxx, i.E.:
4040 is in the middle between 0040 and 8040. So it's decimal 3.
2040 is in the middle of 0040 and 4040. So it's decimal 2.5, and so on.

A040 is in the middle between 8040 and C040. So it's decimal 5.
9040 is in the middle between 8040 and A040. So it's decimal 4.5, and so on.


REMARKS

The declaration for values is for the_livestream version.
For _savedReplays version you have to multiply to all values 1.44 (i.e. 32 = about 46)

Bastian Grupp
Chef-Fahrer
Chef-Fahrer
Beiträge: 120
Registriert: Mi Jan 16, 2019 8:50 am

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Bastian Grupp » Fr Nov 20, 2020 9:00 am

cool, yes i was reminding saying that it switches too fast on the first movies.

maybe Olaf can also teach the tool to recognize abnormal movement (contacts, slides, spins, offtrack) and then focus on these.

Benutzeravatar
Paul Skingley
Moderator
Moderator
Beiträge: 588
Registriert: Di Dez 11, 2018 10:04 pm

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Paul Skingley » Fr Nov 20, 2020 2:32 pm

Bastian Grupp hat geschrieben:
Fr Nov 20, 2020 9:00 am
maybe Olaf can also teach the tool to recognize abnormal movement (contacts, slides, spins, offtrack) and then focus on these.
So you want all the lime light ?


:)


Paul
To finish first, first you have to finish.

Bastian Grupp
Chef-Fahrer
Chef-Fahrer
Beiträge: 120
Registriert: Mi Jan 16, 2019 8:50 am

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Bastian Grupp » Fr Nov 20, 2020 7:32 pm

Haha, i hope i get so ashamed everyone sees me 45 seconds in the hay, that i never do it again ;)

Benutzeravatar
Stefan Roess
Site Admin
Site Admin
Beiträge: 983
Registriert: Fr Dez 07, 2018 1:24 pm
Wohnort: Germany
Kontaktdaten:

Re: 17.11.2020 / GPLRACER 65 / Race 19 / Ardmore Aerodrome 1957 (ardmore)

Beitrag von Stefan Roess » Mi Nov 25, 2020 11:10 am

Bastian Grupp hat geschrieben:
Fr Nov 20, 2020 9:00 am
maybe Olaf can also teach the tool to recognize abnormal movement (contacts, slides, spins, offtrack) and then focus on these.
Good point.
I have asked him:
http://srmz.net/index.php?showtopic=124 ... ntry152736

Antworten

Zurück zu „65 Veranstaltungen [65 events]“