100ms is actually 0.1 franky so 1.0 is 1000ms.

edit: Just to complete, I noticed that too but if you're lagging for a second it should be dark red and flashing with danger signs already!

Last edited by troy, Sat 27 Oct 2012, 19:56.

Small suggestion for the ping in the nameslist:

Would it be possible to graphically give the player an indication on how good/bad his ping is?

below 100ms = green
above 150ms = orange
above 250ms = red

or something along the lines?

Last edited by troy, Sat 27 Oct 2012, 20:13. Reason : typo

Sounds like it defaults to the other monitor output until you're in windows, I got the same thing here when I set my hd4000 internal graphics card as main graphics in the bios options, only once windows boots it actually notices that my gtx260 is plugged in on the main monitor. Check if you got picture on the second monitor, if you do there probably is an option in your bios somewhere to force the correct output.

If that doesnt work you could also try running it with just vga or dvi to see if you get picture somewhere and then check the bios for ways to tell it which output it should prefer.

http://youtu.be/snwKR9SzVjI second try, red bull pulled the first one in no time for whatever reason, after all it was broadcasted on youtube...

Unofficial numbers from the records guy: 1343km/h, Mach 1.24!

some on boards released too: pulled already, thanks red bull

Last edited by troy, Sun 14 Oct 2012, 21:38.

In the german interview that just happened some minutes ago he mentioned that he had no clue if/when he broke the sound barrier, he was way to busy trying to get the tumbling under control. He also was shortly before passing out and still somehow managed to trick the G-Meter so it doesn't go into emergency mode, that would happen with 6s of continuous tumbling, he managed to stop it for a few seconds every now and then, thats why it didn't throw the stabilizing chutes.

Well, that is an anti climax for today, too windy mission aborted. Better luck tomorrow.

The plan is to break the barrier of sound, and yes there will be cameras on felix' suit but we won't be able to see those images live due to technical reasons.

Some radio problems right now, kittinger doesn't sound very happy.

Balloon is rolled out now, felix is getting into the suit could be going upwards in about 2h. For the Germans servustv is broadcasting in hd the whole day already. (can get it via satellite, cable or on the internet)

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 21 UTC
Lap and Location of Incident: -
Your Car Number: 23
Other Car(s) Involved: 06
Brief Description of Incident:

I know it is being discussed already internally but I'd like to have something written down about this: Since only 2 teams where unlucky enough to have a British driver on-line at the time of the incident I can understand you not wanting to red flag the race, still the server was not showing up on the master server nor on lfsremote for a few minutes making it impossible to rejoin for anybody in the respective team. Since all the evidence points on the server to be the problem we lost a good 2 or 3 laps due to no fault of our own.

I will be streaming my stints too if anyone is interested.

http://www.livestream.com/lxo (getting in the car in about 45min)

I will be streaming my stints (and general teamspeak chatter plus some cats if you're lucky ) on here once again: http://www.livestream.com/lxo

Petrov also seems to have lost his complete rear wing on the main straight, there was no proper footage of it happening though, just the end of it was caught on the official fom feed.

I guess that -1 lap thing on disconnects mainly came to life because some "smart" top drivers found a loophole in most of the endurance rulesets to cure engine damage with an intentional disconnect right after crossing the finish line and in that case the penalty is well deserved.

Quote from deCesaris :

4) There should be a tracker, though we have a bit problems with it so can't promise anything.

Driving blind for 24h is certainly no fun, just takes one disconnect and you won't have a clue where you are without the tracker. I do hope you get something sorted, there are plenty of helpful community members around if you struggle on your own (thinking of KlausAdam or boothy/NDR for example)

Quote from Mustafur :

If he wants to stay with Mercedes, maybe head over for V8 Supercar, just a thought?

The only thing I can see him do is DTM, not because he likes it more then any other series out there but because of commercial reasons, would be huge for Merc having the Schumacher brothers back together again.

Question regarding pit entry, is the yellow line rule enforced there?

If it is: right now the layout forces you to slow down on the apex of the last turn (at least in a tbo) which in turn creates a danger for drivers behind somebody trying to pit. Would it be possible to make that yellow line a bit shorter so you can start slowing after the apex where it would be safer to do?

The Sauber offer did sound more like tongue in cheek, unless there was another non German Interview where he worded it completely different.

Quote from Matrixi :

LFS isn't a very good game for bench performance results for modern hardware, since it only makes use of a single processor thread.

i5-3570K is a great CPU for the price, but along with all the other Ivy processors, it isn't as good as the previous generation for overclocking due to the crappy thermal compound Intel used between the heatspreader and the chip itself.

Last I heard the thermal compound myth was debunked since it wouldn't make that much of a difference. It's more likely that the smaller size of the CPU makes it harder for the CPU coolers to get away the heat fast enough.

http://uk.hardware.info/news/2 ... ge-processor-not-worth-it

Well, I don't know if you checked it already but there is http://lfsbench.iron.eu.org/ which is LFS only though but may be a start.

edit: you may want to go back to the Z28 replay for a bigger list of systems, the 0.6B replay is rather new.

There is a PM function you know.

You guys planning on using the test-patch for the 24h race? I do think there are some important improvements on how packets are sent from server to guests and back.

Example: Pit-stops, if you want to overtake the car and somebody is timing out or joining at the same moment you need to wait until the person timed out/joined in the "old" system, with the new test-patch this should instantly work without delay.

I'm sure there is more, faster joining times for example that would make using the test-patch interesting.

As written in the title, just noticed this while doing some screwing around in the test patch B7 (I don't think it's patch related though, so I'm posting here)

Drive Through penalty was cleared after Daniel did a pitstop in his RB4 and I took over the car, I don't think that should be happening since you're not properly driving through the pits? Could it be that it doesn't register because there was no work done on the car?

Replay attached. (Time: 8min40s)

edit: Tested a bit more, it looks like there is never any work done even if you instruct lfs via F12 to do something, but you can give the car to another player which clears the penalty, I don't think that is intended behaviour?

Last edited by troy, Fri 21 Sep 2012, 18:19.

Quote from Nilex :

Rather simple and elegant solution would be to leave it as-is and move the connection bars for all guests into SHIFT+F8 network debug.

If we're talking about moving stuff already, I do think it would fit rather well into the nameslist (N) too, so you could easily figure out the player that is lagging. Usually you have to count lagbars, go to the player list, count players then you know who it was. Would cut down workflow quite a bit. (Mock-up attached)

Of course I got no clue how much work is actually involved in doing this, but I do think it would be a better solution then the current lagbars on the bottom left.

Last edited by troy, Fri 21 Sep 2012, 12:59.

Yes, well at least I couldn't do /clear when I tested.