Recommended Posts

Providing it keeps them 1-2 in the order they are then I don't see anything wrong with it. As I said before, if they are close enough for it to affect each other then do the leader gets first choice thing. But McLaren shoot themselves in the foot with it at times.

Yeah, it can backfire, but it wasn't a known issue during the race on Sunday. The first round of pit stops were as normal. They were right to pit Button first, as he was ahead. They weren't to know what would happen later in the race. The second round of pit stops were unfortunate because of the safety car, but that wasn't due to a fault of McLaren.

Yeah, it can backfire, but it wasn't a known issue during the race on Sunday. The first round of pit stops were as normal. They were right to pit Button first, as he was ahead. They weren't to know what would happen later in the race. The second round of pit stops were unfortunate because of the safety car, but that wasn't due to a fault of McLaren.

Yes, if it wasn't for the safety car then they would have probably been fine with the double pit stop. I'm perhaps overreacting a little, but I saw signs of them repeating past mistakes at Australia. I don't want to see them throwing championships away because of the same poor strategy calls and bad pit stops that we've had previously. Fortunately the latter appears to be fixed but time will tell on the former. Strategy has not been a McLaren strong point for some time.

There does come a point where trying to be fair ends up being unfair because of them sacrificing places. And if the teams behind know their operating procedure they can take full advantage, ala Vettel.

Anyway, I hope Malaysia is as good a race as Australia was. Sunday's race was typical Melbourne but I think there are signs of a much closer racing this year. Would really like to see Sauber get some good points and I'm interested in how Schumacher does against Rosberg.

FIA rejects claims that Mercedes's rear wing is illegal

Lotus and Red Bull Racing's complaints that the DRS-activated F-duct on the Mercedes rear wing is illegal have been rejected by the FIA, AUTOSPORT has learned.

The two outfits wanted clarification on the matter ahead of this weekend's Malaysian Grand Prix, with both teams reckoning the duct that helps stall the Mercedes wings for a straight-line speed boost is a breach of the rules that prevents driver activated aerodynamic devices.

Discussions between the FIA and all the teams involved have taken place throughout Thursday in the Sepang paddock, but the governing body has not changed its stance on the matter.

The FIA informed the outfits that it remains convinced that the concept is legal because it is passive, and there is nothing in the rules that outlaws a device that is activated by movement of the DRS.

FIA race director Charlie Whiting, who is head of the F1 technical department, said in Australia last weekend: "It is completely passive. There are no moving parts in it; it doesn't interact with any suspension. No steering, nothing. Therefore I cannot see a rule that prohibits it."

The news means that Red Bull Racing and Lotus - the two teams most unhappy about the design ? must now choose to either challenge the matter with an official protest in Malaysia this weekend, or go ahead and develop a similar system themselves.

Mercedes-Benz motorsport boss Norbert Haug confirmed that his team's car would be unchanged from how it was in the Australian Grand Prix.

"This car passed scrutineering and got the green light," he said in Malaysia.

Source: Autosport

And the qualifying result:

post-1302-0-04933500-1332579933_thumb.pn

Seeing MSC on P3 pleases me. Vettel gambling with the hard tyre is... odd.

The race is the McLarens' to lose. Who will come behind them is impossible to tell - the times are really close among the top 10.

Of course this being Malaysia we may see rain which would mix up the grid even more...

I want to see MSC on the podium tomorrow. Maybe not on P1, but... who knows. His comments about the car being set up for race pace rather than qualifying make me hopeful.

mclaren untouchable so far. im really proud of that team. and no words for schumacher, this guy is a legend, simply as that. i hope he can finish p3 tomorrow or even p2 or p1 if it rains who knows....

Woo Front row lockout! great start to this season from McLaren!

Vettles choice is interesting...That'll pay if there is any rain in the mid-end of the race...dono if it'll work with a dry race.

Tho the forecast is for rain...http://www.accuweath...-weather/229918 ...tho it says its been raining today which it doesn't seem to have been.

My prediction:

McLaren 1, 2

MSC 3rd, or Seb depending on weather and strategy.

I think its going to be another Mclaren race looking at Quali pace, the only team that can realistically challenge them are Red Bull and they have been off pace all weekend.

Hoping for a Mclaren 1-2 but this is Jensons race to lose, even if it rains I think hes got it in the bag.

This topic is now closed to further replies.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!