Andrew Johnson @untdrew We've released a small patch for @anthemgame today (1.6.1). This will not require any server downtime, so once you download, you should be able to jump back in and play immediately.
You should have a prompt to download a new patch today (1.6.1). This will not require any server downtime, so once you download, you should be able to jump back in and play immediately. If you're currently in a session, you will need to exit the game, download the patch and then start the game again.
Here is what was addressed in the patch:
Fixed a couple of instances in the Icetide Freeplay events that could cause crashes for some players.
I gotta give them credit for understatement … "a couple of instances … that could cause crashes for *some* players."
At least on PC, from folks I've spoken with, it was a bit more than some …
And while it may be "a couple of things" causing the problem … it pretty much could occur at any time, at any place in Bastion.
But props to BioWare … they got this out in under a week … previously, it took longer.
Now if they could just improve QA.
Edit add: recommend doing a game repair after the patch finishes installing … may be superstitious behavior on my part …
But it won't hurt and it's one of the first things tech support will suggest doing if you have issues later.
THis has been adresse dbefore. Even if they make little changes to a lot of files, they need to replace the whole file. That's why pathces are so big.
Good on them, I suppose.
There was a time when patches simply replaced some bad code... from a few bytes to hundreds of bytes of code. The System Programmer applied the patch to the program module and voilà.
Unfortunately, patches grew in numbers and everything got complicated. Patches needed to know if pre-requisit patches were already applied and sometimes if co-requisites ones were installed. Imagine maintaining and tracking these balkanized patched programs.
Re-compiling the fixed program at the source and sending out the "fixed file" is less complicated for the client.
Morpheus: "know what happened happened and that it could not have happened in any other way".
Interesting. Obviously, the point I was making was lost.
A failure between what I was saying in my head and how it was interpreted when others read it.
Other than listing the size of the patch in the first line, none of my comments refered to patch size.
By today's standards, it's a pretty small patch.
My comments were directed at the notion that the game crashes only impacted "some" people … which struck me as an understatement.
Regardless, played a fair amount of freeplay last night, trying to trigger a game crash in ways that seemed to be an issue prior to the patch.
Other than one server disconnect … which didn't require a game reboot … the game was stable through several world events, races, transitions from one zone to another, scoring additional wreaths … all things that occurred in close proximity (time-wise) to a game crash pre-patch.
Interesting. Obviously, the point I was making was lost.
A failure between what I was saying in my head and how it was interpreted when others read it.
Other than listing the size of the patch in the first line, none of my comments refered to patch size.
By today's standards, it's a pretty small patch.
My comments were directed at the notion that the game crashes only impacted "some" people … which struck me as an understatement.
Regardless, played a fair amount of freeplay last night, trying to trigger a game crash in ways that seemed to be an issue prior to the patch.
Other than one server disconnect … which didn't require a game reboot … the game was stable through several world events, races, transitions from one zone to another, scoring additional wreaths … all things that occurred in close proximity (time-wise) to a game crash pre-patch.
My comment was in response to Pilar on the need to replace the whole file after many "little patches" and the 'repair' option that support would inevitably mention.
The "There was a time" was a reflection on my experience as a System Programmer with IBM's OS. The number of patches and their dependencies among the many online systems became
so complex that it forced them to develop an automated tool to apply any patch or unpatch, as the case may be ... which also was complex and difficult to understand.
Let's hope Bio can come up with Anthem 2.0 with a minimum of fuss.
Morpheus: "know what happened happened and that it could not have happened in any other way".
Interesting. Obviously, the point I was making was lost.
A failure between what I was saying in my head and how it was interpreted when others read it.
Other than listing the size of the patch in the first line, none of my comments refered to patch size.
By today's standards, it's a pretty small patch.
My comments were directed at the notion that the game crashes only impacted "some" people … which struck me as an understatement.
Regardless, played a fair amount of freeplay last night, trying to trigger a game crash in ways that seemed to be an issue prior to the patch.
Other than one server disconnect … which didn't require a game reboot … the game was stable through several world events, races, transitions from one zone to another, scoring additional wreaths … all things that occurred in close proximity (time-wise) to a game crash pre-patch.
My comment was in response to Pilar on the need to replace the whole file after many "little patches" and the 'repair' option that support would inevitably mention.
The "There was a time" was a reflection on my experience as a System Programmer with IBM's OS. The number of patches and their dependencies among the many online systems became
so complex that it forced them to develop an automated tool to apply any patch or unpatch, as the case may be ... which also was complex and difficult to understand.
Let's hope Bio can come up with Anthem 2.0 with a minimum of fuss.
I don't know how long ago that job experience was, but in general: the world is more complex now, so why wouldn't something such as patching be as well?
Hello everyone! Just wanted to drop an update on some changes that we made today for Icetide.
Earlier today we pushed a change that was intended to fix an issue with the tracking for the "Bonus Objectives" and "Targets Destroyed" objectives in the Icetide challenges. Essentially there was an issue with the data that affected the tracking and today's change was intended to correct that to show your correct progress. However this change had some unintended side effects on the live servers that changed objective progress for some of you.
To fix this we will be disabling the challenge and resetting it to put players back in a state where they can earn progress again, you’ll see the challenge temporarily change to be listed as “???”. This should be happening soon. We know it doesn't feel good that your progress wasn't counted and we want to reward you for the progress you should've had, as well as give you the actual chance to still earn the Icetide challenges. We apologize if this confused or frustrated some of you.
As soon as we have any additional updates they will be edited into this post to keep you all updated.
Hello everyone! Just wanted to drop an update on some changes that we made today for Icetide.
Earlier today we pushed a change that was intended to fix an issue with the tracking for the "Bonus Objectives" and "Targets Destroyed" objectives in the Icetide challenges. Essentially there was an issue with the data that affected the tracking and today's change was intended to correct that to show your correct progress. However this change had some unintended side effects on the live servers that changed objective progress for some of you.
To fix this we will be disabling the challenge and resetting it to put players back in a state where they can earn progress again, you’ll see the challenge temporarily change to be listed as “???”. This should be happening soon. We know it doesn't feel good that your progress wasn't counted and we want to reward you for the progress you should've had, as well as give you the actual chance to still earn the Icetide challenges. We apologize if this confused or frustrated some of you.
As soon as we have any additional updates they will be edited into this post to keep you all updated.
-Anthem Community Team
Literally every patch you've done up until today has created new issues. Fire your whole QA crew, Fire your coding crew, and hire some compentent monkeys.
Anthem @anthemgame Nothing says "the holidays" like a cozy place to sit, your favourite show, a hot drink in hand, and someone constantly interrupting you while you try to relax. That's Haluk for you. Read up on the first Icetide story, Songs of Icetide. www.ea.com/games/anthem/news/lore-songs-of-icetide
Hello everyone! Just wanted to drop an update on some changes that we made today for Icetide.
Earlier today we pushed a change that was intended to fix an issue with the tracking for the "Bonus Objectives" and "Targets Destroyed" objectives in the Icetide challenges. Essentially there was an issue with the data that affected the tracking and today's change was intended to correct that to show your correct progress. However this change had some unintended side effects on the live servers that changed objective progress for some of you.
To fix this we will be disabling the challenge and resetting it to put players back in a state where they can earn progress again, you’ll see the challenge temporarily change to be listed as “???”. This should be happening soon. We know it doesn't feel good that your progress wasn't counted and we want to reward you for the progress you should've had, as well as give you the actual chance to still earn the Icetide challenges. We apologize if this confused or frustrated some of you.
As soon as we have any additional updates they will be edited into this post to keep you all updated.
-Anthem Community Team
Literally every patch you've done up until today has created new issues. Fire your whole QA crew, Fire your coding crew, and hire some compentent monkeys.
"...Fire your whole QA crew,..."
Hm...
QA's responsibility is to check for inaccuracies, bugs... etc and report them to mgt. Mgt. then decides what to prioritize and what to put in the back burner or simply drop it. Obviously "show stopping bugs" get put in the active debugging queue.... even get moved to the front of the queue. In other words, QA can report Show Stoppers, High, Medium and Low ones.
Remember, cost, time and resources come into play (when making a decision) including customer impact of course. That is my experience working next door with the banking application QA dept. Bio, may have different policies that regulate QA findings.
Bottom line, QA has no control on what must be debugged.... only to report.
Also: I would imagine the cascading bug problems has a lot to do with the existing code structure and the fact that it wasn't written/debugged well enough. There's probably also a number of intertwining mechanics that are leading to alot of conflicts as well.
Literally every patch you've done up until today has created new issues. Fire your whole QA crew, Fire your coding crew, and hire some compentent monkeys.
"...Fire your whole QA crew,..."
Hm...
QA's responsibility is to check for inaccuracies, bugs... etc and report them to mgt. Mgt. then decides what to prioritize and what to put in the back burner or simply drop it. Obviously "show stopping bugs" get put in the active debugging queue.... even get moved to the front of the queue. In other words, QA can report Show Stoppers, High, Medium and Low ones.
Remember, cost, time and resources come into play (when making a decision) including customer impact of course. That is my experience working next door with the banking application QA dept. Bio, may have different policies that regulate QA findings.
Bottom line, QA has no control on what must be debugged.... only to report.
I have worked as QA, and for the rest of my carreer has dealt with QA people in some form or other.
I can tell you, QA usually knows diddly squat about the subject matter. QA is usually young unexperienced people, which leave after abotu a year or 2, 3 when they finally begin to understand what their job is about. QA has literally zero effective stopping power in a company. They are a showpiece.
QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project. Furthermore, any fault QA find is immediately scrutinised with: "yeah, but do you know how much it costs to fix that?", so the fault isn't fixed at all anyway.
QA's responsibility is to check for inaccuracies, bugs... etc and report them to mgt. Mgt. then decides what to prioritize and what to put in the back burner or simply drop it. Obviously "show stopping bugs" get put in the active debugging queue.... even get moved to the front of the queue. In other words, QA can report Show Stoppers, High, Medium and Low ones.
Remember, cost, time and resources come into play (when making a decision) including customer impact of course. That is my experience working next door with the banking application QA dept. Bio, may have different policies that regulate QA findings.
Bottom line, QA has no control on what must be debugged.... only to report.
I have worked as QA, and for the rest of my carreer has dealt with QA people in some form or other.
I can tell you, QA usually knows diddly squat about the subject matter. QA is usually young unexperienced people, which leave after abotu a year or 2, 3 when they finally begin to understand what their job is about. QA has literally zero effective stopping power in a company. They are a showpiece.
QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project. Furthermore, any fault QA find is immediately scrutinised with: "yeah, but do you know how much it costs to fix that?", so the fault isn't fixed at all anyway.
My bottom line is: Even QA reporting is a joke.
I am working as senior QA for gametesting mainly and before worked with QA a lot. I've worked on QA for several high profile games you people have played. I'd say it depends on the company a lot what you'll know and how deep is the participation from the beginning.. at least from those points
"QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project." - In my mind the mistake has been already made, and of course now depends on what kind of QA are we talking about also, if the QA hasnt been with the project from the beginning.
So QA reporting can be a "joke", if the integration hasnt been started early enough, the people deciding dont understand the issues or their severity etc.
Its not a simple thing and we can guess how it goes in several places as we dont know... Sometimes blockers are in the final released product without patching it... this is just life as I know it, but they will be patched off at least for what I've worked.
[ LegendCNCD / AsariLoverFI ] Waiting for ME5 - Look's like sometime in 2186, everything went to hell. We got out just ahead of it! MEA & ME1 (>>>> 3 > 2) -- DAI > DAO > DA2 -- 3500h+ & maxed out all 02/2020 in MEAMP, APEX 137001+, DAIMP (557/726/200), ANTHEM, SW BF II - Drinking tears of MP lamers since DooM & Quake in 90's softknees.bandcamp.com/ Go go go! I will destroy you! Watch out! Enemies everywhere! You must die!
I have worked as QA, and for the rest of my carreer has dealt with QA people in some form or other.
I can tell you, QA usually knows diddly squat about the subject matter. QA is usually young unexperienced people, which leave after abotu a year or 2, 3 when they finally begin to understand what their job is about. QA has literally zero effective stopping power in a company. They are a showpiece.
QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project. Furthermore, any fault QA find is immediately scrutinised with: "yeah, but do you know how much it costs to fix that?", so the fault isn't fixed at all anyway.
My bottom line is: Even QA reporting is a joke.
I am working as senior QA for gametesting mainly and before worked with QA a lot. I've worked on QA for several high profile games you people have played. I'd say it depends on the company a lot what you'll know and how deep is the participation from the beginning.. at least from those points
"QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project." - In my mind the mistake has been already made, and of course now depends on what kind of QA are we talking about also, if the QA hasnt been with the project from the beginning.
So QA reporting can be a "joke", if the integration hasnt been started early enough, the people deciding dont understand the issues or their severity etc.
Its not a simple thing and we can guess how it goes in several places as we dont know... Sometimes blockers are in the final released product without patching it... this is just life as I know it, but they will be patched off at least for what I've worked.
Unfortunate and interesting.
At the Workers' Compensation Board, QA was trained on the specific application(s) and were given scripts to check. Let's hope Bio learned from past lessons.
Morpheus: "know what happened happened and that it could not have happened in any other way".
I am working as senior QA for gametesting mainly and before worked with QA a lot. I've worked on QA for several high profile games you people have played. I'd say it depends on the company a lot what you'll know and how deep is the participation from the beginning.. at least from those points
"QA is in 90% of the cases simply not qualified to find, stop or fix an mistakes / bugs made in the earlier phases of the project." - In my mind the mistake has been already made, and of course now depends on what kind of QA are we talking about also, if the QA hasnt been with the project from the beginning.
So QA reporting can be a "joke", if the integration hasnt been started early enough, the people deciding dont understand the issues or their severity etc.
Its not a simple thing and we can guess how it goes in several places as we dont know... Sometimes blockers are in the final released product without patching it... this is just life as I know it, but they will be patched off at least for what I've worked.
Unfortunate and interesting.
At the Workers' Compensation Board, QA was trained on the specific application(s) and were given scripts to check. Let's hope Bio learned from past lessons.
We can just speculate and guess for real, and even from project to project the points of entry for QA change a lot and of course scopes, responsibilities and deadlines. This is why I would not try to "guess for a fact" anything happening inside from organization to another.
[ LegendCNCD / AsariLoverFI ] Waiting for ME5 - Look's like sometime in 2186, everything went to hell. We got out just ahead of it! MEA & ME1 (>>>> 3 > 2) -- DAI > DAO > DA2 -- 3500h+ & maxed out all 02/2020 in MEAMP, APEX 137001+, DAIMP (557/726/200), ANTHEM, SW BF II - Drinking tears of MP lamers since DooM & Quake in 90's softknees.bandcamp.com/ Go go go! I will destroy you! Watch out! Enemies everywhere! You must die!