Does ForceOneChunkPerFile Actually Assign Files to the Lowest Numbered Chunk?

Development Platform & Builds
, , , ,
1

I have assets that are assigned to specific chunks for individual packaging, but there’s also a fallback label that catches all assets. This means some assets end up in multiple chunks simultaneously.

I have several chunk pak files, but I’m experiencing issues where:

  1. Some chunks are excessively large
  2. Some chunks aren’t actually being written (empty or missing)

I was reviewing the packaging code and noticed that bForceOneChunkPerFile is documented to assign files to “the lowest number requested” chunk, but the implementation uses HashSet<ChunkDefinition> which has undefined enumeration order.

I’m wondering if anyone has actually observed files being assigned to the wrong chunk when this setting is enabled?