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

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • User: "But is it good?" Microsoft: "Well, no. But it is less bad."
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!