Skip to content
This repository was archived by the owner on Oct 23, 2026. It is now read-only.

Decode GTA IV composite collision and qualify local inspection - #38

Closed
Jpatching wants to merge 21 commits into
mainfrom
implement/gtaiv-composite-collision
Closed

Jpatching wants to merge 21 commits into
mainfrom
implement/gtaiv-composite-collision

Conversation

@Jpatching

@Jpatching Jpatching commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

Summary

Owned resource → bounded composite decoding → authored viewer qualification → fixed-camera selected-overlay comparison → named local street connection; ground checkpoints pending.

The read-only inspector decodes one composite level of geometry/BVH polygon meshes, applies explicit child transforms, triangulates unflagged quads and refuses unsupported/malformed input without partial output. Separate authored Unity tooling checks the pinned renderer at literal asymmetric coordinates and provides Hide/Show controls for a selected collision-only root. Investigators can distinguish selected geometry from the surrounding map without relocating either.

Advances #20 under approved spec #39; preserves the bounded outcomes of #40/#41. No Skate runtime or host-game behavior changes. The named local connection is now supported; four retained mesh-coordinate candidates have image support; precise surface qualification remains pending; the owner subsequently confirmed the intended location.

Evidence

  • Decoder before: retained resource returned unsupported / unsupported-root. After: structurally-decoded / validated-geometry. Literal transform and quad tests failed before implementation and passed afterward; 19 focused parser/command tests passed. Decoder source remains unchanged from 47e8a2c.
  • Baseline authored fixture qualified the existing renderer's complete geometry, positions, orientation, scale, height and topology in Unity Editor 6000.4.0f1 (8cf496087c8f). This baseline is qualification, not a claimed behavioral red/green cycle.
  • Visibility before: the authored public menu test compiled but failed with the Hide command missing (CLI wrapper exit 6). After: Hide/Show passed with both children restored at unchanged literal positions/topology and an unrelated renderer still enabled (exit 0). Mixed/absent-selection guard checks also passed, without a separate red/green claim. Final source rerun emitted PASS with no C# errors and exit 0. Explicit API migration is documented; project/package pins were rechecked unchanged.
  • A reviewed private identity parent allows selecting the complete retained overlay. Live digest/count checks passed and loading released normally. Actual HIDDEN/SHOWN markers accompanied a same-camera game-view pair, captured and opened locally. Independent review confirmed disappearance/restoration and consistent landmarks. Some foreground approach/yard/roadside surfaces correspond broadly; farther bridge spans remain uncovered. Arrow-like overlay patterns are not independent map markings. Exact media/identities stay private.
  • Location before: the bridge-only pair left street identity inconclusive. After: new connected Hide/Show views and original base-game references support Industrial, Bohan, around Drill Street / Lompoc Avenue and the unfinished Northern Expressway approach. Independent visual review supports this named local connection. Retained digest/count/loading checks match; the latest pair was opened locally. Exact road/pavement/height-change checkpoints remain pending; the owner subsequently confirmed the intended location. No paired GTA/mesh measurements, ground agreement or wall proof exist. Viewer appearance acceptance does not approve source merge.
  • Checkpoint preparation: four private face-centroid candidates span ordinary road, paved margin and lower/upper points on one unfinished-road carriageway. Independent image review rejected parked-trailer/verge targets and an ambiguous lower-layer association; all corrected image candidates are supported. Exact surface/layer qualification remains incomplete. Comparison rules are frozen before paired GTA data: three valid readings, maximum 0.02 m repeat spread and 0.05 m absolute vertical error for every reading; unavailable results never become passes. No query/comparison implementation or GTA launch occurred.
  • python3 scripts/verify.py: 73 tests and 65-document/context checks passed for the latest documentation follow-up. Independent Standards and Spec reviews of 51e258a...2f228b4, plus publication follow-up, found no actionable findings. Latest location documentation follow-up also passed independent Standards and Spec review with 0 actionable findings. Repository checks do not compile Unity or validate gameplay.

See checkpoint preparation, street-reference follow-up, location verdict and current context.

Focused follow-up tooling is isolated in draft #42,
stacked on this branch with owner authorization. It adds temporary centroid
markers and an authored-tested comparison command; it supplies no GTA collector
or completed physical qualification. New source is not added to this parent PR.
See #20's current status.

Merge Danger

Door: two-way

Blast Radius: tooling

Standalone inspector and Editor inspection commands/fixture; no host runtime or dependency-pin changes. Private bootstrap/read-access changes are outside tracked source and are not a supported viewer integration. BVH search trees, box enclosure, margins/materials and active host collision remain unvalidated. Draft awaits owner source approval; merge alone would not qualify ground checkpoints or authorize gameplay launch/release.

@Jpatching Jpatching mentioned this pull request Oct 9, 2026
3 of 10 tasks
@Jpatching

Copy link
Copy Markdown
Owner Author

Location investigation published at 86564dc on implement/gtaiv-composite-collision, retaining draft #38. Decoder source remains unchanged from 47e8a2c.

Verdict: inconclusive at location. The retained owned WBN digest matches the acquisition record and the exact source archive entry; archive size/timestamp match the retained record. An uncommented IMG directive names that archive. Under the explicitly unverified world-coordinate hypothesis, the decoded horizontal bounds contain 564 map-instance origins across four of the archive's nine WPL entries (3,324 instance records inspected). This narrows a candidate map area but does not establish a street, world placement or active host collision. The owned child matrices were read and are exactly identity; none were substituted.

Independent primary-source investigation traced GTA4Unity's separate static WBN and drawable-instance loading paths and CitizenFX's static-bound versus model-dictionary conversion. These corroborate a candidate interpretation, not the exact-version GTA runtime. The inspected WPL reader supplies no usable BLOK association. GTA4Unity generally omits composite matrices and remains an unqualified viewer/reference. Source-safe details and citations: research/results/2026-10-09-gtaiv-resource-placement.md. Exact provenance, coordinates and correlations remain private and ignored.

The missing link is an independently recognisable street/landmark match with qualified coordinate placement for this exact resource. Resume from the retained candidate records rather than repeat acquisition. Following the owner's stop condition, no measurement tooling, supported parser, game launch, staging or Skate integration was added. No new behavior meant no TDD cycle; temporary read-only map-field inspection is investigation, not a supported implementation.

Validation: python3 scripts/verify.py passed 73 tests and link/context checks across 61 documents; git diff --check passed. Independent Standards review found no hard violations and one wording suggestion, applied. Independent Spec review found no actionable defects. Reviewers assessed public evidence and scope; they did not independently reproduce private observations. HANDOFF is updated. No gameplay or owner acceptance is claimed; #20 remains open and #21/#22 remain blocked.

After the location gate passes: distinctive road/pavement/height-change checkpoints, fixed numeric tolerance and repeatability rules before identical-coordinate GTA/mesh comparison, unavailable results rejected, agreement/disagreement/inconclusive. Agreement covers those ground checkpoints only; walls remain next.

@Jpatching

Copy link
Copy Markdown
Owner Author

Owner-approved spec #39 and tickets #40/#41 are published; #41 has a native dependency on #40. The authored resource-to-viewer scene test boundary is confirmed.

Preparation is preserved on implement/gtaiv-viewer-qualification at 4854d78, based on integration revision 86564dc. It contains an authored two-child identity-composite fixture and procedure at tools/gtaiv-viewer. The C# fixture is uncompiled/unrun. There is no behavioral red/green or viewer qualification pass. Existing upstream behavior remains unchanged; the overlay startup call is still disabled.

Independent static review corroborated framing, layout, literal coordinate expectations and complete fixture output assertions. It found an interactive scene-loss risk; the correction prompts to save modified scenes and returns UNAVAILABLE on cancellation before replacing scenes. Visible pixels, private resource completeness and street identification remain unproved. The preparation worktree's repository gate passed 73 tests; that gate does not compile Unity C#.

The exact official Editor installer (6000.4.0f1, 8cf496087c8f) matches published size/integrity; Editor and Hub installers have valid Unity Technologies signatures. They are staged privately. Hub interactive installer launch was requested; installation, account/licence activation and package resolution have not been verified. The owner asked why Unity is required: it is a dependency of the selected inspection viewer only, not a replacement GTA host or Skate integration engine. Further installation actions are held while that choice/licensing step is clarified. No owned-game bootstrap, GTA launch, asset upload or measurement tooling occurred.

HANDOFF update is a9cb93e on the existing integration branch/draft #38. The parent repository gate passed 73 tests; diff checks passed. #40 remains open and #41 remains blocked. No implementation merge, owner evidence acceptance or release is claimed.

@Jpatching

Copy link
Copy Markdown
Owner Author

The owner reconfirmed proceeding with Unity CLI. The signed CLI installed the required Editor 6000.4.0f1 (8cf496087c8f) separately from the pre-existing newer editor; installation completed and CLI structural verification passed. The actual runtime log confirms the exact engine revision. Project manifest, package lock and ProjectVersion remained byte-identical to the pinned viewer.

The first authored-fixture attempt stopped at compilation, before behavioral assertions. It found an ambiguous CompressionLevel reference in the fixture and Unity package GUID references. Commit bed92c1 on the retained viewer branch qualifies System.IO.Compression.CompressionLevel. Independent static review found no defects. Cached package GUID references changed without agent edits; automatic API migration is plausible but not independently established.

The second unity run attempt compiled with no C# errors, emitted COMBINE_OVERLAY_QUALIFICATION: PASS (scene geometry; pixels unverified), and exited 0. This verifies both authored child meshes, complete expected vertices/world coordinates, topology/winding, active renderers and supported materials. It is qualification of existing renderer behavior, not an invented behavioral red/green implementation cycle.

Visible pixels remain unverified. The isolated interactive unity open capture attempt is waiting at the Windows dialog titled “Unity Editor Software Terms”; the owner was asked to review that agreement. No image was produced. Private logs and setup remain local; no owned-game bootstrap, GTA launch, asset upload or measurement tooling occurred.

HANDOFF is pushed at 3f052a5 on the existing integration branch. Repository gate: 73 tests passed, plus document/context checks. The worker fixture remains unmerged; #40 stays open and #41 stays blocked. No full viewer pass, street-location pass, owner acceptance or release is claimed.

@Jpatching

Copy link
Copy Markdown
Owner Author

Progress under the approved viewer scope; #40 remains open and #41 remains blocked.

The owner approved the Unity terms step. Exact Editor 6000.4.0f1 (8cf496087c8f) repeated the authored scene-geometry PASS, and a local rendered image showed both authored children. Independent review confirmed that narrow pixel-visibility claim and the corrected capture helper's fresh-pass guard. The quadrilateral has low contrast; top-down imagery does not prove height, which remains covered by the coordinate assertions. Workbench opened the actual local evidence.

A reversible private lab configuration was prepared by the retained implementer and independently reviewed. It verifies the exact selected resource digest, leaves full map loading intact, keeps the parent at identity, checks all expected child/vertex/triangle counts, disables ped spawning and enables the existing flight camera after focus creation. Patch SHA-256: 858892757939cc53d341093e4843e5f2947614afb05d24fbf05cc44860b0066a. This is isolated upstream lab configuration, not merged Combine source or a supported viewer.

The first live trial failed before map baking: upstream IMG opening requested read/write access. Windows read-only opening succeeded on the same private archive. A separately reviewed one-line lab correction requests FileAccess.Read, preserving original permissions. Patch SHA-256: a99ace41476ad6541dcae3baaa6ea25947ba670b0ba69a7af31a3bff8597b594. Save cannot write through the resulting stream; Rebuild retains a separate write path and remains uninvoked. This is not a universal no-write mode.

The corrected project compiled and repeated the authored fixture PASS with exit 0 and no C# errors. The subsequent live trial verified the selected digest, matched complete expected mesh counts, completed map baking, spawned flight and released loading through the normal geometry-loaded/no-pending/collision-ready condition, not timeout. Manifest, package lock and ProjectVersion remain identical to the pinned project. An unrelated Unity search-index exception was logged; no error-free runtime claim is made. The authored fixture does not test the new bootstrap guards or flight lifecycle.

A live viewer-window capture was saved and opened locally. The owner provisionally reported both map and overlay viewable. The later warning was Windows Photos asking whether to open the locally generated PNG through the WSL network-style path; at the owner's request, that warning was inspected and Continue opening invoked. A bounded follow-up UI check found no remaining Continue opening prompt. No security setting was changed. The viewer remains available for local inspection.

No unique street/landmark match, active GTA collision, ground agreement or wall proof is claimed. No host-game launch or measurement tooling occurred. Private game inputs, settings, coordinates and raw logs remain outside Git and this tracker. Full visual acceptance/review gates remain before unblocking #41 or merging.

HANDOFF is pushed at 4e43b39 on the existing integration branch; worker source/README remains pushed at 7248517 and unmerged. Repository gate passed 73 tests and document/context checks. The division of work followed ask-matt: parent runtime/evidence, retained implementer for bounded changes, independent source investigation and review; no parallel implementation of the blocked street ticket.

@Jpatching Jpatching changed the title Decode bounded GTA IV composite collision meshes Decode GTA IV composite collision and qualify local inspection Oct 9, 2026
@Jpatching

Copy link
Copy Markdown
Owner Author

Outcome: inconclusive

The bounded investigation is resolved with an inconclusive stop, expressly allowed by spec #39. This closes the investigation ticket, not the street-placement gate. Industrial, Bohan remains a plausible area; no exact named street match or selected-resource road/pavement checkpoint coverage was established.

Fresh close/side views were captured after camera-only input. Independent visual review identified selected overlay correspondence on the building/water tanks and the curved elevated railway; rails/sleepers distinguish it from a road ramp. The exposed asphalt below remained gray in those views. Nearby road markings, pavement margins and different levels cannot supply the missing selected-ground-surface correspondence. Exact resource digest was rechecked and still matches. Private identity, original coordinates, aggregate coverage record and screenshots are retained locally. The latest side view was requested open locally through its native Windows path; owner street confirmation remains absent.

Source-safe verdict: research/results/2026-10-10-gtaiv-viewer-location-verdict.md. Reviewed source integration: 5f2d007 on implement/gtaiv-composite-collision. No resource substitution, placement adjustment, GTA launch, comparison tooling, paired ground measurements or wall proof occurred.

Standards

One stale README current-result paragraph contradicted completed viewer qualification. It was corrected by the retained implementer and independently rechecked. Remaining Standards findings: 0. No other actionable smell suggestions.

Spec

The same README status contradicted the requirement to record actual results and limits. It was corrected and independently rechecked. Remaining actionable Spec findings: 0. The precise inconclusive outcome is allowed by the spec; reviewers did not privately reproduce runtime checks.

Review boundary: 86564dc through 5f2d007. Repository gate passed 73 tests and 63-document/context checks. The existing authored Unity fixture had already compiled and passed on the pinned Editor; no new behavior/TDD cycle or runtime qualification is invented for documentation changes.

Next decisive evidence: independently identify a named junction connecting the landmark group, obtain local owner location confirmation, and establish that this exact mesh covers suitable road, pavement and road height-change checkpoints. If not, stop; do not silently substitute another resource. Draft #38 remains pending owner source approval; #20 gameplay and #39 source approval remain open. Source merge, street placement and active GTA collision remain separate claims.

@Jpatching

Copy link
Copy Markdown
Owner Author

Focused visibility implementation: 2f228b4ae128090d59dde36ffe67cdd916ed5ec6; final evidence/context revision: 9372dfc. Fixed review starting point: 51e258a97d91ac7a6d3368eb6ffa5e3eeba8c133.

The selected-overlay Hide/Show commands preserve geometry placement and unrelated rendering. The authored public-menu test went from missing-command FAIL (compiled; CLI wrapper exit 6) to PASS (exit 0). Final exact-source Unity rerun compiled without C# errors, emitted PASS and exited 0; project/package pins stayed unchanged. Mixed/absent-selection guard qualification passed separately. Repository gate: 73 tests, 63-document/context checks; final publication links/context passed.

The reviewed private identity parent enabled a complete selection. Live digest/count/loading checks passed. Actual HIDDEN/SHOWN markers and an opened same-camera game-view pair demonstrate disappearance/restoration; independent pixel review confirms consistent landmarks. This improves inspection and broad foreground surface correspondence. It does not identify a named street, qualify coordinate checkpoints or establish active GTA collision. Street verdict remains inconclusive; measurement tooling remains stopped.

Standards

Independent review: 0 hard violations and 0 actionable smell suggestions. Publication follow-up: 0 findings. Source stays bounded to Editor inspection tooling; private data and owner approval boundaries remain preserved.

Spec

Independent review: 0 actionable findings. Public authored scene/menu checks, unchanged placement, selection refusal and inconclusive reporting match the bounded spec. Publication follow-up: 0 findings. Reviewers did not reproduce private runtime checks.

Standards: 0 findings; Spec: 0 findings. Draft #38 remains pending owner source approval; #20 remains open. Exact screenshots/logs/resource identities remain local.

@Jpatching

Copy link
Copy Markdown
Owner Author

Named local connection now supported; complete ground-preparation gate remains incomplete.

Camera-only follow-up connects Burger Shot, Menala Metal, adjoining streets, railway and the separated waterfront bridge to the unchanged selected overlay. Original base GTA IV references place the landmarks around Drill Street / Lompoc Avenue and Jackhammer Street / Lompoc Avenue, Industrial, Bohan, beside the unfinished Northern Expressway approach. Independent visual review supports this named local connection. See the base-game guide.

The retained resource digest was rechecked unchanged; complete-count/normal-loading markers and actual HIDDEN/SHOWN markers remain available, with zero C# error entries. The latest same-camera Game-only screenshot pair was automatically opened locally. Exact media, resource identities and coordinates remain private. This is new evidence after #41's initial inconclusive result, not a claim that all its acceptance criteria passed.

Next: pin distinctive road, pavement and road-height-change checkpoints on the exact retained mesh and complete local owner location confirmation. Patchy overlay rendering alone proves neither complete coverage nor gaps. Before any authorized paired measurements, freeze numeric tolerance and repetition rules; compare identical coordinates and reject unavailable results. No measurement tooling, host-game launch, ground agreement or wall proof occurred. Draft #38 still awaits owner source approval; #20 remains open.

Source implementation unchanged: 2f228b4ae128090d59dde36ffe67cdd916ed5ec6. Documentation/evidence revision: 913370c7c400a68dc797919c7c83aadd8e141cfa (pushed on the existing task branch).

python3 scripts/verify.py: 73 tests and 64-document/context checks passed. Independent documentation Standards review: 0 findings; Spec review: 0 findings. These reviews did not reproduce private runtime checks.

@Jpatching

Copy link
Copy Markdown
Owner Author

Checkpoint preparation revision: dca76b746bc021e846a44570790adcfd089836ee, pushed on the existing implement/gtaiv-composite-collision branch. Source implementation remains 2f228b4ae128090d59dde36ffe67cdd916ed5ec6.

Four exact decoded mesh-centroid candidates are retained privately: ordinary road beside Burger Shot, the pale paved margin, and lower/upper points on the same unfinished-road carriageway. A closer actual Hide/Show pair was captured and automatically opened locally. Independent image review corrected trailer/verge pavement targets and the divider-adjacent upper target; all four corrected image candidates are supported. Underpass and ambiguous intermediate/lower-layer associations were excluded. The retained digest/count checks match and live loading/visibility markers remain available, with zero C# error entries.

Qualification remains incomplete. Camera-to-image association uses Inspector display precision. Exact intended surface/layer association and local owner location confirmation remain pending. This does not mark all #41 criteria passed or establish active GTA contact.

Comparison rules are frozen before any paired GTA observations: three valid readings per point; maximum spread 0.02 m; every reading within 0.05 m absolute vertical error of the mesh prediction at identical fixed horizontal coordinates. Unloaded, failed, unstable, non-finite or wrong-layer results are unavailable. Any stable valid failure gives disagreement; only all complete passing points give agreement; otherwise inconclusive. Do not fit offsets, average away a failure or drop points after observing GTA results. Agreement would cover these ground points only; walls remain separate.

No new ground-query/comparison implementation, host-game launch or paired measurement occurred. A stalled private clipboard helper was stopped by its exact identity; no result from it is used. Coordinates, geometry, identities and media remain private. See checkpoint preparation.

python3 scripts/verify.py: 73 tests and 65-document/context checks passed. Independent Standards review: 0 findings; Spec review: 0 findings. No new implementation or behavioral TDD cycle is claimed for documentation/inspection preparation. Draft #38 remains pending owner source approval; #20 remains open. Next: resolve precise surface association and local confirmation before a measurement slice.

@Jpatching

Copy link
Copy Markdown
Owner Author

Superseded by combined candidate #69: this PR head is contained in e0bc36c. Closing the redundant review entry under the owner-approved cleanup; branch and commits remain preserved. #61 owns current evidence and #20 owns acceptance. Closure does not establish gameplay acceptance.

@Jpatching Jpatching closed this Oct 14, 2026
@Jpatching
Jpatching deleted the implement/gtaiv-composite-collision branch October 15, 2026 22:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant