QUOTE (Minardi @ 19 Jan 2015, 03:20)
<{POST_SNAPBACK}>Updated Checklist:
1) Date and time; Weekend March 15/16 March 16 08:00 Auckland time = March 15 19:00 Amsterdam) (*)
That would be fantastic for me! That puts it right in the middle of Saturday afternoon. I almost feel bad that it's such a great time for me.
Here's a URL that shows the other times for that slice of the weekend:
http://www.timeanddate.com/worldclock/meet...2=16&p3=234
I'll ask the other guys who can attend at that time, but I'll assume it's not set in stone until other hosts agree.
QUOTE (Minardi @ 19 Jan 2015, 03:20)
<{POST_SNAPBACK}>2) Lay Out
3) Cars
4) Event settings
5) Racing Rules
All good for me...
QUOTE (Minardi @ 19 Jan 2015, 03:20)
<{POST_SNAPBACK}>WINNER: The team with the most laps. In case of equal amount of laps, qualify result decides the winner.
Doesn't RCS64 have a total race time? The tie breaker could be the total race time, which should show at least a small difference. If the total race time is exactly the same, then qually result could be a second tie breaker.
QUOTE (Minardi @ 19 Jan 2015, 05:04)
<{POST_SNAPBACK}>Route1Racing will kindly provide the tyres
SWEET! Thanks, MrMod!
I'm really looking forward to giving them some run time.
QUOTE (GRUNZ @ 19 Jan 2015, 10:40)
<{POST_SNAPBACK}>- why no pit sensors?
- do we enforce a minimum number of team members? let's say each team must have a minimum number of 2 members?
- Which is the Minimum Room Size and the track pieces that are available to all the members?
- Are we going to use realtime information through TeamViewer/Skype using the sharing desktop features or just updating a thread on the RCS-64 forum with screenshots?
I don't know Marcel's reasoning, but I don't have pit sensors to install on a temp track. Also, they can be problematic when the pit lane is short and cars waggle when entering. I'd rather just pull off the track and take care of things using buttons. I don't think the sensors will be as big a need in this situation, especially as most of us will not be "accidentally" performing pit activities on the track.
I think a team min of 2 is pretty reasonable. I'd say max 3, if not 2. Some groups may be able to field a 5 man team, which wouldn't be very fair to the smaller teams.
I like the idea of Chris being a "master of ceremonies" and overall race controller. I would be fine giving him remote control of my track computer so that he can pause the race or something if a world-wide pause is needed. Also, being able to do screen grabs and updates and such would be pretty slick if one person did them all. Since he wouldn't be racing or mashaling, he can be the Murray Walker of this event (though actually describing the racing would be cool, I'm not implying he needs to). I should be able to set up a web cam using my spare phone, but I'm not sure what's the best service to use for that, and if it can do so into a group thing.
Speaking of which, does anyone know, or have experience with, a video conference calling service that would allow spectators to join and toggle/switch between the different "speakers" (video feeds) of the event? That would be a cool way of doing it.