this post was submitted on 13 Jun 2023
3 points (100.0% liked)

Star Citizen

30 readers
1 users here now

founded 4 years ago
MODERATORS
Rumblestiltskin@lemmy.ml
3
MotD: (Tuesday) We are not expecting a new PTU publish today. (robertsspaceindustries.com)
submitted 1 year ago by MrAegis@lemmy.ml to c/starcitizen@lemmy.ml
2 comments fedilink hide all child comments
 

Could be a good sign. If the Current PTU is stable enough that we haven't seen any hotfixes, we may be in for an update to the Live servers soon.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ProjectPatatoe@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (1 children)

I find confusing when people complain about stability and dont specifcy live or ptu. Seems like ptu is much better overall from last I tried. I'm hopeful for this week. Most of the ones on the known issue list can wait for a 19.2.

I'm mostly concerned with these as they are potentially session enders:

  • ATC - Hangar door - Hangar doors appear open to players; however, when flying into hangar ship collides with closed hangar doors. Hangar Doors Causing Damage/Ship Destruction
  • Ships can explode from collision with invisible asteroids

And these since new player experience and all:

  • Transit - Area18 - Orison - Shuttles/Trains/Trams - Players are falling through sometimes disappearing trams and shuttles to their deaths
  • Locations - ArcCorp / Crusader - Area18 / Orison - Core Tech / Transit Systems - The Trams are out of sync with the station timers, causing trams to overlap or not appear on time
[โ€“] MrAegis@lemmy.ml 1 points 1 year ago

Seems like ptu is much better overall from last I tried.

It gets complicated when we get to the details of what's actually affecting the Live servers. It seems like a large number of the major issues experienced in Live weren't readily visible in the PTU.

The hangar door issue is one I specifically remember from years ago, but could never get enough players that were able to reliably recreate it. Now it seems like it's only something that occurs when the servers are stressed enough.

In a way I'm glad these issues are finally occurring to a point where they need to be addressed. Unfortunately these are also the issues that I suspect require major improvements to the core code. A quick fix may be possible but at a significant hit to server performance? Hopefully they address it soon and let us know what's actually going on.