2.0748?
-
kmunoz
- Ensign
- Posts: 48
- Joined: Sun May 17, 2015 9:00 pm
2.0748?
So I've got a build of 2.0748 from Vice that I've been using for a while and the ...8 builds are usually final builds, but it hasn't gotten to Steam yet. Do we know the timeline on this? I've had a couple people ask me how I'm .002 ahead.
-
Vice
- Administrator
- Posts: 12227
- Joined: Fri Apr 25, 2003 1:38 am
Re: 2.0748?
It's on hold while I continue to review two issues.
First, I'm investigating a 0xc000005 generic Windows stop error one player has run into and I need to determine if I can fix it on my end, or if it is a system-side problem with no solutions I can apply. Unfortunately, this issue requires the involvement of third parties that I have to wait on for some testing results, possibly some debug analysis, and depending on the outcome, strategizing a work-around if one is available for me to apply.
Second, one of the new feature elements is still under testing evaluation and has not yet finished its array of required checklist completions before a final update can roll out. It's a significant control input change that has a higher chance of bugs/problems and is more complex in design. This one should go quicker though and is nearly finished at this point.
As updates are now more finalized in nature, I want to make sure they are solid and reliable before rolling them out. When problems surface or feature changes/additions requires more extensive testing, that can push back a rollout until I'm more confident in the state of such an update. So it will roll out when it is ready, which could be by next week or take a few more weeks before I'm able to complete the various things that need to be done.
First, I'm investigating a 0xc000005 generic Windows stop error one player has run into and I need to determine if I can fix it on my end, or if it is a system-side problem with no solutions I can apply. Unfortunately, this issue requires the involvement of third parties that I have to wait on for some testing results, possibly some debug analysis, and depending on the outcome, strategizing a work-around if one is available for me to apply.
Second, one of the new feature elements is still under testing evaluation and has not yet finished its array of required checklist completions before a final update can roll out. It's a significant control input change that has a higher chance of bugs/problems and is more complex in design. This one should go quicker though and is nearly finished at this point.
As updates are now more finalized in nature, I want to make sure they are solid and reliable before rolling them out. When problems surface or feature changes/additions requires more extensive testing, that can push back a rollout until I'm more confident in the state of such an update. So it will roll out when it is ready, which could be by next week or take a few more weeks before I'm able to complete the various things that need to be done.