129 members have voted

  1. 1. Which team will win the Constructors Cup?

    • McLaren
      48
    • Mercedes GP
      11
    • Red Bull
      29
    • Ferrari
      36
    • Williams
      1
    • Renault
      2
    • Force India
      1
    • Toro Rosso
      0
    • Lotus
      1
    • Campos
      0
    • US
      0
    • Virgin
      0
  2. 2. Who will be the world champion this year?

    • Jenson Button
      11
    • Lewis Hamilton
      33
    • Michael Schumacher
      13
    • Nico Rosberg
      1
    • Sebastian Vettel
      10
    • Mark Webber
      21
    • Felipe Massa
      8
    • Fernando Alonso
      26
    • Rubens Barrichello
      1
    • Nico Hulkenberg
      0
    • Robert Kubica
      3
    • Vitaly Petrov
      2
    • Adrian Sutil
      0
    • Vitantonio Liuzzi
      0
    • Sebastien Buemi
      0
    • Jaime Alguersuari
      0
    • Jarno Trulli
      0
    • Heikki Kovalainen
      0
    • Bruno Senna
      0
    • Jose Maria Lopez
      0
  3. 3. Who will be the world champion this year? Continued

    • Timo Glock
      2
    • Lucas di Grassi
      2
    • VOID VOTE (Because of Neowin's restrictions, select this if you choose not to select the above two drivers
      125


Recommended Posts

What a boring race :l lol Vettel must have been crapping it... Going into every corner knowing his brakes might fail!

However... vettel was only 2 seconds a lap slower coasting/engine breaking... Aren't the virgins/lotus's about 2-3 seconds a lap slower... O.o

Hamilton "tyre management" you point to for today problem could very well be rim failure. ?Vettle had problems with his front wing as well (not being able to move it) ?

oh

btw, it seems this is 2nd time this kind of rim failure has happened for McLaren

Ham

hamilton2010.jpg

Kov., same track in 2008 GP

kova1.jpg

http://forums.autosport.com/index.php?showtopic=122528&view=findpost&p=4334602

it looks more and more that alonso might luck into his 3rd worldchampionship this year. :blink: :(

hamilton has just badluck all the time - im amazed how relaxed he still is.

the same goes for vettel.

i have big problems to see anything positive in that race, well maybe shueys 4th place is the good thing. :yes:

Good result for Webber, was hoping for a little more from Hamilton, but all in all a great race. SC made it very interesting. Good job by Kubica and Vettel (at least his car held together!).

I think MSC will run into problems, one of the rules states that if the SC car pulls in on the last lap, the cars will pass the chequered flag without overtaking, so although it seemed legit, think he might get stung for that.

I think MSC will run into problems, one of the rules states that if the SC car pulls in on the last lap, the cars will pass the chequered flag without overtaking, so although it seemed legit, think he might get stung for that.

Stupid rule in my opinion.

Exciting race nevertheless. Sucks for Button thought. :(

If Red Bull wont win championship this year I will be really surprised.

what a race. the first few laps had it in when alonso had to fight against backmarkers.

then there was a long boredom.

what i saw was a very strong redbull team, and especially webber, it was not their last 1-2 this year.

i also noticed that - given clean air - massa was lapping constantly between 0.4s and 1.1s a lap faster than his teammate which makes me happy as i know he still has it to beat alonso :)

best overtaking scene was the last corner from schumacher. SUPERB!!! now we can really say he is back. there is no way for a penalty, cause SC line is NOT the start/finish line as it used to be many years ago. so cars were free to race the last few meters.

schumi did everything right and alonso cooked it up again.

Regarding the last corner pass by MSC - it should be within the rules. Ballsy move in any case.

Perfect drive by Webber; one can only wonder how far ahead he would have been without the SC phases.

Reject of the race: The McLaren mechanic who forgot to remove the cover from Button's car. Tsk...

Regarding the last corner pass by MSC - it should be within the rules. Ballsy move in any case.

Perfect drive by Webber; one can only wonder how far ahead he would have been without the SC phases.

Reject of the race: The McLaren mechanic who forgot to remove the cover from Button's car. Tsk...

His drive was pretty perfect, can't argue with his quality. Although Maclaren are my favourite team, I want to see Webber win more races, possibly the championship, god knows he deserves it, he's been in F1 for 8 years now, and its only been since his move to Red Bull that he's been able to shine. Like Button last year, just shows that if you give him a decent car, he'll get the job done.

Lolage at the Maclaren mechanic, think he'll get in trouble for that.

The other thing I was wondering is if Rubens will get in trouble for throwing his wheel into the path of oncoming traffic?

His drive was pretty perfect, can't argue with his quality. Although Maclaren are my favourite team, I want to see Webber win more races, possibly the championship, god knows he deserves it, he's been in F1 for 8 years now, and its only been since his move to Red Bull that he's been able to shine. Like Button last year, just shows that if you give him a decent car, he'll get the job done.

Lolage at the Maclaren mechanic, think he'll get in trouble for that.

The other thing I was wondering is if Rubens will get in trouble for throwing his wheel into the path of oncoming traffic?

I would love to see Webber get somewhere this year, as long as they keep up the pace and sort reliability they should be okay. I wouldn't mind seeing him keep his seat at Red Bull or at least picking up a decent drive next year.

As for Button, I was listening to the commentary and a BBC reporter/commentator actually saw it prior to the race start and told Buttons engineer, but they didn't take any action on it (They called it "marginal" I believe) and then it was too late. He'd have dropped a few spots and got some points, as opposed to none at all.

The stewards report for this race will be a bit full even without Rubens throwing his steering wheel into traffic.

I would love to see Webber get somewhere this year, as long as they keep up the pace and sort reliability they should be okay. I wouldn't mind seeing him keep his seat at Red Bull or at least picking up a decent drive next year.

As for Button, I was listening to the commentary and a BBC reporter/commentator actually saw it prior to the race start and told Buttons engineer, but they didn't take any action on it (They called it "marginal" I believe) and then it was too late. He'd have dropped a few spots and got some points, as opposed to none at all.

The stewards report for this race will be a bit full even without Rubens throwing his steering wheel into traffic.

Yeah, they were gonna run with the part still in, but the safety car slowed down the race, causing the engine to heat up because it didn't get enough airflow. Still, that part shouldn't have been left in there at all....

Would LOVE to read the stewarts report!

20 second penalty for schumacher. official.

today f1 really died. fia is doing everything to keep unfairnando alonso in the championship race despite his permanent screw ups. :crazy: :angry:

Michael Schumacher has been handed a 20-second penalty for having overtaken Fernando Alonso on the final corner of the Monaco Grand Prix.

The Mercedes GP driver passed Alonso just as the safety car had left the circuit on the final lap, and stewards deemed the race was still finishing under the safety car.

Under rule 40.13, which states that "if the race ends whilst the safety car is deployed it will enter the pitlane at the end of the last lap and the cars will take the chequered flag as normal without overtaking," Schumacher has been given a penalty.

The German, who had passed Alonso for sixth, drops down to 12th, meaning Toro Rosso's Sebastien Buemi's scores the final point for 10th.

Source: Autosport

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

    • No registered users viewing this page.
  • Posts

    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I found that stability back then was really down to the motherboard manufacturer. Back then i stuck with Microstar motherboards and VIA chipsets as they were ultra reliable. Most stuff was done with jumpers and left little room for user created problems 👍
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      232
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!