over 2 years ago - /u/thearcan - Direct link

Hello everyone,

Welcome to another Dev News Thursday.

https://preview.redd.it/n1gxzxlg3kf71.png?width=2058&format=png&auto=webp&s=53714f1a3648bf2e0fa5c3df1af0725a7db96292

Patch News:

  • We know that you were hoping for a patch release today. We were hoping for it too. Unfortunately, due to the ongoing crash-on-boot issue that is continuing to block this release, the latest patch will not be arriving this week.
  • As our investigation into the crash issue has progressed, we have implemented a number of targeted hot fixes onto the latest patch build but they have proved ineffectual against the issue we’re focusing on in particular. Each Hotfix itself can take a couple days to be developed, cooked and tested and our teams have continued to work tirelessly, including over the past weekend (and work may well continue through this upcoming weekend).
  • Our greatest challenge here is the fact that the crash issue is inconsistent. Only certain PCs appear affected by it and those not even consistently. Without a pattern, it is very hard to understand the trigger and fix against that.
  • However, yesterday we did make some strides towards unlocking further crash logs, something which has been difficult so far. These crash logs give us hope and ideas for further hot fixes to resolve the issue. We are taking today and tomorrow to build and test a few new hotfixes against these particular logs.
  • Should these hotfixes prove effective, we could be in a position to release the patch early next week, but this is a very tentative hope. Only today, tomorrow and this weekend's further testing will be able to further confirm that.
  • We know this is going to be disappointing to read, however, we do not want to release a patch that potentially destabilises the game further and is detrimental to your experience. We will only want to release the patch once we are fully satisfied that it would benefit players and build on the progress we have made on the game since launch.

General News:

  • Stuck at 99% Accolade Progress - RESOLUTION

    • We are today deploying a server-side fix that is aimed at automatically healing accounts whereby players might their overall accolade progress stuck at 99%. No maintenance is required for this fix to go live.
    • If you've encountered this issue, please do login and check to see if it has helped!
  • The below news is similar to last week’s general news, but as it continues to be relevant, we are including it here again.

  • We’re really looking forward to getting this patch out to you and seeing what kind of fun you can get up to with the new build options!

  • Once this current raft of announced changes have been in play for a short while, we will also be taking a look at the most underused Legendary sets in the game and seeing what we can do to make them more viable.

  • One final note in closing: The delay of a patch such as this does not materially affect any of the work, fixes and QOL improvements we have planned for the future. Those are still coming and will be discussed publicly when we have a proper date for their release.

Ongoing list of currently tracked issues:

Note 1: This is not an exhaustive list of things being worked upon. This is also not a list of patch notes for the next patch. Upcoming patches will address issues that may not be listed here.

Note 2: “Investigated” means that we have been able to successfully reproduce an issue on our dev environment and are currently looking at the root causes of said issue. If we have not yet been able to reproduce a specific issue, it may not be listed here, but that doesn’t mean we’re unaware of it.

  • State of Stadia
    • Stadia still needs to be brought in line with other platforms with regards to fixes, bug resolutions and crossplay support.
    • We are continuing to do this work on aligning all platforms, but do not yet have a definite date for when this will be possible.
    • We appreciate that this work is taking longer than expected and do apologize for this.
  • Matchmaking privacy settings may set themselves to Open without input from the player
    • Issue being investigated and will be resolved in a future patch
  • Xbox problems related to signing in
    • Our latest patch significantly increased Xbox sign in times for the vast majority of players. However, a small number of players appear to be affected by a secondary issue, which can cause them to do "alternative account sign in" workarounds.
    • We are investigating this matter and are in touch with a few affected users to investigate their accounts in order to identify the issue
  • Mods and Resources may be lost
    • This issue appears to be quite rare, making it very hard for us to reproduce it and identify it's cause.
    • For anyone affected by this, we recommend getting in touch with our Square Enix Support Team (sqex.to/support), who now have appropriate tools to be able to grant you specific mods and resources that you may have lost. Our support team will also be able to gather the appropriate information to aid us in our investigation.
  • Sprinting with your Sprint option set to Hold (instead of Toggle) may cause the player character to drift to the side
    • Issue being investigated
  • Entering the drained lake during the third enemy encounter in the Scorched Lands Expedition can cause client players to stutter
    • Issue currently being investigated and will be resolved in a future patch
  • Certain enemies, especially Alphas, may break out of Frozen CC as soon as they are damaged
    • Issue being investigated
  • Game stutters when multiple Crawlers are on screen, in particular during certain Expeditions
    • Issue currently being investigated and will be resolved in a future patch
  • Certain Mods not working (properly or consistently), in particular when you’re the client during multiplayer sessions
    • Issue under review following multiplayer improvements
  • Grand Opening Mod (and other mods) may not activate when a player uses their last magazine
    • Issue currently being investigated and will be resolved in a future patch
  • Using the Tier 3 Armor Mod "Pain Transfer" with either the Tier 2 or the Tier 3 "Damage Link" mod drastically reduces framerate.
    • Issue being investigated
  • Tricksters may be unable to revive others or be revived themselves in Multiplayer if using Borrowed Time in Expeditions
    • Issue being investigated.
  • Technomancers Plague Sower Set does not consistently apply it's bonus.
    • Issue being investigated
  • Technomancer Turrets May fall through the ground
    • Issue being investigated
    • There are a few different causes for this, including map specific areas (Mountain Outpost) as well as circumstance specific (such as aiming too closely at your own feet).
  • Journal entries/pick ups not appearing on secondary characters
    • Issue being reinvestigated
  • “Damage Blocked” Stat on Expeditions results screen occasionally appears inconsistently or abnormally low
    • Issue currently being investigated
  • A cutscene during the "The Mentor" Questline may not trigger, meaning players cannot progress past this point
    • Issue currently being investigated
    • Temporary Workaround: In your lobby, change your story checkpoint to an earlier one, then re-attempt this quest.

Recent Informative Dev Reddit Comments & Threads:

Other Helpful links:

External link →
over 2 years ago - /u/thearcan - Direct link

Hello everyone,

Welcome to another Dev News Thursday.

https://preview.redd.it/n1gxzxlg3kf71.png?width=2058&format=png&auto=webp&s=53714f1a3648bf2e0fa5c3df1af0725a7db96292

Patch News:

  • We know that you were hoping for a patch release today. We were hoping for it too. Unfortunately, due to the ongoing crash-on-boot issue that is continuing to block this release, the latest patch will not be arriving this week.
  • As our investigation into the crash issue has progressed, we have implemented a number of targeted hot fixes onto the latest patch build but they have proved ineffectual against the issue we’re focusing on in particular. Each Hotfix itself can take a couple days to be developed, cooked and tested and our teams have continued to work tirelessly, including over the past weekend (and work may well continue through this upcoming weekend).
  • Our greatest challenge here is the fact that the crash issue is inconsistent. Only certain PCs appear affected by it and those not even consistently. Without a pattern, it is very hard to understand the trigger and fix against that.
  • However, yesterday we did make some strides towards unlocking further crash logs, something which has been difficult so far. These crash logs give us hope and ideas for further hot fixes to resolve the issue. We are taking today and tomorrow to build and test a few new hotfixes against these particular logs.
  • Should these hotfixes prove effective, we could be in a position to release the patch early next week, but this is a very tentative hope. Only today, tomorrow and this weekend's further testing will be able to further confirm that.
  • We know this is going to be disappointing to read, however, we do not want to release a patch that potentially destabilises the game further and is detrimental to your experience. We will only want to release the patch once we are fully satisfied that it would benefit players and build on the progress we have made on the game since launch.

General News:

  • Stuck at 99% Accolade Progress - RESOLUTION

    • We are today deploying a server-side fix that is aimed at automatically healing accounts whereby players might their overall accolade progress stuck at 99%. No maintenance is required for this fix to go live.
    • If you've encountered this issue, please do login and check to see if it has helped!
  • The below news is similar to last week’s general news, but as it continues to be relevant, we are including it here again.

  • We’re really looking forward to getting this patch out to you and seeing what kind of fun you can get up to with the new build options!

  • Once this current raft of announced changes have been in play for a short while, we will also be taking a look at the most underused Legendary sets in the game and seeing what we can do to make them more viable.

  • One final note in closing: The delay of a patch such as this does not materially affect any of the work, fixes and QOL improvements we have planned for the future. Those are still coming and will be discussed publicly when we have a proper date for their release.

Ongoing list of currently tracked issues:

Note 1: This is not an exhaustive list of things being worked upon. This is also not a list of patch notes for the next patch. Upcoming patches will address issues that may not be listed here.

Note 2: “Investigated” means that we have been able to successfully reproduce an issue on our dev environment and are currently looking at the root causes of said issue. If we have not yet been able to reproduce a specific issue, it may not be listed here, but that doesn’t mean we’re unaware of it.

  • State of Stadia
    • Stadia still needs to be brought in line with other platforms with regards to fixes, bug resolutions and crossplay support.
    • We are continuing to do this work on aligning all platforms, but do not yet have a definite date for when this will be possible.
    • We appreciate that this work is taking longer than expected and do apologize for this.
  • Matchmaking privacy settings may set themselves to Open without input from the player
    • Issue being investigated and will be resolved in a future patch
  • Xbox problems related to signing in
    • Our latest patch significantly increased Xbox sign in times for the vast majority of players. However, a small number of players appear to be affected by a secondary issue, which can cause them to do "alternative account sign in" workarounds.
    • We are investigating this matter and are in touch with a few affected users to investigate their accounts in order to identify the issue
  • Mods and Resources may be lost
    • This issue appears to be quite rare, making it very hard for us to reproduce it and identify it's cause.
    • For anyone affected by this, we recommend getting in touch with our Square Enix Support Team (sqex.to/support), who now have appropriate tools to be able to grant you specific mods and resources that you may have lost. Our support team will also be able to gather the appropriate information to aid us in our investigation.
  • Sprinting with your Sprint option set to Hold (instead of Toggle) may cause the player character to drift to the side
    • Issue being investigated
  • Entering the drained lake during the third enemy encounter in the Scorched Lands Expedition can cause client players to stutter
    • Issue currently being investigated and will be resolved in a future patch
  • Certain enemies, especially Alphas, may break out of Frozen CC as soon as they are damaged
    • Issue being investigated
  • Game stutters when multiple Crawlers are on screen, in particular during certain Expeditions
    • Issue currently being investigated and will be resolved in a future patch
  • Certain Mods not working (properly or consistently), in particular when you’re the client during multiplayer sessions
    • Issue under review following multiplayer improvements
  • Grand Opening Mod (and other mods) may not activate when a player uses their last magazine
    • Issue currently being investigated and will be resolved in a future patch
  • Using the Tier 3 Armor Mod "Pain Transfer" with either the Tier 2 or the Tier 3 "Damage Link" mod drastically reduces framerate.
    • Issue being investigated
  • Tricksters may be unable to revive others or be revived themselves in Multiplayer if using Borrowed Time in Expeditions
    • Issue being investigated.
  • Technomancers Plague Sower Set does not consistently apply it's bonus.
    • Issue being investigated
  • Technomancer Turrets May fall through the ground
    • Issue being investigated
    • There are a few different causes for this, including map specific areas (Mountain Outpost) as well as circumstance specific (such as aiming too closely at your own feet).
  • Journal entries/pick ups not appearing on secondary characters
    • Issue being reinvestigated
  • “Damage Blocked” Stat on Expeditions results screen occasionally appears inconsistently or abnormally low
    • Issue currently being investigated
  • A cutscene during the "The Mentor" Questline may not trigger, meaning players cannot progress past this point
    • Issue currently being investigated
    • Temporary Workaround: In your lobby, change your story checkpoint to an earlier one, then re-attempt this quest.

Recent Informative Dev Reddit Comments & Threads:

Other Helpful links:

External link →
over 2 years ago - /u/thearcan - Direct link

Originally posted by Electrical-Car912

Just connected right now to see if the progression accolade is fixed but that's not the case, still at 99%.... Is it normal ?

The fix might still be taking a bit of time to deploy, so please do keep checking back over the next few hours. Please do let me know if anything changes (or doesnt).

over 2 years ago - /u/thearcan - Direct link

Originally posted by davidmako

Sorry guys but this is a joke, right?

2 1/2 weeks ago they wanted to release balance changes which some would consider a 'content update' (meaning other than bug fixes). But because they can't seem to figure what makes the game crash at launch for a few people since the last patch nobody can enjoy those balance changes. And those players with crashes still have those issues anyway.

In early April we got immediate nerfs 6-7 days after launch while there were serious issues affecting way more of the player base. But we heard the team doing balance was a different one than the one doing fixes. The balance team had a while now to work on some more balance changes, but now that update is tied to a bug fix...

I am really confused.

Some of these balancing changes require code support since they aren't just changing numbers but also how skills function - for example, the change to the Devastator's Boulderdash ability to stop the skill - they aren't something that can be done via the backend.

If the people encountering this issue were quite low, we would be less likely to let such an issue hold us hostage, but the number of players affected is greater than we are comfortable subjecting to the issue in the interest of the wider community.

over 2 years ago - /u/thearcan - Direct link

Originally posted by difractedlight

It seems like a patch should be separate from buffs. The patch would fix issues, while buffs are just changes to existing skill values. Why are they dependent on each other.

They've all been baked into the same stream at this point and the fact that the crashes were introduced in the previous patch makes splitting the current patch into "buffs" and "other stuff" very difficult at this point.

We've looked at a fair few different scenarios in order to try and support you and get you fun stuff sooner.

over 2 years ago - /u/thearcan - Direct link

Originally posted by davidmako

Sorry for my ignorance here: How can the patch for the balance update and the crash issue be baked together if the guys are still working on the latter?

The crash issue was introduced in the previous patch. The game is its form from that release is what was built upon for these patches. So all changes we've made for this current patch ultimately have the same foundation - which is the previous patch.

over 2 years ago - /u/thearcan - Direct link

Originally posted by davidmako

Thanks for trying to explain.

I can understand the necessity to figure out a fix for those players asap. But other code changes (for the balance changes as you stated) might not change anything for that issue. And while these players wait for a fix everybody else that still gives a damn is also still waiting...

The absolute need to tie those things together is the conundrum why people are frustrated. If it delays one patch a few days, whatsoever, but this could have been 2 patches weeks apart.

I responded in this thread here on a similar question from you.

But I would add that an added complication is that theoretically, we could always be only "24 hours from a green light for the patch". And to split and rebuild the patch with different content, then test is again would probably take a week. Probably longer given the different things that would have to be systematically removed from the build in order to separate things out.

If we had known that the delay would take this long, we likely would have realigned our patch strategy as early as possible, but as it stands, we're in a very difficult grey zone.

Finally, our next patches are already building upon the foundation of this current patch's status - so to significantly alter the composition of this patch could potentially lead to delays on future patches.

over 2 years ago - /u/thearcan - Direct link

Originally posted by vapoorer

Thx for the update

However what i dont understand is the game currently has the bug crash issue already.

You not releasing the patch because you dont have a fix yet for it wont change anything for the crashes but it will change all the other stuff you have added in the patch.

So why not release the patch so we can atleast get all the other stuff, while you continue to work on the fix for the crash.

I really dont see why this patch needs to be held even longer unless you guys also have not finished the other stuff too. Which is what it seems like it to me at this point.

After all one of the last patch you released had issue too and you decided not to delay it further and still released it so we can benifit from the majority of the patch..

At this point its been weeks of delay. Just release the patch so we can get all the other stuff to play with and once you have a fix for the crash do another patch.

NGL its getting a bit ridiculous that this is one of the best patchs to come and its being delayed even further again for a crash issue that is currently in the game already that wont change anything if you release the patch without that fix yet.

IDK. Getting frustrated and burnt out.

There is a chance that the continual tinkering of the code that has been required has led to further issues. Ideally it hasn't but when you have to go into the fundamental code and apply the changes that we're doing, that risk is not zero.

If we were 100% certain that the crash rate of the patch is the same as the live build, we would likely just bite the bullet.

However, as there is an outside possibility that it makes things even a little bit worse, it's not something we want to risk, especially as our previous judgement on how widespread an issue was didn't fully align with the prevalence of the issue out in the wild.

over 2 years ago - /u/thearcan - Direct link

Originally posted by Electrical-Car912

Okey thx for the answer thearcan. Will check in few hours and reply here.

if you still dont have any luck in a few hours, please do DM me your gamertag and then let me know here that you have.

over 2 years ago - /u/thearcan - Direct link

Originally posted by ipStriderLord

Same for me, 99% yet... :(

if you still dont have any luck in a few hours, please do DM me your gamertag and then let me know here that you have.

over 2 years ago - /u/thearcan - Direct link

Originally posted by jmblue52262

I'm still stuck at 99% as well. Logged off then logged back on

if you still dont have any luck in a few hours, please do DM me your gamertag and then let me know here that you have.

over 2 years ago - /u/thearcan - Direct link

Originally posted by davidmako

Hey, thanks u/thearcan for hearing out our frustrations with this topic and for trying to help us understand.

No worries, I'm always keen to shine a light on the behind the scenes as much as I'm able to.

None of the team are happy with the situation and everyone is trying their best for the game and for the players. That's why I'm eager to explain the going ons, so that you too can see our thought processes and understand that such decisions and situations are not bourne of complacency or a lack of care.

over 2 years ago - /u/thearcan - Direct link

Originally posted by vapoorer

I guess thats fair and understandable.. But man i really want to play this patch already. :(

I very much understand :(

over 2 years ago - /u/thearcan - Direct link

Originally posted by Knuppen

The progression accolade worked for me after logging out and in again. Finally got the Monarch of Enoch

Great to hear!

over 2 years ago - /u/thearcan - Direct link

Originally posted by jrohara1

Is there a known issue on pc players stuttering when in a console lobby but only on water like in Scorched Lands? It appears to only happen on puddles.

Yep!

Entering the drained lake during the third enemy encounter in the Scorched Lands Expedition can cause client players to stutter

Issue currently being investigated and will be resolved in a future patch

over 2 years ago - /u/thearcan - Direct link

Originally posted by ipStriderLord

I did DM you about this... nothing has been fixed for me yet... just checked again...

I cant see your DM in either my Chats or my Reddit messages... I'll give you a nudge on chat.