Is it correct that the currently used GGPK viewer doesnt show all files?

[MichaelWahlen]

When writing my own parser I found a lot of files that seemed "orphaned" in that I could not find a proper parent when going down from the original GGPK root record.

Is this indeed the case and does the original GGPK viewer incorrectly not show the complete contents of the GGPK, or am I overlooking the location of the files (or perhaps something else)?

[OmegaK2]

The approach I'm taking is to build the root directory and not do much with the other entries. So it is intended behavior. I think I could add this as a feature though. Have you noticed if the files are actually valid files or if they contain garbage bytes?

[MichaelWahlen]

I haven't experimented with extracting the files beyond the .txt files (and can't find a txt file in either the directory-less files nor in the files that have a directory, but cannot be reached from root). I will be trying to get the DDS extracted from ROOT and from non-ROOT in such a way that I can view either. Afterwards I'll come back here :)

[MichaelWahlen]

Just checked, in the non-root directory there is for instance a file called Glow.dds that actually contains a proper image of a glow. Other example would be double_strike\slash_base.dds

[OmegaK2]

I see, it probably makes sense to add this to PyPoE then. Still makes me wonder though whats up with those "orphaned" files.