Recommended Posts

On 23/01/2022 at 21:54, Emn1ty said:

It just shows that these writers don't understand the whole concept of Star Trek. It's about exploring interesting concepts and conundrums that force an evaluation of character, morals, ethics and perspective. Picard Season 1 did none of that.

Remember, all these writers went to a "Star Trek writing school" held by someone who had NEVER written about, or been involved in, Star Trek...

  • Haha 2
On 25/01/2022 at 07:33, spacelordmaster said:

Come on guys, Star Trek: Picard is not so bad. Just like Discovery. They are two totally different Star Treks.

No, they're not bad as such.... They're just not Star Trek.  When the announcement was made, Patrick Stewart promised he wouldn't be involved in something that didn't have a worthwhile story.  He lied.

 

If you want to watch something that's faithful to the original formula of Star Trek, that made it so successful, give The Orville a shot.

 

Edit:  Honestly, I DO get what they're trying to do with Trek. They want to modernize it into something that appeals to a modern audience. But in doing so they forgot the millions of EXISTING fans and managed to really really REALLY p*** a LOT of them off, big time. 

 

They sacrificed millions of older dedicated franchise fans with money to burn, in favour of a much smaller number of new younger fans who are largely broke... That's really not a clever thing to do.

Edited by FloatingFatMan
On 25/01/2022 at 02:36, FloatingFatMan said:

No, they're not bad as such.... They're just not Star Trek.  When the announcement was made, Patrick Stewart promised he wouldn't be involved in something that didn't have a worthwhile story.  He lied.

 

If you want to watch something that's faithful to the original formula of Star Trek, that made it so successful, give The Orville a shot.

 

Edit:  Honestly, I DO get what they're trying to do with Trek. They want to modernize it into something that appeals to a modern audience. But in doing so they forgot the millions of EXISTING fans and managed to really really REALLY p*** a LOT of them off, big time. 

 

They sacrificed millions of older dedicated franchise fans with money to burn, in favour of a much smaller number of new younger fans who are largely broke... That's really not a clever thing to do.

I agree to a certain point, but in the case of Picard, I think they are trying to make for all that by bringing in fan-favorite characters such as Q and Guinan back. Also, if you remember the very last episode of STNG, Q told Picard: "See you out there." well, we never saw him again, in any of the STNG movies, until now. I love Q. I think this season is going to be a very interesting one.

 

 

  • Like 2

The only thing good about ST Discovery was Jason Isaacs, Anson Mount and Rebecca Romijn performances, the rest was on daytime soap opera level. Heck, Rebecca Romijn did more for Trek in Short Treks than an entire episode of Discovery ever could and we are getting Strange New Worlds out of it. Admittedly there are some good actors in Discovery such as Tig Notaro but it's lost on the crap writing. I won't get into the politically correctness of the show, but that annoys me too.

 

I really hope they don't screw up SNW, but anything's possible with Hollyweird!

 

I'll watch Picard, it's better than Discovery.

On 25/01/2022 at 07:46, spacelordmaster said:

I agree to a certain point, but in the case of Picard, I think they are trying to make for all that by bringing in fan-favorite characters such as Q and Guinan back. Also, if you remember the very last episode of STNG, Q told Picard: "See you out there." well, we never saw him again, in any of the STNG movies, until now. I love Q. I think this season is going to be a very interesting one.

 

 

he was on DS9 (at least once i think) and voyager multiple times

  • Like 5
On 25/01/2022 at 07:46, spacelordmaster said:

I agree to a certain point, but in the case of Picard, I think they are trying to make for all that by bringing in fan-favorite characters such as Q and Guinan back. Also, if you remember the very last episode of STNG, Q told Picard: "See you out there." well, we never saw him again, in any of the STNG movies, until now. I love Q. I think this season is going to be a very interesting one.

 

 

I will give season 2 an honest chance, but really... It's being written by the same people...

On 24/01/2022 at 23:46, spacelordmaster said:

I agree to a certain point, but in the case of Picard, I think they are trying to make for all that by bringing in fan-favorite characters such as Q and Guinan back. Also, if you remember the very last episode of STNG, Q told Picard: "See you out there." well, we never saw him again, in any of the STNG movies, until now. I love Q. I think this season is going to be a very interesting one.

 

 

The implication from the trailers that Q messed with the timeline has me scratching my head. Q never messed with the timeline, he simply created illusions or "influenced" current events. In fact, him messing with the timeline would be in direct violation of what the Continuum would allow. It goes way beyond anything Q has ever actually done in any of the series. The closest being what Picard's life would have been like if he'd never lost his heart, and that was more teaching Picard a lesson than actually changing anything about history. I'm going to watch it, but I have little faith they'll do any of these characters justice anymore.

On 25/01/2022 at 22:08, Emn1ty said:

The implication from the trailers that Q messed with the timeline has me scratching my head. Q never messed with the timeline, he simply created illusions or "influenced" current events. In fact, him messing with the timeline would be in direct violation of what the Continuum would allow. It goes way beyond anything Q has ever actually done in any of the series. The closest being what Picard's life would have been like if he'd never lost his heart, and that was more teaching Picard a lesson than actually changing anything about history. I'm going to watch it, but I have little faith they'll do any of these characters justice anymore.

Q never followed continuum rules, that's why he was always getting in trouble with his superiors. He always did things his way.

On 25/01/2022 at 22:00, spacelordmaster said:

Q never followed continuum rules, that's why he was always getting in trouble with his superiors. He always did things his way.

Yes, but he was also governed and punished by them multiple times for it.

  • Like 1
  • 1 month later...

Today's opener was great. Felt like the Trek we let go of after Voyager. And seeing those ships again, including the Sovereign's first time on the small screen was great. Also the NCC-2000 still around too... 

 

I like how they aged Q at the end too, was wondering how they'd pull that off. 

  • Like 2
On 03/03/2022 at 21:02, shockz said:

Today's opener was great. Felt like the Trek we let go of after Voyager. And seeing those ships again, including the Sovereign's first time on the small screen was great. Also the NCC-2000 still around too... 

 

I like how they aged Q at the end too, was wondering how they'd pull that off. 

It felt like a movie, but yes strong opener..

 

Spoiler

So it looks like yet another Starfleet captain is heading back to "our time" (the 20th/21st century). ;)  

 

  • Like 2

It was OKish, I didn't quite hate it... At least until we discovered that Starfleet is now run by complete and utter morons who think that...

 

Spoiler

... it's a GREAT idea to build a starship incorporating technology derived from a Borg cube.

 

The instant they said that I KNEW it'd be biting them in the ass by the end of the episode...

 

Sorry, but that was beyond stupid and not something Starfleet would have actually done.  

On 04/03/2022 at 04:30, FloatingFatMan said:

It was OKish, I didn't quite hate it... At least until we discovered that Starfleet is now run by complete and utter morons who think that...

 

  Hide contents

... it's a GREAT idea to build a starship incorporating technology derived from a Borg cube.

 

The instant they said that I KNEW it'd be biting them in the ass by the end of the episode...

 

Sorry, but that was beyond stupid and not something Starfleet would have actually done.  

This became canon with Voyager,

 

Spoiler

Seven was responsible for a lot of the Borg technology incorporated into Voyager before they reached Earth, so it's not even a new idea.

 

On 04/03/2022 at 08:54, Steven P. said:

This became canon with Voyager,

 

  Hide contents

Seven was responsible for a lot of the Borg technology incorporated into Voyager before they reached Earth, so it's not even a new idea.

 

I know, and it bit them in the ass a few times then, too!

 

  • 3 weeks later...
On 24/03/2022 at 23:25, Nogib said:

Part of me keeps wondering if they made this whole time travel to 2024 to save money on sets since they can just slap a light dressing to current locations and call it good.

Well that's fairly obvious, but that's how the original series got made, other planets where sets already built for westerns and the like... But forgetting that, the writers, if you can call them that, forgot  a whole storyline that happened in TNG... Every scene in episode 4 had so much wrong with it I was laughing by the end.. reminded me of into darkness, so terrible

I'm enjoying the season so far and like the throw backs to ST:The Voyage home.

 

For instance

Spoiler

 

 

 

 

Spoiler

I wonder if Agnes somehow becomes the new Borg/Legion Queen we saw in the first episode.

 

Spoiler

Is the "watcher" truly Laris or just taken on her form just for Picard?  If she really is Laris I'd like to know why she was assigned to watch Picard and by whom.

 

  • 2 weeks later...

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

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • 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.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!