Recommended Posts

Pinch of salt required but apparently there is a TFR in place for a potential flight on Thursday. 

Given we've not seen any static fires yet my guess is this won't happen that quickly but SpaceX are clearly not slowing down the pace. I'm surprised the changes for the landing sequence has been implemented this quickly but it will be interesting to see how quickly they can keep up these test launches, SN11 looks almost complete.

On 05/02/2021 at 17:49, DocM said:

The SN-08 FAA license violation was a "miscommunication,"

 

 

 

Maybe they'd have less trouble with the FAA if they just said "Hey guys, we're gonna crash one of our ships today, 'kay?  We good? Great!" ;)

 

 

1 hour ago, FloatingFatMan said:

Maybe they'd have less trouble with the FAA if they just said "Hey guys, we're gonna crash one of our ships today, 'kay?  We good? Great!" ;)

 

 

I don't think it's that simple. FAA is probably a bureaucratic body with a lot of incomprehensible and obscure rules, but they're not playing with garden rockets here. If something really goes wrong they could be stopped for months. Better to play by the rules. Of course, asking to have clear rules, precise guidelines and trying to get some people to move from the armchairs they are heating is quite another thing.

  • Like 1
3 hours ago, SteveL said:

I don't think it's that simple. FAA is probably a bureaucratic body with a lot of incomprehensible and obscure rules, but they're not playing with garden rockets here. If something really goes wrong they could be stopped for months. Better to play by the rules. Of course, asking to have clear rules, precise guidelines and trying to get some people to move from the armchairs they are heating is quite another thing.

 

The FAA was bent out of shape over the modelling of blast effects in case of a boomski.

 

Given the vehicles have an autonomous destruct system that breaks them up if they stray (no more guy with a red button), the village had been evacuated, and SpaceX has enough insurance to pay for every privately held property 1000 times over (2 permanent residents; Nomadd and BocaChicaGal, both NASASpaceFlight reporters), and a handful of snowbirds who sometimes winter over...

 

Whatever, the FAA - AST rules change March 12 and the changes are pro-commercial - loosening up licensing.

Edited by DocM
6 hours ago, FloatingFatMan said:

Maybe they'd have less trouble with the FAA if they just said "Hey guys, we're gonna crash one of our ships today, 'kay?  We good? Great!" ;)

 

 

Crashing metal was expected, that's how you do agile development in aerospace. Fly, crash, fix cause, fly again. Repeat.

12 hours ago, anthdci said:

 

Sounds like this one will light all 3 engines then throttle them/cut one if they are all working.

But not until the weather breaks. BocaChicaGal says her car was covered with ice today.

  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • 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!