Star Citizen

Comm-link [robertsspaceindustries.com]

(Below text highlights taken from Pipeline Discord)

• For the first time in our history, we will run 2 live releases in parallel, each with their own progress and persistence.
  
• We acknowledge that we did not have time to get all the mission types working before our holiday break, which is why we have decided to temporarily support two parallel Live tracks: Alpha 3.24.3 will remain available, so you can play the missions and engage in game loops that are not working to our new playability standards in 4.0. Meanwhile, the 4.0 Preview will also be accessible from your launcher as a second Live option.
  
• That said, it's important to note that progress made in Alpha 3.24.3 will remain tied to that version and will not transfer to 4.0. This allows us to maintain a clean slate for the new systems coming online in the 4.0 Preview, ensuring a consistent and stable environment as we look to deprecate 3.24.3 in the new year.
  
• With today’s release, Server Meshing is no longer a question mark, but a reality, and seeing the results of a more densely populated universe, as well as better performance and stability

• As we jump into the new year, our primary focus across our Star Citizen teams is clear: improving playability. Our drive for playability surrounds three critical areas - performance, stability, and content.
  
• To achieve our goals, we are making a fundamental change: decoupling feature development from content creation and general fixes. This means new features will no longer hold up content delivery or risk destabilizing the Live environment. This approach will leverage the Tech Preview Channel, which was reserved for major new pieces of technology, like the Replication Layer and Server Meshing will now extend to gameplay feature testing too.
  
• When a new feature is deemed complex or risky enough to require focused testing, we’ll introduce a separate Experimental PTU (EPTU) channel dedicated to that feature. Testing in this isolated channel will allow us to refine and stabilize the feature without impacting content and broader development work. Only once the feature is fully greenlit will it integrate into our standard Evo/PTU/Live pipeline.
  
• We are taking this approach to deliver more things to do, more often than we have in the past where we have frequently been held hostage by tech or feature work that has taken longer than anticipated.