Patching Overhaul

Jolipinator · June 2020

What is the Patching Overhaul?

The Patching Overhaul is a massive part of the Update 25 base-game patch (arriving February 24 for PC/Mac and March 10 for PlayStation®4 and Xbox One) that completely overhauls how the ESO game client is downloaded, patched, and stored on local hard drives.

What are the benefits of this update?

Once this update is complete, you will see major improvements to the game’s load time and the speed at which assets are loaded into the world.

Most notably, this change dramatically reduces the patch sizes for all future updates, and it results in a major reduction of space taken up by the client on your machine’s hard drive. Our console players will feel this improvement most strongly, and PC/Mac players also benefit from this change.

PS4 Update Sizes:
#26: 47.72GB
#24: 39.7GB
#23: 33GB
#22: 37.15GB

Xbox Update Sizes:
#26: 56.82GB
#24: 58.5GB
#23: 58.14GB
#22: 57.73 GB

I don't see a dramatic reduction anywhere.

smilingmaybe · June 2020

It's probably just server load, but I wonder if this plays into why I've had to force quit multiple times after the game freezes when zoning through a door over the past hour.

Dark_Lord_Kuro · June 2020

You had 47gb?! I got 58gb on ps4

dotme · June 2020

Dark_Lord_Kuro wrote: »

You had 47gb?! I got 58gb on ps4

Same. From my perspective the "Patching Overhaul" has had about the same impact as the past year's worth of "Performance Improvements"

silvereyes · June 2020

Jolipinator wrote: »

What is the Patching Overhaul?

The Patching Overhaul is a massive part of the Update 25 base-game patch (arriving February 24 for PC/Mac and March 10 for PlayStation®4 and Xbox One) that completely overhauls how the ESO game client is downloaded, patched, and stored on local hard drives.

What are the benefits of this update?

Once this update is complete, you will see major improvements to the game’s load time and the speed at which assets are loaded into the world.

Most notably, this change dramatically reduces the patch sizes for all future updates, and it results in a major reduction of space taken up by the client on your machine’s hard drive. Our console players will feel this improvement most strongly, and PC/Mac players also benefit from this change.

PS4 Update Sizes:
#26: 47.72GB
#24: 39.7GB
#23: 33GB
#22: 37.15GB

Xbox Update Sizes:
#26: 56.82GB
#24: 58.5GB
#23: 58.14GB
#22: 57.73 GB

I don't see a dramatic reduction anywhere.

Yeah, something's definitely not working correctly on console. The PC download was 6.64GB for Greymoor, and 42MB for last Wednesday's incremental patch.

Starlock · June 2020

When one game eats a fifth of my allowed download gigs a month.... it encourages me to solidify my notion that this’ll be the last year bothering with this game...

eKsDee · June 2020

smilingmaybe wrote: »

It's probably just server load, but I wonder if this plays into why I've had to force quit multiple times after the game freezes when zoning through a door over the past hour.

That's... not how it works. Servers being heavily stressed has no impact on the size of patches. How stable the patch download is, sure, but not the size.

Vizikul · June 2020

@ZOS_GinaBruno What's up with this? We were promised smaller patch and update sizes but file sizes are still as large as before.

Miswar · June 2020

56gb on PS4. You guys still believing anything ZoS says.

Well reality check just dont.

Jolipinator · June 2020

Dark_Lord_Kuro wrote: »

You had 47gb?! I got 58gb on ps4

I did, but I took these numbers from the official patch notes.

ZOS_GinaBruno · June 2020

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

zergbase_ESO · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Aka expect no fixes and eat it. Same old mantra.

Starlock · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Thanks so much for shedding some light on this, @ZOS_GinaBruno - it's much appreciated! Having only an elementary grasp of programming, I'm not going to pretend to know how challenging this is to sort out.

Aloha · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

OMEGA***

Jarrods32 · June 2020

Instead of patch sizes being of concern can we get game fixes for the lag constant sync issues and over bad performance
Oh and can we fix skills that dont work like umm idk syphon and blastbones
Necro been out a while and this patch is worse than last syphon still totally broke

Destai · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Thanks for giving us some concrete details, it's really appreciated.

Aloha · June 2020

Destai wrote: »

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Thanks for giving us some concrete details, it's really appreciated.

Really 8)

Jolipinator · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Thanks for the info Gina. I hope it can be resolved sooner rather than later.

Hotdog_23 · June 2020

zergbase_ESO wrote: »

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

Aka expect no fixes and eat it. Same old mantra.

This made me laugh to hard

PrimusNephilim · June 2020

ZOS_GinaBruno wrote: »

We were able to figure out why the console patch sizes were still fairly large for Update 26, even though we expected them to be smaller than previous updates. In short, there was an issue with how texture packages were ordered in the packfiles, causing the patcher to think files needed to be patched even though they didn’t change. We have a fix internally and are currently working out when and how to get this published. It may require us to roll out the fix over time, which would mean subsequent patches are still slightly larger than intended until it is fully resolved. We’ll keep everyone updated on what to expect.

in short, this DLC wasn't ready for release but Todd Howard said let it drop anyway

ZOS_GinaBruno · June 2020

Just to update, we're going to move forward with rolling out this fix over time. As previously mentioned, this means the next console incremental patch is going to be larger than usual (compared to other incremental patches) and anything remaining will be added to Update 27. After Update 27, you can expect console patch sizes to be smaller as part of the patching overhaul we did earlier this year.

Hotdog_23 · June 2020

Thanks for the heads up.

Jolipinator · June 2020

Thanks Gina. Bring on update 28.

Aloha · June 2020

Naive