yeh...life is now on a 3hr. rotating schedule
Administer Positions Available
As a way of celebrating the birth of my first child,
I have decided to open up my server to (almost) anyone who wants to be an administrator.
I have decided to open up my server to (almost) anyone who wants to be an administrator.
By submitting the above form, I understand and agree that as a SimRacing.ca administrator I will be held accountable to the highest standards of racing etiquette.
I further understand that my standing as an administrator may be revoked at any time if I'm found to be an ****.
I further understand that my standing as an administrator may be revoked at any time if I'm found to be an ****.
user editable car numbers
did a quick search and didn't find this...
Many of the leagues use the custom number plate idea...most I have see is in the same place soooo...how about 2 car paint templates one with the number plate in a predetermined placed and one without the number plate. Then coded into the game in the player name/options section another field "car number". This then displays the car number variable in the predetermined place where the number plate is...voila, no more repainting each time a number has to change
Many of the leagues use the custom number plate idea...most I have see is in the same place soooo...how about 2 car paint templates one with the number plate in a predetermined placed and one without the number plate. Then coded into the game in the player name/options section another field "car number". This then displays the car number variable in the predetermined place where the number plate is...voila, no more repainting each time a number has to change
Standardized Racing Conduct Agreement v0.2
version 0.1: http://www.lfsforum.net/showthread.php?t=23981
After a quick re-write & re-order I came up with this version I think is more suited to a template. Note: items in blue are to be replaced as per each series. Also I need to figure out some verbage for Turn 1 behaviour. It's not as long as it looks but, if ya need help falling asleep try the following
1. GENERAL CONDUCT
1.1. All decisions made by the series administration are final.
1.2. Series administration staff may participate in an event as a competitor. As such they forfeit their control of the series for 1 hour before & after the event to the marshalling staff. Series administration may compete or marshal, not both.
1.3. LFSMC staff may participate in an event as a competitor. As such they forfeit their LFSMC staff status for 1 hour before & after the event. LFSMC staff may compete or marshal, not both.
1.3.1. LFSMC staff may not alter the outcome of an event except in fulfillment of their role as event facilitators.
1.3.2. LFSMC staff must be clearly identified by their driver names and car skins.
1.3.3. It is the responsibility of each participant to be aware of which LFSMC staff are facilitating the event.
1.4. Events are run & controlled completely by the marshalling staff. All direction given during an event by the marshals will be in full caps and will be presented to the competitors in the following manner:
1.4.1. CAR # - COMMENTS - # LAPS
· CAR # is the car number of the driver (not the qualifying position) being addressed,
· COMMENTS are the direction, ruling or instructions of the marshalling staff
· # LAPS is the time allotted to perform the instructions. (if # LAPS is not given then it is to be understood that the instructions must be performed before the leader completes their last lap.)
1.5. There will be no text chatting whatsoever during an event, with the exception of the marshalling staff.
1.6. All voice communication must be done on dedicated team channels. The public broadcast channel is for marshalling use only. A dedicated channel for marshals must be provided. Dedicated channels are for their respective members only.
1.7. All drivers’ are responsible to be aware of their own track / race position and react / behave accordingly.
1.8. If at all possible, use of signaling is strongly encouraged. Signal markers are understood as follows:
1.8.1. car x indicates LEFT = car x will move/stay LEFT.
1.8.2. car x indicates RIGHT = car x will move/stay RIGHT.
1.8.3. car x indicates HAZARDS = car x is aware a faster car is following and will not impede the faster car’s progress. (This is a courtesy only.)
1.8.4. car x indicates HAZARDS = car x is intending to pit.
· Due to the dual nature of the HAZARD signal, it is the following car’s responsibility to be aware of track position and to anticipate either a move towards the pit lane or a move away from the pit lane if that is off the racing line.
1.8.5. car x flashes HEADLIGHTS = car x is indicating their intention to pass a car a lap down
1.8.6. car x sounds HORN = car x may not be faster but is alerting others to their close proximity
1.8.7. car x sounds HORN = car x is indicating their intention to pass a car a lap down
· Due to the dual nature of the HORN, it is all drivers’ responsibility to be aware of their own track position and react accordingly.
1.9. All participants of an event are encouraged to save a replay.
1.9.1. These replays may be requested by LFSMC staff to review track incidents.
1.9.2. If an incident / penalty is filed against you, your replay is your strongest argument.
1.9.3. Player replays are essential to file a post event incident report.
2. CONTACT
2.1. Due to the competitive nature of racing some contact will occur.
2.2. Contact resulting in any gain or change of position between the contacting cars will be viewed as an offence.
2.2.1. If a driver shows signs that they are aware of responsibility for an offence and said driver takes appropriately timed action to right the wrong then the offence will be deemed righted and no action taken.
2.3. Contact resulting in any gain or change of position between the contacting cars and other non-involved cars will be reviewed by LFSMC staff after the event.
3. TEAMS
3.1. Sprint Team
3.1.1. Will consist of a maximum of # cars, designated at registration.
3.1.2. At no time during an event are more that # cars from any given team allowed on the track area.
3.2. Endurance Team
3.2.1. Will consist of a maximum of # members, designated at registration as follows:
· “Small Team” of # drivers
· “Large Team” of # drivers & # spares
3.3. Endurance Privateer Team
3.3.1. Single drivers are welcome to join. All single drivers will be listed as such and their contact information may be made available. Single drivers are seen as free agents until the series start. During the time period of sign-up through to series start, free agents are encouraged to either form teams as per section 3.2.1 of other free agents or they may be drafted onto other established teams provided the result of such drafting is in accordance with section 3.2..1
3.4. Drivers may only participate in series races as a member of their own team.
3.4.1. In the event that a team would have to forfeit a race due to a contradiction of section 3.2.1, then designated spares may be hired out on a per event bases from any team willing to make their designated spares available. This availability option must be made public at the time of registration.
3.4.2. Designated spares driving for teams other than their registration team are deemed as members of their temporary team for the entire period of the event.
· All team points gained by a hired spare go to the hiring team on a per event basis.
· Individual points gained by hired spares go to the individual driver.
· Infractions incurred by a hired spare are assessed against the driver only. In the event a hired spare incurs a serious enough infraction that would be assessed against his entire team, the penalty will be assessed against the team said driver registered with and not against the hiring team.
3.4.3. Teams may enter the series using a maximum of # cars per team. Team cars do (do not) have to be the same make or class. Specific make & class selections will be as per the series registration process.
3.4.4. All participants must use the prescribed number plate & any other series graphic as provided by the administration
4. EVENT PROCEDURES
4.1. Servers
4.1.1. The following server(s) will be used for this series.
· Date – track – servername
· Date – track - servername
4.2. Disconnect Policy
4.2.1. series administration to set this section
4.3. Scoring
4.3.1. series administration to set this section
4.4. Qualifying
4.4.1. Qualify sessions will start at X:XX hrs UMT.
4.4.2. Qualify sessions will be X:XX min. long
· Qualify events run from the start of the qualify session timer and are completed when the last car has crossed the finish line
4.5. Start
4.5.1. Event start will be at X:XX hrs UMT.
4.5.2. Events will be a standing start based on the previous qualifying session(s).
4.5.3. Turn 1 ??????
4.6. Event Duration
4.6.1. Events will be X:XX hrs long (XX laps)
· Events run from start of the formation lap, OR as soon as the engines are started on the grid OR when the first driver is called onto the track, and are completed when the last car has crossed the finish line
4.7. Pitting
4.7.1. Non-pitting cars must be aware of the pit exit lines and maintain sufficient control of their cars so as to be able to stay off the racing line to allow exiting cars to rejoin safely
· For an example of the meaning of this rule please see the exit/race lines at Westhill & South City.
4.7.2. Exiting cars must keep 2 (4) wheels within the yellow pit exit lines. Any contact as a result of a breech of this rule will be deemed the responsibility of the exiting car.
· This may be overturned by the LFSMC staff if they agree that a non-pitting car was in contradiction to section 4.7.1.
4.8. Passing & Lapped Traffic
4.8.1. See section 1.8
· All drivers are responsible for their own safety and the safety of all the other competitors. Accidents in sim racing should be treated with the same respect as real life racing.
4.8.2. The primary responsibility for safe passing resides with the faster car, not the car being passed / lapped.
4.8.3. Cars to be passed may not block faster cars. One move / change of line is allowed to protect a lead, any more is considered blocking.
4.9. FLAGS
4.9.1. Green
4.9.1.1. Indicates the start of the race as per section 4.5.
4.9.2. Yellow
4.9.2.1. Indicates a hazardous situation either locally or full course.
4.9.2.2. There is to be no passing under the yellow flag.
4.9.3. Blue
4.9.3.1. Does not necessarily indicate a car faster car behind, but rather that the car behind is at least 1 lap ahead.
· If the car being shown the blue flag is faster than the following car and is pulling away then no action need be taken.
· If the car being shown the blue flag is slower than the following car and is losing ground then the slower car must safely allow the faster car by.
4.9.3.2. See section 4.8.2.
4.9.3.3. See section 1.8.
4.9.4. Black
4.9.4.1. Drivers being shown a black flag are a danger to themselves, the other races, all the spectators, commentators, sponsors, TV viewers & planet earth in general…they must GTF off the track immediately!
4.9.4.2. The above section is serious.
4.10. Safety Car
4.10.1. series administration to set this section
4.11. Incidents & Penalties During an Event
4.11.1. See section 1.4.
4.12. Post Event Reporting
4.12.1. Incident reporting may be done no sooner than X hours of an event and no later than X hours of the event. LFSMC to set these numbers
4.12.2. See section 1.9.3.
4.12.3. Under no circumstances are incidents to be reported on the LFS main forum.
4.12.4. Incidents are to be reported directly to the LFSMC forum in a series of threads the subject of which must be:
· LeagueName, EventDate, Incident #
· The first post in this thread will be in the following format:
· LFSMC Facilitator(s) ________________________
· Report Filed By
· LFSname: ________________________
· PLAYERname: ________________________
· Report Filed Against
· LFSname: ________________________
· Description of Incident
· Lap / Time: ________________________
· Alleged Incident: ________________________
4.12.5. Incident ruling will be a locked thread the subject of which will be:
· LeagueName, EventDate, Ruling #
5. ENDURANCE RACES
5.1. No driver may travel more than # % race distance.
5.2. No stint may be longer than # km. or # minutes.
5.3. Driver changes may only take a time generally equivalent to 1 lap to be completed at which time the out-going driver must leave the server. Teams must make all necessary preparations to ensure that incoming drivers are aware of when to join the event server to ensure that the incoming driver does not join until the current driver has started their in-lap. Such preparations must not be in contradiction to sections 1.5 or 1.6
it's easier to read when the tabs stay intact
After a quick re-write & re-order I came up with this version I think is more suited to a template. Note: items in blue are to be replaced as per each series. Also I need to figure out some verbage for Turn 1 behaviour. It's not as long as it looks but, if ya need help falling asleep try the following
Standardized Racing Conduct Agreement
1. GENERAL CONDUCT
1.1. All decisions made by the series administration are final.
1.2. Series administration staff may participate in an event as a competitor. As such they forfeit their control of the series for 1 hour before & after the event to the marshalling staff. Series administration may compete or marshal, not both.
1.3. LFSMC staff may participate in an event as a competitor. As such they forfeit their LFSMC staff status for 1 hour before & after the event. LFSMC staff may compete or marshal, not both.
1.3.1. LFSMC staff may not alter the outcome of an event except in fulfillment of their role as event facilitators.
1.3.2. LFSMC staff must be clearly identified by their driver names and car skins.
1.3.3. It is the responsibility of each participant to be aware of which LFSMC staff are facilitating the event.
1.4. Events are run & controlled completely by the marshalling staff. All direction given during an event by the marshals will be in full caps and will be presented to the competitors in the following manner:
1.4.1. CAR # - COMMENTS - # LAPS
· CAR # is the car number of the driver (not the qualifying position) being addressed,
· COMMENTS are the direction, ruling or instructions of the marshalling staff
· # LAPS is the time allotted to perform the instructions. (if # LAPS is not given then it is to be understood that the instructions must be performed before the leader completes their last lap.)
1.5. There will be no text chatting whatsoever during an event, with the exception of the marshalling staff.
1.6. All voice communication must be done on dedicated team channels. The public broadcast channel is for marshalling use only. A dedicated channel for marshals must be provided. Dedicated channels are for their respective members only.
1.7. All drivers’ are responsible to be aware of their own track / race position and react / behave accordingly.
1.8. If at all possible, use of signaling is strongly encouraged. Signal markers are understood as follows:
1.8.1. car x indicates LEFT = car x will move/stay LEFT.
1.8.2. car x indicates RIGHT = car x will move/stay RIGHT.
1.8.3. car x indicates HAZARDS = car x is aware a faster car is following and will not impede the faster car’s progress. (This is a courtesy only.)
1.8.4. car x indicates HAZARDS = car x is intending to pit.
· Due to the dual nature of the HAZARD signal, it is the following car’s responsibility to be aware of track position and to anticipate either a move towards the pit lane or a move away from the pit lane if that is off the racing line.
1.8.5. car x flashes HEADLIGHTS = car x is indicating their intention to pass a car a lap down
1.8.6. car x sounds HORN = car x may not be faster but is alerting others to their close proximity
1.8.7. car x sounds HORN = car x is indicating their intention to pass a car a lap down
· Due to the dual nature of the HORN, it is all drivers’ responsibility to be aware of their own track position and react accordingly.
1.9. All participants of an event are encouraged to save a replay.
1.9.1. These replays may be requested by LFSMC staff to review track incidents.
1.9.2. If an incident / penalty is filed against you, your replay is your strongest argument.
1.9.3. Player replays are essential to file a post event incident report.
2. CONTACT
2.1. Due to the competitive nature of racing some contact will occur.
2.2. Contact resulting in any gain or change of position between the contacting cars will be viewed as an offence.
2.2.1. If a driver shows signs that they are aware of responsibility for an offence and said driver takes appropriately timed action to right the wrong then the offence will be deemed righted and no action taken.
2.3. Contact resulting in any gain or change of position between the contacting cars and other non-involved cars will be reviewed by LFSMC staff after the event.
3. TEAMS
3.1. Sprint Team
3.1.1. Will consist of a maximum of # cars, designated at registration.
3.1.2. At no time during an event are more that # cars from any given team allowed on the track area.
3.2. Endurance Team
3.2.1. Will consist of a maximum of # members, designated at registration as follows:
· “Small Team” of # drivers
· “Large Team” of # drivers & # spares
3.3. Endurance Privateer Team
3.3.1. Single drivers are welcome to join. All single drivers will be listed as such and their contact information may be made available. Single drivers are seen as free agents until the series start. During the time period of sign-up through to series start, free agents are encouraged to either form teams as per section 3.2.1 of other free agents or they may be drafted onto other established teams provided the result of such drafting is in accordance with section 3.2..1
3.4. Drivers may only participate in series races as a member of their own team.
3.4.1. In the event that a team would have to forfeit a race due to a contradiction of section 3.2.1, then designated spares may be hired out on a per event bases from any team willing to make their designated spares available. This availability option must be made public at the time of registration.
3.4.2. Designated spares driving for teams other than their registration team are deemed as members of their temporary team for the entire period of the event.
· All team points gained by a hired spare go to the hiring team on a per event basis.
· Individual points gained by hired spares go to the individual driver.
· Infractions incurred by a hired spare are assessed against the driver only. In the event a hired spare incurs a serious enough infraction that would be assessed against his entire team, the penalty will be assessed against the team said driver registered with and not against the hiring team.
3.4.3. Teams may enter the series using a maximum of # cars per team. Team cars do (do not) have to be the same make or class. Specific make & class selections will be as per the series registration process.
3.4.4. All participants must use the prescribed number plate & any other series graphic as provided by the administration
4. EVENT PROCEDURES
4.1. Servers
4.1.1. The following server(s) will be used for this series.
· Date – track – servername
· Date – track - servername
4.2. Disconnect Policy
4.2.1. series administration to set this section
4.3. Scoring
4.3.1. series administration to set this section
4.4. Qualifying
4.4.1. Qualify sessions will start at X:XX hrs UMT.
4.4.2. Qualify sessions will be X:XX min. long
· Qualify events run from the start of the qualify session timer and are completed when the last car has crossed the finish line
4.5. Start
4.5.1. Event start will be at X:XX hrs UMT.
4.5.2. Events will be a standing start based on the previous qualifying session(s).
4.5.3. Turn 1 ??????
4.6. Event Duration
4.6.1. Events will be X:XX hrs long (XX laps)
· Events run from start of the formation lap, OR as soon as the engines are started on the grid OR when the first driver is called onto the track, and are completed when the last car has crossed the finish line
4.7. Pitting
4.7.1. Non-pitting cars must be aware of the pit exit lines and maintain sufficient control of their cars so as to be able to stay off the racing line to allow exiting cars to rejoin safely
· For an example of the meaning of this rule please see the exit/race lines at Westhill & South City.
4.7.2. Exiting cars must keep 2 (4) wheels within the yellow pit exit lines. Any contact as a result of a breech of this rule will be deemed the responsibility of the exiting car.
· This may be overturned by the LFSMC staff if they agree that a non-pitting car was in contradiction to section 4.7.1.
4.8. Passing & Lapped Traffic
4.8.1. See section 1.8
· All drivers are responsible for their own safety and the safety of all the other competitors. Accidents in sim racing should be treated with the same respect as real life racing.
4.8.2. The primary responsibility for safe passing resides with the faster car, not the car being passed / lapped.
4.8.3. Cars to be passed may not block faster cars. One move / change of line is allowed to protect a lead, any more is considered blocking.
4.9. FLAGS
4.9.1. Green
4.9.1.1. Indicates the start of the race as per section 4.5.
4.9.2. Yellow
4.9.2.1. Indicates a hazardous situation either locally or full course.
4.9.2.2. There is to be no passing under the yellow flag.
4.9.3. Blue
4.9.3.1. Does not necessarily indicate a car faster car behind, but rather that the car behind is at least 1 lap ahead.
· If the car being shown the blue flag is faster than the following car and is pulling away then no action need be taken.
· If the car being shown the blue flag is slower than the following car and is losing ground then the slower car must safely allow the faster car by.
4.9.3.2. See section 4.8.2.
4.9.3.3. See section 1.8.
4.9.4. Black
4.9.4.1. Drivers being shown a black flag are a danger to themselves, the other races, all the spectators, commentators, sponsors, TV viewers & planet earth in general…they must GTF off the track immediately!
4.9.4.2. The above section is serious.
4.10. Safety Car
4.10.1. series administration to set this section
4.11. Incidents & Penalties During an Event
4.11.1. See section 1.4.
4.12. Post Event Reporting
4.12.1. Incident reporting may be done no sooner than X hours of an event and no later than X hours of the event. LFSMC to set these numbers
4.12.2. See section 1.9.3.
4.12.3. Under no circumstances are incidents to be reported on the LFS main forum.
4.12.4. Incidents are to be reported directly to the LFSMC forum in a series of threads the subject of which must be:
· LeagueName, EventDate, Incident #
· The first post in this thread will be in the following format:
· LFSMC Facilitator(s) ________________________
· Report Filed By
· LFSname: ________________________
· PLAYERname: ________________________
· Report Filed Against
· LFSname: ________________________
· Description of Incident
· Lap / Time: ________________________
· Alleged Incident: ________________________
4.12.5. Incident ruling will be a locked thread the subject of which will be:
· LeagueName, EventDate, Ruling #
5. ENDURANCE RACES
5.1. No driver may travel more than # % race distance.
5.2. No stint may be longer than # km. or # minutes.
5.3. Driver changes may only take a time generally equivalent to 1 lap to be completed at which time the out-going driver must leave the server. Teams must make all necessary preparations to ensure that incoming drivers are aware of when to join the event server to ensure that the incoming driver does not join until the current driver has started their in-lap. Such preparations must not be in contradiction to sections 1.5 or 1.6
it's easier to read when the tabs stay intact
yeh that was my intent...i got a bit sidetracked as i read through an earlier draft
Based on the discussion this generates, I'll update as we go and at some point publish it to the wiki
As a quick start, here's what I got so far, have at it:
1. Teams
1.1. Endurance Team
1.1.1. Will consist of a maximum of 6 members, designated at registration as follows:
· “Small Team” of 2 drivers
· “Large Team” of 4 drivers & 2 spares
1.2. Endurance Privateer Team
1.2.1. Single drivers are welcome to join. All single drivers will be listed as such and their contact information may be made available. Single drivers are seen as free agents until the initial race date. During the time period of sign-up through to initial race date free agents are encouraged to either form teams as per section 1.1.1 of other free agents or they may be drafted onto other established teams provided the result of such drafting is in accordance with section 1.1.1.
1.3. Sprint Team
1.3.1. Will consist of a maximum of 3 cars, designated at registration.
· At no time during an event are more that 3 cars from any given team allowed on the track area.
1.4. Team Regulations After Series Start
1.4.1. Teams are deemed set once the series start time has been reached.
2. Series Participation
2.1.1. Drivers may only participate in series races as a member of their own team.
· In the event that a team would have to forfeit a race due to a contradiction of section 1.1.1, then designated spares may be hired out on a per event bases from any team willing to make their designated spares available. This availability option must be made public at the time of registration.
2.1.2. Designated spares driving for teams other than their registration team are deemed as members of their temporary team for the entire period of the event.
· All team points gained by a hired spare go to the hiring team on a per event basis.
· Individual points gained by hired spares go to the individual driver.
· Infractions incurred by a hired spare are assessed against the driver only. In the event a hired spare incurs a serious enough infraction that would be assessed against his entire team, the penalty will be assessed against the team said driver registered with and not against the hiring team.
2.1.3. Teams may enter the series using a maximum of 2 cars per team. Team cars do not have to be the same make or class. Specific make & class selections will be as per the series registration process.
2.1.4. All participants must use the prescribed number plate & any other series graphic as provided by the administration.
3. Events
3.1. General Conduct
3.1.1. All decisions made by the series administration are final.
3.1.2. Series administration staff may participate in an event as a competitor. As such they forfeit their control of the series for 1 hour before & after the event to the marshalling staff. Series administration may compete or marshal, not both.
3.1.3. LFSMC staff may participate in an event as a competitor. As such they forfeit their LFSMC staff status for 1 hour before & after the event. LFSMC staff may compete or marshal, not both.
3.1.4. Events are run & controlled completely by the marshalling staff. All direction given during an event by the marshals will be in full caps and will be presented to the competitors in the following manner, where CAR # is the car number of the driver (not the qualifying position) being addressed, COMMENTS are the direction, ruling or instructions of the marshalling staff and # LAPS is the time allotted to perform the instructions. (if # LAPS is not given then it is to be understood that the instructions must be performed before the leader completes their last lap.)
· CAR # - COMMENTS - # LAPS
3.1.5. There will be no text chatting whatsoever during an event, with the exception of the marshalling staff.
3.1.6. All voice communication must be done on dedicated team channels. The public broadcast channel is for marshalling use only. A dedicated channel for marshals must be provided. Dedicated channels are for their respective members only.
3.2. Point System
3.3. Disconnect Policy
3.4. Sessions, Lengths & Start Times
3.5. Qualifying Procedures
3.6. Start Procedures
3.7. Pitting Procedures
3.8. Flags & Procedures
3.9. Safety Car Procedures
3.10. Passing & Lapped Traffic Procedures
3.11. Incidents & Penalties Procedures
3.11.1. During an Event
3.11.2. After Event Reporting
3.12. Endurance Races
3.12.1. No driver may travel more than 1/2 race distance.
3.12.2. No stint may be longer than 100km. or 60minutes, whichever is longer.
3.12.3. Driver changes may only take a time generally equivalent to 1 lap to be completed at which time the out-going driver must leave the server. Teams must make all necessary preparations to ensure that incoming drivers are aware of when to join the event server to ensure that the incoming driver does not join until the current driver has started their in-lap.
1. Teams
1.1. Endurance Team
1.1.1. Will consist of a maximum of 6 members, designated at registration as follows:
· “Small Team” of 2 drivers
· “Large Team” of 4 drivers & 2 spares
1.2. Endurance Privateer Team
1.2.1. Single drivers are welcome to join. All single drivers will be listed as such and their contact information may be made available. Single drivers are seen as free agents until the initial race date. During the time period of sign-up through to initial race date free agents are encouraged to either form teams as per section 1.1.1 of other free agents or they may be drafted onto other established teams provided the result of such drafting is in accordance with section 1.1.1.
1.3. Sprint Team
1.3.1. Will consist of a maximum of 3 cars, designated at registration.
· At no time during an event are more that 3 cars from any given team allowed on the track area.
1.4. Team Regulations After Series Start
1.4.1. Teams are deemed set once the series start time has been reached.
2. Series Participation
2.1.1. Drivers may only participate in series races as a member of their own team.
· In the event that a team would have to forfeit a race due to a contradiction of section 1.1.1, then designated spares may be hired out on a per event bases from any team willing to make their designated spares available. This availability option must be made public at the time of registration.
2.1.2. Designated spares driving for teams other than their registration team are deemed as members of their temporary team for the entire period of the event.
· All team points gained by a hired spare go to the hiring team on a per event basis.
· Individual points gained by hired spares go to the individual driver.
· Infractions incurred by a hired spare are assessed against the driver only. In the event a hired spare incurs a serious enough infraction that would be assessed against his entire team, the penalty will be assessed against the team said driver registered with and not against the hiring team.
2.1.3. Teams may enter the series using a maximum of 2 cars per team. Team cars do not have to be the same make or class. Specific make & class selections will be as per the series registration process.
2.1.4. All participants must use the prescribed number plate & any other series graphic as provided by the administration.
3. Events
3.1. General Conduct
3.1.1. All decisions made by the series administration are final.
3.1.2. Series administration staff may participate in an event as a competitor. As such they forfeit their control of the series for 1 hour before & after the event to the marshalling staff. Series administration may compete or marshal, not both.
3.1.3. LFSMC staff may participate in an event as a competitor. As such they forfeit their LFSMC staff status for 1 hour before & after the event. LFSMC staff may compete or marshal, not both.
3.1.4. Events are run & controlled completely by the marshalling staff. All direction given during an event by the marshals will be in full caps and will be presented to the competitors in the following manner, where CAR # is the car number of the driver (not the qualifying position) being addressed, COMMENTS are the direction, ruling or instructions of the marshalling staff and # LAPS is the time allotted to perform the instructions. (if # LAPS is not given then it is to be understood that the instructions must be performed before the leader completes their last lap.)
· CAR # - COMMENTS - # LAPS
3.1.5. There will be no text chatting whatsoever during an event, with the exception of the marshalling staff.
3.1.6. All voice communication must be done on dedicated team channels. The public broadcast channel is for marshalling use only. A dedicated channel for marshals must be provided. Dedicated channels are for their respective members only.
3.2. Point System
3.3. Disconnect Policy
3.4. Sessions, Lengths & Start Times
3.5. Qualifying Procedures
3.6. Start Procedures
3.7. Pitting Procedures
3.8. Flags & Procedures
3.9. Safety Car Procedures
3.10. Passing & Lapped Traffic Procedures
3.11. Incidents & Penalties Procedures
3.11.1. During an Event
3.11.2. After Event Reporting
3.12. Endurance Races
3.12.1. No driver may travel more than 1/2 race distance.
3.12.2. No stint may be longer than 100km. or 60minutes, whichever is longer.
3.12.3. Driver changes may only take a time generally equivalent to 1 lap to be completed at which time the out-going driver must leave the server. Teams must make all necessary preparations to ensure that incoming drivers are aware of when to join the event server to ensure that the incoming driver does not join until the current driver has started their in-lap.
Last edited by KSheppard, .
Reason : spelling :)
Standardized Racing Conduct Agreement
Hey racers, after following a few threads regarding standard race conduct & rules I think it's time to start fleshing this idea out sooooo, to get the ball "officially" rolling, please start posting some ideas you'd like to see incorporated into a standardized rule / conduct document.
As a reference take a look at these:
LFS Marshal Community: http://www.lfsforum.net/showthread.php?t=23901
blue flag: http://www.lfsforum.net/showth ... 6&highlight=blue+flag,
and http://www.lfsforum.net/showth ... 4&highlight=blue+flag,
and http://www.lfsforum.net/showth ... 5&highlight=blue+flag
BTW I think we also need to agree on some definitions:
As a reference take a look at these:
LFS Marshal Community: http://www.lfsforum.net/showthread.php?t=23901
blue flag: http://www.lfsforum.net/showth ... 6&highlight=blue+flag,
and http://www.lfsforum.net/showth ... 4&highlight=blue+flag,
and http://www.lfsforum.net/showth ... 5&highlight=blue+flag
BTW I think we also need to agree on some definitions:
- track area
- All asphalt or concrete (grass, sand etc… are off track)
- series start
- 0:00.00hrs of the day of the first race
- Event
- Race events run from start of the formation lap, or as soon as the engines are started on the grid and are completed when the last car has crossed the finish line
- Qualify events run from the start of the qualify session timer and are completed when the last car has crossed the finish line
- Race events run from start of the formation lap, or as soon as the engines are started on the grid and are completed when the last car has crossed the finish line
Interesting ideas here, nice to see that there is some positive thoughts about marshalling (server police ) and general racing rules/conduct.
I was just starting to think through drafting up a set of standardized rules and TBH I don't think it would be all that hard...draft a section, start a poll & discussion, after x number of days close the discussion and revise the draft, post it.
Thoughts on the wiki:
1....it should be within the LFS Manual wiki
2....needs a special PW so only a few people may make changes
(I'm available to help out with drafting the document if someone wants help.)
) and general racing rules/conduct.I was just starting to think through drafting up a set of standardized rules and TBH I don't think it would be all that hard...draft a section, start a poll & discussion, after x number of days close the discussion and revise the draft, post it.
Thoughts on the wiki:
1....it should be within the LFS Manual wiki
2....needs a special PW so only a few people may make changes
(I'm available to help out with drafting the document if someone wants help.)
I have the DFP, this is how I have it setup:
Commands:
signal left=7 Press, 7 Release
single cancel=0 Press, 0 Release
Cycle Command:
turn left= signal left, signal cancel
Key Mapping:
square=left marker
Result:
press the square to indicate left, press it again to cancel it...2 buttons (3 counting hazards mapped to fwd gear shift)
and another thing we have turn signals, use them to let others know what you are intending to do...if your gonna stay left then put your left blinker on
see my post here: http://www.lfsforum.net/showthread.php?t=10424&page=3
Based on this and the other discussions here, anyone want to draft up the LFS RULES OF RACE CONDUCT GUIDE ?
We can then vote on it point by point and once we get a general consensus it can be adopted as ver.1, hosts who are in accordance with the guide can then tag their server name something like: RRC-<hostname>
edit
I'm thinking someone like Becky (cause you need MORE to do :P) or one of the other major leagues who could just modify their existing rule set
We can then vote on it point by point and once we get a general consensus it can be adopted as ver.1, hosts who are in accordance with the guide can then tag their server name something like: RRC-<hostname>
edit
I'm thinking someone like Becky (cause you need MORE to do :P) or one of the other major leagues who could just modify their existing rule set
I like this idea it would make spectating much more interesting to watch, a few thing come to mind:
it would make spectating much more interesting to watch, a few thing come to mind:- perhaps LFSWorld could add an upload for "host logo graphic" at some predefined size
- If could it be paired to LFSTVdirector (http://www.lfsforum.net/showth ... 47&highlight=lfstv) I bet you'd get many more people interested in just spectating but that would take up far too many server slots, can a current race "spectate session" be cloned?
and ONLY those spectating would be able to see the "chat session"
I know, not the exact right place for this but just a comment on global warming:
1. CLIMATE is a 30year average of WEATHER
2. only JUST 30years ago the science guys claimed we were in a global cooling trend, that means the global CLIMATE has changed in one 30year period?
3. even a 30year average is a miniscule timeframe on the global/solar timescale...as our planet moves through the milky way, we move through solar dust clouds, these dust clouds partly obscure the sun, and the result is frozen polar regions..we are in a dust cloud now, as we move out of it the earth will warm up to the point that the polar ice caps will melt and the water level will rise and more fresh water wil enter the oceans and the gulf stream will change - it's the planetary way
4. there was a DRASTIC temperature jump in the 1920's, about 1/2 of the total reported global warming reported recently...why? Because in the 20's the USA and UK got together and changed the methodology for measuring temperature...before the 20's a bucket of water on the deck of a ship had a thermometer placed in it, in the 20's they took the same bucket of water and took it's temperature in the engine room of the same ships...I'd bet it's a little warmer there
5. cattle produce far more harmful methane gas/year than any city
6. temperature readings are taken in large metropolitan areas, they should also be taken in remote areas as well and then the mean number reported
Not to bad mouth mother nature but it might be time to do my own research and think for myself, there's at least 2 sides to every story and there are a lot of science guys who count on the global warming report for their livelyhood listen to these:
60sec.: http://www.640toronto.com/stat ... 62813&jor=62813#video
60sec.: http://www.640toronto.com/stat ... 64709&jor=64709#video
interview with David Suzuki: http://www.640toronto.com/john ... 60672&jor=60672#video
Facts are meaningless. You could use facts to prove anything that's even remotely true! H.J. Simpson
1. CLIMATE is a 30year average of WEATHER
2. only JUST 30years ago the science guys claimed we were in a global cooling trend, that means the global CLIMATE has changed in one 30year period?
3. even a 30year average is a miniscule timeframe on the global/solar timescale...as our planet moves through the milky way, we move through solar dust clouds, these dust clouds partly obscure the sun, and the result is frozen polar regions..we are in a dust cloud now, as we move out of it the earth will warm up to the point that the polar ice caps will melt and the water level will rise and more fresh water wil enter the oceans and the gulf stream will change - it's the planetary way
4. there was a DRASTIC temperature jump in the 1920's, about 1/2 of the total reported global warming reported recently...why? Because in the 20's the USA and UK got together and changed the methodology for measuring temperature...before the 20's a bucket of water on the deck of a ship had a thermometer placed in it, in the 20's they took the same bucket of water and took it's temperature in the engine room of the same ships...I'd bet it's a little warmer there
5. cattle produce far more harmful methane gas/year than any city
6. temperature readings are taken in large metropolitan areas, they should also be taken in remote areas as well and then the mean number reported
Not to bad mouth mother nature but it might be time to do my own research and think for myself, there's at least 2 sides to every story and there are a lot of science guys who count on the global warming report for their livelyhood listen to these:
60sec.: http://www.640toronto.com/stat ... 62813&jor=62813#video
60sec.: http://www.640toronto.com/stat ... 64709&jor=64709#video
interview with David Suzuki: http://www.640toronto.com/john ... 60672&jor=60672#video
Facts are meaningless. You could use facts to prove anything that's even remotely true! H.J. Simpson
Meaning no course defining barriers? The admin / host would then be able to add driving line, barriers, s/f line, sectors etc... to define a track? Maybe no manditory barriers...might be fun to try and discover the layout, you'd need a new message thought "you're off the track doofus!"
Now that is a sweet idea. With the 3d terraforming programs that already exist AND the modding tools for other games (rF, NascarHEAT) I could see an enterprising programmer create an app to do just that. (The coding already exists, it might be as simple as a cut and paste job except for the little part of getting all the bits to talk to each other) I could further see exporting of the resultant map to multiple platforms. (rF, NH, LFS...)
Anyone looking for a uni project
Now that is a sweet idea. With the 3d terraforming programs that already exist AND the modding tools for other games (rF, NascarHEAT) I could see an enterprising programmer create an app to do just that. (The coding already exists, it might be as simple as a cut and paste job except for the little part of getting all the bits to talk to each other) I could further see exporting of the resultant map to multiple platforms. (rF, NH, LFS...)
Anyone looking for a uni project
Teammates could be able to access/set it at LFSW then, to not require a slot on the server?
Tire Temp Data
while i'm thinking about it, it would be nice to have the tire temp graphic/data from the previous laps displayed in the pit screens to aid in camber/pressure assessment
Qualify List
my last post got shot down while i was looking through the improvement list so i thought i'd try again....i wanna ashut off the qualify list, it's too long and blocks my view of the apex on right handers.
FGED GREDG RDFGDR GSFDG