Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
MurderMostFoul wrote: »ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
Here's to hoping the range bug, the set bonus bug, the companion item lost bug, and any other new bugs I'm forgetting are all included in this incremental as well
ZOS_GinaBruno wrote: »We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
BlakMarket wrote: »Honestly this is crazy I changed two toons from nord to imperial because of sustain issues, to realize it was a BUG!!!!!!!! Who would I speak to, to get a refund of race change tokens.
MurderMostFoul wrote: »ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
Here's to hoping the range bug, the set bonus bug, the companion item lost bug, and any other new bugs I'm forgetting are all included in this incremental as well
ZOS_GinaBruno wrote: »MurderMostFoul wrote: »ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
Here's to hoping the range bug, the set bonus bug, the companion item lost bug, and any other new bugs I'm forgetting are all included in this incremental as well
The range bug and set bonus bug should also be fixed in the first incremental. The Companion item loss bug was actually able to be hotfixed with launch so that shouldn't be an issue.
ZOS_GinaBruno wrote: »MurderMostFoul wrote: »ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
Here's to hoping the range bug, the set bonus bug, the companion item lost bug, and any other new bugs I'm forgetting are all included in this incremental as well
The range bug and set bonus bug should also be fixed in the first incremental. The Companion item loss bug was actually able to be hotfixed with launch so that shouldn't be an issue.
ZOS_JessicaFolsom wrote: »BlakMarket wrote: »Honestly this is crazy I changed two toons from nord to imperial because of sustain issues, to realize it was a BUG!!!!!!!! Who would I speak to, to get a refund of race change tokens.
Hey @BlakMarket our Support team should be able to help you out with this. I'm checking on what ticket category they'd recommend you use. Are you also looking to switch your characters back to their original races?
Calypso589 wrote: »@ZOS_GinaBruno Love you for putting up with what you do. So much ignorance in here. Yeesh.
I hope the studio has a rage room. :P
Here's your new car... we know the brakes don't work, but we will fix that in the next inspection. Enjoy!
When did it become ok to knowingly release broken products?
Postpone the release and release it with the fix... Not knowingly break a whole class, and just release anyways?
So what are tanks now supposed to do, not block? In vet dungeons and trials?
Or are they not supposed to play for a few weeks?
This is just totally not acceptable...
ZOS_GinaBruno wrote: »Texecutioner187 wrote: »ZOS_GinaBruno wrote: »Dabulousness wrote: »When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?
As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
Thank you. When is that incremental scheduled?
We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
katanagirl1 wrote: »They said something about a console incremental patch, lol I didn’t think we even had those.
<snip>
While I realize from 7 to 8 there's not enough time to push a build... 5 days to fix a gamebreaking bug like this (hitting PVP and PVE alike) might tip not enough effort/skills into it.
And proceeding with the launch despite this... i hope you realize how players feels: like the passengers of a ship (ESO) that is KNOWN to have issues but the commander (ZOS) sails anyway because else he'd have to refund some ticket (Blackwood chapter) due to delay of launch-date and pre-orders.
If you KNOW consoles especially have to cope with wathever you push live for at least 2 weeks... you should be VERY sure that wathever you push is working, at the very least, in its core functions (we can cope some inventory bug but if you mess up the combat you mess up too deep).
<snip>
<snip>
While I realize from 7 to 8 there's not enough time to push a build... 5 days to fix a gamebreaking bug like this (hitting PVP and PVE alike) might tip not enough effort/skills into it.
And proceeding with the launch despite this... i hope you realize how players feels: like the passengers of a ship (ESO) that is KNOWN to have issues but the commander (ZOS) sails anyway because else he'd have to refund some ticket (Blackwood chapter) due to delay of launch-date and pre-orders.
If you KNOW consoles especially have to cope with wathever you push live for at least 2 weeks... you should be VERY sure that wathever you push is working, at the very least, in its core functions (we can cope some inventory bug but if you mess up the combat you mess up too deep).
<snip>
What you may be unaware of is that console patches have to be vetted by Sony and Microsoft. This is a long and painful process. There are no hotfixes in this realm. Once they get the approval to go on a patch, that's all they are allowed to push live. So if they find something after that build has gone for approval, they have to wait. That's just the proceedure for console.
katanagirl1 wrote: »They said something about a console incremental patch, lol I didn’t think we even had those.
This is not fixed in the stone but generally i noticed this:
We get 1 mainteance/week when servers stops, updates and reboot. This is a server-side incremental patch, does not require you to download anything, whatever can be fixed server-side excusively can be fixed here but NOT if the fix includes changes in the client.
Every 2 weeks or so we get to DL a client update in our system too. This is a client and server side incremental patch where both are updated. Note that Sony, as many others, will not allow a software house to push too many builds in a restricted amount of time. On very rare occasions ttho Sony might DEMAND a fix in a shourter amount of time tho: remember what happened whem, couple patches ago, the game was crashing every 10 minutes on bluescreen?
Many ppl used the build-in error reporting tool (alas available only for "bluescreens") so Sony been covered with those and FORCED ZoS to patch that before the usual amount of time (a game making user unhappy is a game ppl might ask refund for, Sony as any other company does not like when this happens and they might even decide to remove a game from the store in extreme cases).
I believe 2 weeks is, pretty much, the time required to push a build, get it accepted etc. this can't be hastened by ZoS in any way (but could be prevented by not pushing live a build containing known major bugs)
katanagirl1 wrote: »<snip>
Yes, it would be nice if they could postpone the update for us when there are known major bugs, but my experience in software programming is that the people who make the decisions (the managers) see nothing wrong with patching it later because they view a schedule slip as the worst thing in the world. It is unfortunate but the way it is.
katanagirl1 wrote: »katanagirl1 wrote: »They said something about a console incremental patch, lol I didn’t think we even had those.
This is not fixed in the stone but generally i noticed this:
We get 1 mainteance/week when servers stops, updates and reboot. This is a server-side incremental patch, does not require you to download anything, whatever can be fixed server-side excusively can be fixed here but NOT if the fix includes changes in the client.
Every 2 weeks or so we get to DL a client update in our system too. This is a client and server side incremental patch where both are updated. Note that Sony, as many others, will not allow a software house to push too many builds in a restricted amount of time. On very rare occasions ttho Sony might DEMAND a fix in a shourter amount of time tho: remember what happened whem, couple patches ago, the game was crashing every 10 minutes on bluescreen?
Many ppl used the build-in error reporting tool (alas available only for "bluescreens") so Sony been covered with those and FORCED ZoS to patch that before the usual amount of time (a game making user unhappy is a game ppl might ask refund for, Sony as any other company does not like when this happens and they might even decide to remove a game from the store in extreme cases).
I believe 2 weeks is, pretty much, the time required to push a build, get it accepted etc. this can't be hastened by ZoS in any way (but could be prevented by not pushing live a build containing known major bugs)
Many console players say they don’t bother reporting, but I do. Even if I get booted in the middle of a siege and want to get back hopefully before the AP tick, I put one in. Like you said, if it’s a game freeze you don’t have that option and have to close app and restart.
Good for Sony to look out for us on that one.
Yes, it would be nice if they could postpone the update for us when there are known major bugs, but my experience in software programming is that the people who make the decisions (the managers) see nothing wrong with patching it later because they view a schedule slip as the worst thing in the world. It is unfortunate but the way it is.