I'm sure you probably know already, but lfs.net news still points to 6D. I'm sure weekenders will be visiting there first and will still download the broken version.
Possibly related to the server outage, but I cannot log into LFSWorld. A guest login works, and my last races haven't been logged when viewing my stats as guest.
Whatever the changes are, they should have been clearly stated, and the timing of their implementation should have been made clear.
Changing regs midway through the season is unprecedented, and they are even changing them midway through a race weekend. There is an exception, and that was purely on safety grounds after the sad Imola weekend where we lost Senna and Ratzenburg. Coulthard mooted a little while ago on BBC, that it could even be dangerous becuase drivers are going out not knowing the car at all with the fundamental handling changes.
Changing regs midway through the season is unprecedented, and they are even changing them midway through a race weekend. There is an exception, and that was purely on safety grounds after the sad Imola weekend where we lost Senna and Ratzenburg. Coulthard mooted a little while ago on BBC, that it could even be dangerous becuase drivers are going out not knowing the car at all with the fundamental handling changes.
I was just watching a long shot, and saw Swallows or House Martins swooping low over parts of the track. I wonder if bird strikes are ever a problem?
I suggest we move this conversation to the British GP thread which is where we will see the impact, or the general 2011 season thread for the overall picture.
I can't quite make out what all the fuss about the sounds is. A couple of interesting points from Ant Davidson and Murray Walker during FP3 Silverstone.
- Back in the 80's we had 1.5 litre turbo engines and nobody complained about the noise or lack of.
- The more energy wasted producing noise, is less energy being delivered to the wheels.
Indeed.
Both drivers slow during the "conference" but set the pace afterwards, hmmm....
Good to hear Murray on the mic. When told he was trending globally he asked "what's that?" Classic lol.
Ted Kravitz BBC just announced that Charlie Whiting has rescinded the 50% blowing that Renault were allowed. Now we're back to 10% only for hot and cold blowing. Team principals are with Charlie right now.
As an aside, Wiki has some enlightening takes on the various versioning systems over the years.
http://en.wikipedia.org/wiki/Software_versioning
The upshot is, no it doesn't really matter, and the developers can choose whatever method suites them.
http://en.wikipedia.org/wiki/Software_versioning
The upshot is, no it doesn't really matter, and the developers can choose whatever method suites them.
Using the hotlap system is a good idea, but if the layout goes off track - like a rally stage for example - the HL becomes invalid (ground) and even the slightest touch of an object will invalidate the lap. Just keep to spr's would be my suggestion.
I'd like to echo that sentiment.
It's good to see some well composed videos of the races, and this is an excellent example. Keep up the good work
It's a parallel of Godwin's Law unique to LFS
In other words,
/thread
Not as much action as I expected. Some nice battles further down the field but overall a fairly processional race.
Happily I was completely wrong about the steering wheels, and nothing appeared to be amiss.
Happily I was completely wrong about the steering wheels, and nothing appeared to be amiss.
There are 2 base ignition modes plus 11 selectable ignition/fuel modes that can be selected at any time.
I'm looking forward to plenty of overtaking today. Hopefully while all four wheels are on the track.
Convention says that < 1 version numbers are in alpha and not feature complete. That could be said of LFS, and we did have the alpha tag until recently, but who says LFS has to be conventional?
At the end of the day, who gives a F*** as long as each iteration gets better. I'd suggest masturbating with stolen cheese as a good therapy.
At the end of the day, who gives a F*** as long as each iteration gets better. I'd suggest masturbating with stolen cheese as a good therapy.
The teams are allowed 2 base ignition maps, and these can only be changed by the driver while the car is stationary for at least 3 seconds. A pit stop qualifies here. The new ruling prevents the teams from reprogramming the engine maps between qualifying and the race. ie an aggressive map used for qualifying, must then be used for the race. A qualifying map could potentially cause reliability problems, and fuel consumption would be much higher. Red Bull seem to have had a very good qualifying pace, but come the race, and particularly after the first stop, they seem much slower. This may or may not be due to the reprogramming that was allowed.
It takes approx 2 minutes to upload the ECU maps from a laptop connected via an ethernet link. We know the ECU and the dash are sealed units which communicate over a CAN2.0b bus, however, I cannot see anything to prevent a connection over ethernet from the steering dash as well. If, and this is highly speculative on my part, the ECU could be reprogrammed during the race without the need for an external laptop connection, then the first part of the race can be run on the qualifying map, and then switched to the softer maps during pitting. At least 2 pit stops would be needed, the first to select an intermediate map and change the software over, and the second to switch to the softer race map.
This is just a gut feeling, and checking the regs, original specification of the ECU, and the attention being paid to steering wheels lately make me suspect a loophole might have been found. The race will reveal if any of this is true.
Another question/prediction to throw into the mix, and to show I'm not just RB bashing - Ferrari will make another perfect start today. How do they manage that, some kind of legal launch control? hmm...
It takes approx 2 minutes to upload the ECU maps from a laptop connected via an ethernet link. We know the ECU and the dash are sealed units which communicate over a CAN2.0b bus, however, I cannot see anything to prevent a connection over ethernet from the steering dash as well. If, and this is highly speculative on my part, the ECU could be reprogrammed during the race without the need for an external laptop connection, then the first part of the race can be run on the qualifying map, and then switched to the softer maps during pitting. At least 2 pit stops would be needed, the first to select an intermediate map and change the software over, and the second to switch to the softer race map.
This is just a gut feeling, and checking the regs, original specification of the ECU, and the attention being paid to steering wheels lately make me suspect a loophole might have been found. The race will reveal if any of this is true.
Another question/prediction to throw into the mix, and to show I'm not just RB bashing - Ferrari will make another perfect start today. How do they manage that, some kind of legal launch control? hmm...
You're right, they don't normally, however, if they were to include a game cartridge style loader inside the wheel, then a live load could feasibly be achieved while they stay in one particular map mode after the pit stop. That 2 minute load time can be done while on the move. Plug 'n' Play if you will. I don't see anything to prevent this happening.
It'll be interesting to see how it pans out. There seems to have been a little too much attention paid to steering wheels lately, so something is afoot.
Shouldn't you have said nothing has changed?
I think that some clever shenanigans are going on. The changing of engine maps between qualifying and the race have been removed, but that doesn't prevent a team changing the map during the race.
I'll stick my neck out on this theory - Red Bull will do a short first stint, and change steering wheels on both cars during the pit stops.
Looks like it will be a good qualifying. From the practice sessions, they each have different sections where they have different strengths.
I have a sneaking suspicion we might see steering wheel changes during the race. If not tomorrow, then Silverstone.
I have a sneaking suspicion we might see steering wheel changes during the race. If not tomorrow, then Silverstone.
Thanks for the replies.
I was probably just remembering it wrong then. I've lost my archive of older LFS revisions, so was unable to check back. Somehow, I mistakenly believed we had a little more control over the start parameters, and I'm probably confusing it with some other software. When I did resort to RTFM, I was left non the wiser, so perhaps the distinction between LFS cfg.txt and LFS (host) cfg.cfg could be clarified in the documentation?
/windowed= as a startup parameter would be most beneficial. Sometimes, other applications might need attention when we start LFS, and to be able to override the config would help here without flipping from the last stored window state in the config.
To be able to specify a /cfg= for a single session would allow us to make different shortcuts when different hardware is involved. In particular, I have a projector that is very picky about its resolution and refresh rate, so if I forget to change screen modes after I've used my desktop monitor, it causes problems when I start up next time with the projector connected. (hence the need for windowed mode) The same goes for controllers. A visit to options is required every time a different controller is used because this is the only place the settings are stored. The rest of the adjustments I need to make can be controlled via an InSim connection or autoexec.lfs of course, but display and controllers aren't included.
I suppose what I was expecting was, to be able to specify a profile at the command line/shortcut without needing to visit options every time.
There is a workaround and that involves a copy of the install so the different configs can be used. This is suboptimal and can cause synchronisation problems between installs. More ideally, (but doesn't work on XP) is to create a virtual install using symbolic links for everything but the config, logs and autoexec.lfs. This allows the linked LFS to have its own configuration all of its own. All of this could be much simpler though.
I can't find anything on /hlvc. What does this do? I tried it and got a server style window pop up briefly. There's some red warning text, but it disappears too quickly to be read. The log doesn't give anything away either.
It's a shame I hadn't spotted the documentation anomalies before the last round of patches. I understand that as things grow organically, documentation can get overlooked, but I think commands.txt needs a little more clarity, and better distinction made between host commands and general commands. It might be fair to say that many of us can interpret which is which, but when something doesn't go as expected, the docs -the first port of call- should be concise. This might be especially true for non English speakers where a literal translation can be even more misleading and contradictory.
I realise that the tyre physics and related works are now the focus of your attention, but could you please make a note to make some clarifications in the docs come the next round of patches?
I was probably just remembering it wrong then. I've lost my archive of older LFS revisions, so was unable to check back. Somehow, I mistakenly believed we had a little more control over the start parameters, and I'm probably confusing it with some other software. When I did resort to RTFM, I was left non the wiser, so perhaps the distinction between LFS cfg.txt and LFS (host) cfg.cfg could be clarified in the documentation?
/windowed= as a startup parameter would be most beneficial. Sometimes, other applications might need attention when we start LFS, and to be able to override the config would help here without flipping from the last stored window state in the config.
To be able to specify a /cfg= for a single session would allow us to make different shortcuts when different hardware is involved. In particular, I have a projector that is very picky about its resolution and refresh rate, so if I forget to change screen modes after I've used my desktop monitor, it causes problems when I start up next time with the projector connected. (hence the need for windowed mode) The same goes for controllers. A visit to options is required every time a different controller is used because this is the only place the settings are stored. The rest of the adjustments I need to make can be controlled via an InSim connection or autoexec.lfs of course, but display and controllers aren't included.
I suppose what I was expecting was, to be able to specify a profile at the command line/shortcut without needing to visit options every time.
There is a workaround and that involves a copy of the install so the different configs can be used. This is suboptimal and can cause synchronisation problems between installs. More ideally, (but doesn't work on XP) is to create a virtual install using symbolic links for everything but the config, logs and autoexec.lfs. This allows the linked LFS to have its own configuration all of its own. All of this could be much simpler though.
I can't find anything on /hlvc. What does this do? I tried it and got a server style window pop up briefly. There's some red warning text, but it disappears too quickly to be read. The log doesn't give anything away either.
It's a shame I hadn't spotted the documentation anomalies before the last round of patches. I understand that as things grow organically, documentation can get overlooked, but I think commands.txt needs a little more clarity, and better distinction made between host commands and general commands. It might be fair to say that many of us can interpret which is which, but when something doesn't go as expected, the docs -the first port of call- should be concise. This might be especially true for non English speakers where a literal translation can be even more misleading and contradictory.
I realise that the tyre physics and related works are now the focus of your attention, but could you please make a note to make some clarifications in the docs come the next round of patches?
Last edited by Squelch, .
FXR Team == FXR Guest == (Password .jpg)
All of the other downloads look ok.
Edit: the link on the page is wrong. FXR dds can be found here
http://alkospirt.ucoz.ru/skins_alkospirt/dds/FXR_AS_2011.rar
All of the other downloads look ok.
Edit: the link on the page is wrong. FXR dds can be found here
http://alkospirt.ucoz.ru/skins_alkospirt/dds/FXR_AS_2011.rar
Last edited by Squelch, .
Reason : added link
Classic!
I blame Matt Lucas for setting the trend
I had trouble seeing what the problem was at first, but if you look at the currency symbols in the images I think that is what the OP is referring to.
Track is very dusty in FP1. Lots of brake zone issues for drivers so far.
I just posted in the main F1 2011 thread that Red Bull are running the Silverstone spec engine map. Vettel is way down the timing screen, and Ant noticed his car sounded flatter than usual. I feel RB are quite worried about their pace come the new rules. The Qualifying pace might not be there for them.
I just posted in the main F1 2011 thread that Red Bull are running the Silverstone spec engine map. Vettel is way down the timing screen, and Ant noticed his car sounded flatter than usual. I feel RB are quite worried about their pace come the new rules. The Qualifying pace might not be there for them.
Red Bull have confirmed they will be running Silverstone mapping at Valencia this morning. Vettel currently way down the timing screen, but that may be down to high fuel/other tests. It's interesting that Vettle might be the one who will end up most disadvantaged by the ban on blown diffusers.
FGED GREDG RDFGDR GSFDG