You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extraction record consists of a file list, which only holds files that were successfully extracted to the destination. However, I did run into an issue once installing a poser-formatted file structure where some of the files did not extract despite the extraction record indicating that it was.
It may be exclusive to poser-formatted file structures or it may be an issue with the logic in DPZipArchive or DPRARArchive.
The text was updated successfully, but these errors were encountered:
Issue occurred due to a folder down 4 levels from root was named "Scene", which is a common content folder (in other words, in the user's list of common content folders), and resulted in that being determined to be a content folder even though a more qualified content folder was populated. So technically, the extraction record was correct, the file was extracted but at an unexpected location within the user's destination path. I will update the extraction records soon as well.
For example, "My Product/Environments/My Name/Scene", would fail because of two reasons.
"Scene"'s parent folder has isPartOfContentFolder and content folder set to false, which makes it eligible to be considered as a content folder.
"Scene" is in the user's common content folder lists, which is a requirement to be considered as a content folder.
Because of this, the relative paths of the children of this folder were set to this folder, meaning that the calculated expected location would output: "D:/My Daz 3D Library/Scene", instead of (the correct path): "D:/My Daz 3D Library/Environments/My Name/Scene".
Additionally, it means there was a flaw w/ isPartOfContent logic that needs to be checked. Because technically, The "Environments" folder had isPartOfContentFolder set as true, which should've meant that "MyName" and "Scene"'s isPartOfContent would also set to true.
An upcoming solution now replaces the current code that goes from bottom of the tree up, to up to down, hopefully making isPartOfContent accurate.
The extraction record consists of a file list, which only holds files that were successfully extracted to the destination. However, I did run into an issue once installing a poser-formatted file structure where some of the files did not extract despite the extraction record indicating that it was.
It may be exclusive to poser-formatted file structures or it may be an issue with the logic in DPZipArchive or DPRARArchive.
The text was updated successfully, but these errors were encountered: