Recommended Posts

They aren't strictly aerodynamic parts - they are the camera mountings. As far as I know, the teams can choose to mount them anywhere they like on the nose, so in their case they've decided to put them right at the front.

Oh yeah I had forgotten about the camera mountings. I thought they had to be as small as possible and have no impact on aerodynamics. There must be a reason they have stuck them out there right on the front. It must make a difference to the aerodynamics. I wonder if there will be some controversy about this.

Ah that makes more sense about the noses. I suspect then that McLaren is the only ones who have a thin enough bulkhead ready then. The others are waiting until the have to do it. I guess the benefits of more air going underneath outweighs it hitting the step. Unless the other teams couldn't redesign their bulkheads and suspensions in time for this season and are having to do the best with what they have.

Oh yeah I had forgotten about the camera mountings. I thought they had to be as small as possible and have no impact on aerodynamics. There must be a reason they have stuck them out there right on the front. It must make a difference to the aerodynamics. I wonder if there will be some controversy about this.

Ah that makes more sense about the noses. I suspect then that McLaren is the only ones who have a thin enough bulkhead ready then. The others are waiting until the have to do it. I guess the benefits of more air going underneath outweighs it hitting the step. Unless the other teams couldn't redesign their bulkheads and suspensions in time for this season and are having to do the best with what they have.

I think the camera mountings are a standard shape/size. If you look at the one located on the Sauber's engine cover, it appears to be the same. Last year's Red Bull had them right at the end of the nose as well: http://www.racecar-e...011/01/RB7a.jpg

From what I understand of the reasoning on the noses, you are right. As McLaren were close to 2012 legal it was a question of lowering the nose by a few centimetres - plus the rest of the car was already designed around a low nose so it isn't a big deal. Everyone else would need to lower the nose considerably, which would require a complete redesign of the whole car as they're based around this high-nose concept.

I still can't get my head around how unrefined the step on the Ferrari's nose looks though...

I think the camera mountings are a standard shape/size. If you look at the one located on the Sauber's engine cover, it appears to be the same. Last year's Red Bull had them right at the end of the nose as well: http://www.racecar-e...011/01/RB7a.jpg

I think I must have just been subconsciously filling those away before. Must be the new nose designs making them look more prominent because they are so thin. Just doesn't look like they are the exact same pods on all the cars. Even though they have to be.

BBC has a good analysis of the McLaren and the difference between it and the step noses.

but yeah as fourjays has said it is to do with a regulation change and airflow...the the reg is not just for a T-Bone impact its also to try and stop cars climbing ontop of another like Webber did.

http://www.bbc.co.uk/sport/0/formula1/16864721

BBC has a good analysis of the McLaren and the difference between it and the step noses.

but yeah as fourjays has said it is to do with a regulation change and airflow...the the reg is not just for a T-Bone impact its also to try and stop cars climbing ontop of another like Webber did.

http://www.bbc.co.uk...rmula1/16864721

Interesting take on it. I hope he is wrong and the McLaren does make a difference. Be nice to see someone else leading the pack instead of everyone following Red Bull.

Red Bull is the most interesting car so far, aside from the McLaren. Here is a good picture of the inlet on the nose:

rbrnose3.jpg

There is a rule against holes right through the nose (was mentioned on Twitter this morning in relation to a hole on the top of the Sauber's nose), although I'm not sure about channels going right through the car (I'd expect so, otherwise it would have been done already). The only hole allowed is a single hole for driver cooling - which this could be. There is a drawing of the Red Bull without a hole in the nose tip, but I can't find any photos to confirm that.

Interesting whatever it is about.

Edit:

No its either an aero trick to keep the flow attached to the nose or the driver cooling inlet

- Tweet by Scarbs (respected F1 tech journalist).

Newey on the RB8:

The restriction nose height which is a maximum height just in front of the front bulkhead hasn?t really changed the chassis shape very much. We?ve kept more or less the same chassis shape, but had to drop the nose just in front of the front bulkhead, which, in common with many other teams, has led us to I think I?d probably say a slightly ugly looking nose. We?ve tried to style it as best we can, but it?s not a feature you would choose to put in were it not for the regulation.

Doesn't sound positive for the stepped noses.

The bull duct is for driver cooling according to Newey

via RacecarEngineer on Twitter, retweeted by Scarbs

So, morning test is over and Raikkonen is top. First time on the Pirellis for him so quite possibly pushing a bit to get used to the tyres. Interesting to see him top though.

Pos Driver Team Time Laps

1. Kimi Raikkonen Lotus-Renault 1m19.670s 50

2. Paul di Resta Force India-Mercedes 1m19.772s 52

3. Nico Rosberg Mercedes 1m20.219s 56

4. Daniel Ricciardo Toro Rosso-Ferrari 1m20.694s 40

5. Mark Webber Red Bull-Renault 1m21.474s 8

6. Kamui Kobayashi Sauber-Ferrari 1m21.534s 29

7. Jenson Button McLaren-Mercedes 1m22.402s 22

8. Felipe Massa Ferrari 1m23.056s 51

9. Heikki Kovalainen Caterham-Renault 1m23.178s 32

10. Pastor Maldonado Williams-Renault 1m23.371s 23

11. Pedro de la Rosa HRT-Cosworth 1m24.322s 16

via Autosport

Raikkonen leads Di Resta on first day of Jerez test

Kimi Raikkonen got his F1 comeback off to a positive start as he set the quickest time in testing at Jerez.

Raikkonen ran a series of rapid laps in the morning culminating in a 1?19.670 which put the Lotus E20 at the top of the times.

Paul di Resta came closed to deposing him with a best effort just a tenth of a second slower in the new Force India.

As always, the headlines times should not be taken as a simple reflection of who?s quickest and who?s slowest. For example, HRT (running last year?s car) were only 5% slower than the fastest time, well below the 7-8% range typically seen in last year?s races.

With nine new cars in action on the first day of the test some teams had comparatively quiet days.

Mark Webber got the year off to a slow start for defending champions Red Bull. He was unable to run during the first few hours of the session as fog at the track delayed the arrival of parts for the new RB8.

Heikki Kovalainen logged 28 laps in the new Caterham CT01 but his day?s running came to an end when the car?s starter developed a fault.

Another driver whose test ended early was Daniel Ricciardo. A drop in oil pressure on his Toro Rosso STR7 caused him to pull over with just over half hour remaining, causing the first red flag of the day.

?We had a very productive morning, doing over 40 laps and we made good progress with our programme,? said Ricciardo.

?Then in the afternoon, we did a couple of longer runs, but had to cut it short, although we only lost an hour. I was using the medium tyre on that last run, having used hard tyres for the rest of the day.?

Meanwhile Kamui Kobayashi, who had shaken down the Sauber C31 yesterday, did over 100 laps in the new car today. But he hit trouble with less than half an hour left in the session, bringing the red flags out a second time.

A brief restart gave Pedro de la Rosa time to post the final improvement of the day in last year?s HRT, before the chequered flag brought the first official test day of 2012 to an end.

Jerez test times

post-1302-0-40008500-1328630926.png

Source: F1 Fanatic

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!