Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
We get many complaints about this, but the only thing we could realistically do would be uncompress the data completely, which is what games like Ark do. They don't pack the data and leave it all unpacked, and uncompressed.
If we tried to do this with Icarus, it would very dramatically increase both the load times and RAM used by assets during loading, as well as filesize very dramatically.
Unfortunately it seems following the best practice guidelines for packing data for Unreal, which we did, triggers big problems for steam downloads. I raised the issue with valve who told me to get customers to raise tickets, which I passed on. However, valve then just closed the tickets. So sadly, I think we all just have sit with how it is until Valve decide to change that.
This is a reason why we limit the project to only one update a week.
Perhaps you misunderstood me; but the phrase "highly optimized binarized data" is just a descriptive way of saying "packing" something. It's just a factual statement describing how the files are packed.
Take for example if you took your whole computer hard drive and "zipped" it up. By saying its binarized and highly optimized, I wouldn't be necessarily saying its the best way to work on those files, but it is the most efficient way of storing it. Additionally, if when zipping it, the packing process looked at what files reference what others, and in particular, what files you typically work on after others - and group them together - this is what the engine packing does. Extending the analogy further, by zipping your whole harddrive up in this manor, if you updated *one* file, then depending on how it gets distributed to customers, the software used to download it might use novel ways to copy, apply the delta state change, and then unpack it.
hi kinda off topic how much will the upcoming dlc cost?
Thank you very much for this very informative, and interesting, response. Please don't see my post as a complaint. I was only curious about how things worked is all. I really appreciate you taking the time to give us all such a detailed explanation and insight into how the mechanics of patching works. I find it very interesting.
You guys are doing an excellent job with the updates, and I love the game. Please keep up the good work! =D
Community engagement is how we have gotten the game to the much better position it is in now, and part of that is having good "robust" discussions and liaison with the community. We hope we keep delivering good updates and a better game!
"highly optimized binarized data"
it was about overcompressed type of archive -> solid archive
Wiki (if anyone wants to read more about what it is) -> https://en.wikipedia.org/wiki/Solid_compression
And there, file layout schemes for compression can really be extremely sophisticated. For example: I think everyone knows that there are official games, and there is a 'torrent edition' (I think it's clear what I'm talking about).
So, some repackers through 7z archiving manage to almost halve the size of the game installer, taking into account the fact that initially all the game resources were already in the archives, so this is really a very serious thing (solid archive).
Very true. I've got a Corsair MP600 2TB NVMe and it's orders of magnitude faster than a 7200 rpm HDD. I know a lot of people just have a small SSD boot drive to run their OS off of, but I put everything on my NVMe. Load times almost completely disappear in some games.
Also, you don't run Icarus on HDD. Just don't. You will get a bunch of "out of VRAM", stutters etc. just cause your drive can't handle it. Max speed SSD will solve a lot of problems especially for this game. Leave the HDD for museums. That tech is no longer acceptable for gaming.
I agree completely. The funny thing is, there are people out there that think a game requiring an SSD is "ridiculous", and that's it's "too soon", for games to be requiring SSDs. SSDs have been on the market for over 15 years at this point. And, like you said, they are very affordable. If gaming is your main hobby, or source of recreation at least, there's no reason to not have an SSD. The increase in speed is astronomical.
Steam use to have a problem where games that had not been played for awhile or had just been patched would somehow become corrupted. I thought this was fixed but I've had issues with RDR 2, GTA V, Icarus and other games on other drives that have had issues with this. Personally I think there is a bug somewhere in Steam's update system that is causing failed patches. I cannot 100% verify this but I have scanned all my drives (a mixture of SSDs and hard disk) and all are fine yet my games continually crash b/c they become corrupted over time even if they never had a CTD during my gaming sessions. But after a patch or after not playing for a bit they CTD.
So after every update I recommend you first verify files. Make sure that what Rocketwerkz put out there is what your system downloaded. B/c I know for sure this is not true in all cases.
I've often had RDR 2 go into super low res mode and fail to load in a new area. Then when I verify files Steam downloads some common Steamworks redist file and all is well. But after time the same thing happens no matter how often or how infrequent I play. I have no idea why Steam update has been so odd as of the past year or so. All my drives cannot be bad and no non Steam applications have any issue. MSVS starts up all the time every time and that is far more complicated. So either it just so happens all my drives are corrupt only where my Steam games are (highly unlikely) or Steam has introduced an issue in their update system that has not yet been fixed and/or found.
Just out of curiosity, do you install your games to an SSD or to a HDD? I only ask because you said that you, quite often, encounter file corruption when downloading/installing games or patches,etc. This made me wonder if,perhaps you were using a HDD and it is malfunctioning in someway. In over ten years and hundreds of games downloaded,installed, and patched on Steam, I have never encountered any sort of file corruption, or errors such as the ones you are reporting.