|
|
TT RACING SERIES |
|
|
|
|
TEAM SPEAK |
|
|
|
|
|
|
|
|
|
|
|
INTRODUCTION TO TT RACING SHORT TRACK SERIES |
|
|
THE TT RACING
SHORT TRACK SERIES IS SPONSORED BY
FALCONGRAFIX. FASTT RUNS UNDER THE
TT RACING LEAGUE
BANNER. TT RACING RUNS SEVERAL SERIES RUNNING AT DIFFERENT
TIMES AND DAYS IF YOU ARE LOOKING SOMETHING DIFFERENT THAN
SHORT TRACKS CHECK OUT THE OTHER SERIES FROM
TT RACING LEAGUE.
FASTT RUNS SHORT TRACK THAT ARE NOT IN THE ORIGINAL GAME YOU WILL NEED TO KNOW
HOW TO INSTALL TRACKS IN THE GAME. FASTT IS USING THE OUTLAW LATE MODEL MOD FROM
SIM THUNDER
AND RUNS FIXED SETUPS IN SIMULATION MODE WITH A 3X PIT STOP
FREQUENCY, REALISTIC DAMAGE LEVEL, SINGLE FILE RESTARTS WITH
THE "LUCKY DOG RULE", AND FIXED "NORMAL" WEATHER. TTR WAS
ESTABLISHED IN MAY 2002 WHEN IT BEGAN AS AN ARCADE
MODE LEAGUE RUNNING PAPYRUS' NASCAR RACING 2003.
|
|
|
|
|
SERIES OFFICIALS
(SO's) |
|
|
The FALCONGRAFIX ASSOCIATED SHORT TRACK TOUR Administrator
(heretofore referred to as the Admin) is the owner and top
official of the series. The Admin is ultimately responsible
for the final decision on any matter regarding the series
with the exception of appeals as laid out in Section VII,
Rule k. The Admin also holds the sole responsibility for
approving or rejecting driver applications for FASTT
membership and all driver car files. The Admin can also at
his discretion designate anyone of his choosing to make such
decisions or assist him in the running of the series. The
current and founding Admin is Mic Olafson, and he can be
e-mailed at
micolafson@kickenasphalt.com.
The Short Track Series Race Officials (heretofore referred
to as the RO's) have been designated by the Admin to be his
regular assistants in all matters regarding the series. The
RO's, among other things, help with enforcing rules during
an event, issuing penalties, clearing incorrect penalties
given out by NR2003, and general race management.
Collectively, the Admin and RO's are known as the Series
Official (heretofore referred to as the SO's). The SO's main
responsibility is to perform the post-race review which
includes, but is not limited to, checking the replay after
the event to apply the FASTT Penalty Points System and take a
look at any possible infractions brought to the SO's
attention by e-mail (see Section VII for the details on
these procedures).
Should one or more of the SO's not be able to show up for an
event, those remaining reserve the right to appoint one or
more temporary RO's to assist with either in-race rulings,
post-race rulings, or both. Again, with the exception of
appeals, all decisions made by either permanent or temporary
members of the SO's are final.
|
|
|
|
|
SECTION
I: TEAMSPEAK
AND FORUM CONDUCT |
|
|
a) NO PROFANITY OR FLAMING ON TEAMSPEAK OR IN THE
FORUMS THERE ARE MINORS SO PLEASE RESPECT THE OTHER PEOPLE THAT ARE ON THERE
b) If there us a
problem with and on track incident do not discus it in the
open forums or accuse some one on Teamspeak please email on
of the NSTS official and we will review the incident.
c) Any flaming or profanity in the forums or on
Teamspeak can result in ejection from the race or banning
from the FASTT or all TT Racing leagues.
|
|
|
|
|
SECTION
II: PRE-APPLICATION |
|
|
a) All applicants must be 16
years old to join the FASTT
b) ALL APPLICANTS HAVE TO HAVE A STEADY INTERNET
CONNECTION (DSL OR CABLE).
A DRIVER THAT WARPS DURING A NSTS EVENT WILL BE ASKED
TO PARK THERE CAR
IF THE PROBLEM CONTINUES THE MAY BE ASKED TO RETIRE FROM THE
SERIES.
c)
TEAMSPEAK
IS REQUIRED FOR ALL PARTICIPANTS. TEAMSPEAK MAKES IT EASY
FOR THE
THE RACE ADMINS TO COMMUNICATE WITH THE DRIVERS FOR CLEARING
PENALTIES AND
GIVING LAPS BACK FOR THE THE LUCKY DOG
d) Applicants will need the NASCAR RACING 2003 SEASON
(NR2003) game and the outlaw late model mod from
SIM THUNDER. The RLM ARENA is required to
log into the race, you will not be allowed to join in any
other way. All applicants will also need a steering wheel
and a microphone (for Teamspeak).
|
|
|
|
|
|
SECTION
III: APPLICATION |
|
|
a)
Once all of
the conditions listed in Section II have been met, drivers must submit an
application by going to the
sign up
page of the FASTT web site. Make sure to fill out the form as
completely as possible and triple-check the spelling. This application only
applies to the short track series and does not gain a driver admittance into any
other TTR series. All other TTR series must be applied for separately.
b)
Before sending in the application, visit the FASTT
drivers
page to make
sure the car number to be requested is not already taken. The number submitted
must exactly match the number on the car file to be used in an event (for
example, one cannot request 028 yet have just 28 appear on the car). If you
request a number that starts with 0 and that regular number is not taken
(example you request the #015 but no one is driving the #15 car you will
get the #15 )
c)
Applicants will be notified by e-mail from the Admin of acceptance or
rejection. If accepted, a driver will receive the password for the TTR racing
server, instructions on how to gain access to the
TT Racing Forums
and TTR
Team Speak channel, as well as a request to send in a car file.
d)
Car files must be submitted via RLM Car File Manager (CFM). Access to the CFM
will be given upon acceptance to the short track series. The Admin reserves the
right to reject any car file for any reason.
e)
Drivers who have not previously been a member of the FASTT will be
admitted on a probationary period of three races. This is to insure that
drivers who are new to the series are a good fit for the FASTT and vice versa.
This is in no way meant to discourage people who are new to online league racing
from joining nor is everybody expected in any way to be a perennial
front-runner. The FASTT just wants to
make sure that all new members can generally control their cars and that their
attitude fits in with the spirit that TTR was founded upon. Unless a message is
received stating that the probationary period was not passed, a driver can then
consider him or herself as a permanent member in good standing of the FASTT. Procedures
for those who do not pass the probationary period will be at the discretion of
the Admin, and may include but are not limited to anything from an extension of
the probationary period to notice of permanent removal from the FASTT. |
|
|
|
|
|
SECTION IV: BEFORE
AN EVENT
|
|
|
a)
All FASTT
participants are responsible for keeping up on any announcements made by the
SO's
as well as any rule changes. Drivers should regularly check the e-mail account
submitted to the Admin and visit the
TTR Racing Forums
as often as possible. Drivers who change their e-mail address must submit the
new one to the
SO's
and
update it in their TT Racing League Forum member profile. The FASTT is not
responsible for anybody who misses such information that causes that person to
miss an event or receive any sort of penalty. Also, failure to at least
occasionally log into the
TTR Racing Forums
can result in a login name being deleted from the membership list due to
inactivity.
b)
Before
entering the server, all participants should download any new car files using
the CFM. This will insure that drivers easily know who they are near on the
track and who they should be communicating with.
c)
All drivers must have the latest version of any required software running before
entering the TTR server. |
|
|
|
|
|
SECTION V: RACE
SPECIFICATIONS |
|
|
a) General FASTT Race
Settings:
Races are held
via RLM Arena - Info will be given once an application
has been accepted
Vehicles -------------------------------- Outlaw late model mod
Season Length ----------------------- 10 races
Practice Session Opens ---------- Fridays at 8pm Eastern Time
Driving Mode -------------------------- Simulation
Practice Length ---------------------- 45 minutes
Happy Hour Length ----------------- 5 minutes
Race Length -------------------------- 100 laps
Pit Stop Frequency ---------------- 3x
Full Pace Lap ------------------------ on
Damage Level ------------------------ realistic
Yellow Flags -------------------------- on
Double File Restarts --------------- off
Conditions ----------------------------- Clear
Temperature -------------------------- 65 degrees Fahrenheit
Wind Direction ---------------------- North
Wind Speed -------------------------- 0 mph
Setups --------------------------------- fixed PWF "expert" ("fast" if some
kind of "expert" setup is not available)
b) The Admin
(or RO's if the Admin is not present) reserves the right to start, restart, or
stop an event at any time. However, be aware that the traditional TTR
"gentlemen's agreement" is to not restart a race once the first lap has been
completed without incident.
d) Following
the qualifying session, the Admin or one of the RO's will take a verbal roll
call to make sure everybody is in compliance with the "TeamSpeak Rule" (see
Section II, Rule d ).
e)
The "Lucky Dog Rule" will be in effect at all NSTS races. A "Lucky Dog"
will not be awarded if the caution flag waves with less than 10 laps to go in an
event or if the driver who was eligible to receive the "Lucky Dog" caused the
incident that resulted in the caution being shown. Upon the throwing of a
yellow flag, the SO's will check at their earliest convenience to see what car
is the first one a lap or more down to the leaders. If eligible, the driver
will be informed of his or her "Lucky Dog" status over TeamSpeak. The "Lucky
Dog" should then enter the pits on the lap after the lead lap cars have pitted
and exceed the speed limit in a safe manner. This will result in NR2003 issuing
an "end of the longest line" ("EOLL") penalty insuring that the "Lucky Dog" will
start at or near the end of the line. Upon hitting the backstretch after a
restart, the "Lucky Dog" will be given back one lap by the SO's. Since NR2003
was programmed before NASCAR implemented the "Lucky Dog Rule," this system is
admittedly imperfect and will not always result in the "Lucky Dog" being the
very last car in line upon the restart or the SO's being able to implement it in
the intended manner. The SO's is not responsible for any driver who fails to
follow procedures thus resulting in the "Lucky Dog" not being awarded or any
game or track glitches, bugs, or other various oddities that prevent a definite
ruling on who should be the "Lucky Dog."
f)
The SO's reserves the right to bring out a yellow flag or extend an existing
caution period at any time. This is normally only done to give time to
straighten out any confusing situations on the track, mainly when a caution
comes out during a pit cycle that began under green flag conditions (a situation
that NR2003 always seems to have a hard time dealing with properly). In such
cases the right is also reserved to clear black flags and give back laps to
drivers who were incorrectly penalized by NR2003.
|
|
|
|
|
SECTION VI: RACE
CONDUCT |
|
|
a)
Intentional wrecking by a driver, whether it involves another car or not, will
not be tolerated. Any such occurrence seen during a race by the SO's will
result in immediate ejection of the offending participant from the server. If
not found by the SO's until after the event is completed, a driver guilty of
intentional wrecking will have his or her scorecard pulled on the lap completed
before such a violation took place. However brought to the attention of the
SO's, drivers who have committed an intentional wreck will receive PPD
(see Section VII) and will thus have to serve an immediate suspension of at least
one race. The SO's will then review the circumstances of the wreck and take
into account the past behavior of the driver in question. The SO's reserves the
right to employ further penalties including, but not limited to, increasing the
length of the suspension, various points penalties, or a lifetime ban from the
series.
b) Laying
back more than one car length on the start or any restart in order to get a jump
on the car(s) ahead is prohibited. Any such incident seen during the race by
the SO's will result in a black flag penalty for the offending car. Any such
incident not seen or confirmed by the SO's until after the event is completed
will result in a one lap penalty for the guilty driver.
c) On the
start and restarts you are not allowed to pass on the inside of the first corner
unless there is less than 10 laps to go. Doing so before then will result in a
PPD (section VII) or a black Flag
d)
Using the apron or grass on any track in order to improve one's position is
prohibited. Whether intentional or not, any driver who makes such a move must
let the cars he or she passed back by as soon as it is safe. If a driver fails
to let the illegally passed car(s) back around and it is seen during a race by
the SO's, a black flag penalty will be assessed against the offending car. Any
such incident not found until after the event by the SO's will result in a one
lap penalty for the guilty driver. The only case in which a pass made on the
apron or grass will be allowed and not penalized is if the driver making such a
move does so only to avoid an occurring wreck.
e)
Any participant seen "warping" during an event may be asked by the SO's to fall
to the back of the pack until the "warping" stops or, in extreme cases, to park
his or her car for the remainder of the race. "Warping" is defined as any car
that appears to blink on and off the track for any period of time or one that
appears to be moving wildly across the racing surface. If a driver is aware
that he or she is warping, the Hot Wheels Series appreciates it if action to
prevent endangering one's fellow drivers is taken before it has to be
requested. Drivers who are severely affected by warping over a multiple race
period may even be asked by the Admin to leave the series until the problem is
resolved.
f)
Any driver who intends to enter pit road and who is being followed closely by
another car must publicly announce his or her intention to do so. This can be
done either through the in-game chat message or over Teamspeak.
g)
Cars that are a lap or more down, especially if they are damaged, must do their
best to stay out of the way of lead lap and/or faster cars when they are coming
up to pass. Lapped and damaged cars should announce their intention on whether
the upcoming drivers should go low, high, or designate some other instructions
on how and where they can pass. Such instructions can be given either through
the in-game chat messages or over Teamspeak. If a driver is strictly lapped but
is still running at a comparable speed to the leaders, use good and careful
judgment as to whether or not mixing it up with the leaders can put one in a
position to get a lap back or stay ahead of a nearby competitor; and use
Teamspeak to inform the lead lap cars for this presence amongst them.
h)
If a restart is going to occur with ten or fewer laps remaining in a race, all
cars a lap or more down to the leaders must enter the pit road once it is opened
for lapped cars whether or not they stop for service. This is intended to allow
cars on the lead lap to race for the win with as little interference from lapped
cars as possible. If a participant fails to comply and it is seen during the
event by the SO's, a black flag will be shown to the offending car. Any such
incident not found until after the race by the SO's will result in a one lap
penalty for the guilty driver.
i)
Blocking has always been a controversial subject from top the echelons of real
racing all the way down to a friendly league such as TTR. Each incident
involving blocking on which there is a wreck or a complaint that is received by
the SO's will be looked at on a case-by-case basis. While the SO's reserves the
right to rule otherwise depending on the circumstances, the traditional
"gentlemen's agreement" in TTR has usually been that the leading car can change
its line once within a reasonable amount of time to block the car(s) attempting
to make a pass. More than one move in such a circumstance then has the
possibility of becoming dangerous and unsportsmanlike and makes a driver
performing such blocking moves more liable to receive a penalty from the SO's
which can include, but is not limited to, a warning, a black flag, a one-lap
penalty, or various points penalties. With all of that being said, the NSTS
also realizes that positions are very hard to earn on almost every track and
that all drivers should be mature enough to not take it personally when they get
blocked. This is especially true in the closing few laps of any race when the
SO's is going to be much less likely to issue a penalty for blocking, but yet
still reserves the right to do so if the incident is viewed as being excessive
or dangerous. Do be aware that if a leading car has a one or more second lead
and is well clear of any other drivers that it has every right to weave as much
as it wants in order to break the draft and that such behavior is allowable and
not considered blocking.
j)
When a caution comes out
during an event, drivers are NOT allowed to race back to the line. this is
not necessary with the "Lucky Dog Rule" in place (see Section V, Rule e),
maintain speed till is is safe to slow down and catch up with the pace car this
is best way to avoid a pileup.
k)
Any driver who causes three cautions during a single race (meaning that no if it
was a self-spin that brought out the caution or you spun another driver) that
also bring out yellow flags must immediately retire from the event if the driver
does no retire they will receive a PPD (see Section VII, Rule ).
l)
While the use of Teamspeak and the in-game chat messages are highly encouraged,
they can certainly be overused and abused. Use of Teamspeak and the in-game
chat messages during the qualifying session are prohibited. Using Teamspeak
during the start or restarts should only be done to convey important race
information. During the rest of the event, use good judgment as to when to use
the communications systems and what is appropriate. Make sure to be aware of
the various situations on the track before possibly causing a distraction that
might be costly to one's fellow drivers.
m)
The use of profanity or any other kind of degrading speech, whether directed
at another participant or just a general comment, is prohibited. Use of such
language can result in a penalty ranging from a warning, various points
penalties, ejection from the server, or even a lifetime ban from the NSTS.
Drivers are strongly encouraged to set Teamspeak to "push to talk" instead of
"voice activated" to avoid the accidental release of foul, disparaging, or
hateful language.
o)
The SO's reserves the right at all times to issue black flags, penalty laps,
various points penalties, or eject any driver from the TTR Server or remove them
from the series for any length of time deemed necessary for any conduct found to
be detrimental to the series or for any infraction for which there is not a
specified penalty. Drivers who receive a post-race one lap (or more) penalty
will be placed behind any other drivers who finish with the same amount of laps
as the penalized car. |
|
|
|
|
|
SECTION VII: POST RACE PENALTY POINT DEDUCTIONS |
|
|
a)
Each and every incident that brings out a yellow flag during a FASTT
race will be reviewed by the SO's at their earliest convenience. Any driver
determined by the majority of the SO's to have been the sole cause of a caution
period during an event will receive one, two, or three points depending on the
type of infraction under the Hot Wheels Series Penalty Points Deduction (PPD) for
each such incident for which that driver is found to be responsible. The PPS
has been put in place by the Hot Wheels Series to deter careless, reckless, and
overly-aggressive driving as well as to promote as much racing under the green
flag as possible. The results of the SO's
findings will be linked next to each
race listed on the FASTT
Schedule
web page and will be updated as soon as possible after every Hot Wheels Series
event. Drivers who disagree with the findings of the
SO's are encouraged to
submit an appeal for a final decision (see Rule k below).
b) Not
every incident that brings out a yellow flag will result in a PPD being
given. The
SO's reserves the right to call any incident a "racin' deal" where no
fault can be assigned to one particular driver.
c) The
SO's
reserves the right to issue PPD or any other type of penalty deemed
appropriate and necessary even on incidents which do not bring out a yellow flag
and that do not have a penalty specified elsewhere in these rules. Other types
of penalties that can be used by the
SO's include, but are not limited to, a
warning, lap deduction, points deduction, suspension, or a lifetime ban from the
series.
d) If an
incident not found by the
SO's is not reported to the Admin or one of the
SO's or
they didn't see it during an event, it is considered not to have ever occurred.
The reporting of incidents is important if the FASTT is to remain a
clean and competitive series. The
SO's cannot see every possible incident since
its members are racing at the same time as everybody else. If it is believed
that there was a rules violation that went unnoticed during the event, it should
be reported to any member of the
SO's in an e-mail with a description of the
infraction and the lap number of the occurrence.
e) When
reviewing incidents that occur when a pass is being made or attempted, the FASTT generally goes by the traditional rule that it is the
responsibility of the driver attempting to pass to make that pass safely.
However, it is also understood that racing can get hot and heavy during a
passing situation, especially when it is late in the race. This is why all
factors will be considered by the
SO's if the incident comes into question.
While the main emphasis is put on the trailing car to make a safe pass, the
leading car has responsibilities as well. For one example, if the leading car
fails to recognize that the following car has pulled fully up alongside the
front car's rear fender and then the leading car moves into the following car,
that would make the front car more liable to receive a PPD point.
h)
In addition to the "Three Yellows and Park It Rule" (see Section V, Rule
k), any driver who causes three such cautions whether another car is hit or not
will receive PPD point in addition to having to retire from the event.
i)
The time honored tradition of the "bump and run" is allowed in the
FASTT. The
"bump and run" involves a leading car being bumped by a trailing car hard enough
to make the leading car get loose so the trailing car can pass, but gentle
enough so that the leading car does not cause a wreck either to the car being
bumped or any other drivers. A "bump and run" that is not done correctly which
also results in a wreck whether it involves the cars involved in the "bump and
run" or any others will result PPD being given to the
driver who initiated the "bump and run." For that reason as well as wishing to
keep the friendly spirit upon which the FASTT and TTR were founded,
drivers are warned that they perform the "bump and run" at their own peril and
that one should think twice or even thrice before trying it. Because the intent
of a "bump and run" is to move a car without wrecking it, such moves that do
result in an incident will not be considered intentional wrecking as defined in
Section V, Rule a.
j)
Any driver who feels that he or she incorrectly received any type of penalty
from the SO's is completely welcome and totally encouraged to file an appeal.
Absolutely nothing will be held against any TTR participant for wanting to take
advantage of this process. Appeal requests must be sent by e-mail to the
Admin at
micolafson@kickenasphalt.com
and should include a full description of the incident in question. If possible
and needed, a zip file containing any screenshots or edited version of the
incident from the race replay should be attached to the same message. Without
adding any additional comment, the Admin will then be responsible for forwarding
the appeal to all other available TTR Admins (with the exception of any TTR
Admins who are directly involved in the incident in question) who will then
review the evidence and individually send their decisions back to the FASTT Admin. The Admin will then count up the votes and inform the driver who
submitted the appeal by e-mail if it was accepted or rejected. In the case of a
tie vote by the TTR Admins, the FASTT Admin will re-review the case
by himself taking into consideration the new opinions submitted by the TTR Admins and then cast the deciding vote. In such cases, the decision of the
Nascaracepix Short Track Series Admin will be final.
k)
All incident reports and appeals will be handled through e-mail and kept
strictly confidential. If a driver is reported as a possible rules
violator, the incident will be verified by the Admin prior to contacting the
person in question. If the Admin in conjunction with the SO's deems that a
penalty is not warranted, the driver in question will never know of the report
nor will the person who submitted the report be notified of the decision.
Under no circumstances should violations, appeals, or their resulting penalties
(or, lack thereof) be posted or discussed anywhere in the TT Racing League
Forums. Such posts will be deleted immediately and may result in any
penalty deemed necessary by the Admin, the TTR President, or the TTR Vice
President.
|
|
|
|
|
|
SECTION VIII: NSTS POINTS BREAKDOWN |
|
|
a)
Points
awarded for finishing spots in the FASTT are as follows:
1st -- 100 points
2nd -- 97 points
3rd -- 94 points
4th -- 91 points
5th -- 88 points
6th -- 85 points
7th -- 82 points
8th -- 79 points
9th -- 76 points
10th - 73 points
11th - 70 points
12th - 67 points
13th - 64 points
14th - 61 points
15th - 48 points
16th - 45 points
17th - 42 points
18th - 39 points
19th - 36 points
20th - 33 points
21st - 30 points
22nd - 27 points
23rd - 24 points
24th - 21 points
25th - 18 points
26th - 15 points
27th - 12 points
28th - 9 points
29th - 6 points
30th - 3 points
31st - 0 points
b)
Bonus
Points Awarded Per Race:
leading one lap during the race --------- 3 points
leading the most laps during a race ----- 3 points
c)
A
driver who knows in advance that he or she will not be able to make an event can
nominate a substitute driver. Substitute driver nominations must be submitted
by e-mail only to the Admin at
micolafson@kickenasphalt.com,
and potential nominees must be a member in good standing of at least one other
TTR series. The Admin will then forward the request to the RO's. Any proposed
substitute driver will have to be approved by a unanimous vote of the SO's. If
the vote is not unanimous, the Admin will inform the driver seeking a substitute
that another driver must be nominated or that he or she can take a "provisional"
(see Rule d below). If approved, the substitute may then participate in the
designated race, but must use the car in which the driver being substituted for
normally uses. Substitute drivers will be just as responsible for knowing and
following the FASTT rules as regular FASTT members. Any
post-race penalty incurred by the substitute driver which includes, but is not
limited to, various points penalties and suspensions will be applied towards the
FASTT driver who requested the substitute. This will insure that FASTT drivers choose substitutes carefully and that substitutes will
take events as seriously as a regular series participant.
d) FASTT
members in good standing who cannot find a substitute driver, do not wish to use
one, or who have a circumstance where they do not have time to find a substitute
and thus miss a race will receive a "provisional" points award. The
"provisionals" will be given automatically upon a driver having missed his or
her race. “Provisionals” are only giving to official FASTT members and are not
given to part timers. "Provisionals" are offered because the SO's fully realizes
that life outside the online racing world often requires one's full attention.
"Provisionals" will allow drivers who miss races to not fully plummet in the
season standings. Taking a "provisional" will make it more difficult, yet not
totally impossible, for a driver to still compete for a higher finishing spot at
the end of a season. If more than one driver misses the same event, each member
will receive the same amount of provisional points. Provisional points
will be 50 POINTS
|
|
|
|
|
SECTION IX: THE MOST IMPORTANT
RULES |
|
|
a) This will be the the rule we in the
FASTT
live by have fun
|
|
|
|
|
|
|
|
|