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

    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I found that stability back then was really down to the motherboard manufacturer. Back then i stuck with Microstar motherboards and VIA chipsets as they were ultra reliable. Most stuff was done with jumpers and left little room for user created problems 👍
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      232
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!