F1 World Championship 2008 Thread



Recommended Posts

Funny how you're wrong.

Seems you are right. Came across that while searching for the rule against corner cutting... There isn't, specifically, a rule against corner cutting. The rule Lewis was penalised under is:

30.3 a) During practice and the race, drivers may use only the track and must at all times observe the

provisions of the Code relating to driving behaviour on circuits.

Under that rule nearly everyone should be given a 25 second penalty, no?

The FIA are not only incapable of reading their own rules (Valencia) but can't write them either? Seems they just make them up as they go along...

he was also guilty of Appendix L Chapter 4 Article 2 (g) of the international sporting code which says the same as the above quote (the track must be used), however, part (f) of the same article:

f) The repetition of serious mistakes or the appearance of a lack of control over the car (such as leaving the track) may entail the

exclusion of the drivers concerned.

massa at silverstone anyone?

Under that rule Mike, everyone on slicks should be excluded from the race - none were really in control at all. How about the one about using unsafe tyres? Kimi's accident wouldn't have happened had he (and the rest) pitted for the right tyres.

Quite simply, the entire rule book is vague. The FIA/Stewards make up their own rules according to how they feel like interpreting the rules on that particular day. It's a pathetic way to run a sport.

It's the same deal in GP2 too. :/

GP2 seems fairer, eg the guy who got released into another car in the pit lane in GP2 got a drive through, massa got a pointless fine

now they give hamilton a penalty for something that didnt warrent one and to seem like they are consistent have supposedly handed one down to a GP2 driver doing something similar (after they did hamiltons penalty)

it's also been pointed out, massa / kubica last year when they were all over the track and surrounding area racing, each one gaining advantage by going off track, and nothing was done

the FIA know the rule book is vague and probably leave it that way, that way they can screw over anyone who impededs ferrari in any way. I await a penalty for kimi for using off-track areas to gain an advantage at the end of the race!

What about when Kimi had been over taken by Hamilton and went wide on one of the bends?? He just took the corner at a fast pace on the run off area, surely this is of the equivalent of Hamilton using the run off area of the chicane?

As I am pretty sure Kimi was using the run off area to gain an advantage as if he had to rejoin the track as soon as he could he would of lost alot of speed, I believe it was just before Hamilton had to avoid Nakajima and Kimi re-took the lead.......

The decision is utter bs.

Did he? Check this out. He seems to be going full speed.

full speed? definately not. he is barely touching the throttle whilst skipping the corner, then kimi is ahead then he starts accelerating, speed != acceleration, and also from that onboard, kimi wasn't in the picture at the turn in when they were relatively close so you cant tell when kimi gets to be passing him in that video

3 years ago, similar situation with Alonso (Japanese GP)

http://www.formula1.com/news/headlines/2005/10/3701.html

Alonso had some dramas as he lost ground going off in the chicane and dirtying his tyres on the 8th lap as he passed Klien. He duly let the Austrian back through then immediately re-passed him into Turn 1. However, stewards decided that the Spaniard had still gained an advantage and he was forced to slow, let the Red Bull back through and then finally re-pass for good.

FYI, Alonso was well behind Klien (at least the length of one and a half vehicle), but was still forced to slow down.

I guess FIA hates Alonso too.

WTF was Kimi doing? He pretty much handed Hamilton the lead with a few laps to go. He's supposed to be one of the most difficult drivers to get around. Why did he stop 500M before that one turn off the long straight? It looked to me like he wanted Hamilton to rear end him so that they'd both go out.

I don't agree with this decision at all though.

I've always tried to defend the FIA and Ferrari to the conspirators out there, but this is getting out of hand.

That video actually shows he did not gain an advantage. If he had his foot hard on the pedal after the corner, and Kimi still came out in front (after going all the way round) and still had a 6 kph advantage over the line, then Lewis gained no advantage. You can't be slower and still gain an advantage. All the video proves is how slow the Ferrari was in the wet as Lewis was able to make-up that 6kph disadvantage down the straight easily.

Loads of guys were going off-track at the start to gain an advantage at the start, although the advantage part is irrelevant according to the rules. But who follows the rules... :rolleyes:

Utter nonsense (referring to Hamilton's penalty), the FIA needs to get their heads out of their asses. Whether or not Hamilton had extra moment coming out of the turn, which I personally don't think he did, R?ikk?nen did use the high friction line to gain the ground back. I usually don't get to involved in conspiracies, but this time I really think the FIA is far to biased. Hamilton gave back the position and gained it back far and square IMO.

If they don't win then i think F1 will lose quite a lot of fans as it clearly isn't a level playing field.

I have not wanted to believe that there is a conspiracy against mclaren or one in favour of ferrari but after this race i am struggling to think otherwise....

If they don't win then i think F1 will lose quite a lot of fans as it clearly isn't a level playing field.

I have not wanted to believe that there is a conspiracy against mclaren or one in favour of ferrari but after this race i am struggling to think otherwise....

i dont think there is one *against* mclaren, just more in the favour of ferrari. what is more dodgy is that the race control even said that lewis had let kimi retake the position in a way that was inline with the rules:

McLaren have revealed that they were told twice by FIA race officials during the Belgian Grand Prix that Lewis Hamilton had given back the race lead to Kimi Raikkonen in an 'okay' manner.

With the team confirming on Tuesday that they were pressing ahead with their appeal against Hamilton's 25-second penalty for gaining an unfair advantage, McLaren's F1 CEO Martin Whitmarsh claims that the team enquired twice with Race Control whether or not their driver had acted in a legitimate manner.

Whitmarsh said: "From the pit wall, we then asked Race Control to confirm that they were comfortable that Lewis had allowed Kimi to repass, and they confirmed twice that they believed that the position had been given back in a manner that was 'okay'.

"If Race Control had instead expressed any concern regarding Lewis's actions at that time, we would have instructed Lewis to allow Kimi to repass for a second time."

source: http://www.autosport.com/news/report.php/id/70443

Ron Dennis even said to the ITV people after the race that Charlie Whiting was happy with what happened and said it was within the rules. When you have past drivers and people involved with safety and running F1 races saying it was fine you really do have to wonder what exactly the stewards are thinking/doing. Good to see McLaren not taking it anymore and actually trying to fight it (Y)

I've been surprised at how many Ferrari fans disagree with the penalty. Shows how messed up it is really.

Good that McLaren have decided to go ahead with the appeal on the basis of race control saying it was fine. They can hardly expect Lewis to let Kimi through if he was told it was ok. :/ Although race control said exactly the same at the French GP - probably why they asked twice this time.

It seems only fair to me that when you have to ask race control if something was legit (because the rules are too vague to judge on your own) that what race control says should be considered as part of the decision.

Not fair to say race control only express opinion, when the rule is so vague that no-one but the stewards, at the time of the decision making, has a clue what it actually is. In that case, everyone might as well ignore the rules, race like madmen and hope they don't get a penalty. Would probably be fairer. :laugh:

Did he? Check this out. He seems to be going full speed.

Kimi was going to cut him up there, he'd have gone over the huge lumps of green concrete they have at the side of the track and smashed both cars up completely, if he hadn't turned left to avoid it. It's Kimis fault for not going faster (and letting himself get caught).

And the incident I mention, the 'avioding dying' thing, that was not on the approach to the first corner in the chicane, but the second. Get your facts right.

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

    • No registered users viewing this page.
  • 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!