Stargate Universe (Season 1)


Poll added by Fred Derf on April 10th  

157 members have voted

  1. 1. Who should lead on Destiny?



Recommended Posts

After this weeks episode I couldn't help but notice some parallels to Voyager. At the beginning of Voyager there was the tension between Starfleet and Maquis crew. Eventually the came together and resolved their differences. Universe has the civilians vs. the military. There is still the underlying tension between them but it seems for the most part that they are moving beyond that. Voyager had a doctor that was thrown into a situation which was totally out of their element which is basically TJ.

I am not trying say that's a bad thing. I am liking this show more and more with each episode.

An utter trash episode IMO. These kind of episodes along with time travel and flashback types are filler episodes and should never be shown this close to the end of a season. Overall I don't feel it added anything to the story and will be easily forgettable.

I know they aren't the same show but when you look at the amazing writing they have on Fringe where each of the last few episodes have built on top of each other towards the main storyline and feel like they are adding own to the story. Then you look at Universe where each episode just feels like a random episode and seems to have little value on it's own merit, I just feel there's alot more they could do with it.

Destiny is the coolest ship I've ever heard of: I mean for goodness sakes, it safely dives in to a star when it needs power. It travels faster than light through normal space, and it's already gone billions of light-years. I bet if it jumped in to the Death Star, it would just punch through it.

Where did that rendering come from??

Yeah the episode was trash. That Greer *** is teh suxer isn't he?

I personally liked seeing the fears that each person had and the blending between what was real and what was hallucinations. Greer going off the deep end versus Chloe's rather subtle hallucination. It was nice how it all played together.

I agree, they've been working through a lot of peoples personal problems over the course of the season. Making them come out in the hallucinations was a nice touch, it's like a cheesy clip show but with emotional content rather than graphical.

I have to say I was rather disappointed with last nights episode "Pain" Just did not feel as if it was going anywhere. there was also a continuity issue i had with the episode.

I thought they were traveling between galaxies at the moment and it was going to take a rather long time, however, at the end of the episode they came out of FTL (that wasn't supposed to be possible.)

I thought they were traveling between galaxies at the moment and it was going to take a rather long time, however, at the end of the episode they came out of FTL (that wasn't supposed to be possible.)

the only thing i can think of is a solar system that got flung out of the galaxy.

I have to say I was rather disappointed with last nights episode "Pain" Just did not feel as if it was going anywhere. there was also a continuity issue i had with the episode.

I thought they were traveling between galaxies at the moment and it was going to take a rather long time, however, at the end of the episode they came out of FTL (that wasn't supposed to be possible.)

my guess is we're to assume that they had already travelled several months before and during the time of this incident and had reached the other galaxy. you notice at the end Rush or Young weren't like OMG a planet now, this isn't suppose to be. So it was completely expected.

Finally, something interesting. Subversion looks like it's going to be a good episode. As for the previous episode, they haven't left the galaxy yet

because we know the Lucian Alliance is going to infiltrate the ship soon.

Stargate Universe - Episode 1.17 - Pain - Promotional Photos

"Pain" Press Release

A few members of the Destiny crew begin experiencing disturbingly realistic hallucinations bringing their personal fears or desires to life. Some worry that the stress of life on board the ship has finally begun to trigger nervous breakdowns.

After isolating those affected Dr. Tamara Johansen believes the hallucinations are related to the last planet the away team visited. But just as she thinks she?s contained those at risk, she discovers the cause of the hallucinations is transferring to other members of the crew. When the hallucinations become life threatening, she and the crew must track down whatever is causing the episodes before someone dies as a result.

This didn't address the issue of the chair. Perhaps I missed the first few minutes but it was as if this episode designed to be aired before the episode arc where they were leaving one galaxy and heading towards another.

This didn't address the issue of the chair. Perhaps I missed the first few minutes but it was as if this episode designed to be aired before the episode arc where they were leaving one galaxy and heading towards another.

No, TJ was definitely much bigger than before. It aired in the correct place.

They did address the chair. Said they called off the search for Franklin.

Search was called off.

I agree with deadite about your assumption of why everyone wasn't surprised at the end of the episode.

I'm curious to see how the next episode ties into where things stand with the crew and what the IOA thinks has transpired thus far.

It would have been a great twist if the aliens actually were boarding the ship, but the audience were lead to believe it was in Rush's head. You have a scene where somebody else sees an alien and it becomes a holy-crap moment. Wasted potential, but I still liked the episode overall.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 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
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | 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
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!