F1 World Championship 2008 Thread



Recommended Posts

Interesting. I think and hope that Hamilton has a lot of fuel, but we'll see. And I think something needs to be done regarding Heidfeld's "incident" on his last lap. All these slow cars ruined his lap and it was very dangerous.

Edited by .mcman

what an exciting result and with predicted rain tomorrow it could be the race of the year :D

i am very happy for massa that was a very special lap but i think both ferraris have not the race pace and not ennough fuel in their cars to win this race.

in post-quali interview hami complained about his (quali)setup but thinks it wont be an issue for the race.

to heidfeld. i dont understand him. this guy has a real mercedes-complex. it was perfectly well for him to block alonso last year wherever he could and well today he had to realize how it feels if slower cars are in front of you. it was clear from the beginning after they (wrongly imho) did away with the single-lap qualifying of 2003-2005 that traffic now will be a problem again. but i guess there wont be any perfect quali-format for everyone. :p

Ouch, 5 place penalty for Hamilton and Kovalainen for blocking Heidfeld/Alonso at end of the session..

http://www.autosport.com/news/report.php/id/66021

I bet that wouldn't be the case if it was the 2 Ferrari's blocking. **** it. :angry:

Hoping for the 2 Ferrari's to run into each other in either T1 or T2. (awaits gun shots) :p

Edited by Fergie
What a crazy start to the season. Disappointed by the results (or lack of) by Ferrari.

What a let down for Sebastian Bourdais.

Congrats to Hamilton, Heidfeld, Rosberg.

Brilliant bhoooooo on the grand stand from the public after a VICTORY.... wander what's going to be this time?

Ouch, 5 place penalty for Hamilton and Kovalainen for blocking Heidfeld/Alonso at end of the session..

http://www.autosport.com/news/report.php/id/66021

Serves right to McCrucks team!

I went there at around 11.30 in the morning, arrived and collected my tickets and had a stroll around the Main Concourse. Qualifying was really good and it ran like clockwork. Nearly every team went out straight away as they were all afraid of the rain that looked like it was bursting :p ! Not that much changed as most of the front runners were posting good times, especially during Q2. However, Hamilton disappointed me as he was very much behind his team mate and only went 4th (before being penalised). Another team that surprised me was BMW Sauber, who were really quick, especially through Q2.

I really enjoyed it, much has improve since my last visit two years ago but there is still some room for improvement. One thing that was bothering me was that there was hardly any entertainment before qualifying, and the appointed radio stations were just blaring out pop hits. Parking was improved, as well as general amenities, such as toilets and surau's. Formula team merchandise still cost the earth, evident by the fact that one of the shirts cost RM500, about more than a quarter of my salary :p !

I just hope that tomorrow it doesn't rain so much. When I came back from Sepang, there was a thundering storm so anything like that during the race will certainly result in a delay, or even a cancellation. I want rain, just not that much :p !

I'm going to bed now as I'll probably leave at around 11 in the morning, so I see you another time. I'm at Hill Stand at Turn 1, so there will certainly be a lot of action!

Scirwode

First of all hats of too BMW and too Ferrari. I loved the Qualifying session and I can't wait till the race tomorrow.

Secondly, Does anyone seriously think it is going to rain tomorrow? All the drivers are hoping to avoid the rain cause of lack of traction control... Will be interesting.

I agree with the penalty on the McLaren's, but I feel there were another 3 cars that should've also been penalised or at least warned. Hamilton, Kovalainen, Massa, Raikkonen and Kubica (or Webber, unsure which) were all going far too slow and pretty much in the way. Was a slalom for Heidfeld and Alonso, although I doubt it would have made much difference anyway.

I think Hamilton is partly heavy on fuel and partly struggling with the car. He seemed to have some oversteer problems. Might be rain tomorrow so it will be interesting to see how it all plays out.

Edited by Fourjays
I agree with the penalty on the McLaren's, but I feel there were another 3 cars that should've also been penalised or at least warned. Hamilton, Kovalainen, Massa, Raikkonen and Kubica (or Webber, unsure which) were all going far too slow and pretty much in the way. Was a slalom for Heidfeld and Alonso, although I doubt it would have made much difference anyway.

I think Hamilton is partly heavy on fuel and partly struggling with the car. He seemed to have some oversteer problems. Might be rain tomorrow so it will be interesting to see how it all plays out.

But the Mclaren's were on the racing line which was unacceptable at those slow speeds. Rain tomorrow will stir things, wet start with no traction control will be interesting.

Maybe Ferrari can pull out a win on my Birthday. :fun: It's a shame the McLaren's won't be right behind them at the start, they were not the only two cars that were in the way. If it rains it'll really interesting, especially without TC.

Edited by CrashGordon

I agree with the penalty too and I understand why only McLaren drivers were penalised. But I think cars that are going to the pits shouldn't be moving so slow when the others are still racing. Anyway, if there will be a rain tomorrow, I hope it won't be too heavy. Start+safety car= :x

Here's the revised Grid:

At least three drivers will drop from their original qualifying positions on the grid for Sunday?s Malaysian Grand Prix. McLaren?s Heikki Kovalainen and Lewis Hamilton both lose five places for impeding rival drivers in Q3, while Williams? Kazuki Nakajima starts from the back after his ten-place penalty for a collision with BMW Sauber?s Robert Kubica at the last round in Australia.

The full provisional grid is as follows (the final grid will be published as usual by the FIA on Sunday morning - we will bring you details of any additional changes):

1. Felipe Massa, Ferrari

2. Kimi Raikkonen, Ferrari

3. Jarno Trulli, Toyota

4. Robert Kubica, BMW Sauber

5. Nick Heidfeld, BMW Sauber

6. Mark Webber, Red Bull

7. Fernando Alonso, Renault

8. Heikki Kovalainen, McLaren

9. Lewis Hamilton, McLaren

10. Timo Glock, Toyota

11. Jenson Button, Honda

12. David Coulthard, Red Bull

13. Nelson Piquet, Renault

14. Rubens Barrichello, Honda

15. Sebastian Vettel, Toro Rosso

16. Nico Rosberg, Williams

17. Giancarlo Fisichella, Force India

18. Sebastien Bourdais, Toro Rosso

19. Takuma Sato, Super Aguri

20. Adrian Sutil, Force India

21. Anthony Davidson, Super Aguri

22. Kazuki Nakajima, Williams

I'm thinking they were using Kovalainen and Hamilton as examples.. I bet we won't see as much coasting in the next Q.

Anyway, something had to be done. Seeing the last lap from Heidfeld's car was crazy, everyone else doing under 80 and Heidfeld blasting past at full speed, dodging cars from side to side.

Ferrari's probably got this one in the bag, the important thing is how much can McLaren pick up.

You would think so, but you never know, hopefully Ferrari's Engine will hold up this race :p

But still I think this race will be a good one, Hamilton is gonna have to push really hard to gain grown on the Ferrari's and if it rains, god knows what will happen!

Rain + No Traction Control = Guaranteed Mayhem.

Just look how many cars finished in Melbourne, that was in the dry too!

But the Mclaren's were on the racing line which was unacceptable at those slow speeds.

I disagree with the slow speeds altogether, regardless of the racing line. All the cars I saw (except Heidfeld and Alonso) treated it as "session over", but they crossed the line with 38 seconds still to go, meaning some may still be doing (or starting) a hot lap even though they had done theirs. If cars purposely went that slowly in the middle of a session (say 7 minutes to go) I'm sure they'd be in serious trouble over it.

It's an exploit that has come out of removing the race fuel credits from the knock-out qualifying system. Until the session has finished, they should be required to return to the pits in a timely manner.

I'd also go with 15 in a dry race. They all seem more comfortable with the cars at Malaysia. Wet race I think would be as bad as Australia - I think chaos will break out as no-one has driven these new cars in the rain yet.

I'd also go with 15 in a dry race. They all seem more comfortable with the cars at Malaysia. Wet race I think would be as bad as Australia - I think chaos will break out as no-one has driven these new cars in the rain yet.

The first wet race is going to be interesting to say the least. :yes:

I disagree with the slow speeds altogether, regardless of the racing line. All the cars I saw (except Heidfeld and Alonso) treated it as "session over", but they crossed the line with 38 seconds still to go, meaning some may still be doing (or starting) a hot lap even though they had done theirs. If cars purposely went that slowly in the middle of a session (say 7 minutes to go) I'm sure they'd be in serious trouble over it.

It's an exploit that has come out of removing the race fuel credits from the knock-out qualifying system. Until the session has finished, they should be required to return to the pits in a timely manner.

Yes it is, I believe that they should scrap the fuel qualifying system and have it like the two previous sessions, that would mean that they can bring back the days of 1-stop and 2-stop strategies.

But the cars do go slow on there in and out laps, but the fact that the Mclaren's where on the racing line makes it dangerous and effects anybody racing a hot lap.

Even I support the scrapping off race fuel. But because of the engine rules, they will still go a slowish pace.

They may have to rejigg how many cars can be out on the track at the same time, then as soon as the driver enters the track, the clock starts for them. If he comes into the pit, then no one else can go out till his time has run out.

Thats is a way to get rid of this stupid slow lap stuff.

I'll wait till I see footage tomorrow to judge, but I'm sure the other slow cars were causing problems as well.

now that was a boring race and not worth watching it :sleep: :sleep: :sleep:

after ferrari screwed up massa in the pitlane i am happy that he showed them that this time he won't support his teammate to another lucky championship but has to do it on his own now. and you could see the face of jean todt - he was not amused what they did with felipe.

mclaren was bad today but in damage control mode and got some points. the gap between hamilton and raikkonen is even bigger than between raikkonen and kovalainen which is a very nice surprise.

alonso - not possible to do more with such a truck of a car.

6 ferrari engines blown up already ... will for sure reach double digits before season is over. :laugh:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!