v1.4: recursive occlusion isolation and native-mask counterpart diagnostics - #31
Draft
Datamining00 wants to merge 15 commits into
Draft
v1.4: recursive occlusion isolation and native-mask counterpart diagnostics#31Datamining00 wants to merge 15 commits into
Datamining00 wants to merge 15 commits into
Conversation
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
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.
Follow-up test branch after the consecutive-transform fix was visually verified on the previous livery.
Current real-world findings
layers 2416-2761; the supplied refined sheet narrows it further tolayers 2718-2761. The other seven refined ranges contain only small/sparse artwork.0x0100, type0x100100, and no resolved native resource. It must not be silently skipped.source_offsetis relative to the C_livery layer-data body, while v2 sliced the full decompressed payload directly. In the supplied sample the real direct02 00 01 ...record is exactly one layer-data base (0x48/ 72 bytes) after the v2 nominal position. v3 resolves the body base before reading raw bytes.v3 simple diagnostic policy
*-occluder-pass-N.png,*-occluder-candidates.png, and*-occluder-candidates.jsonwith source offset/type/shape/mask metadata for the final candidates.No car ID, creator, livery name, section coordinate, layer number, shape word, or resource alias is hard-coded into runtime behavior. Existing parser transform fixes remain unchanged.
Validation
b2ad040ba360f37b19764f3102b85f2aae92afa2d221b065978499bade91af51.64057d545b8b18ade19f966d41dbe79d577ff95e2ca7f7f2aaa260595b6d5669.This PR remains draft until the final Left candidate sheet/JSON and the new Right v3 mask report are checked on the supplied real-world cases.