Recommended Posts

On 2/16/2020 at 3:36 PM, shockz said:

I can definitely see that, after the dominion war, mars incident, etc... and that they took Picards mothball concept and went with it. I still have a feeling we'll see a starship or two by seasons end.

Mar's isn't Starfleet's only shipyard, merely its main one.  I'm sure that in the intervening years since it burned, they've upgraded others.

5 hours ago, FloatingFatMan said:

Mar's isn't Starfleet's only shipyard, merely its main one.  I'm sure that in the intervening years since it burned, they've upgraded others.

Doesn’t look like it, with old recycled shuttles and them nowhere to be seen.  

Even during the Mars attack there were dsc ships sitting in space dock. 
 

starfleet seems to have a capacity issue after dom war, there weren’t enough ships seems to be a constant theme with this series. 
 

In reality it’s probably some red tape issue where the majority of ship designs we’ve saw are part of cbs/Viacom differences, and the show was completed before the merger discussions happened. I’m sure season 2 will have more ships. 

Edited by shockz
10 hours ago, FloatingFatMan said:

Mar's isn't Starfleet's only shipyard, merely its main one.  I'm sure that in the intervening years since it burned, they've upgraded others.

That's accepted Trek cannon.  But can you, without looking anything up, name another?

 

I can't.

12 minutes ago, Human.Online said:

That's accepted Trek cannon.  But can you, without looking anything up, name another?

 

I can't.

I thought there was one near Jupiter, wasn't it also largely featured in Into Darkness with the secret ship piloted by Robocop? (all this without looking anything up) 😛 

 

Edit: I wasn't far off 😛 

Quote

In the 2013 sequel, Montgomery "Scotty" Scott discovers a covert Starfleet facility, near Jupiter, that has built a much larger Federation warship, USS Vengeance. Source

 

4 minutes ago, Steven P. said:

I thought there was one near Jupiter, wasn't it also largely featured in Into Darkness with the secret ship piloted by Robocop? (all this without looking anything up) 😛 

 

Edit: I wasn't far off 😛 

 

Different timeline ;)

28 minutes ago, Human.Online said:

That's accepted Trek cannon.  But can you, without looking anything up, name another?

 

I can't.

Without looking anything up, I can name two.  One at Deep Space 5, and another in San Francisco.  WITH looking it up, there are a lot more...

 

40 Eridani A Starfleet Construction Yards

Antares Ship Yards

Baikonur Cosmodrome

Beta Antares Ship Yards

Copernicus Ship Yards

Deep Space 5

Earth Station McKinley

Iadara colony

Luna Shipyards

Marin County Starfleet Yards

Oakland Fleet Yards

Proxima Maintenance Yards

Riverside Shipyard

San Francisco Fleet Yards (also known as "San Francisco Naval Yards" or "San Francisco Yards")

Starbase 47

Starbase 234

Tranquility Base

University of Copernicus

Utopia Planitia Fleet Yards (also known as "Utopia Planitia Ship Yards")

Tri-Rho Nautica (Located close to the Klingon border and the largest of Starfleet's shipyards)

 

Everyone should know the San Francisco one.. It's the orbital drydock facility near Earth, as seen in Star Trek the Motion Picture and several others.

 

maxresdefault.jpg

2 minutes ago, FloatingFatMan said:

Without looking anything up, I can name two.  One at Deep Space 5, and another in San Francisco.  WITH looking it up, there are a lot more...

 

40 Eridani A Starfleet Construction Yards

Antares Ship Yards

Baikonur Cosmodrome

Beta Antares Ship Yards

Copernicus Ship Yards

Deep Space 5

Earth Station McKinley

Iadara colony

Luna Shipyards

Marin County Starfleet Yards

Oakland Fleet Yards

Proxima Maintenance Yards

Riverside Shipyard

San Francisco Fleet Yards (also known as "San Francisco Naval Yards" or "San Francisco Yards")

Starbase 47

Starbase 234

Tranquility Base

University of Copernicus

Utopia Planitia Fleet Yards (also known as "Utopia Planitia Ship Yards")

Tri-Rho Nautica (Located close to the Klingon border and the largest of Starfleet's shipyards)

 

Everyone should know the San Francisco one.. It's the orbital drydock facility near Earth, as seen in Star Trek the Motion Picture and several others.

OK yeah, the San Fran one was kinda obvious.  The others, are they cannon?

 

My point being, there has to be some explanation for the lack of modern ships:

 

1) Not as many shipyards as we thought

2) Throwing accepted cannon out the window

3 minutes ago, Human.Online said:

OK yeah, the San Fran one was kinda obvious.  The others, are they cannon?

 

My point being, there has to be some explanation for the lack of modern ships:

 

1) Not as many shipyards as we thought

2) Throwing accepted cannon out the window

I'm pretty sure every single one has featured in at least one TV episode throughout the years.  Some may only be in ST:TAS, but those are still official canon as they were on TV; which is the primary criteria.

 

I think Starfleet has plenty of the regular ships; it just doesn't have COLONY ships. Big massive people movers that would be necessary for moving entire worlds of people.  Something like the holoships we saw in Insurrection.  IMO, that's almost certainly the sort of thing they were referring to, given the context of the Romulan evacuation.

1 minute ago, FloatingFatMan said:

I'm pretty sure every single one has featured in at least one TV episode throughout the years.  Some may only be in ST:TAS, but those are still official canon as they were on TV; which is the primary criteria.

Hence the latter then?

 

See - we saw the San Fran campus and it was busy with uniformed people and people literally constantly beaming in and out via those archway transporters.

 

Where are the ships in orbit?  Hell where was spacedock?

It's obvious that Earth has improved its transporter technology enough so that it's now instant instead of taking several seconds to cycle.  That alone has probably negated the need for so many ships in orbit. As for the orbital station, just because they didn't show it, doesn't mean it's not there.

 

Also, I would imagine that they're expending quite a lot of resources to put Mar's out...

I don't think ship counts or showing off brand new ship designs were the goal for the show to start.  Who knows what we might see later or in season 2 but I just think they didn't plan for them and the VFX team hasn't done any work on more ships.

9 minutes ago, George P said:

I don't think ship counts or showing off brand new ship designs were the goal for the show to start.  Who knows what we might see later or in season 2 but I just think they didn't plan for them and the VFX team hasn't done any work on more ships.

This is for certain the OOC reason, but you know fans.. Always trying to figure out and IC reason for something they didn't show on TV. :p

 

16 minutes ago, FloatingFatMan said:

It's obvious that Earth has improved its transporter technology enough so that it's now instant instead of taking several seconds to cycle. 

Hell, in Picard they were just walking through a "doorway" and they were transported.

5 hours ago, spacelordmaster said:

Rumor has it Worf is the new captain of the Enterprise and that he, and the Enterprise, will make an appearance at some point in the series.

Well, it's known he was on set at one point as his signature is on one of the "wrap" clapboards, but they've been vehemently denying he was shooting anything. I *would* love to see Worf again though, and Dorn would jump at the chance to be in Trek again, especially considering he tried to get them to create a Worf based show...

2 hours ago, FloatingFatMan said:

Well, it's known he was on set at one point as his signature is on one of the "wrap" clapboards, but they've been vehemently denying he was shooting anything. I *would* love to see Worf again though, and Dorn would jump at the chance to be in Trek again, especially considering he tried to get them to create a Worf based show...

I am pretty sure they are denying it just like they denied bringing Frakes and other characters. They just don’t want to spoil the surprise. I am quite sure we will see the Enterprise once again and Worf and Crusher and Geordi. I know for sure Q will be there soon. Probably by the end of the season on the last episode.

3 hours ago, George P said:

The newest episode was good, we hardly got any answers though, just some good 7 character development. 

Yes, and then at the very end, even more questions!

Nothing wrong with it either, shes still trying to "find herself"

One thing I'm not a fan of though is how the phasers seem to be more like projectile weapons now... Thanks JJ..

3 minutes ago, Matthew S. said:

Nothing wrong with it either, shes still trying to "find herself"

I mean she embraced her humanity by the end of voyager, especially near the end of its run, and now she’s a soulless renegade? I mean, sure, losing a “son/kin” would be traumatizing and anyone would seek revenge, but I don’t like that she’s gone full vigilante. Almost dexter style.  Also, not seeing the Bi angle. 

  • Like 2

While she did embrace it, I don't believe she found her purpose by the end of VOY.  Also remember there's about a 16 year gap minimum between when VOY got back to the Alpha Quadrant and Picard too...

17 minutes ago, Matthew S. said:

While she did embrace it, I don't believe she found her purpose by the end of VOY.  Also remember there's about a 16 year gap minimum between when VOY got back to the Alpha Quadrant and Picard too...

I could go with the angle of helping the helpless, especially with xB, but out right premeditatedly murdering someone? That’s not Seven. A plot that was subtly explored during voyagers run (see: Infinite Regress, Imperfection, Survival Instinct, Prey), especially with the guilt of being a borg drone assisting in the countless destruction and murder of people while being in the collective. It’s just counter to everything her character was made into.

Edited by shockz

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!