#sc-patch-notes

Patch Notes and Spectrum Testing MOTD.

This uses a feed from the very nice people at TrackerSC.com :star:

Spectrum MOTD:

(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.

Spectrum MOTD:

(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!

Wakapedia-CIG:

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

Spectrum MOTD:

(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.

Star Citizen Alpha 3.23.1a PTU.9204897 Patch Notes

Audience: Open PTU

Testing/Feedback Focus

  • 3.23.1a is highly focused on Jumptown and Xenothreat events. Today’s build combines many of the service and server hotfixes we’ve applied to the PTU since the last PTU release.

Features and Gameplay

Ships & Vehicles

  • Hornet Tuning Updates
  • F7A Hornet Mk2 Lateral strafe capabilities have been fixed and should now be in line with tuning expectations. F7CR upstrafing capacity adjustment. Lowered boost fuel use of the entire Anvil Hornet series.

Bug Fixes

  • Fixed - Players can’t access PU due to 30k crash or infinite load - “WaitForTutorialMission” (This will fix some accounts once build is on LIVE so nothing to test on PTU)

Technical Updates

  • Fixed 1 Server Crash

@GeneralNews

Spectrum MOTD:

(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.

Spectrum MOTD:

(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.

Star Citizen Alpha 3.23.1a LIVE Patch Notes

Features and Gameplay

Gameplay

  • Missile Adjustments
  • Reduced Salvage Coverup Rewards

Ships & Vehicles

  • Hornet Tuning Updates
  • Increased Sabre Firebird missile count from 12 → 24
  • Sabre Firebird ARMR has been modified to reduce all emissions by 40%
  • Updated Retaliator to have Size 3 guns on all turrets and updated turret constraints

Core Tech

  • Removed vehicle entrance markers when in a different zone or too far away
  • Made Further Client Performance Optimizations
  • Vehicle Hit Damage Network Performance Optimizations
  • Full Ship Weapon Audio Mixing Pass

Bug Fixes

  • Fixed an issue causing clients to experience a generic 30000 error and disconnect when loading into the PU
  • Elevators at the Pyro Jump Point Station should now arrive when called
  • Fixed an issue causing carriable objects to fall through many floors around the PU
  • Fixed and issue causing to not hit their target when the target is rotating
  • Fixed AI’s reacting to non-hostile players firing causing them to not get an attention target
  • Ship shield VFX should now play correctly
  • Fixed an issue causing many Exit/Get up prompts to be missing from beds
  • Destroying the illegal probes during the Halt illegal Surveillance missions should no longer cause players to get a crimestat
  • Fixed precision targeting gimbal mode active without being in precision mode
  • Asphyxiation issues should no longer be present in different locations of the AEGIS Retaliator
  • GRIN Pyro Multi-Tool’s Tractor beam attachment should no longer force weapon sensitivity depending on lifted weight
  • The Sabre Raven base paint will no longer replace the paint of the Firebird almost entirely regardless of paint applied
  • The ANVIL Ballista gunner seat should now have proper interaction points
  • The Crusader Spirit Olympia Paint should no longer be missing
  • Fixed missing Jumptown locations
  • Fixed Nox missing left and right thrusters
  • Kopion Horn and Marok Gem should now be able to be sold
  • Origin 400i Interior elevator’s panel should no longer disappear
  • The F8C Lightning should no longer get a hazy cockpit view while flying through space clouds
  • Fixed various visarea issues around the Aegis Hammerhead

Technical Updates

  • Fixed 6 Client Crashes
  • Fixed 5 Server Crashes
  • Fixed a Main Thread Deadlock
  • Fixed an OOM - Out of system memory Client Crash

@GeneralNews

Wakapedia-CIG:

No 3.23.2 PTU with evocati today! We are targeting Tuesday/Wednesday but will know better by tomorrow!

Spectrum MOTD:

(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 Release Notes

RSI Launcher 2.0.1 can be found here

Fixed From IC:

  • Launcher listen to key bindings when not focus (LCH-52)
  • Launcher music did not unmute When Start Citizen closed (LCH-48 and LCH-292)
  • Removing session from Connected Devices stays “logged in” (LCH-115)
  • Mute/Unmute does not work when minimized (LCH-160)
  • Download tooltip says “download_resume”(LCH-185)
  • Fixed the name of the directory with no space between “Star” and “Citizen” (LCH-210)
  • Fixed error_os_requirement_text (LCH-221)
  • Fixed Nickname WordWrap (LCH-224)
  • Session expired every 10 to 15 min (LCH-252)
  • Remember me does not work, logs me out every 30 seconds. (LCH-292 and LCH-342)
  • Wipe from right to left on Settings (Polish) (LCH-329)
  • Launcher forgets login after PC Sleeps (LCH-276)

Other Fixed issues:

  • Updated error handling to directly display the type of error 2000. That way, users do not have to look at their logs to know what type of error they encountered
  • Copywrite update
  • Added “Don’t show this again” checkbox on closing dialog
  • Improved base pack corrupted error (3001)
  • Fixed: Channel getting added to queue being stucked
  • Fixed: User can access previsous verison of the game in the first 10min after an update
  • The Game button stays stuck on Waiting on Queue when refusing ToS

Wakapedia-CIG:

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

Spectrum MOTD:

(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.

  • First - We are looking to get 3.23.2 into Evocati’s hands over the next couple days for cargo/hangar testing.
  • Second - We have a slight chance of a new Tech-Preview Server Meshing test as early as Friday with with lots of new network changes if all goes well with internal testing.

Wakapedia-CIG:

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

Spectrum MOTD:

(Wednesday) Goals for this week:

  • Thursday - We are looking to do a TECH-PREVIEW test with all backers for 4-6 hours with a more efficient hardware structure to test the meshing benefits. This test will split Stanton into 3 servers per shard with a more efficient setup and we will be monitoring network/server performance.
  • By Friday - We are still looking to have a Cargo/Hangar build out for Evocati this week. We have a couple blockers still preventing this but are getting closer.

Wakapedia-CIG:

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!

Test Instructions

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)

  • Audience: All Backers
  • Channel: TECH-PREVIEW
  • Build: sc-alpha-322-tp-9211082
  • Server Info: US Region Only - PU Only
  • Times: Test will run approx. 2-5 hours starting at 1900 UTC | 2pm CDT

Known Meshing Issues

  • SERVER MESHING SPECIFIC - Stanton Split - Subdivision - Game code / Vehicles - Unexpectedly getting dropped out of QT when Quantum travelling to different locations - Repro 100%
  • SERVER MESHING SPECIFIC - Stanton Split - Subdivision - Game code / UI - Missions wont be accepted if they are located on a different DGS - Repro 100%

Thank you all so much for your help in testing these new and exciting tech updates!

@GeneralNews

[TECH-PREVIEW Playtest] Meshing Efficiency Playtest

Wakapedia-CIG:

**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.