I'll try to find some time for it...

www.jamendo.com

lots of cool FREE music.

XFR_ky2r Z name

So I use trackcode, lfs version (helpfull after physic updates) and a name (either Qual and Race for final sets and v0-X while doing sets)

I'm german...

Rolling Stones - Sympathy for the Devil

Quote from need :

Yeah, I know, it just struck me as strange that the replay shows it for the full race and then disqualifies them at the race end.

eh? not in mine (my own one).
Anyway, provisional result is in the first post of this thread and this is the one you should look at till we publish the official one

Quote from need :

Now maybe it's just me, but does that replay really show that Mercury drove the entire race with a stop-go penalty showing for jumping the pace lap?

That was cleared by the admins.
Not much sense in giving a dt for a jump start in the formation lap as it doesn't affect the start or result.

Quote from Dragonmen :

Lap 114 for GT1 (our lap 30 after our discon.) timestamp: 5h 04min 38sec
Sector 1, hairpin
Protest against #02

as reported by driver:
#02 trying to pass #01 under draft but outbrakes himself and hits us, #40, spinning us...

mpr uploading... 40MB...

EDIT: timestamp added

#02 tries to pass #40 in an impossible situation. He dive-bombs into the corner resulting in a contact between #40 and #02.

Drive through penalty for an avoidable contact while overlapping.

Quote from CSF :

• 110 (GT2) (incl pace)
• #38 and #39
Sector 1 just before the hairpin
• Conquest have been trying to unlap themselves, so into the hairpin before the chicane, but outbraked themselves so Jason went back past. Conquest again got a run on us before the hairpins, but came up track and spun them both off track. Not cool at all. Replay to follow when Jason finishes up. (or if anyone has before, since Jason will be in car for... 2 1/2 hours. )

Both drivers only show very little respect for each other which caused the incident.
Both Teams receive a final warning to drive with more respect, no penalty given.

Quote from seldon :

protest #37 against #35

lap 34: in T8 car 35 did not left enough space

Replay

After reviewing the protest: It#s a normal racing incident. Both drivers didn't give enough room to each other held on when they probably could have backed up.

No penalty given, normal racing incident.

Quote from r4ptor :

Lap 12
#5 (my3id) and #3 (f1rst)
~31 min 50sec

F1RST nudges our car during turn exit resulting our driver to lose control and spin.

Replay

dt for #03 for avoidable contact with another car (#05) and spinning him off the track

Replay of the start can be found here: http://www.mediafire.com/?dmw9zm10lji

Provisional Result

Full Replay

Last edited by amp88, Thu, 26 Mar 2009 08:33.

I'd like to remember that every Team must have a representant available in the IRC channel (#moe @gamesurge) using your team tag (example: MoE|nickname) at all time during the race.

If your team has cars in both classes one person will be enough

meh

Start procedure:
Normal start, start at 15:00UTC, drivers should be in the server at latest 14:50UTC

45% rule:
GT1: 246 laps
GT2: 231 laps

State your protest here:

Include the following in your protest
• The correct lap,
• The cars (/teams) involved
• The lap/sector/time
• And a short description from your point of view.

Include a replay with at least 10s before and 10s after the event for which you protest (link). Additionally a movie of the incident may be useful as well, but protests have to include a replay.

Free sites to upload movies are: http://www.mediafire.com
http://www.rapidshare.com

Trackmap:

Last edited by three_jump, Sat, 24 Jan 2009 15:17.

# - Penalty - Event - Timestamp
Qualify

Race
dt for #42 for changing the name on server (wrong name format)
dt for #03 for avoidable contact with another car (#05) and spinning him off the track (given at 17:30 UTC, served)
dt for #33 for chatting (given at 18:07 UTC, served)
dt for #17 for chatting (given at 10:19 UTC, served)
dt for #02 for causing an avoidable crash with #40 (given at 21:38 UTC, served)
dt for #14 for unsafe overtaking. (given 23:27 UTC, served)
dt for #11 - blocking/unblocking message - chat penalty(given at 2329, server at 23:30)
dt for #16 - blocking/unblocking message - chat penalty (given at 01:44 UTC, served)
dt for #05 - avoidable contact w/ #40 (given at 04:12 UTC, served at 04:14)
dt for #39 - chatting (given at 07:16 UTC, severd)
+1 lap for #03 - shift+s
dt for #11 - blocking/unblocking message - chat penalty(given at 10:16 UTC, served)
dt for #09 - chatting (given at 11:19 UTC, served)
dt for #05 - chatting (given at 12:06 UTC, served)
dt for #06 - avoidable contact /w #14 (given at 12:26, served)
dt for #33 - chatting (given at 12:53 UTC, served)
dt for #17 - chatting (given at 13:53 UTC, served)

Last edited by three_jump, Sun, 25 Jan 2009 13:56.

It seems that Bourdais gets his deserved 2nd chance: http://www.scuderiatororosso.com/Team/

nothing official yet...

It was much more then the current KB - Stabilized

Quote :

Explanation of Recent Keyboard Changes - 21 Feb 2004

Here's an explanation of the reasons for the new keyboard steering systems found in the recent patches.

Explanation of the need for the Keyboard Changes :

The keyboard steering changes were introduced for the benefit of the Live for Speed Community - Keyboard users and Analogue users alike. They are meant to promote better competition and online racing and the LFS developers believe that these changes will achieve this.

Problems with the old system that the changes are designed to tackle :

Because of the extreme, accurate, predictive steering help, the old keyboard steering system automatically corrected skids for the user, in a sense before they even happened, so efficiently that a rear wheel drive car could be kept at full throttle even when a driving wheel was on the grass. This is not possible in real life or in Live for Speed either, due to human reaction time, when using any other control device such as a steering wheel or mouse. The same thing with hitting kerbs at high speed, as in real life, analogue users must be careful about hitting kerbs and release the throttle and attempt to control the car when these situations are unavoidable. Great skill can overcome many of the drawbacks of human reaction time, but never fully, and not to the standard of the computerised automatic steering that was present in the now obsolete keyboard steering system. This introduced 3 clear problems into the Live for Speed competitive environment.

1) Beginner Problem : Beginners found it too easy to drive the cars at high speed, being able to drive the cars very fast while mouse and wheel users at the same level of experience were still learning to control the car on the limit.

2) Hotlapping Problem : Keyboard users were able to refine their lines and take straighter lines through bends and chicanes because of their freedom to use the kerbs and grass edges due to the computer help.

3) Online Racing Problem : Keyboard users had very little fear of crashing and bumping with other cars. The slightest impact is very hard to control with mouse or wheel, as in real life racing, because of the upset balance of the car. A minority of keyboard drivers would use this to their advantage, often ramming their way through the field at turn 1 of a race, giving them an unfair advantage and making the analogue drivers lose the race when it had hardly begun.

...

http://www.lfs.net/?page=kb_explain

Quote from Fuse5 :

You should get back to LFS instead of trolling here

And yes. the vegetables. How could I have forgotten about those.



Comes to CR, vegteablz, we haz dem!!

Dresscode: Pink Racing leathers and a sexy helmet

I added what you forgot

Quote from dougie-lampkin :

One thing I noticed when playing with vLite though - they've named it Windows 6.1

Cause that's the version number of the kernel. It's a slighty improved Vista, but due the "bad" name Vista has the PR departed said: "We're gonna make it a 7".

It's a Windows Vista SE (second edition)

Quote from pb32000 :

Yer it's all gone to shit. Bearing in mind I'm using an absolutely positioned div here, which TBF is created and positioned dynamically using jQuery, IE8 can't work it out properly. In compatibility mode (I assume falls back to IE7) its fine, as it is when tested in native IE7 (god knows what 6 would do with it).

IE8 will need conditional stylesheets sadly.

so business as usual:
modern_browser.css
old_ie.css
ie7.css
ie8.css

at least they are consistent with it...

can someone make use of this wonderful stats too we have?

Quote from pb32000 :

...And then there's IE8. Haven't used this before due to it being beta etc. Fire it up, first site I go to is the latest web application I'm working on. Positioning is out. Thank you m$, so that'll be ANOTHER conditional stylesheet then

So it's not just me then? IE8 seems to handle divs different then previous versions but I haven't figured out yet where to fix it.

Concept racing builing an army?

Use the above format only.

Deadline is Friday January 23, 21:00 UCT.

Teams with provided drivers list
GT1
#01 Mercury Racing Team
#02 #low-racing
#03 F1RST Racing
#04 SK Gaming
#05 My3id Gaming
#06 spdoRacing
#07 mb.racing
#09 Serbian Racing Team
#10 LFSLA
#11 CoRe Racing
#14 XFusion Racing
#15 n1Racing
#16 Team Inferno
#17 Speed Core Racing Team
#18 The Danish Racing Team

GT2
#30 CoRe Racing
#32 XFusion Racing
#33 prodrive' Racing
#34 spdoRacing
#35 F1RST Racing
#36 GVR Team
#37 Infinity Skills
#38 Sonicrealms Racing
#39 Conquest Racing
#40 AutoMotoTrke.net Sim Racing
#42 Teamsport Online

Missing entries
GT1


GT2


Driver names should be announced the Friday before the start of the race by 21:00 UTC. Teams who fail to meet this deadline will start at the rear of their respective class grid.

Last edited by DeadWolfBones, Fri, 23 Jan 2009 19:15.