Repository navigation
VFS: Support Encodingless CASC + A bunch of TVFS fixups - #38
Open
neptuwunium wants to merge 7 commits into
Open
neptuwunium wants to merge 7 commits into
neptuwunium wants to merge 7 commits into
Conversation
neptuwunium
force-pushed
the
encodingless-vfs-behavior
branch
from
September 27, 2026 13:10
65364cf to
2fe45f5
Compare
neptuwunium
force-pushed
the
encodingless-vfs-behavior
branch
from
September 28, 2026 01:09
4c7039c to
b798bcf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We need a better way to determine IsStaticContainer.
Fenris (Diablo 4) on Steam does not use CASC Encoding at all. It's just not present.
Instead the entire game just depends on TVFS. CKeys are useless in these cases.
As such Root and Encoding are both not present in the build config (as is stuff like build-name.)
Some todos: We probably should pull the espec from encoding as well, and the espec specifies BLTE block sizes too for whatever that's worth.