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

Wow, Rosberg once again can't deal with Hamilton having a good passing run on him.  Rosberg is now under investigation for causing a collision and failing to stop with a seriously damaged car.

Edited by SecretAgentMan
  • Like 1

Almost forgot that Wehrlein picked up his first F1 point; well done to him and Manor (and the stewards for not punishing him for briefly being in the wrong starting position)!

 

 

If anyone here still wants more after that, the final Formula E race of the season is starting very soon on ITV.

Poor driving from Rosberg there. He could afford second and threw away at least 13 points. Should take a penalty for forcing Lewis off the track and causing the collision, but probably will get away with driving with the broken car.

Mercedes announces A-class Rosberg Edition

Quote

Mercedes has announced a special ‘Nico Rosberg’ edition of its A45 AMG hot hatchback which boasts a number of bespoke features including a unique ‘brake fault’ that provides the driver with the perfect excuse for acting like a bellend.

 

Sources in Stuttgart say the A45 Nico Rosberg Edition is specifically tuned for manoeuvres such as failing to take a corner properly, twatting into another motorist and other situations in which the driver deliberately doesn’t use enough steering lock like a silly ######.

 

In the event of an accident, the A45 Nico Rosberg Edition comes with a comprehensive recovery package which entitles the owner to a full diagnostic check, after which the dealer will tell them there is a ‘brake fault’ even though that doesn’t really tally with the dick move that got them into trouble in the first place.

 

On top of the made up brake problems and inadequate steering lock, each Nico Rosberg Edition A-class is registered in three different countries and designed to emit a regular whining sound.

And in the small ads...

Smallad160704.jpg

  • Like 2
On 7/3/2016 at 3:36 PM, MightyJordan said:

Almost forgot that Wehrlein picked up his first F1 point; well done to him and Manor (and the stewards for not punishing him for briefly being in the wrong starting position)!

tbh I don't think it's a good thing he went unpunished. Reversing on the starting grid could have disastrous consequences. Fortunately he had started doing it before the lights had come on. If Whiting hadn't seen it/wasn't told about it and therefore delayed the countdown, he could well have been reversing into someone about to launch off the line. You're not supposed to go backwards on track for obvious reasons. I don't see why it should be any different on the grid.

Quote

Hamilton "destroyed" room after Baku qualifying mistake - Lauda

 

Lewis Hamilton was so furious about losing pole position to Nico Rosberg at the European Grand Prix that he "destroyed" his private room at the Mercedes offices, team chief Niki Lauda has revealed.

 

Lifting the lid on what Lauda said was a "lie" when Hamilton claimed he was getting on better than ever with his teammate, the Mercedes non-executive chairman has given a fascinating insights into the tensions going on behind the scenes.

 

In an interview for Red Bull channel Servus TV, which was recorded last Friday but only broadcast last night, Lauda confirmed that speculation Hamilton had been left in a rage after his qualifying error in Baku was correct.

 

Pushed by veteran journalist Roger Benoit on the programme about reports Hamilton had destroyed his room after Rosberg took pole position, Lauda said: “He did it because he had crashed. He’ll have to pay for that [the destroyed room]. You can count on that.

 

“He told me I couldn’t come in because he was going to destroy everything. This is how it was.”

 

Lied in interview

 

Although the tensions between Hamilton and Rosberg erupted in the Austrian race, even at the time the interview was done it was clear to Lauda that things were far from as perfect as had been suggested.

 

In an interview with the Mail on Sunday ahead of the Austrian GP, Hamilton had claimed that things with Rosberg were better than they had ever been.

 

“It’s actually really good with Nico at the moment,’ said Hamilton. “Really, really good. Surprisingly.

 

“I would definitely not have expected it to be where it is. I guess it is probably with age.

 

"He’s a family man. He’s got a kid. He has probably grown in that process and I have grown and come of age. The respect that we have always talked about is bigger than it has ever been.”

 

But Lauda has said that Hamilton's claims are well wide of the mark, and the situation between the pair is nowhere near as rosy.

 

“Lewis lied about that, simple as that,” explained Lauda. “He just said something. He wanted to be the softener in order to have his peace last weekend.

 

"He does what he can. The fight gets hotter the longer Nico is in front.”

Source: Motorsport.com

20 minutes ago, what said:

tbh I don't think it's a good thing he went unpunished. Reversing on the starting grid could have disastrous consequences. Fortunately he had started doing it before the lights had come on. If Whiting hadn't seen it/wasn't told about it and therefore delayed the countdown, he could well have been reversing into someone about to launch off the line. You're not supposed to go backwards on track for obvious reasons. I don't see why it should be any different on the grid.

Charlie Whiting saw what he was doing and waited until he got into position before turning on the red lights. And Wehrlein knew from his DTM days that it isn't against the rules to reverse on the track - only in the pitlane - so he technically didn't do anything wrong and cleverly recovered from that mistake (which most of us would have made, too). Anthony Davidson's analysis on it is worth a look: https://streamable.com/85gd

  • Like 1
1 hour ago, MightyJordan said:

Charlie Whiting saw what he was doing and waited until he got into position before turning on the red lights. And Wehrlein knew from his DTM days that it isn't against the rules to reverse on the track - only in the pitlane - so he technically didn't do anything wrong and cleverly recovered from that mistake (which most of us would have made, too). Anthony Davidson's analysis on it is worth a look: https://streamable.com/85gd

So the stewards wanted to punish him, but there's no rule saying you can't reverse on the grid. I bet that'll change soon ;) As I said, had Whiting not seen it, there could have been a problem.

2 minutes ago, what said:

So the stewards wanted to punish him, but there's no rule saying you can't reverse on the grid. I bet that'll change soon ;)

Yeah, we know the FIA love to close a loophole as soon as a driver finds one. A perfect example: Michael Schumacher winning the 1998 British Grand Prix from the pit lane (then they changed the rules so that you'd get an extra penalty on top of the original if you didn't serve it during the race).

 

10 minutes ago, what said:

So the stewards wanted to punish him, but there's no rule saying you can't reverse on the grid. I bet that'll change soon ;) As I said, had Whiting not seen it, there could have been a problem.

Whiting hadn't, but the green flag guy a the back had, and Whiting can't (or shouldn't) activate the light sequence until he's cleared, he's there for exactly that reason, so be a 2nd pair of eyes and ensure cars further back aren't having problems before the start.

So was all fine.

7 minutes ago, philcruicks said:

Whiting hadn't, but the green flag guy a the back had, and Whiting can't (or shouldn't) activate the light sequence until he's cleared, he's there for exactly that reason, so be a 2nd pair of eyes and ensure cars further back aren't having problems before the start.

So was all fine.

From memory the green flag had been waived straight away and there was a delay before the countdown started while Wehrlein sorted himself out?

 

I also believe in Baku the race started while the green flag man was still on circuit because he took too long to get across.

1 hour ago, what said:

From memory the green flag had been waived straight away and there was a delay before the countdown started while Wehrlein sorted himself out?

 

I also believe in Baku the race started while the green flag man was still on circuit because he took too long to get across.

Yep, the guy with the green flag was definitely waving so it must have been someone like Whiting who spotted it although does the lights sequence only start once the green flag guy has reached the pitwall? I can't say I've taken that much notice before but I don't think it does, there seemed to be a much longer pause before the lights started imo.

 

IF Ant Davidson is right and it's not against the rules I'd say it should be at least considered, in this case it was a simple yet easy mistake because Massa wasn't on the grid but they need someway of being 100% sure everyone is stationary and people don't use it to lay some extra rubber down.

Pretty sure the flag guys stops half way across or at least slows, and only resumes/speeds up when Wehrlein stops reversing.

 

Either way, he was within the rules and scored a point which is great for him and Manor.

  • Like 2

That's a great video. I think the most impressive part is how quickly he looks at the mirror coming out of the pits. Blink and you'll miss the dot moving across and back. To be able to decide whether not its clear in that time is serious skill.

 

The bit about the lights is slightly wrong though. Drivers react to the red light going out, not the green light switching on. That's why F1 races start with the red lights going out. They used to use green lights, but they realised they were pointless.

I hadn't considered Max for one second to get DoTD, would have thought either Button or Wehrlein for sure, as both did very well.

 

I think now more than ever it's showing a changing of the guard is needed at Sauber to bring them back, it all went downhill as soon as Peter Sauber left.

Just now, MightyJordan said:
<snip>

I was just talking to someone about this yesterday saying that Mercedes are going to be pretty frustrated after Lewis is telling everyone everything is fine and then non-exec board member has came out and just completely ruined all that positive PR, not only by calling him a liar but leaking what could be some pretty embarrassing behaviour! 

 

They can issue whatever statement they want but that seed has been planted now, it won't go away.

Whoops, well done Niki.

Someone's been at the concept F1 car renders again, love the Ferrari and the LeMans Gulf ones.

http://www.topgear.com/car-news/concept/these-renders-prove-f1-designers-need-their-game#1

This topic is now closed to further replies.
  • Posts

    • 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.
    • Yes, I actually glossed over the Linux part from the OP. You could always go for a 9070 XT and if you really want to play Ray Traced games in the future, GeForce Now is pretty damn good on Linux https://www.neowin.net/news/nvidias-native-geforce-now-app-for-linux-bridges-the-gaming-gap-hands-on/
  • 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
      252
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      Skyfrog
      67
  • Tell a friend

    Love Neowin? Tell a friend!