110 members have voted

  1. 1. Which team will win the Constructor's Championship?

    • Red Bull Renault
    • McLaren Mercedes
    • Ferrari
    • Mercedes GP
    • Lotus Renault GP
      0
    • Williams Cosworth
    • Force India Mercedes
      0
    • Sauber Ferrari
    • Scuderia Toro Rosso Ferrari
      0
    • Team Lotus Renault
    • Hispania Racing Team Cosworth
    • Marussia Virgin Racing Cosworth
  2. 2. Which driver will win the World Driver's Championship?

    • Sebastian Vettel
    • Mark Webber
    • Lewis Hamilton
    • Jenson Button
    • Fernando Alonso
    • Felipe Massa
    • Michael Schumacher
    • Nico Rosberg
      0
    • Nick Heidfeld
    • Vitali Petrov
      0
    • Rubens Barichello
      0
    • Pastor Madonaldo
      0
    • Adrian Sutil
      0
    • Paul di Resta
      0
    • Kamui Kobayashi
    • Sergio Perez
    • Sebastian Buemi
    • Jaime Algersuari
    • Other (specify below)
      0


Recommended Posts

Laughable. He had the move done, and Massa turned in on him, something Massa is prone to doing when being passed. I thought the stewards were over the top here, however I am pleased to see another penalty for the Maldonado incident is unlikely

What a load of twaddle. The thing Massa is most prone to doing while being passed is jumping well out of the way.

Such a lame ending. Ferrari & Alonso had the perfect strategy and it was a Senna-Mansell-esque fight to the chequered flag if not for the amateurs that belong in GP2. Drop Hamilton back there for a couple of races too, he fits in nice with the crashfest.

pile of crap. :x

Laughable. He had the move done, and Massa turned in on him, something Massa is prone to doing when being passed. I thought the stewards were over the top here, however I am pleased to see another penalty for the Maldonado incident is unlikely

He tried the same pass as Paul Di Resta, and he got got a drive thro' why don't you think Hamilton should have been punished. I doubt Massa was expecting Hamilton to pass there, hence why he might have turned in.

As for the Maldonado "pass", that was just plain bad driving. He could have caught him coming out of the tunnel, and left everyone on track.

He tried the same pass as Paul Di Resta, and he got got a drive thro' why don't you think Hamilton should have been punished. I doubt Massa was expecting Hamilton to pass there, hence why he might have turned in.

Look at the line Felipe took, if Lewis wasn't inside that corner Massa would've taken Webber out (which he almost did despite that btw). It was Massa's intention to crash into Lewis in my view.

He tried the same pass as Paul Di Resta, and he got got a drive thro' why don't you think Hamilton should have been punished. I doubt Massa was expecting Hamilton to pass there, hence why he might have turned in.

As for the Maldonado "pass", that was just plain bad driving. He could have caught him coming out of the tunnel, and left everyone on track.

I don't think Di Resta should have been penalised either, he came off worse in that incident. If you penalise drivers for doing what Lewis and Paul did, they will be to nervous of penalty to try risky overtakes in the future, and for me that's not a route Formula 1 should be heading down.

post-286512-0-57438600-1306694321.jpg

This is a shot taken as Massa started to turn into the corner, the angle of his car clearly suggests that he was trying to squeeze Lewis to the apex of the corner and run him off the track

post-286512-0-78043200-1306694332.jpg

And this is taken from the point that he hit webber. He was focused so much on Lewis he didn't even see webber.

There's no way that he didn't see Lewis coming.

Since Massa is ahead, it's up to him what line he takes around a corner. He doesn't have to get out of the way. Lewis tried to pass him on the inside in probably the tightest corner of any F1 circuit. If Massa didn't jerk to the right into Webber, him and Hamilton would have touched for sure.

Since Massa is ahead, it's up to him what line he takes around a corner. He doesn't have to get out of the way. Lewis tried to pass him on the inside in probably the tightest corner of any F1 circuit. If Massa didn't jerk to the right into Webber, him and Hamilton would have touched for sure.

Racing etiquette dictates that if someone's making a pass on you, and they're far enough alongside to be visible then you should not try to squeeze them off the track. It's way above defending your position when you actively try and run your competitor off the track, and that's why Schumacher was punished at Hungary last year.

Racing etiquette dictates that if someone's making a pass on you, and they're far enough alongside to be visible then you should not try to squeeze them off the track. It's way above defending your position when you actively try and run your competitor off the track, and that's why Schumacher was punished at Hungary last year.

Racing etiquette is one thing, rules are another. In situations where there is plenty of space available, I agree. In this corner, Massa was trying to turn it as was his right. Hamilton didn't pass him so he had no reason to expect Massa to get out of the way. He was coming in at a narrow angle, he should have known the risks.

Racing etiquette is one thing, rules are another. In situations where there is plenty of space available, I agree. In this corner, Massa was trying to turn it as was his right. Hamilton didn't pass him so he had no reason to expect Massa to get out of the way. He was coming in at a narrow angle, he should have known the risks.

Sure, it was risky, but if a driver were to be punished every time they took a risk there would be practically no passing at all. It's a dick move by the FIA to punish it when you're trying to encourage more overtaking.

Sure, it was risky, but if a driver were to be punished every time they took a risk there would be practically no passing at all. It's a dick move by the FIA to punish it when you're trying to encourage more overtaking.

He wasn't penalised for just taking a risk. He was punished for a dangerous manoeuvre that led to an avoidable collision. Is that Monaco hairpin really the best place to overtake with traffic ahead of you?

Pirelli: Ban red flag tyre changes

Pirelli has called for a change to the red flag rules in Formula 1 to prevent teams from changing tyres if a race is stopped - after feeling fans were robbed of a great finish to the Monaco Grand Prix.

The battle for victory in Monte Carlo was finely poised between Sebastian Vettel, Fernando Alonso and Jenson Button in the closing stages of the race, with all three running around on tyres that were at very different stages of their wear life.

But with their individual situations set to create a thrilling climax to the race, the battle came to a premature end when a late-race red flag, caused by Vitaly Petrov's accident, meant they were allowed to change rubber.

....

Source: Autosport

So.

F***ing

True.

Too right. If they weren't allowed to change tyres yesterday, then maybe Alonso or Button would have won instead, as when the red flag came down, Vettel had the worst tyres of the three; he'd done about 50 laps on that set alone! Alonso had a fresher set, and I think Button had an even fresher set, so it could have been an epic finish to an epic race if they weren't allowed to change tyres.

Too right. If they weren't allowed to change tyres yesterday, then maybe Alonso or Button would have won instead, as when the red flag came down, Vettel had the worst tyres of the three; he'd done about 50 laps on that set alone! Alonso had a fresher set, and I think Button had an even fresher set, so it could have been an epic finish to an epic race if they weren't allowed to change tyres.

Agreed, letting them change tyres ruined the last laps...would have been more interesting to see Vettel fend off Alonso, whilst alonso trying to attack vettel and fending of Button at the same time..

I think Mark Webbers tweet said it all...

"Did 2 F1 races on Sunday,1 long one 1 short one. In the short race you can change wings,tyres,engine,oops where's the 1000 page rulebook?!"

It was right to continue the race. It wasn't over and they were in the 2 hour time limit.

However 75% of the race had been completed, and full points could have been awarded. I believe it's up to the race director to make that call, which he's fully entitled to do.

IMO, I think fans would have preferred that option as apposed to the farcical half dozen parade lap that it turned it turned into.

He wasn't penalised for just taking a risk. He was punished for a dangerous manoeuvre that led to an avoidable collision. Is that Monaco hairpin really the best place to overtake with traffic ahead of you?

You could make that argument for almost any corner on any track at one point or another. Overtaking almost always carries some risk, and if you stifle drivers risk taking, you dull the sport.

Source: Autosport

So.

F***ing

True.

Amen, this regulation needs to be changed, quickly.

The opportunities to overtake at Monaco are so few that you have to take chances to try and make the move.

Let's face it, Hamilton and Kobayashi are the only drivers who really will take the risks to over take these days.

Ayrton Senna once said 'If you no longer go for a gap, then you are no longer a race driver'.

Long live the race drivers.

Ayrton Senna once said 'If you no longer go for a gap, then you are no longer a race driver'.

Long live the race drivers.

That quote popped straight into my mind when I saw the people on here complaining about Hamilton. (Y) Everyone has to remember that the Monaco circuit is much harder to overtake than the other circuits on the calendar, so the stewards shouldn't have punished Hamilton. He made a clean overtake in the tunnel (which until yesterday, almost everyone would have said is impossible to do without crashing), then Massa screws up, and Hamilton gets penalised. Makes you wonder if the FIA are biased towards Ferrari? I mean, Jean Todt is the president after all...

You could make that argument for almost any corner on any track at one point or another. Overtaking almost always carries some risk, and if you stifle drivers risk taking, you dull the sport.

I have no problem with drivers taking risk without undesired consequences. If a driver takes a risk that results in avoidable damage, he should be punished. There is no reason for irresponsible risk-taking.

This topic is now closed to further replies.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • 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
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!