110 members have voted

  1. 1. Which team will win the Constructor's Championship?

    • Red Bull Renault
    • McLaren Mercedes
    • Ferrari
    • Mercedes GP
    • Lotus Renault GP
      0
    • Williams Cosworth
    • Force India Mercedes
      0
    • Sauber Ferrari
    • Scuderia Toro Rosso Ferrari
      0
    • Team Lotus Renault
    • Hispania Racing Team Cosworth
    • Marussia Virgin Racing Cosworth
  2. 2. Which driver will win the World Driver's Championship?

    • Sebastian Vettel
    • Mark Webber
    • Lewis Hamilton
    • Jenson Button
    • Fernando Alonso
    • Felipe Massa
    • Michael Schumacher
    • Nico Rosberg
      0
    • Nick Heidfeld
    • Vitali Petrov
      0
    • Rubens Barichello
      0
    • Pastor Madonaldo
      0
    • Adrian Sutil
      0
    • Paul di Resta
      0
    • Kamui Kobayashi
    • Sergio Perez
    • Sebastian Buemi
    • Jaime Algersuari
    • Other (specify below)
      0


Recommended Posts

felipe massa outsmarting his slowish teammate in the wet... well, who would have thought... (monaco 2k8 and interlagos 2k8 , rings ur bells? ^^)

proper loving this race so far. shame about hamilton he would be fighitng for the lead right now im sure.

I SO love this race... can any1 help me on a question... ? its the number of laps massa pited after alonso i said it was maximum 2 my best friend said it was at least 5+ laps...

afaik alonso pitted first (ofc.) and then after 1 or 2 lap massa pitted together with vettel - kobayashi took the lead - and then alonso pitted again back to heavy wets togehter with button......

sorry lads, i just cant help but properly enjoyning a BIG BIG FAAAT 4 positions between felipe massa and fernando alonso .... :laugh: :devil:

lol just seen the grid and i love it how rob smedley basically runs ferrari b team instead of being a simple race engineer... haha :laugh:

Alonso rightly paid the price for causing that incident with Button. (Y)

100% true.... :)

that race is a thriller... absolutely loving it!!! 200% action and loads of uncertainities...

They're investigating the incident with Button and Alonso now. Maybe a grid penalty for Alonso in the next race? :whistle:

EDIT: No wait, I forgot it's the FIA; the "F" standing for "Ferrari". :p

Penalty for Button would be the right course of action for bumping off Alonso.

Get off! Button was on the racing line, he had the inside of the corner, and Alonso went into him. It doesn't matter if Alonso was just ahead, he caused the incident.

massa

schumacher

vettel

u read it here first.

Hmm, I don't think so. Vettel's pulling out a big lead once again now. He's more than 5 seconds ahead of Kobayashi. I reckon Vettel will win, and Massa will probably just snatch 2nd from Kobayashi, and he'll finish 3rd.

BTW, the incident involving Heidfeld and di Rests is being investigated now.

Rosberg and Sutil are under investigation now. Probably a drive-through penalty for Sutil.

Get off! Button was on the racing line, he had the inside of the corner, and Alonso went into him. It doesn't matter if Alonso was just ahead, he caused the incident.

Alonso did not go into him. Button approached on the right rear side and then slammed into Alonso as he tried to turn right. Alonso was ahead and he didn't have to get out of the way. Button had to go into Alonso from quite far back to have turned him clockwise so much and pitch him up on the curb.

Drive-through penalty for Paul di Resta. It's bad enough that he had to pit in to replace his front wing after that incident. :/

...well damn, I got that wrong then. Schumacher and Massa just both passed Kobayashi. Schumi's in 2nd, and Massa's in 3rd.

This topic is now closed to further replies.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and also managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!