Cold Fire (2013-01-13)

[Komeuppance]

Man you guys race early!!  I missed out with my Pacific time zone.

-Robert

[Duplode]

Man you guys race early!!  I missed out with my Pacific time zone.

The conventional meeting time used to be 20:00 GMT, though we tend to start racing closer to 21:00. That's around lunch hour under PST We should try to coordinate a different meeting time in one of these weekends (and not to mention Zak, who is now back in China...).

Please, rewrite this document here.
In short:
4th - Friker - 8 laps 38 tiles
3rd - dreadnaut - 8 laps 39 tiles
2nd - Duplode - 9 laps 22 tiles
1st - Chulk - 9 laps 31 tiles

Thanks for the compilation 

Code: [Select]

DUP/TT DUP/LT CHU/TT CHU/LT DRE/TT DRE/LT FRI/TT FRI/LT
1 0:57.15 0:57.15 0:57.50 0:57.50 1:00.70 1:00.70 1:01.10 1:01.10
2 1:47.40 0:50.35 1:47.10 0:49.60 1:53.85 0:53.15 1:53.25 0:52.15
3 2:39.40 0:52.00 2:35.85 0:48.75 2:47.70 0:53.85 2:48.70 0:55.45
4 3:28.55 0:49.15 3:24.25 0:48.40 3:39.40 0:51.70 3:42.50 0:53.80
5 4:18.25 0:49.70 4:10.95 0:46.70 4:31.80 0:52.40 4:33.55 0:51.05
6 5:07.60 0:49.35 4:57.25 0:46.30 5:24.95 0:53.15 5:30.30 0:56.75
7 5:59.10 0:51.50 5:47.10 0:49.85 6:20.70 0:55.75 6:25.00 0:54.70
8 6:50.10 0:51.00 6:35.50 0:48.40 7:16.35 0:55.65 7:19.15 0:54.15
9 7:38.85 0:48.75 7:24.35 0:48.85 39 tls. 0:43.65 38 tls. 0:40.85
10 22 tls. 0:21.15 31 tls. 0:35.65

Fastest lap: Chulk (#6, 46:30)

The numbers speak by themselves - a superlative victory for Chulk.

[Chulk]

I didn't think I had won so clearly... I was the fastest every lap but the last one where Dup was the fastest. And for the 2nd time in a row, I had the fastest lap too. It seems I should learn to do this fast laps more regularly...

[Friker]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

[CTG]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

If you put some ice on the track right before the start, it will be really hard to cheat.

[Friker]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

If you put some ice on the track right before the start, it will be really hard to cheat.

I was thinking about a slalom block/a big ice corner...

[Chulk]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

I don't get it. One can modify the track on an already created replay?

[CTG]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

I don't get it. One can modify the track on an already created replay?

Yep. Like you can move a good start from one replay to another (don't dare to build a Countach track with downhill in the first tile after start line, else I'm going to cheat with it ). It's basic hexediting.

Of course it only makes sense if the modification has no effect on your car's behaviour (for example you cut a certain corner in every lap - if you change it to an icy one, it won't have an effect).

[Duplode]

btw I think that we should modify a track before start (or not to edit anything), because it is really not a big problem to edit the track in the replay file in 12 minutes.

I don't get it. One can modify the track on an already created replay?

Yep. Like you can move a good start from one replay to another (don't dare to build a Countach track with downhill in the first tile after start line, else I'm going to cheat with it ). It's basic hexediting.

Or by hex-editing the track directly (the .RPL file contains a copy of the track).

If we were really going to bother ( ) with standardizing the small change to the track, I guess the easiest option would be changing the terrain of a corner in the pitlane (e.g. the very first left turn in Cold Fire), as that would affect the car behaviour without changing the "real" track.

[Komeuppance]

Alright, I stayed up all night (it's 8am now), drinking... I think I am ready to race.  (Don't be confused by how well I can type while HAMMERED, I can type 85 WPM with only my left hand lol)

What are the rules to doing a live race, without searching it looks like 8 laps, cheat/cut corners allowed... correct??  Sober I struggled with doing 3 laps without crashing lol, perhaps my inebriation will increase my skill level, makes sense at the moment.

I've watched some replays, you guys are definitely pushing the physics of Stunts lol.  Top pipsqueaks using keyboard or joystick control??

-Robert

[Duplode]

Alright, I stayed up all night (it's 8am now), drinking... I think I am ready to race.  (Don't be confused by how well I can type while HAMMERED, I can type 85 WPM with only my left hand lol)

That's the spirit 

What are the rules to doing a live race, without searching it looks like 8 laps, cheat/cut corners allowed... correct??  Sober I struggled with doing 3 laps without crashing lol, perhaps my inebriation will increase my skill level, makes sense at the moment.

You have to drive 8 minutes according to the in-game clock, and you must finish the replay (and post it on the forum) within 12 minutes. In addition to shortcuts, you can rewind and continue if you crash or mess up badly - but don't rely too much on that or you will miss the 12-minute deadline.

I've watched some replays, you guys are definitely pushing the physics of Stunts lol.  Top pipsqueaks using keyboard or joystick control??

Keyboard - driving with joysticks is an horrible experience (mouse is even worse  ).

[Komeuppance]

Thanks for the reply.

I nominate a mouse only race lol... minimum of three beers/equivalent cocktails/shots required.

-Robert