Recommended Posts

5 hours ago, philcruicks said:

CRS 10 has slipped again to:

18th Feb 1501 GMT (10:01 a.m. EST)

Even better! 

 

52 minutes ago, jjkusaf said:

I love me some Sat/Sun launches...especially the morning ones.  Eat some pancakes, drink some coffee and watch a controlled explosion.

Amen! 1501UTC is a great time for a beer, some chips and a lovely bright Landing.

Especially when it'll be the first daylight landing at LZ-1. :yes: Worthy of tailgate parties and grills ... I know I'd rather tailgate one of these than football or [barf.suppression=1] Nascar. It'll be "full glory" mode this time.

  • Like 2

So long ago already, seems a bit unreal when you let that sink in :)

 

Also still remember everything from the COTS-2 demo mission as if it only happened just recently. Especially since Dutch astro Andre Kuipers was part of the capture team that very first time around :)

  • Like 2

My understanding is they want LC-40 back up and running by June or July. I'm expecting August or September, there's a lot of GSE that got trashed in the mishap that they want to upgrade (since they're doing work there anyway).

A bit OT, but what the hey 

 

http://www.teslarati.com/craft-brewery-opens-spacexs-backyard-creates-beer-employees/

 

Quote

 

When their shifts are over, SpaceX employees in Hawthorne, CA only have to walk a short way to their favorite new hangout: Los Angeles Ale Works. The soft opening of the area’s first craft brewery a couple of weeks ago has allowed SpaceX employees to personally sample a variety of what will be the house signatures brews — two-dozen taps pouring a wide variety of styles of small batch beer. Starting Thursday, when the grand opening will take place, crowds will descend upon the former industrial building and Hawthorne’s first brewery and tasting room. For now, a bunch of the SpaceX employees and locals have been savoring Los Angeles Ale Works’ inviting space.

 

Los Angeles Ale Works already serves two varieties named after SpaceX: a low-alcohol session India Pale Ale named Space XPA and a Space XPA Full Thrust double IPA.

 

 

SpaceX-beer-Hawthorne-Aleworks.jpg

  • Like 2

After all the handwriting by Andy Pasztor in WSJ, the GAO report on SpaceX  turbopump cracks is out.

 

For SpaceX the risks are getting enough Block 5 flights in before certification and the turbopump now non-issue  

 

Quote

During qualification testing in 2015, SpaceX identified cracks in the turbines of its engine. Additional cracks were later identified. Program officials told us that they have informed SpaceX that the cracks are an unacceptable risk for human spaceflight. SpaceX officials told us that they are working closely with NASA to eliminate these cracks in order to meet NASA’s stringent targets for human rating. Specifically, SpaceX has made design changes that, according to its officials, did not result in any cracking during initial life testing.

  • Like 2

I smell a deliberate stalling attempt here. Not once has a SpaceX Falcon-9 engine failed during launch. This is, at most, an issue of reuse -- which SpaceX have already said they wouldn't reuse for anything that would be flying people on-board, NASA regulations aside -- and those S1's would follow a recertification process before being flown again.

 

SpaceX have addressed the issue and they appear to have corrected it, however slight that issue was. They're SpaceX -- nothing left to chance. But what it says to my mind is that whomever initiated this whole fiasco (let's call it what it is) was acting on the interests of others. They had to be. There's no other explanation for anyone to be digging around inside the reports like this and making such a huge deal out of it when it was already being dealt with internally. Only someone who knew what they were looking for could find reports like this -- and since the Merlin designs are available for scrutiny, all it takes is a couple of Engineers who are familiar with such problems to point out design shortcomings. And turbopump cracking is an easy one. That's happened to just about every Jet and Rocket engine that uses turboprops or turbopumps. Same basic idea behind turbocharged anything, really.

 

When we look at who would benefit from such a delay and the time it takes in addressing the turbopump cracking "issue" -- something that never was made an issue during the Shuttle Program -- the usual players are right there, playing in their sandbox trying to look innocent.

 

I think someone in OldSpace initiated this fiasco as a way to stall for time. SpaceX have been making too many leaps in too short a time and OldSpace is getting stressed out about their inabilities to meet milestones or even get their gear to work properly.

 

And anyone who has ever had to deal with Mil/Gov Contractors knows how absolutely dirty they can be if they've been backed into a corner and are on a deadline. I've seen VP's shout down Majors before. Absolutely vicious ... ehh .. "people". They're used to getting their way and will go to some pretty extraordinary ends to do it.

 

Of course there will never be any "fessing up" about Industrial Harassment or anything. It's not illegal to harass your competitor -- regardless of it being generally bad behavior, and unprofessional as hell -- but more and more I get the sense that OldSpace just can't keep up, and will start resorting to tactics like these more often just to level the playing field unless some sort of "business arrangement" is made.

 

Like ULA and Orbital-ATK did. Talk about having cake and eating it .... yeeesh. That's a whole other subject.

There was one launch that did have an engine failure. It was one of the early Falcon 9 missions and the mission overall was successful even with the 1/9 failure. I can't remember which one but will try to look it up.

 

Edit: It was CRS-1

 

Having said that, I agree with everything you said. I think there is a level of "well that's just business" especially when there are billions of dollars at stake but it is still pretty sad that the industry as a whole pretty much stopped innovating in the 70s until SpaceX came along.

  • Like 1
7 minutes ago, rdlenk said:

There was one launch that did have an engine failure. It was one of the early Falcon 9 missions and the mission overall was successful even with the 1/9 failure. I can't remember which one but will try to look it up.

 

Edit: It was CRS-1

 

Having said that, I agree with everything you said. I think there is a level of "well that's just business" especially when there are billions of dollars at stake but it is still pretty sad that the industry as a whole pretty much stopped innovating in the 70s until SpaceX came along.

Yep... One engine failure... but it wasn't the turbo pump iirc, but a material defect in the chamber.  Cool thing about that failure is it didn't lead to RUD. :)

  • Like 1
16 minutes ago, jjkusaf said:

Yep... One engine failure... but it wasn't the turbo pump iirc, but a material defect in the chamber.  Cool thing about that failure is it didn't lead to RUD. :)

If anything it showed that the rocket would be fine if one/some did fail, and that the engine could power out without destroying itself

  • Like 2

CRS-1 was a partial failure as its secondary cargo (Orbcomm-2) had to be released early to meet ISS safety regulations and burned up in the atmosphere. Overall it did show the F9 to be very robust and demonstrated its engine-out capability. The secondary payload was only lost because of an abundance of cation (fully deserved when dealing with human life) for objects that might potentially get close to the ISS orbit. Orbcomm knew about this regulation and that it increased the chance of losing their payload but the agreed to it because they got a discount on launch fees. 

 

I brought this up only because Unobscured Vision said the F9 had never had an engine failure during launch which just isn't the case.  Maybe 'failure' is a strong word for CRS-1 as the engine actually just shut itself down due to a detected pressure drop in the chamber and did not really 'fail'. So if anything, it just reinfored how well F9 can deal with issues and gracefully handle anomalies.

  • Like 1
This topic is now closed to further replies.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!