Patch Notes and Spectrum Testing MOTD.
This uses a feed from the very nice people at TrackerSC.com
(Thor’s Day) We are currently cooking a new 3.23.1a build with further updates for XenoThreat with the plan on running XenoThreat on PTU tonight and over the weekend along with jumptown.
(Thor’s Day) Tonight’s 3.23.1a PTU build was redlit due to a new server crash that would have made it a worse experience. We’ll try again tomorrow!
We’re still looking through multiple issues internally before I can make a call on a new PTU build today. Xeno hit a snag that caused it to only run once and not cycle over the weekened. We are looking into that as well as other stability issues that are affecting LIVE
(Tuesday) We are currently cooking a new 3.23.1a build for release onto the PTU this afternoon. On the current PTU we are testing a backend change to XenoThreat to see if the changes will work by causing a fail state in about 2 hours. If the data looks good from this and the new build then this will be a LIVE RC for later this week.
Ships & Vehicles
@GeneralNews
(Wednesday) We are currently not planning on any further 3.23.1a PTU publishes with 9204897 being our LIVE RC for a possible release late Thursday/Friday.
3.23.2 is still being worked on and will update with more info as soon as we are ready to test it with Evocati.
(Thursday) We are not planning on publishing a new PTU build today. Current goal is to continue warming the new LIVE environment and release 3.23.1a build 9204897 later today.
Gameplay
Ships & Vehicles
Core Tech
@GeneralNews
No 3.23.2 PTU with evocati today! We are targeting Tuesday/Wednesday but will know better by tomorrow!
(Monday) We are opening up the HOTFIX channel on the launcher soon for a 3.23.1a hotfix that will connect to the LIVE servers. This fixes a handful of server and client crashes, a deadlock, and landing service not functioning issues. If all is well it will be pushed over into the LIVE servers when ready.
RSI Launcher 2.0.1 can be found here
Fixed From IC:
Other Fixed issues:
We are still working on getting a .2 build ready for Evocati. It won’t be today but goal is still to have a build ready asap
(Tuesday) We have pushed a new 3.23.1a hotfix onto LIVE with multiple server and client crash fixes. We currently have 2 PTU goals this week if all goes as planned.
No cargo build yet today
We’re going to open the Server Meshing Tech-preview tomorrow to all backers and have the build up 4-6 hours
(Wednesday) Goals for this week:
Today we are focusing on the TECH-PREVIEW build. The environment is being built now and goal is to start a 4-6 hour playtest with you all by around 19-21:00 UTC.
This test is purely focused on the new hardware structure so we aren’t worried about bug reporting unless it is very specific to the mesh.
Heya Star Citizen Testers!
Starting today at 19:00 UTC (2pm CDT) we will be running a 2-5 hour playtest (Depending on new hardware stability) on the TECH-PREVIEW channel to test a more efficient hardware setup with a slightly lower amount of players per VM!
This test will have each Stanton shard split into 3 authoritative zones for about 200 total players each mesh.
We are mainly looking for server performance and will be running an older 3.22.x build for A/B testing compared to the previous meshing tests we have run. We will be doing many server captures over the length of the test to gather performance data.
During the test, missions may not function completely (leaving an authority zone may abandon missions) so you may have to avoid them, but otherwise, play as normal! Spread out around Stanton’s moon’s and planets, run cargo, dogfight.
As this is an older build, we are not looking for bug reporting on gameplay issues unless they are very specific to (sic)
Thank you all so much for your help in testing these new and exciting tech updates!
@GeneralNews
**We are just about to take down the TECH-PREVIEW test for tonight! The new hardware was working great but we have found an issue with code that isn’t working correctly tonight and causing some mesh deadlocks which will require a new build. **
We are looking to attempt another run at this tomorrow morning (as early as <t:1718982000:t> ) with a different build that shouldn’t have the same issues.