Runboard.com
Слава Україні!
Community logo


runboard.com       Sign up (learn about it) | Sign in (lost password?)

 
amtronic Profile
Live feed
Blog
Friends
Miscellaneous info

Administrator

Registered: 01-2012
Posts: 586
Reply | Quote
[AppRuleInnerLoop] vs. [AppRuleCutCourse]


Tutorial 01 - [AppRuleInnerLoop] vs. [AppRuleCutCourse]


Some definitions:
dlong - a point "longways" down a track. Usually in meters as that is the sandbox default.
dlat - a point lateral from the centerline of a track. Left of the centerline is a positive number, right of the centerline is a negative number.


Credits - Butter_ covered part of this in his tutorial in 2003, KingD.A. added information in a post from 2005.
Intent - This will attempt to condense and clarify just what constitutes [AppRuleCutCourse] and [AppRuleInnerLoop] and what makes them different.
What to remember - [AppRuleCutCourse] creates checkpoints you MUST pass thru, [AppRuleInnerLoop] creates a box you MAY NOT enter.

Description - (see picture #1)(right click, open in new tab)
[AppRuleCutCourse] as implemented at Daytona. A set of checkpoints are created just prior to the S/F line that the driver must pass thru to avoid a penalty. The driver must pass thru both of the checkpoints. This is to prevent the driver from cutting across the grass and cheating. There is also a switch in the [AppRuleCutCourse] parameters that controls if the rule applies to only qualifying or to both qualifying and the race. In this case, the rule is only enforced during qualifying at Daytona. Note that the rule as applied at Daytona is on a curved portion of the track. The command works regardless if it is a straight or curved portion. There is no "box" created, only a minimum of two checkpoints. Note: To avoid multiple black flags, the second checkpoint should be large enough to insure the car passes over it, this resets the black flag trigger and prevents additional black flags given in error.
[AppRuleCutCourse] creates two lines you must pass over.

(see picture #2) (right click, open in new tab)
[AppRuleInnerLoop] as implemented at Watkins Glen. In this example, two boxes are created at the inner loop area. This is due to the shape of the inner loop. Both boxes are areas that you cannot violate, from any side. You enter the box from any direction, you receive a penalty when you exit the box. There is no option to apply to only qualifying as with the cut course function. N2K3 supports a maximum of two such zones.
[AppRuleInnerLoop] is an area of no trespassing.


clipped from Daytona track.ini:
---------------------------------------------------------------------

[AppRuleCutCourse]
qual_only=1 ; only enforce checkpoints during qualifying session

[ configuration_0 ]
   ; Format: dlong, start dlat, end dlat, time penalty (sec), 0 (required)
   ; 2 checkpoint minimum
; prevents cutting grass (qual only)
checkpoint_0 = 3900.00 -3.50 13.00 0 0
checkpoint_1 = 4000.00 -3.50 13.00 0 0

---------------------------------------------------------------------


clipped from Watkins Glen track.ini:
---------------------------------------------------------------------

[AppRuleInnerLoop]
; Format: start dlong, end delong, right dlat, left dlat making up the corners of the box.
; This order must be followed -- start, end, right, left.
num_areas = 2
area_0 = 2094.62 2191.46 -5.22 8.42
area_1 = 2105.96 2166.95 -22.22 -5.22

---------------------------------------------------------------------





Picture #1
AppRuleCutCourse.jpg

Picture #2
AppRuleInnerLoop.jpg






Last edited by amtronic, 5/22/2012, 9:10 am


---
http://nr2k3tracks.com/
for tracks, mods, and utilities.
1/14/2012, 10:09 am Link to this post PM amtronic Blog
 
amtronic Profile
Live feed
Blog
Friends
Miscellaneous info

Administrator

Registered: 01-2012
Posts: 586
Reply | Quote
Re: [AppRuleInnerLoop] vs. [AppRuleCutCourse]


More info on [AppRuleCutCourse] --
(I have updated the above post to incorporate this information, this post gives much more detail in the issue)

In trying to set up three such areas on Imola, I kept running into a problem not with setting up the zones, but with clearing black flags thrown as a result of cutting the course in the chicane areas. In addition, there was a persistent problem that if you cut the first chicane, you also were black flagged for cutting the second chicane, even if you were extremely careful about not cutting again. (this also played true if you cut chicane #2 you would get an additional black flag for chicane #3 even if you didn't cut the course there.) The end result was that you accumulated multiple black flags, with different penalties ranging from drive-thru to "hold you for a while" timed penalties. These seemed to confuse the sim to the point that you could never clear the black flags before you were disqualified.

First off, there is some info out that you can set up a [configuration_0] and additional [configuration_1] [configuration_2] etc., zones in the [AppRuleCutCourse] stanza.
This never worked in all testing I did. I never found this in other tracks that was set up as such, so forget that.

I have found thru a lot of testing that [AppRuleCutCourse] sets up a checkpoint you must pass over, and is required there be 2 of them. The problem stems from, if you miss the first checkpoint, likely you will miss the second checkpoint also for that specific chicane area, which then triggers a second black flag when you reach the third checkpoint.

The solution is to set the second checkpoint of the pair to a set of values where you absolutely do pass over the checkpoint. That seems to close the set-reset checkpoint function.
(picture to follow)

To give a description of what it looks like, there is first a narrow set of points you either hit or miss. The second set of checkpoints is from wall to wall so you must pass thru these without question.
This seems to close the black flag trigger so you do not get a second black flag at the next [AppRuleCutCourse] zone, unless you also miss the first checkpoint in that track area.
Below is the part of the track.ini file for Imola. I separated them so you can see how they are paired up.

[AppRuleCutCourse]
qual_only=0 ; always enforce checkpoints
[ configuration_0 ]
  ; Format: dlong, start dlat, end dlat, time penalty (sec), 0 (required)
  ; 2 checkpoint minimum

checkpoint_0 = 725.00 -9.00 29.00 15 0 ; prevents cutting chicane #1 Variante Tamburello
checkpoint_1 = 765.00 -29.00 29.00 0 0 ; with either disqual or a time penalty

checkpoint_2 = 1380.00 -9.00 29.00 15 0 ; prevents cutting chicane #2 Variante Villeneuve
checkpoint_3 = 1420.00 -29.00 29.00 0 0 ; with either disqual or a time penalty

checkpoint_4 = 3345.00 -9.00 12.00 15 0 ; prevents cutting chicane #3 Variante Alta
checkpoint_5 = 3385.00 -29.00 22.00 0 0 ; with either disqual or a time penalty



Last edited by amtronic, 5/22/2012, 9:19 am


---
http://nr2k3tracks.com/
for tracks, mods, and utilities.
5/21/2012, 6:50 pm Link to this post PM amtronic Blog
 
JNorton61 Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user

Registered: 08-2014
Posts: 84
Reply | Quote
Re: [AppRuleInnerLoop] vs. [AppRuleCutCourse]


Great info... Thanks for taking the time to post this..

---
Wild Customs & Cars

https://www.facebook.com/groups/wildkustomcars

https://wildkustomcars.weebly.com
3/15/2017, 9:04 am Link to this post PM JNorton61 Blog
 


Add a reply





You are not logged in (login)
Back To Top