The reason for this is pragmatism. The assets for video games are what make up the large file sizes you have to download to play them. Keeping the total size to a manageable amount involves the reuse of textures, meshes, and other assets whenever possible to save on disk space. You'll see repetition in houses, cities, caves, and dungeons and even some assets being reused in completely different ways. There's one case where two bookcases are pushed together to form a table (you can still read the book however).

LOL... Elder Scrolls Ikea.

cjmarsh725b14_ESO wrote: »

The reason for this is pragmatism. The assets for video games are what make up the large file sizes you have to download to play them. Keeping the total size to a manageable amount involves the reuse of textures, meshes, and other assets whenever possible to save on disk space. You'll see repetition in houses, cities, caves, and dungeons and even some assets being reused in completely different ways. There's one case where two bookcases are pushed together to form a table (you can still read the book however).

Meshes are NEVER reused in an engine like this. It's not effecient for the technology so it's not done.

Plus every mesh in the game combine likely amounts to somwhere in the 0.5-1% of the total disk space.

Textures are reused for sure. But the overall model designs COULD vary wildly with no real impacts on filesize or performance.

It's done beccause of 1 simple reason:
Time.
Retexturing a few inns and slightly modifying there contents takes many hours less then making entirely new ones.

And yea, a game thats 30gb is not one where the developers at all cared about disk space.
They could of fit the exact same game in 10gb or less with very minor use of compression, they didn't because it's not something most devs care about with todays tech.

The only thing they compressed decently was hte audio. (If they didn't do that, with this games billlion hours of dialog, it would be like 500gb). Textures and most everything else are just plain uncompressed.

Anything Dragon Age 2 can do, ESO can do better.

Axer wrote: »

cjmarsh725b14_ESO wrote: »

The reason for this is pragmatism. The assets for video games are what make up the large file sizes you have to download to play them. Keeping the total size to a manageable amount involves the reuse of textures, meshes, and other assets whenever possible to save on disk space. You'll see repetition in houses, cities, caves, and dungeons and even some assets being reused in completely different ways. There's one case where two bookcases are pushed together to form a table (you can still read the book however).

Meshes are NEVER reused in an engine like this. It's not effecient for the technology so it's not done.

Plus every mesh in the game combine likely amounts to somwhere in the 0.5-1% of the total disk space.

Textures are reused for sure. But the overall model designs COULD vary wildly with no real impacts on filesize or performance.

It's done beccause of 1 simple reason:
Time.
Retexturing a few inns and slightly modifying there contents takes many hours less then making entirely new ones.

And yea, a game thats 30gb is not one where the developers at all cared about disk space.
They could of fit the exact same game in 10gb or less with very minor use of compression, they didn't because it's not something most devs care about with todays tech.

The only thing they compressed decently was hte audio. (If they didn't do that, with this games billlion hours of dialog, it would be like 500gb). Textures and most everything else are just plain uncompressed.

While time is a factor in reusing assets, certainly, and the audio is definitely compressed, everything else is not true.

I always get a feeling of deja vu when I do anything now. Towns, dungeons, people, etc....Probably my only real complaint about the game. You did see it a few times in Skyrim, but no where near this much duplication.