vcaptmattsmith
Members +
It's our pleasure to today reveal to the community a preview of this year's race. We're not revealing too many details, but we want to give everyone a heads-up about certain things. We'll monitor the various team forums and, of course, our own forum on this website, for questions.
1.
Weather.
In 2010 all pilots will use the MSFS Default (Jeppesen) weather engine. Select Real weather with 15 minute updates (if you can possibly do so).
It is now apparent that we need a level playing field with respect to the weather. Other weather systems have terrific features, but the need for competitive balance mandates this uniform standard. You may use the textures of the other weather programs, of course, but must use the MSFS weather engine.
2.
Informal Norms.
We would like to encourage pilots to fly in a realistic world. In particular, we want to avoid pressure to fly over a "bald earth," without terrain or autogen, with merely minimal cloud coverage. On the other hand, we understand that some pilots' computers impose limits on the realism with which they can fly—and they should choose reasonable settings for their machines. So for the moment, we lay out a set of norms. Think of these as minimum standards for pilots with modern computers. They apply to both FS2004 and FSX unless otherwise noted.
* Scenery. Autogen density: Normal. Scenery Complexity: Normal.
* Mesh. Keep the terrain mesh you normally use. A minimum standard would be default mesh (with a 38m resolution setting in FSX only).
* Weather. Weather options: Real-world weather (updated every 15 minutes). Cloud draw distance: 60mi. Detailed clouds/Cloud coverage density: Medium. (And for FS2004, 3-D cloud percentage: 100.)
Again, we appreciate the variety of pilots' computers and merely suggest these as informal norms.
3.
Aircraft types.
Beyond the normal range of aircraft, teams might want to practice their water landings before the race.
4.
NOTAMS (New for 2010 - note that unless overturned, previous years' determinations still stand).
The Epic LT (Lionheart) proved faster than our initial tests in 2009. When flown well above its real operational ceiling, the model can obtain speeds far in excess of any published maximum speeds. Understanding that a number of pilots have purchased this aircraft for the race, we are reluctant to make an outright ban for 2010. Accordingly, the Epic LT is allowed but restricted to a 31,000 ft hard ceiling. (Any flight exceeding 31,000 ft will be considered invalid and must be re-flown. Pilots should give themselves a large margin of error to guard against unexpected weather changes. At its realistic FL280-300 high altitude cruise, the Epic LT is plenty fast.)
The FSX Acceleration P-51 is allowed in 2010. The rules do not allow for racer versions of aircraft, so this is an exception for 2010.
Tim Horton has developed the ENB "Bloom" utility that provides night vision for FS2004 and FSX. This clever night vision utility, or any similar modification, is not allowed in the race.
In general, pilots may not use gauges or special effects that produce unrealistic aircraft behavior. This includes, by way of specific example, the "arrester gauge" designed for carrier traps and used elsewhere.
Subsonic jets remain those whose max_mach (Mmo) parameter is no greater than 1.00. We have no sure way to assess the actual level-flight characteristics of all jets without conducting extensive tests that are beyond our capability.
FSX pilots may use Jim Keir's "Lumberjack" scenery files as appropriate. (Search for agexcl_3x.zip and agexcl_5x.zip.)
5.
Continental Briefing Sheets.
In addition to the normal requirements, teams must land at the same 12 designated airports, located two per continent. Those 12 airports are fixed before the race, probabilistically selected by the chair of the Executive Committee, who does not participate in the race, and their identities described in six separate password-protected briefing sheets. Teams will be able to request the passwords to these sheets as they proceed around the world. The system works in the following way:
1. At least 24 hours before the race, each team will receive the full set of briefing sheets, a secret team access code, and the password to the first continent's briefing sheet—which may be unlocked immediately. Teams are responsible for maintaining the security of these items.
2. Teams become eligible to request the password for one (1) additional continent upon reaching (that is, completing a leg at) the first designated airport at which they arrive on a given continent, or shortly thereafter, (but not another when reaching the second designated airport.) They then unlock the briefing sheet and proceed accordingly. Thus teams are able to ‘see’ only one continent into the future routing of the race.
3. Password requests must not be made before a team becomes eligible to make them. Because the system is automated, the requested password will be sent whenever it is requested, regardless of whether the team is eligible. Thus the integrity of the race depends on strict adherence to this rule. Accordingly, we have put the following security measure into place:
4. All password requests are logged. Premature password requests will be investigated and assessed an eight (8) hour penalty per request. Again, the responsibility for maintaining security lies with the team.
5. Password requests are made in the following manner:
1. Send an email to fsrtwrace@gmail.com with an empty body. The subject line should include the name of the continent followed by a space and the team access code.
2. An email will automatically be sent with password requested.
3. In the event of an error, the team may contact the RTWR Executive Committee member acting as Duty Officer at the current time. A schedule and email addresses will be provided.
6. Anticipating a question:
Q. Since we get only one briefing sheet at a time, how do we know which continent to choose or in what order to visit them?
A. Everyone begins at the same point and that will determine the "first" continent. All continents have similar possibilities, challenges, and alternate routings, so the order of subsequent continents depends not on content but rather on a team's preference for an overall route. Teams should decide their next continent as early as possible so there is no confusion about which briefing sheet they wish to open next.
This briefing sheet system will - we promise - simplify planning and introduce a touch of mystery to the event.
6.
Continental Briefing Sheets - Preparation.
Teams need to organize a way to maintain internal control over the unlocked briefing sheet files and the team access code. If the access code is made public, then anyone can use it to make bogus requests. Teams are responsible for maintaining the security of their team access code and ensuring that it is not used before the team becomes eligible to use it.
In view of this, each team needs to identify the group of individuals it wishes to grant access to the team password and forward their names and e-mail addresses to the Executive Committee at fsrtwrace@gmail.com before the distribution of the access codes - which happens 24 hours before the race.
7.
Bonus Airports.
Teams may optionally select a small number of Bonus Airports from a somewhat larger pool. The briefing sheets provide the identities.
8.
Special Events
At 1400 UTC on Saturday, February 20, 2010, there will be a Kickoff event that rewards the participation of many pilots. The Race portion will begin at 1630 UTC. In addition, there will be optional team flights and an airmanship challenge.
1.
Weather.
In 2010 all pilots will use the MSFS Default (Jeppesen) weather engine. Select Real weather with 15 minute updates (if you can possibly do so).
It is now apparent that we need a level playing field with respect to the weather. Other weather systems have terrific features, but the need for competitive balance mandates this uniform standard. You may use the textures of the other weather programs, of course, but must use the MSFS weather engine.
2.
Informal Norms.
We would like to encourage pilots to fly in a realistic world. In particular, we want to avoid pressure to fly over a "bald earth," without terrain or autogen, with merely minimal cloud coverage. On the other hand, we understand that some pilots' computers impose limits on the realism with which they can fly—and they should choose reasonable settings for their machines. So for the moment, we lay out a set of norms. Think of these as minimum standards for pilots with modern computers. They apply to both FS2004 and FSX unless otherwise noted.
* Scenery. Autogen density: Normal. Scenery Complexity: Normal.
* Mesh. Keep the terrain mesh you normally use. A minimum standard would be default mesh (with a 38m resolution setting in FSX only).
* Weather. Weather options: Real-world weather (updated every 15 minutes). Cloud draw distance: 60mi. Detailed clouds/Cloud coverage density: Medium. (And for FS2004, 3-D cloud percentage: 100.)
Again, we appreciate the variety of pilots' computers and merely suggest these as informal norms.
3.
Aircraft types.
Beyond the normal range of aircraft, teams might want to practice their water landings before the race.
4.
NOTAMS (New for 2010 - note that unless overturned, previous years' determinations still stand).
The Epic LT (Lionheart) proved faster than our initial tests in 2009. When flown well above its real operational ceiling, the model can obtain speeds far in excess of any published maximum speeds. Understanding that a number of pilots have purchased this aircraft for the race, we are reluctant to make an outright ban for 2010. Accordingly, the Epic LT is allowed but restricted to a 31,000 ft hard ceiling. (Any flight exceeding 31,000 ft will be considered invalid and must be re-flown. Pilots should give themselves a large margin of error to guard against unexpected weather changes. At its realistic FL280-300 high altitude cruise, the Epic LT is plenty fast.)
The FSX Acceleration P-51 is allowed in 2010. The rules do not allow for racer versions of aircraft, so this is an exception for 2010.
Tim Horton has developed the ENB "Bloom" utility that provides night vision for FS2004 and FSX. This clever night vision utility, or any similar modification, is not allowed in the race.
In general, pilots may not use gauges or special effects that produce unrealistic aircraft behavior. This includes, by way of specific example, the "arrester gauge" designed for carrier traps and used elsewhere.
Subsonic jets remain those whose max_mach (Mmo) parameter is no greater than 1.00. We have no sure way to assess the actual level-flight characteristics of all jets without conducting extensive tests that are beyond our capability.
FSX pilots may use Jim Keir's "Lumberjack" scenery files as appropriate. (Search for agexcl_3x.zip and agexcl_5x.zip.)
5.
Continental Briefing Sheets.
In addition to the normal requirements, teams must land at the same 12 designated airports, located two per continent. Those 12 airports are fixed before the race, probabilistically selected by the chair of the Executive Committee, who does not participate in the race, and their identities described in six separate password-protected briefing sheets. Teams will be able to request the passwords to these sheets as they proceed around the world. The system works in the following way:
1. At least 24 hours before the race, each team will receive the full set of briefing sheets, a secret team access code, and the password to the first continent's briefing sheet—which may be unlocked immediately. Teams are responsible for maintaining the security of these items.
2. Teams become eligible to request the password for one (1) additional continent upon reaching (that is, completing a leg at) the first designated airport at which they arrive on a given continent, or shortly thereafter, (but not another when reaching the second designated airport.) They then unlock the briefing sheet and proceed accordingly. Thus teams are able to ‘see’ only one continent into the future routing of the race.
3. Password requests must not be made before a team becomes eligible to make them. Because the system is automated, the requested password will be sent whenever it is requested, regardless of whether the team is eligible. Thus the integrity of the race depends on strict adherence to this rule. Accordingly, we have put the following security measure into place:
4. All password requests are logged. Premature password requests will be investigated and assessed an eight (8) hour penalty per request. Again, the responsibility for maintaining security lies with the team.
5. Password requests are made in the following manner:
1. Send an email to fsrtwrace@gmail.com with an empty body. The subject line should include the name of the continent followed by a space and the team access code.
2. An email will automatically be sent with password requested.
3. In the event of an error, the team may contact the RTWR Executive Committee member acting as Duty Officer at the current time. A schedule and email addresses will be provided.
6. Anticipating a question:
Q. Since we get only one briefing sheet at a time, how do we know which continent to choose or in what order to visit them?
A. Everyone begins at the same point and that will determine the "first" continent. All continents have similar possibilities, challenges, and alternate routings, so the order of subsequent continents depends not on content but rather on a team's preference for an overall route. Teams should decide their next continent as early as possible so there is no confusion about which briefing sheet they wish to open next.
This briefing sheet system will - we promise - simplify planning and introduce a touch of mystery to the event.
6.
Continental Briefing Sheets - Preparation.
Teams need to organize a way to maintain internal control over the unlocked briefing sheet files and the team access code. If the access code is made public, then anyone can use it to make bogus requests. Teams are responsible for maintaining the security of their team access code and ensuring that it is not used before the team becomes eligible to use it.
In view of this, each team needs to identify the group of individuals it wishes to grant access to the team password and forward their names and e-mail addresses to the Executive Committee at fsrtwrace@gmail.com before the distribution of the access codes - which happens 24 hours before the race.
7.
Bonus Airports.
Teams may optionally select a small number of Bonus Airports from a somewhat larger pool. The briefing sheets provide the identities.
8.
Special Events
At 1400 UTC on Saturday, February 20, 2010, there will be a Kickoff event that rewards the participation of many pilots. The Race portion will begin at 1630 UTC. In addition, there will be optional team flights and an airmanship challenge.
