F1 World Championship 2012 Thread

By +Frank B.
in The Sporting Arena

 Share

Recommended Posts

Grand Master

MightyJordan

Posted
Posted

Reject of the race: Two contenders imho - Maldonado and Grosjean

I'd opt for Maldonado there for jumping the start, and then seeing karma come round to kick him up the arse after the restart. :p

Fantastic drive from Jenson. Hopefully we'll see some more wins from him this season; that'd help to blow the WDC race wide open.

Grand Master

+Frank B. Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Belgian GP: Romain Grosjean gets one-race ban for start crash

Romain Grosjean has been given a one-race ban for triggering the Belgian Grand Prix start crash.

The Lotus driver moved across on Lewis Hamilton on the run towards the first corner of the Spa race, causing the McLaren to take to the grass.

The two cars then made contact and ploughed into Fernando Alonso's Ferrari and the two Saubers.

Grosjean said he could not be sure who had caused the crash.

" a very good start and then boom - it was the end of the race. I haven't seen the images and I need to see them to have any point of view," he said.

"But the main thing is that everybody is OK. That is the most important for me."

But the Frenchman was widely held responsible and has now been given a one-race ban for next week's Italian GP.

Lotus has former Virgin racer Jerome D'Ambrosio as a reserve driver.

Source: Autosport

Grand Master

+Frank B. Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Belgian GP: Pastor Maldonado gets double grid penalty for Timo Glock crash and jump-start

Pastor Maldonado will be demoted 10 places on the Italian Grand Prix grid as a punishment for both jumping the start in Belgium and colliding with Timo Glock.

The Williams driver had already been given a three-place grid penalty at Spa for blocking Nico Hulkenberg in qualifying.

He then made a premature getaway in the race, before being tagged into a spin as the crash involving Romain Grosjean, Lewis Hamilton, Fernando Alonso and the Saubers unfolded.

Maldonado rejoined, only to collide with Timo Glock's Marussia at the restart, ending his race.

Although Glock was able to continue, the stewards ruled that Maldonado's actions in the clash deserved a five-place penalty.

They also bestowed an additional five-place drop as he had been unable to take the usual drivethrough penalty for a jump-start in the race due to his early retirement.

"The driver failed to finish the race so the usual penalty for a false start could not be imposed," said an official statement.

Maldonado accepted the blame for the start error.

"I made a slight mistake at the start because the clutch slipped out of my hands before the red light switched off," he said.

Source: Autosport

Grand Master

Noir Angel

Posted
Posted

Although it does seem to me that the FIA have banned Grosjean in a somewhat reactive manner simply based on how bad that pileup was I can't really argue against the FIA's decision it was a dangerous manoeuvre but I do agree that Maldonado gets away with far too much. It's just lucky that Alonso wasn't injured more severely, and Lewis loses even more ground through no fault of his own. Great drive from Jenson, but disappointment for Lewis again.

Grand Master

what

Posted
Posted

The thing with Grosjean is that he's had many similar incidents at the start this year. Remember the one at Monaco? It could have been a lot worse than it was, but it was the exact same mistake. A race ban may stop him from being quite so aggressive on the start.

Maldonado shouldn't be in Formula 1. He is a complete moron. He even crashed on a PR stunt in Venezuela ffs. Here's a list of penalties he's had so far this year (remember he was the top of the list for number of penalties last year as well):

Chinese GP: 1) Pastor Maldonado (Williams) Impeding Heikki Kovalainen during Q1, reprimand

Bahrain: -2) Pastor Maldonado (Williams) Drops 5 places on the grid for taking a replacement gearbox

Monaco: 3) Pastor Maldonado (Williams) Breach of Article 16.1 of the FIA's Sporting Code, 10 place grid drop

Canada: - 4) Pastor Maldonado (Williams) Investigated for impeding Kimi Raikkonen (Lotus) during Q1, racing incident, no further action

- 5) Pastor Maldonado (Williams) Drops 5 places on the grid for taking a replacement gearbox

Europe GP: - 6) Pastor Maldonado (Williams) Speeding in the pitlane during FP3, 66.1 km/h fined ? 1,400,

7) Pastor Maldonado (Williams) Collision with Lewis Hamilton (McLaren) Drive through penalty post race, 20 seconds added to elapsed time

British: - 8) Pastor Maldonado (Williams) Caused a collision with Sergio Perez (Sauber) Fined ?10,000 and given a reprimand

German: -9) Pastor Maldonado (Williams) Speeding in the pitlane during FP1 66.0 kmh, fined ?1,200

Hungary: - 10) Pastor Maldonado (Williams) Caused a collision with car no 11 Paul di Resta, drive through penalty

Spa: - 11) Pastor Maldonado (Williams) The driver of Car 18 impeded Car 12 at Turns 18 and 19, drop of 3 grid places

- 12) Pastor Maldonado (Williams) The driver of Car 18 jump start, 5 grid drop penalty

13) Pastor Maldonado (Williams) causing a collision with cAR 24 on Lap Five. 5 grid drop penalty

(crossed out the gearbox penalties though iirc one of them may have been caused my Maldonado anyway)

Just to make that clear: he's had THREE grid penalties handed to him in this weekend alone.

  • Lovell and MightyJordan
  • Like 2
Grand Master

Noir Angel

Posted
Posted
Jenson Button admits that he was left disappointed after Lewis Hamilton posted some of McLaren's technical information on Twitter.

Frustrated be McLaren's decision to run the team's old rear wing in qualifying for the Belgian GP which contributed to his eighth spot on the grid, Hamilton took to Twitter to vent his frustration.

"Damn, WTF!! Jenson has the new rear wing on, I have the old. We voted to change, didn't work out. I lose 0.4 tenths just on the straight," he wrote.

"Nothing I could do. Now, it's about picking up every point I can from there. Jenson should win easy with that speed."

While the former World Champion later removed the tweets, he was at it again on Sunday, this time posting telemetry data.

While McLaren have decided not to take any action against Hamilton, Button admitted to being let down by his team-mate's actions.

"I'll say disappointed," Button said of his feelings on the matter. "We work so hard to improve the car and to keep things like that private.

"I didn't want to see it on Twitter. It was the whole telemetry from qualifying. It wasn't just the rear wing. I was very surprised and disappointed."

While Hamilton may have been left frustrated by the weekend's action, Button enjoyed quite the opposite, winning the race from pole.

Source

Quite the furore over Lewis's posting of his telemetry on twitter, an admittedly silly thing to do. Opinions?

Grand Master

what

Posted
Posted

I think he was just getting carried away with tweeting, trying to do one better than Alonso who has taken loads of pictures from his training and inside the Ferrari facilities. They were in a race to 1 million followers.

Lewis is definitely more susceptible to letting his emotions dictate his public behaviour though.

Grand Master

Noir Angel

Posted
Posted

That I agree with. Up until now he's done a reasonable job of keeping a lid on them this season but this is a bit of the old emotional Lewis coming through. What's odd is that he apparently agreed with the team's decision to use the high DF rear wing so he must share some of the blame. The old F1 adage is that you win as a team and lose as a team.

Veteran

philcruicks

Posted
Posted

Lewis Hamilton 'set for move to Mercedes from McLaren'

Lewis Hamilton is on the verge of leaving McLaren to drive for Mercedes next season, according to BBC F1 chief analyst Eddie Jordan.

The former team boss says Hamilton will replace Michael Schumacher, who will retire from driving for a second time at the end of the year.

"I believe Hamilton and Mercedes have already agreed personal terms and a deal could be imminent," Jordan said.

source: http://www.bbc.co.uk...rmula1/19489930

Grand Master

Noir Angel

Posted
Posted

Great performance from the McLaren boys there, Ferrari tried to play the team role and failed, amusingly badly. Would like to know what went wrong for Alonso on his final run there. A front row lockout on Ferrari turf is always satisfying!

Grand Master

Noir Angel

Posted
Posted

Apparently the roll bar failed in Alonso's car just before the start of Q3 and they didn't have time to fix it, which explains his poor pace and why it was he that gave Massa the slipstream. Could prove to be pretty costly if my suspicion that Massa won't be quick enough to interrupt the McLarens plays out.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Nick H. · Posted

      I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • Halo: Campaign Evolved is out next month with new prequel missions

      By +pmrd · Posted

      As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Malisk · Posted

      I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • Microsoft confirms a new, useful Teams' app is coming very soon

      By Malisk · Posted

      I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame

      By hellowalkman · Posted

      Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.

  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!