Formula 1 World Championship 2016 Season Discussion


Formula 1 World Championship 2016 Poll  

52 members have voted

  1. 1. Who do you think will win the 2016 Drivers Championship?

    • Lewis Hamilton
      30
    • Nico Rosberg
      10
    • Sebastian Vettel
      5
    • Kimi Räikkönen
      0
    • Valterri Bottas
      1
    • Felipe Massa
      0
    • Daniil Kvyat
      0
    • Daniel Ricciardo
      0
    • Sergio Pérez
      0
    • Nico Hülkenberg
      0
    • Kevin Magnussen
      0
    • Jolyon Palmer
      0
    • Max Verstappen
      0
    • Carlos Sainz, Jr.
      0
    • Felipe Nasr
      0
    • Marcus Ericsson
      0
    • Jenson Button
      0
    • Fernando Alonso
      1
    • Pascal Wehrlein
      1
    • Rio Haryanto
      1
    • Romain Grosjean
      0
    • Esteban Gutiérrez
      0
  2. 2. Who do you think will win the 2016 Constructors Championship?

    • Mercedes AMG Petronas F1 Team
      41
    • Scuderia Ferrari
      4
    • Williams Martini Racing
      0
    • Red Bull Racing
      0
    • Sahara Force India F1 Team
      0
    • Renault F1 Team
      0
    • Scuderia Toro Rosso
      0
    • Sauber F1 Team
      0
    • McLaren Honda
      2
    • Manor Marussia F1 Team
      2
    • Haas F1 Team
      0


Recommended Posts

But...

Quote

Nico Rosberg may face a penalty for driving too slowly during Q1.

 

The Mercedes driver is under investigation for breaking article 27.5 of the sporting regulations which specifies a maximum time for driving between the pit lane exit and entrance.

 

Rosberg set two flying laps during Q2 but did a much slower 2’26.444 in between them. This was almost half a minute slower than team mate Lewis Hamilton drove when he backed off.

 

Safety Car line two is at the pit lane exit and line one is at the pit lane entrance. The maximum permitted time for the drivers to pass between them is one minute and 45 seconds.

 

The rule, which was introduced in 2010, is intended to prevent drivers lapping too slowly during qualifying to save fuel, creating a potential safety risk.

 

Article 27.5 of the sporting regulations states:

“At no time may a car be driven unnecessarily slowly, erratically or in a manner which could be deemed potentially dangerous to other drivers or any other person. This will apply whether any such car is being driven on the track, the pit entry or the pit lane.”

 

“In order to ensure that cars are not driven unnecessarily slowly on in laps during and after the end of qualifying or during reconnaissance laps when the pit exit is opened for the race, drivers must stay below the maximum time set by the FIA between the Safety Car line after the pit exit and Safety Car line before the pit entry.”

 

“The maximum time will be determined by the race director at each event after the first day of practice but may be amended later in the Event if deemed necessary. The time will normally be based upon 145% of the best dry [first practice or second practice] time.”

http://www.f1fanatic.co.uk/2016/07/09/rosbergs-second-place-threat-investigation/

Quote

Nico Rosberg has been cleared of breaking the rules during qualifying.

 

The Mercedes driver was investigated for exceeding the maximum time limit during Q1 measured between the Safety Car lines at the pit lane exit and entrance.

 

However the stewards decided to take no action after ruling Rosberg “was not on an in-lap when the time between the Safety Car lines was set”.

 

Rosberg therefore keeps his place alongside Lewis Hamilton on the front row of the grid for Sunday’s British Grand Prix.

 

“The team has given us an incredible car,” he said after qualifying. “It really was a pleasure to drive out there today – especially through these spectacular high-speed corners where it’s just awesome. It’s like the car is on rails, which is just what you want as a driver, so a big thank you to everyone for that.”

 

“It wasn’t my day out there today – but congratulations to Lewis, who did an awesome job. Tomorrow is the day and it’s all to play for and it will be a great battle between Lewis and me.”

http://www.f1fanatic.co.uk/2016/07/09/rosberg-avoids-penalty-slow-driving-q1/

6 minutes ago, what said:

I think Mercedes would happily take that. Not saying anything could have resulted in a DNF for Rosberg. All they've lost is three points.

Hamilton will be very happy with that; he's now leading the championship by a point. :p Mercedes have lodged an appeal, so it isn't over yet. Also...

 

I was lucky enough to get tickets in Club Corner - what a show to the crowd by Hamilton!

 

Unfortunately, not able to get all the radio traffic when you're there in person so I'm not quite sure what got said to Rosberg. Do feel like he's been a bit hard done by though if he was on the verge of retirement!

1 hour ago, Biohead said:

Unfortunately, not able to get all the radio traffic when you're there in person so I'm not quite sure what got said to Rosberg. Do feel like he's been a bit hard done by though if he was on the verge of retirement!

Rosberg was told how to fix the problem, but then told not to use 7th gear. It was for the second part that he received the penalty, 55 seconds onwards on http://www.bbc.co.uk/programmes/p041111q 

Big fan of Team LH, not of this rule. It's almost as if the FIA want cars dropping out of races and not being able to overtake. It robbed us of a chance to see Lewis do some overtaking at Baku, and now a driver has been penalised because the team didn't want his car to drop out of the race. Time to drop the radio rules IMO.

14 hours ago, Biohead said:

I was lucky enough to get tickets in Club Corner - what a show to the crowd by Hamilton!

 

Unfortunately, not able to get all the radio traffic when you're there in person so I'm not quite sure what got said to Rosberg. Do feel like he's been a bit hard done by though if he was on the verge of retirement!

More info on exactly what was said and reason for the penalty.

http://www.bbc.com/sport/formula1/36760027

The settings change was fine, it was the shift through 7th they got the penalty for.

Well now that we know that a radio breach costs a 10 second penalty, Mercedes, more than anyone, may use that to their advantage, knowing say, Lewis has a 20 second lead yet has issues, they get him to fix them, take the penalty yet he still wins.

 

Interesting times.

  • Like 2
36 minutes ago, Steve B. said:

Well now that we know that a radio breach costs a 10 second penalty, Mercedes, more than anyone, may use that to their advantage, knowing say, Lewis has a 20 second lead yet has issues, they get him to fix them, take the penalty yet he still wins.

 

Interesting times.

Yeah I thought the penalty was too lenient to be honest. Also think it should hurt the team more than the driver seeing as Nico didn't ask to be told the info that ultimately cost him the penalty.

  • Like 1
39 minutes ago, i11usive said:

Yeah I thought the penalty was too lenient to be honest. Also think it should hurt the team more than the driver seeing as Nico didn't ask to be told the info that ultimately cost him the penalty.

Well he asked the question do i shift through it, I know in the heat of the moment its hard, but he should know its not something he can ask/can't get a response.

 

While I agree some might now use this to advantage knowing it's 10secs, I suspect the stewards will crack down harder on serial offenders if they start to use it that way.

3 hours ago, philcruicks said:

Well he asked the question do i shift through it, I know in the heat of the moment its hard, but he should know its not something he can ask/can't get a response.

 

While I agree some might now use this to advantage knowing it's 10secs, I suspect the stewards will crack down harder on serial offenders if they start to use it that way.

I can see all teams getting harsher penalties, rather than everyone knowing at worst they'll get 10 seconds. 

 

Maybe it's something like amount of information conveyed, or if it allows the driver to have any unfair advantage etc.

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
      250
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      FloatingFatMan
      67
  • Tell a friend

    Love Neowin? Tell a friend!