Alright so we had a day 1 patch.
Then we had a day 3 patch (The one that broke the game) that had to be submitted through certification in a 3 day window seeing as how it addressed a bunch of launch day issues.
And now we had to wait damn near 2 weeks for them to address the day 3 patch that was apparently submitted to certification around the 27th of February.
Now my question is, Since the certification system clearly isnt a quality assurance thing…wtf is it? Also if the “certification system” allowed the day 3 patch to go through in a matter of 3 days…Why is it we have to wait 7 days (and counting) for it to clear the patch thats supposedly gonna undo the problems brought on by the 3rd day patch?
Middle men. It’s part of Microsoft’s archaic “certification” process for consoles. They would get a much better turnaround on patches by releasing betas like many developers do on Steam allowing players to help do QA on future patches.
We can point this out but don’t expect the system to change anytime soon. There are too many people who would lose their jobs.
I don’t have the game yet, but I’m a super fan of RTS games and if the patch fix all the problems and balance issues like jackrabbit, sentinels etc. that makes the game unplayable at the moment i will buy it. And I don’t know why it takes them so long to release this fixes, also i hope the game will not be the new Battlefield 4 scenario…
Not playable in the current state.
> 2533274885445659;2:
> Middle men. It’s part of Microsoft’s archaic “certification” process for consoles. They would get a much better turnaround on patches by releasing betas like many developers do on Steam allowing players to help do QA on future patches.
>
> We can point this out but don’t expect the system to change anytime soon. There are too many people who would lose their jobs.
The process is detrimental to the games health, We have to wait 2 weeks(ish) for a patch that may end messing up the game up even further (like the day 3 patch).
90% of devs use PC as a testing platform for patches, Were waiting for a patch that may make things worse lol instead of just dumping it off pc to find out if it actually fixes anything then paving the way for the console release.
Microsoft is the only console to release games that could end up unplayable for the first 2 weeks, Do they release games in worse states than any other triple A dev…Nope, they just dont have the capability to patch those games in a reasonable time frame.
There was a Day One patch was for the Xbox One, but the patch a few days after for PC was essentially the same thing - it was the Day One PC patch it was just released a little later.
The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc. It’s not something I see MS giving up, nor something I think should be taken out of the mix. My understanding is that it’s like a series of checklists and if everything passes it gets released. 343 will have their own Q/A team that will do final testing before certification. If for any reason new bugs come to light or it fails, that can delay it for a little while longer.
The last thing you want to do is just dump a bunch of code out into the wild and hope for the best, I don’t know of any sane developer that would do that.
The nature of software development can be a cruel world - I live it daily myself. Fixing bugs within certain time sometimes just isn’t possible. Like there are a few things in my own work right now that we’d love to to push on with, but out standing issues with other libraries (React Router / Redux / TypeScript) hold us back. There are bugs out there that can be over 10 years old and still not fixed. We all wish it were easier, we’re just not there yet.
No offense, but other developers (Valve for example) almost always fix any “gamebreaking” bug within 24 hours on dota 2. I know it’s your job to defend 343i, but you have to appreciate the players that are here and the position they’re in. We have had no solid news in days (nearly weeks) - oh, apart from that dlc is expected every 3rd Wednesday of the month. DLC? when the game doesn’t even work? Where are the priorities? For those of us who spent more to pre-order the game it has been 2.5 weeks since launch with these same issues. 17 days, with only two official posts from the development team about progress.
In all honesty, I am beyond angry, I feel completely let down by 343i. The online community will likely never recover and the game will be left as a carcass. The low population on PC will be used as a reason not to bring future titles to the platform, or not support them when they do, and everyone loses out. I am personally giving it 1 more week before I get a refund, but I am not hopeful.
RIP Halo Wars 2. 17/02/2017 - 17/02/2017.
> 2533274813317074;6:
> There was a Day One patch was for the Xbox One, but the patch a few days after for PC was essentially the same thing - it was the Day One PC patch it was just released a little later.
>
> The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc. It’s not something I see MS giving up, nor something I think should be taken out of the mix. My understanding is that it’s like a series of checklists and if everything passes it gets released. 343 will have their own Q/A team that will do final testing before certification. If for any reason new bugs come to light or it fails, that can delay it for a little while longer.
>
> The last thing you want to do is just dump a bunch of code out into the wild and hope for the best, I don’t know of any sane developer that would do that.
>
> The nature of software development can be a cruel world - I live it daily myself. Fixing bugs within certain time sometimes just isn’t possible. Like there are a few things in my own work right now that we’d love to to push on with, but out standing issues with other libraries (React Router / Redux / TypeScript) hold us back. There are bugs out there that can be over 10 years old and still not fixed. We all wish it were easier, we’re just not there yet.
Appreciate the response.
Im gonna quote you here, “The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc.”
The day 1 patch did everything the “certification process” is supposed to prevent lol.
> 2533274885738925;8:
> > 2533274813317074;6:
> > There was a Day One patch was for the Xbox One, but the patch a few days after for PC was essentially the same thing - it was the Day One PC patch it was just released a little later.
> >
> > The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc. It’s not something I see MS giving up, nor something I think should be taken out of the mix. My understanding is that it’s like a series of checklists and if everything passes it gets released. 343 will have their own Q/A team that will do final testing before certification. If for any reason new bugs come to light or it fails, that can delay it for a little while longer.
> >
> > The last thing you want to do is just dump a bunch of code out into the wild and hope for the best, I don’t know of any sane developer that would do that.
> >
> > The nature of software development can be a cruel world - I live it daily myself. Fixing bugs within certain time sometimes just isn’t possible. Like there are a few things in my own work right now that we’d love to to push on with, but out standing issues with other libraries (React Router / Redux / TypeScript) hold us back. There are bugs out there that can be over 10 years old and still not fixed. We all wish it were easier, we’re just not there yet.
>
> Appreciate the response.
>
> Im gonna quote you here, “The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc.”
>
> The day 1 patch did everything the “certification process” is supposed to prevent lol.
Bullcrap.
Read about the process. Its to prevent damage or security concerns with the console. This did not brick your console.
> 2533274852578016;7:
> I know it’s your job to defend 343i
It’s not, my job here is to keep the forums clean. There’s decisions 343 have made that I haven’t been happy about and I have voiced my concerns on those in the past, I just try to stay as neutral as possible (wherever possible) when I post. I can understand from the customers POV totally, but I’ve had a history of Tech Support and Software / Web Dev so I kinda understand a bit more what goes on behind the scenes and why things are as they are.
> 2533274846171508;9:
> > 2533274885738925;8:
> > > 2533274813317074;6:
> > > There was a Day One patch was for the Xbox One, but the patch a few days after for PC was essentially the same thing - it was the Day One PC patch it was just released a little later.
> > >
> > > The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc. It’s not something I see MS giving up, nor something I think should be taken out of the mix. My understanding is that it’s like a series of checklists and if everything passes it gets released. 343 will have their own Q/A team that will do final testing before certification. If for any reason new bugs come to light or it fails, that can delay it for a little while longer.
> > >
> > > The last thing you want to do is just dump a bunch of code out into the wild and hope for the best, I don’t know of any sane developer that would do that.
> > >
> > > The nature of software development can be a cruel world - I live it daily myself. Fixing bugs within certain time sometimes just isn’t possible. Like there are a few things in my own work right now that we’d love to to push on with, but out standing issues with other libraries (React Router / Redux / TypeScript) hold us back. There are bugs out there that can be over 10 years old and still not fixed. We all wish it were easier, we’re just not there yet.
> >
> > Appreciate the response.
> >
> > Im gonna quote you here, “The certification process is in place to make sure that any patches or updates released won’t adversely affect the console in any way - cause it to crash, etc.”
> >
> > The day 1 patch did everything the “certification process” is supposed to prevent lol.
>
> Bullcrap.
>
> Read about the process. Its to prevent damage or security concerns with the console. This did not brick your console.
Ok so whats the point of having a “Windows Certification” process again?
To prevent harm to my pc? lol.
We dont need this silly wall that assures nothing at the end of the day because it clearly did jack -Yoink- for the day 1 patch.All its doing now is preventing the devs from rolling out a working patch.
> 2533274885738925;11:
> Ok so whats the point of having a “Windows Certification” process again?
>
> To prevent harm to my pc? lol.
>
> We dont need this silly wall that assures nothing at the end of the day because it clearly did jack -Yoink- for the day 1 patch.All its doing now is preventing the devs from rolling out a working patch.
It’s doing a lot more than that. Trust me when I say that policies lkike this are vital in shipping stable software. I’m working on a large scale project right now, not Halo scale, but we have pretty in-depth measures being put in place to ensure that code committed will be tested, peered and signed off before being merged and a while host of other things before a release even gets near the door.
Everyone would love to have their game fixed in 5 minutes, i’m pretty sure everyone at Createive Assembly and 343 would love to have this shipped, but it’s just not as simple mashing the keyboard and throwing a patch into the wild. You want a stable game? You need to be patient
> 2533274813317074;12:
> > 2533274885738925;11:
> > Ok so whats the point of having a “Windows Certification” process again?
> >
> > To prevent harm to my pc? lol.
> >
> > We dont need this silly wall that assures nothing at the end of the day because it clearly did jack -Yoink- for the day 1 patch.All its doing now is preventing the devs from rolling out a working patch.
>
> It’s doing a lot more than that. Trust me when I say that policies lkike this are vital in shipping stable software. I’m working on a large scale project right now, not Halo scale, but we have pretty in-depth measures being put in place to ensure that code committed will be tested, peered and signed off before being merged and a while host of other things before a release even gets near the door.
>
> Everyone would love to have their game fixed in 5 minutes, i’m pretty sure everyone at Createive Assembly and 343 would love to have this shipped, but it’s just not as simple mashing the keyboard and throwing a patch into the wild. You want a stable game? You need to be patient
Developers compile the patch, Test the patch (to the best of theyre ability), Roll it out…
The certification system used here is obsolete on the pc, Steam has been allowing Devs to compile/test then roll out theyre own patches since its inception. This treating windows like a closed system thing is only pushing people away from investing in the microsoft store ( i know i have buyers remorse).
Everyday that passes without these game breaking issues being addressed are just leading to negative store reviews piling up and more and more people forgetting they even own this game.
If this were steam this game would have been patched on Feb 27th (the day the patch was ready).
No it wouldn’t. The patch hasn’t been ready since the 27th, this one incorporates issues that have cropped up since he game was released. You cant patch something that hasn’t even been reported yet 