- Messages
- 5,196
Hotfix 2.3.1a
Just posted hotfix 2.3.1a with some resource issue fixes from @cbrgamer2! This should help with a few production issues that may have cropped up since 2.3.0.
--------------------------------------
Patch 2.3.2
For those of you who haven't hear from one of my recent videos, 2.3.2 is going to be a couple weeks away still as I've been working on some 3.0.0 stuff that I need to ensure is fully tested with the live code before releasing 2.3.2.
2.3.2 will be the last major patch before 3.0.0. Though there will still be hotfixes in between for any severe issues we can fix.
The goal for patch 2.3.2 is to take care of as many confirmed issues as are feasible. So if you have a known bug, be sure to keep checking in the Support section to see if someone else has repeated your issue. If you have not had any luck finding someone else with your issue, either through posting and getting no response, or searching and finding nothing similar, if you can replicate an issue yourself in an SS2 only save file* and post the save, I can use that as well to fix the issue!
For such a save file, just upload it to Google Drive, share it publicly, and make a post in the support section describing the issue and include a link to the SS2 only save file*. Mention in the title of your post that you have a confirmed issue save file and someone will push it to our confirmed issues list after they verify.
*SS2 only save file would be a save that was started with only Workshop Framework, HUD Framework, SS2, and SS2-related mods (ie. Chapter 2, addon packs, and City Plans) - and then was able to recreate the issue.
If the issue only occurs in a fully-modded save, it's nearly impossible to figure out which mods are triggering the issue, and if you remove mods to make it an SS2 only save, the file will be completely unstable and not useful in troubleshooting. These must be files that were made with only SS2/WSFW/ and related files for the sake of testing.
--------------------------------------
3.0.0 and Chapter 3
I don't have a timeline for 3.0.0, as we have a lot left to do for Chapter 3 still, and 3.0.0 represents the "day 0 patch" for Chapter 3. I can only say this will be the longest period between patches we'll ever have had as I really need to hunker down and focus on Chapter 3. I will still do news videos and Live Streams, but otherwise, you won't hear much from me.
Our goals with 3.0.0 and Chapter 3 are to beat Starfield to release (which we should be able to do so long as they don't surprise drop it on us in the next couple months!) and to be our most bug-free release ever.
To help with the latter goal, we started alpha testing WAY sooner than before - we have had various alpha tests going since April of last year, and the new code has been perpetually worked into the existing live code in small chunks to ensure it will be compatible with existing saves the entire way. In addition, once we get to Beta of 3.0.0/Chapter 3, we'll be reaching out to a larger pool of testers than we normally do to try and get more eyeballs and load orders on it.
Once we get closer, I will release details on how to be a part of that testing phase.
-kinggath
Just posted hotfix 2.3.1a with some resource issue fixes from @cbrgamer2! This should help with a few production issues that may have cropped up since 2.3.0.
--------------------------------------
Patch 2.3.2
For those of you who haven't hear from one of my recent videos, 2.3.2 is going to be a couple weeks away still as I've been working on some 3.0.0 stuff that I need to ensure is fully tested with the live code before releasing 2.3.2.
2.3.2 will be the last major patch before 3.0.0. Though there will still be hotfixes in between for any severe issues we can fix.
The goal for patch 2.3.2 is to take care of as many confirmed issues as are feasible. So if you have a known bug, be sure to keep checking in the Support section to see if someone else has repeated your issue. If you have not had any luck finding someone else with your issue, either through posting and getting no response, or searching and finding nothing similar, if you can replicate an issue yourself in an SS2 only save file* and post the save, I can use that as well to fix the issue!
For such a save file, just upload it to Google Drive, share it publicly, and make a post in the support section describing the issue and include a link to the SS2 only save file*. Mention in the title of your post that you have a confirmed issue save file and someone will push it to our confirmed issues list after they verify.
*SS2 only save file would be a save that was started with only Workshop Framework, HUD Framework, SS2, and SS2-related mods (ie. Chapter 2, addon packs, and City Plans) - and then was able to recreate the issue.
If the issue only occurs in a fully-modded save, it's nearly impossible to figure out which mods are triggering the issue, and if you remove mods to make it an SS2 only save, the file will be completely unstable and not useful in troubleshooting. These must be files that were made with only SS2/WSFW/ and related files for the sake of testing.
--------------------------------------
3.0.0 and Chapter 3
I don't have a timeline for 3.0.0, as we have a lot left to do for Chapter 3 still, and 3.0.0 represents the "day 0 patch" for Chapter 3. I can only say this will be the longest period between patches we'll ever have had as I really need to hunker down and focus on Chapter 3. I will still do news videos and Live Streams, but otherwise, you won't hear much from me.
Our goals with 3.0.0 and Chapter 3 are to beat Starfield to release (which we should be able to do so long as they don't surprise drop it on us in the next couple months!) and to be our most bug-free release ever.
To help with the latter goal, we started alpha testing WAY sooner than before - we have had various alpha tests going since April of last year, and the new code has been perpetually worked into the existing live code in small chunks to ensure it will be compatible with existing saves the entire way. In addition, once we get to Beta of 3.0.0/Chapter 3, we'll be reaching out to a larger pool of testers than we normally do to try and get more eyeballs and load orders on it.
Once we get closer, I will release details on how to be a part of that testing phase.
-kinggath