#rb steve.robb
#ROBOMERGE-SOURCE: CL 12450992 via CL 12450999 via CL 12457993
#ROBOMERGE-BOT: (v672-12450963)
[CL 12458149 by johan torp in Release-Engine-Staging branch]
[FYI] johan.torp, steve.robb, eric.knapik
#rnx
#ROBOMERGE-SOURCE: CL 12434782 via CL 12434783 via CL 12437070
#ROBOMERGE-BOT: (v671-12333473)
[CL 12443982 by david hamm in Release-Engine-Staging branch]
#rb steve.robb, eric.knapik
#ROBOMERGE-SOURCE: CL 12371098 via CL 12372591 via CL 12388959
#ROBOMERGE-BOT: (v671-12333473)
[CL 12390565 by johan torp in Release-Engine-Staging branch]
Legacy pak file versions encode pak entries in FPakFile::LoadLegacyIndex. That function repeatedly serializes bytes from the pakfile on disk into a reused FPakEntry. Serialize expects the FPakEntry to be in an empty constructed state, and it was not empty due to serializing previous PakEntries into it.
Added a reset function and call it in this one place where FPakEntry is reused.
#rb Graeme.Thornton
#rnx
[CL 12000363 by Matt Peters in Main branch]
#rb none
#testing iOS Client
#ROBOMERGE-SOURCE: CL 11843182 via CL 11843195 via CL 11843203
#ROBOMERGE-BOT: (v656-11643781)
[CL 11879820 by thomas ross in Main branch]
#ROBOMERGE-SOURCE: CL 11458135 via CL 11458136 via CL 11458137 via CL 11458138
#ROBOMERGE-BOT: (v654-11333218)
[CL 11458139 by matt peters in Main branch]
[REVIEW]
#rb Graeme.Thornton
Optimize Pak file indices by computing the PathHashIndex in unrealpak rather than using strings at runtime.
This also removes the need to shrink the string indices for performance, which was triggering a bug due to unsynchronized multithreaded access.
#ROBOMERGE-SOURCE: CL 11442058 in //Fortnite/Release-12.00/... via CL 11442063 via CL 11442073 via CL 11442081
[CL 11443295 by Matt Peters in Main branch]
#rb steve.robb
#ROBOMERGE-SOURCE: CL 11303014 via CL 11303031 via CL 11303037 via CL 11303042
#ROBOMERGE-BOT: (v0-11244347)
[CL 11303201 by graeme thornton in Main branch]
Name the number in pakchunk file pakchunk index and the number of a platform chunk chunk id to avoid confusion. Also keep this naming convention consistent across all platform code.
#ROBOMERGE-SOURCE: CL 11131543 via CL 11132441 via CL 11132504
#ROBOMERGE-BOT: (v640-11091645)
[CL 11132564 by hongyi yu in Main branch]
Partially back out changelist 11106714, only keeping intended merged code
[FYI] Dan.Phillips
#ROBOMERGE-SOURCE: CL 11107908 via CL 11107911
#ROBOMERGE-BOT: (v640-11091645)
[CL 11107914 by bob tellez in Main branch]
Allow a read request to tell the pak cache not to keep the memory after the request is completed.
Make virtual textures give up their pak cache memory immediately after loading.
[REVIEW] ben.woodhouse, steve.robb, david.harvey
#ROBOMERGE-OWNER: dan.phillips
#ROBOMERGE-AUTHOR: dan.phillips
#ROBOMERGE-SOURCE: CL 11106543 via CL 11106714 via CL 11106736 via CL 11106740
#ROBOMERGE-BOT: (v640-11091645)
[CL 11106744 by dan phillips in Main branch]
#rb Justin.Marcus
#ROBOMERGE-SOURCE: CL 11064634 via CL 11064641 via CL 11064653
#ROBOMERGE-BOT: (v637-11041722)
[CL 11064661 by hongyi yu in Main branch]
Add some more stats for detecting bad seeks between pak files and contiguous reads
[FYI] ben.woodhouse
#ROBOMERGE-SOURCE: CL 10981267 via CL 10981268 via CL 10981271
#ROBOMERGE-BOT: (v632-10940481)
[CL 10981277 by dan phillips in Main branch]
#jira UE-86394
#rnx
#ROBOMERGE-SOURCE: CL 10925126 via CL 10925127 via CL 10925128
#ROBOMERGE-BOT: (v626-10872990)
[CL 10925130 by graeme thornton in Main branch]
[FYI] bob.tellez
#ROBOMERGE-SOURCE: CL 10903752 via CL 10903753 via CL 10903755
#ROBOMERGE-BOT: (v626-10872990)
[CL 10903757 by graeme thornton in Main branch]
#rnx
#rb none
#ROBOMERGE-OWNER: ryan.durand
#ROBOMERGE-AUTHOR: ryan.durand
#ROBOMERGE-SOURCE: CL 10869210 via CL 10869511 via CL 10869900
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870549 by ryan durand in Main branch]
#jira
#rb Graeme.Thornton
#ROBOMERGE-SOURCE: CL 10791547 via CL 10791568 via CL 10791573 via CL 10791579 via CL 10791601
#ROBOMERGE-BOT: (v610-10636431)
[CL 10791615 by jamie dale in Main branch]
- Always look for pak files in the standard locations to determine whether we should create the platform layer
- When looking up a decryption key, check the registered list for all guids, even empty ones. We want to support pak mounting in non-monolithic builds where we don't have an embedded key.
- Remove the initialization-time check that the decryption key exists for pak files with an encrypted index. The condition to test is more complex when considering editor pak mounting, and we will get a meaningful error almost immediately afterwards anyway.
#ROBOMERGE-SOURCE: CL 10482630 via CL 10482631
#ROBOMERGE-BOT: (v606-10482310)
[CL 10482632 by graeme thornton in Main branch]
