Hot Wheels: Stunt Track Driver 2
Hot Wheels: Stunt Track Driver 2 — Get ’N Dirty
- Developer
- Semi Logic Entertainments, Inc.
- Publisher
- Mattel Interactive
- Version
- 1.0 (shipped ReadMe)
Hot Wheels: Stunt Track Driver 2 — Get ’N Dirty is a Windows racing game developed by Semi Logic Entertainments and published by Mattel Interactive in 2000. It includes outdoor courses and a custom track editor.
This game meant so much to me growing up, from being one of the first PC games I ever played, to being formative in my love for Video Game OSTs. Revisiting it on the horizon of turning 30, with all of my knowledge now, through the lens of excavation, has absolutely blown me away. I think you’ll want to see this too… 👁️👁️
Omitted editor pieces
The normal editor offers 25 selectable pieces. Its shared scene list has 27 entries, including the grid and base. These additional scenes are outside the normal selection and saved-track paths.
Browse the 26 findings in this section
Omitted from normal editor selection
Juggler
Link to this discovery ↗juggler.lws contains a terrain tile with three openings and two ball models.
What remains unknown: Authored motion is preserved, but retail interpolation, collision and gameplay behavior have not been demonstrated.
Read about how this was found: Juggler
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Authored keys move the balls along airborne arcs. The scene is omitted from the normal editor selection.
Recorded check
The eager parser at 0x47B730 and deferred parser at 0x480BB0 consume the same 27 names. Juggler is absent; the deferred list’s sole extra-model name is 90turnl.lwo.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare juggler.lws with the 27 scene names consumed by both editor-list parsers. Follow each LoadObject dependency separately from catalog occurrences.
- Inspect the authored object keys in juggler.lws. Keys demonstrate stored motion; the inspection animation does not validate retail interpolation or collision.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 90turnl.lwo· 11,084 bytes592f45f700e583880f38c88cced3f7079ea61c1e0b037793d688f562ccb22af3edpieces.cag / 90turnl.lws· 2,051 bytes63384f77a3db3d3e52b213ef481613ad3e461241f843076123a47718f64894f4edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / pspbrwse.jbf· 185,605 byteseaf8637d9344ed0129a93a447de359719afe46a9a767bb00e844393c480fa7cdedpieces.cag / uedit.txt· 461 bytes836fcca9cd6ac863815292f8d220bb017ba01af546ac4ccc309478fc287adca4
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Bunker
Link to this discovery ↗bunker.lws contains grassy terrain resembling a sand bunker, omitted from the normal editor selection.
What remains unknown: Its intended gameplay behavior and reason for omission are unknown.
Read about how this was found: Bunker
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
A denser related mesh, Odip.lwo, uses the same texture and material definition.
Recorded check
Bunker has 258 vertices / 497 triangles; Odip has 1,089 / 2,048. Their bounds and SURF bytes match. 249 Bunker vertices occur exactly in Odip; the greatest nearest-vertex distance is about 0.100106 model units.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare bunker.lwo and Odip.lwo by vertex coordinates, bounds and individual PNTS, POLS and SURF chunks. Keep full-file equality separate from chunk equality.
- Check bunker.lws against the selected scene list and distinguish Odip’s material reference to bunker.tga from a scene loading Bunker.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / bunker.lwo· 8,384 bytese408e4733d71671099fe23e2a8f37a8d04650c0cf7fd531f60b49de57c469390edpieces.cag / bunker.lws· 1,407 bytes8e779407b6da9a91a611fa744098c8717a6cbd96b6445a86ea5b9b37c540404bedpieces.cag / bunker.tga· 196,652 bytes6716a18e9e6b5797ded8c2381f8cd4fcd88b30423c93e76b56057652f676e7c2edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / Odip.lwo· 33,866 bytesb031011ca05ee61cb15caf79fdfab7282961b2c1264ed885463a8483e6533b9fedpieces.cag / pspbrwse.jbf· 185,605 byteseaf8637d9344ed0129a93a447de359719afe46a9a767bb00e844393c480fa7cdload.cag / cdrefmap.tga· 196,652 bytes975d890f7e4f35231d1b6e00e92c4352eaae8c0abd899e4c799184ae21507338
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Pipe family
Link to this discovery ↗strbentpipe.lws depicts exposed pipe openings in a mound. straight_pipe.lws is also omitted; straightpipe and strbentpipe have matching unique point and triangle-coordinate sets at the tested precision.
What remains unknown: The geometry comparison is precision-bounded. Related geometry does not establish development order.
Read about how this was found: Pipe family
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Ptunnel is a related partial-geometry variant.
Recorded check
The scene contains a static model with 403 vertices and 724 triangles. straight_pipe.tga is also named by Ptunnel.lwo and straightpipe.lwo; sharing that image does not prove selection of any complete assembly.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Follow strbentpipe.lws to strbentpipe.lwo. Search complete model basenames in scene LoadObject records; inspect material references independently.
- Compare with straight_pipe.lws and its model as a related configuration. A scene reference is stronger than an archive catalog hit, but still needs a route from the normal editor list.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / Ptunnel.lwo· 14,398 bytesb2497d5155a2bc0d48051123ba3f671c9a53a6600730a4aa862f41c6f2ed3023edpieces.cag / straight_pipe.lws· 1,392 bytesb3c08141da2871c8c26f1dbd5b0699fbf4e965bb7d187ec7468e73411faeb87eedpieces.cag / straight_pipe.tga· 197,147 bytesff392d733b7ce555ab4cc8b72ef9097cd41c0d9bf35147586a13be0d3e132aa0edpieces.cag / straightpipe.lwo· 13,484 bytes5a206dcf7a634ba9df2e839619025d92ea9ab50f01e28bb594f641d1ab934f82edpieces.cag / strbentpipe.lws· 1,435 bytes1ec9047ea01b8e75582ea4824a4982fae7edf0c69694aeaaad66013942596c65uedit.cag / bentpipe.tga· 16,428 bytesb1e293b8f74cb506420cb21a8572a641a70bf1336687ec71a3e440760b318f2b
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Raptor box
Link to this discovery ↗raptorbox.lws contains a sandbox with a bucket, shovel and green dinosaur toy.
What remains unknown: The sandbox is omitted from the editor list; dinosaur subjects in campaign footage are a separate question.
Read about how this was found: Raptor box
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Sbox.lwo preserves the same geometry with different material settings.
Recorded check
The 948-vertex / 1,717-triangle models have identical point, polygon and surface-name chunks. Material #1 instead names raptorboxM0CL.tga in Raptor box and 256grass.tga in Sbox.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Extract PNTS, POLS and SRFS chunks from raptorbox.lwo and Sbox.lwo and compare their bytes. Compare SURF definitions separately.
- Preserve archive-qualified texture identities: edpieces/rapbox.tga and uedit/rapbox.tga differ. Neither shared geometry nor a matching filename establishes another selectable piece.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 256Grass.tga· 196,652 bytesbcc2c51489dbfb0e022efa0d3a2db700778b0bb62c56a605bf28deee8f59c1ceedpieces.cag / rapbox.tga· 261,785 bytese4dd940d574386a666511093e88cb7f9b86293558fe189b8bab1ba93250e5f72edpieces.cag / rapbox_Material #2_CL.tga· 261,785 bytese4dd940d574386a666511093e88cb7f9b86293558fe189b8bab1ba93250e5f72edpieces.cag / raptorbox.lwo· 29,412 bytes6aeb241e33182d67ce550efef5f32b86330da2faf925e9e8ef7f6eb4794af7acedpieces.cag / raptorbox.lws· 1,489 bytesba3a2a939ee1a71d71a1d7dea0d74d4e58d879cd66718fb760608599f866955fedpieces.cag / raptorboxM0CL.tga· 196,652 bytesbc33999a2b1b90796021f7cf80e265fa88bb758862c9df750d0ca87982668622edpieces.cag / Sbox.lwo· 29,472 bytes7d226117e8394a45715b0f770b29706f33e2707857f06fd7d9285622b0ffeed7uedit.cag / rapbox.tga· 12,332 bytes6d5d2d07128b8b81a54a0f08c2de8f4305bd1420d4c3beaeb7d1209c3d953f0e
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Spinning top
Link to this discovery ↗spintop.lws combines terrain and a top with three authored motion keys. spinner.lws places the same top with different ground and a small initial height difference.
What remains unknown: The keys do not establish retail playback, collision behavior or the order in which the scenes were created.
Read about how this was found: Spinning top
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Both scenes are omitted from the editor selection.
Recorded check
Both scenes reference the same top and are omitted from selection. spinner.lwo and spintopgnd.lwo are byte-identical ground models; spintop.lws instead names spintop_grnd.lwo.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read the top’s ObjectMotion keys in spintop.lws and spinner.lws, and compare their LoadObject names against the editor list.
- Compare the first top Y value: 1.75 in spinner versus 1.7 in spintop. These stored differences do not establish scene chronology or retail playback.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / base.tga· 49,196 bytesd133c4e53cfa2001dc58de9319cd1bcd1b6cb39d76510394838173faa44097f4edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / spinner.lwo· 7,378 bytesae0448bd169627d95e7c84eee947fa0f8ab6bbe7a46b774a0a1f2142b7e6bd51edpieces.cag / spinner.lws· 2,102 bytesb29d6432894b7ec3c6e514736e6996dbc20572b1003e1e015a803e863e6360b2edpieces.cag / spintop.lws· 2,006 bytes725fd22c47d15ba3e565e732bffd4311d1c2ca6d1a8346195cf35ad3cbf0711dedpieces.cag / spintop_grnd.lwo· 33,780 bytese79854e46823baf456da4fb9891fcd32c21fed9224d1b99e48a25b1677534a08edpieces.cag / spintopgnd.lwo· 7,378 bytesae0448bd169627d95e7c84eee947fa0f8ab6bbe7a46b774a0a1f2142b7e6bd51edpieces.cag / spintopM0CL.tga· 197,147 bytesf99152e87d7841cbc57f2898a9d08f13a5cc62092d69a323d2e485fe2c8bdb86uplay.cag / base.tga· 196,652 bytes1be7339d7765f16572a575125d9f1cd90b8939d340b7e76a22f36486fe2a4d31
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Sprinkler
Link to this discovery ↗sprinkler.lws contains a base and separate sptop.lwo head.
What remains unknown: Water emission and intended gameplay effects are unverified.
Read about how this was found: Sprinkler
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Two authored head keys specify 720 degrees of heading rotation. Water emission and intended gameplay effects are unverified.
Recorded check
The head has two authored keys taking heading from 0 to 720 degrees. The base’s UV sidecar matches 858 polygon records.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Follow sprinkler.lws to the static sprinkler.lwo base and separate sptop.lwo head. Read their ObjectMotion keys.
- Check normal scene selection separately. Rotating-head keys do not supply evidence of water emission, collision or a functioning gameplay effect.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / sprinkler.lwo· 15,788 bytes793447ca9ea5db4912f33ba5558d9df22bd06a82d2e34b5de8d6963929728d77edpieces.cag / sprinkler.lws· 1,739 bytes42d3f078580f7475074776d833c3a4bfa226934a715573a4fbd018909e935a31edpieces.cag / sptop.lwo· 2,886 bytese36171712a77b5ca63d1258e1eb9cb6c8fcdf57d71fdff5d2ad12aaf93ddc7f3
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Robot and variants
Link to this discovery ↗robotrun.lws assembles an eight-part humanoid robot with limb motion and body bounce.
What remains unknown: Neither the gun-shaped prop nor authored motion establishes a functioning weapon or gameplay mechanic.
Read about how this was found: Robot and variants
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
An alternative environment includes three robot paths; the inspected normal loader selects a different, robot-free environment. A separate robot.lwo carries a gun-shaped prop and has 4,328 triangles; no recovered scene references it. Weapon functionality is unverified.
Recorded check
The normal call requests uplay.lws, which has no robot filenames. uplayrobot.lws contains three eight-part assemblies; the eight body meshes have exact PNTS/POLS matches across edpieces and uplay.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare robotrun.lws with uplayrobot.lws, then inspect the executable’s normal environment-load call at 0x482B3C to scene loader 0x460820.
- Keep the alternate master keys through frame 336 distinct from its saved LastFrame 60. Neither proves retail playback through the full authored path.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / robotrun.lws· 4,477 bytes6f75026dbd3a89abe7abdecb58bf20ace4cd355a38ba50b1878e812d7f5d7d83uplay.cag / uplayrobot.lws· 21,255 bytes6b8a8d3365f36180254041275b7e30ac3ab42c18f088d20740caa2c864ca2881uplay.cag / uplay.lws· 20,980 bytes45cbf46c407daec1df18bcff26d6eea8da4ee37b7dee4f09c5b127ce1e207692uplay.cag / robotrun2.lws· 5,159 bytes38410a2a205cce6af6aeb08a5fee8d910d385fd3e9864598a1bee59868c94e51uplay.cag / robotrun.lws· 4,477 bytes6f75026dbd3a89abe7abdecb58bf20ace4cd355a38ba50b1878e812d7f5d7d83
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Spider
Link to this discovery ↗spidey3.lwo is used by 90turnSPIDEY.lws and spdwlkx2.lws, neither selected by the normal editor.
What remains unknown: The movie match is likely; exact production-model identity, walking and skinning remain unproved.
Read about how this was found: Spider
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
The former includes a 57-bone rig, leg and mandible controls, and a returning movement route. Exact walking, skinning and gameplay behavior remain unverified. The model likely corresponds to the spider seen in the Underground course movie: comparison shows a similar back and distinctive mandibles, while green eye details become visible during the close pass. Cached spdrtop.iff and spdrface.iff previews also resemble its imagery. This finding concerns the omitted editor scenes, not absence of the spider from retail footage.
Recorded check
Both spider scenes are omitted. The turn assembly contains a 57-bone rig. Its turn and coin share transforms with 90turn.lws, but the coin controller’s EndBehavior differs.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Find exact spidey3.lwo LoadObject references and compare 90turnSPIDEY.lws and spdwlkx2.lws with the editor list.
- Treat the Underground film comparison as a likely subject match. Editor omission does not imply that the spider was absent from campaign footage, and the preview does not solve the original skinning or IK.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 90turn.lwo· 12,436 bytes698e9193642c50ed6f1997dac63e953de3c445a427747f120de996fb4a1c1cbaedpieces.cag / 90turn.lws· 2,050 bytes7e46d26ad6de70195908f9cc8492d27140a771dfc13e48fd5079a1954ddd232dedpieces.cag / 90turnl.lws· 2,051 bytes63384f77a3db3d3e52b213ef481613ad3e461241f843076123a47718f64894f4edpieces.cag / 90turnSPIDEY.lws· 26,449 bytes84e53fe7d0de8cf39aa584c5a2f0f76389e266832cad0f2775af3b701113473bedpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / spdwlkx2.lws· 25,340 bytes30c1fb3af60e48a036fc4177d7a5ccaadde0d094120dc7c825e3ba28ab9d2c0dedpieces.cag / spidey3.lwo· 28,870 bytes37734bfbab10364eb17d2a660b22fca0533b42c63096395019b64e2aacbed28duedit.cag / butt.lws· 4,216 bytes4ac57d6cdcf2da449b8bccf954894a2510bac0398a308cc3c89fdf15ec9ce8e2
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Ducky
Link to this discovery ↗A duck-and-terrain arrangement survives outside the normal editor scene selection.
What remains unknown: No movement, collision response or gameplay interaction has been demonstrated.
Read about how this was found: Ducky
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
The finding concerns the assembled editor content, not whether a duck appears in campaign footage.
Recorded check
Ducky.lwo is named by its own scene; its materials use ducky.tga and shared set1.tga. The scene is omitted from the normal list.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read Ducky.lws and check its sole static model against exact LoadObject basenames in all selected scenes.
- When auditing references, keep shared terrain-image use separate from use of the complete duck-and-terrain assembly.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / Ducky.lwo· 12,984 bytes5037a2fd46104f817566ed3d28ee038b5c0193ff8efda849da1a9a897fc2c7c6edpieces.cag / Ducky.lws· 1,423 bytesf51d8a18e41d50418cb1bafeb2248229c94092358edd13b0267c801f35d70bc4edpieces.cag / Ducky.rar· 4,463 bytesd26d4245af1108526c8029d1bc073f5ce42794f03b860e423d7edb20a5e0f233edpieces.cag / ducky.tga· 147,500 bytes52e2be86ae5aeafb001d9aa97ad90d52b667e4be4b60191298906d43a546d4bbedpieces.cag / set1.tga· 196,652 bytes8421fabf78c07c34fa103be8ce95a057448c4f662a84a9b294c6ba719e7bf9b9
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Wagon
Link to this discovery ↗A static wagon track-piece scene remains in the editor archive but is omitted from the normal selection.
What remains unknown: Its intended gameplay behavior and reason for omission are unknown.
Read about how this was found: Wagon
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
No alternate whole-model geometry copy was found in the bounded comparison.
Recorded check
The scene has one identity pose. The model declares four diffuse-color materials and no image textures. Four two-point polygons are omitted from the inspection render.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read Wagon.lws, then inspect wagon.lwo’s polygon records and SURF definitions.
- Separate stored polygon records from triangulated visible faces. A static handle and wheels do not establish animation or interaction.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / wagon.lwo· 17,044 bytes314670debcdb797f2a67b5e560d50f019f70e5afcf3853d542a1e13e8003e766edpieces.cag / Wagon.lws· 1,419 bytesf0b041d408790844de59f8938605e6e70fa7febceb79e87569927d71ae9011f1
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Mushrooms
Link to this discovery ↗shrooms.lwo contains terrain and three mushrooms with 414 triangles each.
What remains unknown: The relationship between the two mushroom groups and their complete original materials is unresolved.
Read about how this was found: Mushrooms
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
A separate unreferenced 4way_Part1.lwo contains four mushrooms with 88 triangles each. The additional group is not simply the same stored mushrooms moved into a different arrangement.
Recorded check
The model has 916 vertices and 1,754 triangles, with one identity pose. Five named mushroom images were absent from the recovered member-name inventory.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read shrooms.lws and count the mesh’s PNTS and triangulated POLS data. Compare its named image dependencies against the decoded-member inventory.
- That exact-name check does not exclude renamed images. The diffuse-color preview preserves geometry but does not recover the missing mushroom materials.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / shrooms.lwo· 31,466 bytesd42ea8d5d86479dcd1eb94b910e471d98dd98896ff09ff6114564ea1be0a1215edpieces.cag / shrooms.lws· 1,410 bytes43fec857febaad9e179c4e86969cb04c93a6b7c3adf8c270fee05151c8bf8d90
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Tunnel
Link to this discovery ↗tunnel.lws depicts a low dirt mound with a recessed passage-like shape.
What remains unknown: Traversability has not been tested; resemblance to a selected model does not establish identical geometry.
Read about how this was found: Tunnel
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its geometry differs from the selected ptowel model in the original-coordinate comparison. Traversability is unverified.
Recorded check
Tunnel has 239 unique points / 460 triangles; ptowel has 273 / 512. Their coordinate sets do not intersect in that frame; the maximum bidirectional nearest-point distance is about 2.5 units.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare tunnel.lwo and selected ptowel.lwo in original coordinates, rounding to five decimals without fitting alignment.
- Reject but_tunnel.lwo and Ptunnel.lwo substring hits as exact tunnel.lwo references. The preview’s basename resolution does not prove the original historical path loaded successfully.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / ptowel.lws· 1,999 bytesdc9617c29bef196bf429d216d4523dae81bbcc2ba0b9609fe757fec5273b9789edpieces.cag / Ptunnel.lwo· 14,398 bytesb2497d5155a2bc0d48051123ba3f671c9a53a6600730a4aa862f41c6f2ed3023edpieces.cag / tunnel.lwo· 7,708 bytes6df1f3ff4b4384c212b2b41446536596487b6497187292e7cfc5c796c1d1f3e3edpieces.cag / tunnel.lws· 1,417 bytesdd5f453abb3883cbe1d52163ba9d8a5fb9cd9997eceab10a24ba80bb27e3391auedit.cag / butt.lws· 4,216 bytes4ac57d6cdcf2da449b8bccf954894a2510bac0398a308cc3c89fdf15ec9ce8e2
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Broken pipe
Link to this discovery ↗A static damaged-pipe configuration survives outside the editor selection.
What remains unknown: The damaged shape is static evidence, not proof of a runtime breakage mechanic.
Read about how this was found: Broken pipe
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
It differs from the compared straightpipe and bent-pipe geometry. The model does not establish a runtime breakage mechanic.
Recorded check
Broken pipe has 589 rendered triangle records but 587 unique triangle geometries and 312 unique positions. No same-coordinate point or triangle overlap was found with the two compared pipe models.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare broken_pipe.lwo with straightpipe.lwo and strbentpipe.lwo using unique, unordered triangle-coordinate sets at five decimals.
- Read its single static scene pose. The damaged shape is stored geometry, not an observed breaking animation.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / base.tga· 49,196 bytesd133c4e53cfa2001dc58de9319cd1bcd1b6cb39d76510394838173faa44097f4edpieces.cag / broken_pipe.lwo· 10,284 bytes47b8620640e937e12dbc8868551c001f5327f45226e0eb5e7d83ef1219020edbedpieces.cag / brokenpipe.lws· 1,416 bytesd512a7cac989a989f63fc3ca8d1dee6e83dfc3e0fb9d3fabe03d4bb2371f040euplay.cag / base.tga· 196,652 bytes1be7339d7765f16572a575125d9f1cd90b8939d340b7e76a22f36486fe2a4d31
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Double helix
Link to this discovery ↗A double-helix track configuration survives outside the editor selection.
What remains unknown: A replacement relationship with the selected helix slide has not been established.
Read about how this was found: Double helix
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
It is distinct from the familiar selected helix slide; no replacement relationship is claimed.
Recorded check
Double helix contains 1,359 vertices / 2,584 triangles, versus the selected slide’s 161 / 272. All 2,584 double-helix UV polygon records validate.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare dblhelix.lws with selected helix.lws and follow each to its own model; verify the UV sidecar against polygon indices and surface assignments.
- The two names do not establish a replacement sequence. Keep shared base.tga outside any claim that every dependency is unused.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / base.tga· 49,196 bytesd133c4e53cfa2001dc58de9319cd1bcd1b6cb39d76510394838173faa44097f4edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / dblhelix.lwo· 42,558 bytesb28fa57ef02f91ea7a9b11584a89c7fddfb0523440f7322b33f4c0ae309ed2c2edpieces.cag / dblhelix.lws· 1,455 bytesb4cfee15c9a8d2032a176f29b70217406b8c86bfb12ed4c3ba4c1d48bbb70088edpieces.cag / helix.lwo· 7,146 bytes9eda79c138e28c4ff5b1fe4789bdc9da1c877fefe8daa20ae5d51272fc6f4811edpieces.cag / helix.lws· 2,077 bytescaa8a91bd1c791d66e1a06abb382dd03307fd7dcb7387b0128bb38878833ef08uplay.cag / base.tga· 196,652 bytes1be7339d7765f16572a575125d9f1cd90b8939d340b7e76a22f36486fe2a4d31
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
90tunturnR turn
Link to this discovery ↗90tunturnR is an omitted terrain-turn configuration distinct from the four selected turn models tested.
What remains unknown: The exact configuration is omitted; its familiar appearance does not establish normal selection.
Read about how this was found: 90tunturnR turn
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its retail-like banked-turn appearance does not establish that the exact configuration is selected.
Recorded check
No complete match was found. The candidate has 289 points / 512 triangles; the maximum overlap with 90turnl/r is 64 points and two triangles.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare 90tunturnR.lwo with 90turnl, 90turnr, T90turnl and T90turnr, testing four Y quarter-turns and optional X reflection about the original origin at five decimals.
- 90tunturn.lwo instead matches 90turn.lwo’s 406-point / 726-triangle coordinate sets. Do not infer a left/right pair from the two tunnel-turn filenames.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 90tunturn.lwo· 21,350 bytes00ba8d39dba7238d37e901f19840cba5e81e797f82774320aaa84aaec43137acedpieces.cag / 90tunturn.lws· 1,435 bytesbffa26c74d65bf6717eb080b0362e69823053e095abf2ff779b29781ac625779edpieces.cag / 90tunturnR.lwo· 8,684 bytesa3b8ee92d00881da718d5f0f1edde7921b283f994caa3f4c3ad8294493b78bbfedpieces.cag / 90tunturnR.lws· 1,411 bytesda71203638340fc8356c3d3d4423f337fc12b06e19c68d261d5010c9c57f41b0edpieces.cag / 90turn.lwo· 12,436 bytes698e9193642c50ed6f1997dac63e953de3c445a427747f120de996fb4a1c1cba
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
High-jump terrain
Link to this discovery ↗hijump is an omitted terrain configuration with dirt and grass surfaces.
What remains unknown: The final grass rendering is incompletely reconstructed. Inspection artifacts are not retail defects.
Read about how this was found: High-jump terrain
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its appearance resembles other editor terrain, but the investigated scene is not selected.
Recorded check
No coincident point/triangle sets were found in those comparisons. Its 574 triangle records reduce to 524 unique triangle-coordinate sets when duplicates and winding are ignored.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare hijump.lwo with 90turn.lwo and the four selected turn models under origin-based Y quarter-turns and optional X reflection at five decimals.
- Exclude but_hijump.lwo substring hits. Grass orientation and masking are inspection-render limits, not evidence of a retail visual defect.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 90turn.lwo· 12,436 bytes698e9193642c50ed6f1997dac63e953de3c445a427747f120de996fb4a1c1cbaedpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / hijump.lwo· 10,762 bytes67ce97296e32305820ffafc008c231577a4b974ea45a8cf6fdd6866b9437dea0edpieces.cag / hijump.lws· 673 bytesecc3508876e9b41fdef4522f9f2a581fbed295ca06daf2cbc8136cb633a2ef73uedit.cag / butt.lws· 4,216 bytes4ac57d6cdcf2da449b8bccf954894a2510bac0398a308cc3c89fdf15ec9ce8e2
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Trench family
Link to this discovery ↗intrench, outrench, humptrench and straightun form a group of omitted channel-like terrain configurations.
What remains unknown: The pieces are grouped by appearance and structure; common derivation is not established.
Read about how this was found: Trench family
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Sturn and trenchpot add bridge and flowerpot assemblies. Tbase is another unreferenced straight channel. These are editorially grouped; common derivation is not established.
Recorded check
No complete selected-model match was found. Related Sturn shares 318 of straightun’s 346 unique triangle geometries in original coordinates; this is substantial partial reuse, not whole-model identity.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare intrench, outrench and humptrench with all 29 models directly named by selected scenes, using four Y quarter-turns and optional X reflection at five decimals.
- Treat straightun, Sturn, trenchpot and related terrain as an editorial family. Do not assign a common derivation, intended connection order or identical base merely from appearance.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / grid.lwo· 366 bytes2270d4d318a0bfccf6a8f91eb1a4284e21a19fcbf2e4abe25a78ce4d0cf42a50edpieces.cag / humptrench.lws· 444 bytes0ea3fa49cca66b060ae7f140c0a8cd52ee6f5f3723d3d5c483f733bc17dd9bfeedpieces.cag / intrench.lws· 1,409 bytes5c43a70f286d730e5e88c8645ac6fa05792d821c8fea43da7af536da2b6c78d3edpieces.cag / outrench.lws· 1,409 bytes23597a1a6e78deffbab71febf546fb44f663f858ad4465eeb424a0f1e2184d2e
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
POND terrain
Link to this discovery ↗The edpieces POND configuration is omitted from selection and differs from the same-named track-selection asset.
What remains unknown: Partial reuse and a familiar style do not make the complete arrangement a selected piece.
Read about how this was found: POND terrain
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its retail-like appearance and partial terrain reuse are retained as qualifications.
Recorded check
The editor model has 265 vertices / 464 triangles; the selection-menu model has six / four. The executable does contain pond filenames, so literal-name absence is not the claim.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Resolve POND by archive, then compare edpieces/POND.lwo with seltrack/pond.lwo and inspect each scene’s actual LoadObject path.
- The editor model shares 26 same-coordinate triangles with each of hijump, outrench and humptrench at five decimals. Partial reuse does not select the complete omitted arrangement.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / POND.lwo· 9,502 bytesfd5a85005a957ef9b7830f98dbc688fbd4354d1307b088fd5d55e37fe8e794d3edpieces.cag / POND.lws· 1,418 bytes61e0a295858bef508f1babbb9066db76544a15496849e5b1158a469223c0a35egame.cag / Copy of pond.lws· 30,382 bytesb543527031386d8a7c326d4b150df4cacdec076a0cb7dae2b80121318e00269dgame.cag / pond.lws· 29,207 bytes503120a305d354529d253773ff0cc2c84edb7be569fb79f23d1d69e91fa526d2seltrack.cag / pond.lwo· 518 bytesf62b0990cd50a71513f24461b6510cc39c72bd8935db5e78d6469a175b056c9e
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Puddle basin
Link to this discovery ↗Puddle forms a basin assembly outside the normal scene selection.
What remains unknown: The assembly is omitted, but its shared water and coin assets are not independently unused.
Read about how this was found: Puddle basin
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Shared water and coin assets are not counted as separate unused content.
Recorded check
The omitted assembly uses puddle.lwo, pondw.lwo and a coin. T4way explicitly uses pondw.lwo and coin.lwo too. The basin has 266 vertices and 705 triangle records, or 509 unique coordinate triangles at five decimals.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read puddle.lws’s three object records, then compare them with selected T4way.lws.
- Exclude the but_puddle.lwo button hit and classify the omitted basin assembly, not its shared water and coin, as the finding.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / coin.lwo· 1,724 bytes788acb906cc711d7aad1204e0f3bb2ce1c838de07a416fa33a850127265996d4edpieces.cag / pondw.lwo· 844 bytes8596130d5ab9de5cd8c924263ad824e156e27bb58a75d62793bed83c92895b02edpieces.cag / puddle.lwo· 10,498 bytes2c028fc3815c7691c01ed9946b1142b7822c91926fa98e8c0c95cc834b05015dedpieces.cag / puddle.lws· 1,905 bytes4e8b22f145f51fb450c3305585ba3f5e57b83b9fda10fa797a3ac6a02235720aedpieces.cag / set1.tga· 196,652 bytes8421fabf78c07c34fa103be8ce95a057448c4f662a84a9b294c6ba719e7bf9b9game.cag / coin.lwo· 1,724 bytes788acb906cc711d7aad1204e0f3bb2ce1c838de07a416fa33a850127265996d4main.cag / coin.lwo· 3,910 bytes38af3fa126e68b9ea822a49903b19e5922082485a88a848c740cc87c966dfa2fratings.cag / coin.lwo· 1,672 bytes8c6b1c821ad58daf60dc4678c058c61db1def6a2be36fbf4dff3423cc991a0ebuedit.cag / butt.lws· 4,216 bytes4ac57d6cdcf2da449b8bccf954894a2510bac0398a308cc3c89fdf15ec9ce8e2
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Water-jump assembly
Link to this discovery ↗Two omitted water-jump scenes preserve matching corresponding terrain and water geometry.
What remains unknown: Water rendering and intended gameplay behavior remain incompletely reconstructed.
Read about how this was found: Water-jump assembly
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
They are treated as one related assembly, not two independently different obstacles. The water rendering remains incompletely reconstructed.
Recorded check
Each pair has identical geometry chunks. Terrain has 144 vertices / 277 triangles; water has 25 / 32. Both scenes use static identity poses and are omitted from the list.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare PNTS/POLS bytes for jump_ow.lwo versus jumpwater.lwo, and straight_wat.lwo versus straight_wapl.lwo. Read both jump_water.lws and jumpwater.lws.
- Count the paired scene/model names as one configuration. Whole-file equality, finished water rendering and runtime effects are separate questions.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / !water.tga· 49,196 bytes41c62c18f4d92c806ff2f7436176d91d915d2dad5ea01703a40e45778f16de76edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / jump_ow.lwo· 4,790 bytesf613975af82010c8cf4bea837652224b9d44b347e309d214cfecdd79e0397481edpieces.cag / jump_water.lws· 1,582 bytes844805a1ac27b4d82b9e53c1d969d53ae3e0d4dc34edce2d3ce895510da0faa7edpieces.cag / jumpwater.lwo· 4,828 bytes3f1ab6e60e0304d39b583df06d67f2b0fe420cfdca0d3dcb96fb76110c1d062dedpieces.cag / jumpwater.lws· 1,638 bytese2d7e5ef533b3c71142955cb44387c62331d01ce519133bc0d5d68d473a8d31aedpieces.cag / jumpwater.tga· 197,147 bytes4dda5d52cab9841db22b2132e216713df1eef22ea5fb6f04c570c2109d23e151edpieces.cag / straight_wat.lwo· 898 bytesd6050266a650164dc9c478987214f2d7930ff2a8276bb36f5cd1ecb467f5db24
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Hill looping structure
Link to this discovery ↗hill preserves an omitted looping structure distinct from the compared looping models.
What remains unknown: Intended traversal behavior is unverified.
Read about how this was found: Hill looping structure
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its intended traversal behavior is unverified.
Recorded check
Hill has 398 vertices / 786 triangles and stored diffuse RGB 28,28,177, without an image map. The tested same-coordinate triangle sets do not overlap with those three relatives.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Inspect hill.lws, hill.lwo’s mesh and diffuse material, and compare it with selected loop/helix and omitted dblhelix in original coordinates.
- Use exact LoadObject basenames: overhill.lwo is not a hill.lwo reference. Neither the looping shape nor the filename establishes drivability.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / hill.lwo· 12,764 bytesf99d3d4e3697de91c17be94bed82ef853905caf7878f69e147b6e54543bf0011edpieces.cag / hill.lws· 1,439 bytesb359421273d7b3fc214ff5c8d16a2e4aa1d11701e1aee7d33cd8f8cf7c86bce5edpieces.cag / hills.lwo· 7,910 bytes928c7f9f07122a0237b34750ce1b606d2e8048cd30379d4b90c0db7408b84e7dedpieces.cag / mound.lwo· 7,910 bytes928c7f9f07122a0237b34750ce1b606d2e8048cd30379d4b90c0db7408b84e7dedpieces.cag / mound.lws· 1,385 bytesfe9915f0d12aeae98419188b4ce830896dc1157bb30f07547556960c8456b56fedpieces.cag / mound.tga· 197,147 bytes0a902dafce4f85597e3ff8a88756ac56d848310102edff944d7fa0ebe8bee4cbedpieces.cag / overhill.lwo· 6,508 bytesb6f8de80689a19a60d64fb0878c579d4976a7b2a589014d1e02551d793fd64ddedpieces.cag / overhill.lws· 1,397 bytes8481e746eaa9896c2802a197eb5680af93cee6c2f2294326e6c1962ebeb84fd3
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Mound
Link to this discovery ↗mound and hills preserve identical PNTS/POLS geometry.
What remains unknown: Identical stored geometry does not explain the different names or development history.
Read about how this was found: Mound
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
They represent one terrain finding under different names, not two separate pieces.
Recorded check
Their geometry chunks match. Mound has 243 vertices / 471 triangles and is loaded by omitted mound.lws; no decoded scene names hills.lwo.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare mound.lwo and hills.lwo’s PNTS/POLS chunks, then search exact LoadObject basenames for each.
- Treat hills as a geometry alias/variant within this finding. Material and full-file equality, naming rationale and development order are not established.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / hill.lwo· 12,764 bytesf99d3d4e3697de91c17be94bed82ef853905caf7878f69e147b6e54543bf0011edpieces.cag / hill.lws· 1,439 bytesb359421273d7b3fc214ff5c8d16a2e4aa1d11701e1aee7d33cd8f8cf7c86bce5edpieces.cag / hills.lwo· 7,910 bytes928c7f9f07122a0237b34750ce1b606d2e8048cd30379d4b90c0db7408b84e7dedpieces.cag / mound.lwo· 7,910 bytes928c7f9f07122a0237b34750ce1b606d2e8048cd30379d4b90c0db7408b84e7dedpieces.cag / mound.lws· 1,385 bytesfe9915f0d12aeae98419188b4ce830896dc1157bb30f07547556960c8456b56fedpieces.cag / mound.tga· 197,147 bytes0a902dafce4f85597e3ff8a88756ac56d848310102edff944d7fa0ebe8bee4cbedpieces.cag / overhill.lwo· 6,508 bytesb6f8de80689a19a60d64fb0878c579d4976a7b2a589014d1e02551d793fd64ddedpieces.cag / overhill.lws· 1,397 bytes8481e746eaa9896c2802a197eb5680af93cee6c2f2294326e6c1962ebeb84fd3
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Overhill
Link to this discovery ↗overhill is an omitted ridge/path configuration.
What remains unknown: The comparison found no complete selected-model match; development history remains unknown.
Read about how this was found: Overhill
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its visual style is familiar, while the exact arrangement is unrecognized; no complete selected-model match was found under the tested comparisons.
Recorded check
No complete match was found. The scene has one identity pose; the mesh contains 200 vertices / 382 triangle records and references overhill.tga.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare overhill.lwo with the 29 directly selected models under four Y quarter-turns and optional X reflection at five decimals about the original origin.
- No arbitrary translation, scale or vertex correspondence was fitted. Familiar terrain style is compatible with a distinct omitted configuration.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / bumpy.lws· 1,359 bytes3e891beffe766027851595c2e5e13d4a5413c7dbd40906bb7d3016f4ed204df2edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / overhill.lwo· 6,508 bytesb6f8de80689a19a60d64fb0878c579d4976a7b2a589014d1e02551d793fd64ddedpieces.cag / overhill.lws· 1,397 bytes8481e746eaa9896c2802a197eb5680af93cee6c2f2294326e6c1962ebeb84fd3
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Bumpy terrain
Link to this discovery ↗bumpy preserves irregular terrain outside the editor selection. bumpyOLD has 2,048 triangles versus 512 in bumpy.
What remains unknown: The OLD filename and differing triangle counts do not establish revision order.
Read about how this was found: Bumpy terrain
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
The flat bumpyS relative is not treated as another obstacle, and filenames alone do not establish revision order.
Recorded check
Bumpy has 289 vertices / 512 triangles and no assigned image map. bumpyOLD has 1,089 unique points / 2,048 triangles. bumpyS partially overlaps selected t4way and sfinish.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare bumpy, bumpyOLD and bumpyS in original coordinates; keep raw records and unique coordinate sets separate.
- The OLD suffix does not date the models. Do not assign bumpydef.tga from filename similarity or describe every shared terrain fragment as unused.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / bumpy.lwo· 8,684 bytes948ebeb7333a0d37aa5b58cd50310e4f3f16fbbcca90f181c113f7f8bcba761eedpieces.cag / bumpy.lws· 1,359 bytes3e891beffe766027851595c2e5e13d4a5413c7dbd40906bb7d3016f4ed204df2edpieces.cag / bumpydef.tga· 196,652 bytes6c1780c8c67ffce93d232d9e8afc0fc3f0dc788bba183e1d1a8618d46e86331dedpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Straightb corridor
Link to this discovery ↗straightb is an omitted irregular corridor-like terrain configuration.
What remains unknown: Recognition and reachability of the separate newstr candidate remain unresolved.
Read about how this was found: Straightb corridor
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Its relationship to the separate newstr and straightun scenes does not supply recognition of newstr, which remains unresolved.
Recorded check
The model stores 1,316 vertices but only 300 unique positions, with 485 triangles. No complete selected-model match was found under the tested transforms.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read straightb.lws and compare STRAIGHTB.lwo with all 29 directly selected models using origin-based quarter-turn/reflection tests at five decimals.
- Duplicate vertices are not additional shape detail. Keep newstr’s separate unresolved recognition out of this finding’s verdict.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / straightb.lws· 1,409 bytesc486fcf315a79a3336fd1ff4d77066cad8f04490f1fe68242d1a3ff8b0284bf2edpieces.cag / straightun.lwo· 16,518 bytes0c67359ab7e952fdc48588106953529a7ee4c205c3a3805b842c9c7c8cc50b87edpieces.cag / straightun.lws· 1,411 bytes37436275f15468ed36637f44a691826cd0be46e2150ccdfeb581f072d7c2bccb
Examined release and shared evidence scope · Back to section
Omitted from normal editor selection
Olly and Bjump
Link to this discovery ↗olly depicts a steep dirt peak.
What remains unknown: The fitted geometric relationship does not establish which version came first.
Read about how this was found: Olly and Bjump
The editor and saved-track consumers resolve numeric piece IDs through the shipped uedit.txt scene list. The scene configuration described here is omitted from those normal selection paths. Scene dependencies and related geometry were investigated separately; similar objects can still appear in campaign movies.
Bjump shares ordered triangle indices and a near-exact height-scale/offset relationship with olly in the tested fit. They are grouped rather than counted as separate designs; chronology is unproved.
Recorded check
Both have 289 vertices / 512 triangles and identical ordered triangle-index lists. The fit gives Y scale 1.249999996 and offset about −0.002473538, with maximum Euclidean residual 2.782e−7 units.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare Bjump.lwo and olly.lwo’s ordered triangle indices, then fit corresponding vertex coordinates from Bjump to olly.
- The fit operates on model coordinates, excluding olly’s scene heading. It supports a height variant without proving which model came first.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / contents.obv· 302,703 bytes8ba24a802eb4d1553f5b80096917a0eab7b2179579cc51e9b4a877961e100ca5edpieces.cag / jump.tga· 196,652 bytes3d481f67a06d5eea8493a6f55aeb3fa61daf61aa2f9f1a032f3996862c5057acedpieces.cag / olly.lwo· 8,820 bytes813dd365b7b8f856cbb19868f4318df239d45da6e4fb4df8b0a41dc99af243dbedpieces.cag / olly.lws· 1,404 bytes5cf5c3d2e1da3b4d044e760f1c8e75949d01922f9aad274023cd24ada23a04c3edpieces.cag / Sturn.lws· 1,397 bytes2672e00d0b2c1babf4b8478a9906ce01e1d6929938c87eb87c5b4560335f1dd0edpieces.cag / trenchpot.lws· 446 bytes46c8341c04f2de35c87a1966ab1f56721dd5cc3ccdc078c9d46a4a1d45cb58deuedit.cag / butt.lws· 4,216 bytes4ac57d6cdcf2da449b8bccf954894a2510bac0398a308cc3c89fdf15ec9ce8e2
Examined release and shared evidence scope · Back to section
Unreferenced models
These model configurations have no recovered scene reference. Comparisons distinguish complete matches, partial reuse and geometric relatives.
Browse the 7 findings in this section
No recovered scene reference
Newpiece
Link to this discovery ↗newpiece.lwo contains shallow uneven terrain.
What remains unknown: The intended role is unknown; transformed or partial reuse is bounded by the recorded comparisons.
Read about how this was found: Newpiece
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
No recovered scene references it, and no complete selected-model match was found under the tested transforms. Its intended role remains unknown.
Recorded check
No scene reference or complete selected-model match was found in the recorded scope. Newpiece has 289 vertices / 512 triangles; small overlaps of 64 points/two triangles exist with some compared terrain.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Search exact newpiece.lwo scene references, then compare its coordinates with the 29 selected models and bumpy/straightb relatives.
- No newpiece.lws was recovered. A test of that hypothetical scene name must not be presented as a surviving omitted scene.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / newpiece.lwo· 8,684 bytes7ce12e33fa49e6b4123f8a48c60920dba742f695d219ddaea26b15225ed6d7db
Examined release and shared evidence scope · Back to section
No recovered scene reference
Ljump
Link to this discovery ↗Ljump.lwo preserves a low ramp configuration with no recovered scene reference or complete selected-model match under the tested transforms.
What remains unknown: Intended use and development history remain unknown.
Read about how this was found: Ljump
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
Recorded check
Ljump has 193 vertices / 356 triangles. No recovered scene names it and no complete selected-model match was found in those tests.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Search exact Ljump.lwo scene references and compare its geometry with the 29 directly selected models under origin-based quarter-turns and reflection at five decimals.
- Keep Bjump with the fitted olly height variant. The L prefix supplies no proof of intended function or development order.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / Bjump.lwo· 8,820 bytes92998b8b0c74f4c39fda0b7292af98e3dff44afe4160d03364debc1b37ad61e8edpieces.cag / Ljump.lwo· 6,108 bytes34788a4fbe191f3bf7010d69b6d81f4c56a80c01bcd4656c153f393db755f786
Examined release and shared evidence scope · Back to section
No recovered scene reference
Mirrored turn family
Link to this discovery ↗Lturn and Rturn are mirrored terrain equivalents, with S90turn2 forming an alias in the family.
What remains unknown: Partial selected-geometry overlap exists. The family is not three independent removed pieces.
Read about how this was found: Mirrored turn family
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
These names do not represent three independent findings. Partial selected-geometry overlap remains documented.
Recorded check
All three correspond under those transforms: 289 points / 512 triangles. Partial overlap with selected t4way reaches 134 points / 73 triangles in the recorded test.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare Lturn with X-reflected Rturn and untransformed S90turn2 using unique point and unordered triangle-coordinate sets at five decimals.
- This ignores winding, materials and duplicated coordinates. It establishes one geometric family, not three byte-identical files or wholly novel terrain.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / Lturn.lwo· 10,400 bytesfbca6305970046882744891f16a802d898b72da8a138e862f8750fc30d2ed3d9edpieces.cag / Rturn.lwo· 10,400 bytes7cc343bcb5661ff75443822c638d4ba9974fbe0b88c8ca1e258dac4db8125e33edpieces.cag / S90turn2.lwo· 10,400 bytesf77d7b912c87012c8d5016052e595866cbc34f011c9f26cd6f9721c7bcc6aca6
Examined release and shared evidence scope · Back to section
No recovered scene reference
Neo90turn1
Link to this discovery ↗neo90turn1 is an uneven turn configuration with no recovered scene reference or complete selected-model match in the tested comparisons.
What remains unknown: Predicted driving difficulties have not been tested.
Read about how this was found: Neo90turn1
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
Predicted driving difficulties have not been tested.
Recorded check
The 289-vertex / 512-triangle model has no recovered scene reference or complete selected-model match in that test.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Search neo90turn1.lwo’s scene references and compare it with the 29 selected models under the recorded origin-based transforms.
- Same-index affine failures against seven models do not prove absence of a reordered relationship: their triangle indices differ and vertex correspondence was not established. Driving behavior remains untested.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / neo90turn1.lwo· 8,684 bytes22cc03d93ad04c938ce06896d6623acd343f31691df0e6fed50871d217353133
Examined release and shared evidence scope · Back to section
No recovered scene reference
1.5pipe
Link to this discovery ↗1.5pipe.lwo contains an open ramp configuration not referenced by recovered scenes.
What remains unknown: Finished shader appearance and intended function remain unresolved.
Read about how this was found: 1.5pipe
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
Finished shader appearance and intended function remain unresolved.
Recorded check
The model has 289 vertices / 512 triangles. No complete match was found under the recorded transforms; the same-index halfpipe fit has maximum residual about 7.32 units and different triangle indices.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare 1.5pipe.lwo with selected halfpipe/helix and the tested pipe relatives. Inspect the same-index halfpipe fit separately from coordinate-set tests.
- That rejects the narrow fit only. Missing matching UV data and unresolved UViewShader behavior prevent a claim of recovered finished appearance.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 1.5pipe.lwo· 9,902 bytes97c0bd8938384d694484db9b52286777769e0a8264a36e9d8ef57715acf64539
Examined release and shared evidence scope · Back to section
No recovered scene reference
Upright carrot
Link to this discovery ↗Carrot.lwo depicts one upright carrot with an opening near its base, unlike the two-carrot arch in selected CarrotS.lwo.
What remains unknown: The polygon counts do not establish optimization history, and the selected game already contains carrots.
Read about how this was found: Upright carrot
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
The complete models have 1,524 and 394 triangles respectively. No recovered scene references the upright variant; the counts do not establish optimization history.
Recorded check
The entire loose model has 802 vertices / 1,524 triangles; selected CarrotS has 241 / 394, including terrain. No recovered scene names Carrot.lwo.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare Carrot.lwo with CarrotS.lwo and confirm that selected carrots.lws names CarrotS.lwo, not the loose upright model.
- The roughly 74.1% lower selected triangle count is a measurement, not proof of optimization motive or revision order. Carrots as a subject are used.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / Carrot.lwo· 26,888 bytes1199b4c73e51f10d1b7f6fafe283680b2b2b9c88db98f5f608fd9ab161d5919aedpieces.cag / CarrotS.lwo· 10,564 bytesa38bacddbf208ec08bc93fa69c2dcba22fc12732f1f97e9530d0d7d097f05d89edpieces.cag / carrots.lws· 2,027 bytesad5cd9cbe273cb866f732efc72b26862d624662b0efc43b50867bd0919774123
Examined release and shared evidence scope · Back to section
No recovered scene reference
Tjump2
Link to this discovery ↗Tjump2.lwo has a broad raised profile with rounded grassy shoulders and uses the shared terrain texture.
What remains unknown: The intended role and development order of this variant remain unknown.
Read about how this was found: Tjump2
The recovered scene dependencies and bounded filename scans were compared with the candidate model. Geometry comparisons use the recorded coordinate or topology tests; no universal exclusion of transformed or compiled reuse is claimed.
It has 512 triangles versus 440 in selected tjump. No recovered scene references Tjump2.
Recorded check
Tjump2 has 289 vertices / 512 triangles, versus tjump’s 260 / 440. Its UV surfaces name shared set1.tga. No decoded scene LoadObject names Tjump2.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare Tjump2.lwo with selected tjump and validate each model’s own UV sidecar against polygon/surface records.
- Do not promote count differences into development history or interpret omitted grass masking in the comparison as retail appearance.
Examined release and shared evidence scope · Back to section
Textures and menu artwork
Stored images and menu objects retain designs outside the examined loading paths. Reference absence is scoped to the inspected executable and recovered assets.
Browse the 7 findings in this section
Static asset and reference evidence
Asphalt road texture
Link to this discovery ↗STREET.TGA is a 128 by 128 asphalt-road image with a dashed yellow centerline and pale edges.
What remains unknown: The texture does not establish a cancelled road course.
Read about how this was found: Asphalt road texture
No recovered model, UV or scene references it. Its presence does not establish a cancelled road course.
Recorded check
The image is 128×128. The recorded 2,032-file name scan found only archive and image-browser-cache occurrences; no identical other image was found among 885 decoded images.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Search complete STREET.TGA references across recovered model, OLD, UV, scene and executable data; compare dimensions and decoded RGBA pixels against the image corpus.
- Cache/catalog hits are storage evidence. Whole-image equality cannot exclude cropped, resampled, atlas-contained or movie use; no paved course was recovered.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / 90turn.tga· 197,147 bytesac92fee1acadad2a5d885d4dc6f91b23a198cf6fe22365c1117506cbcc43b76dedpieces.cag / 90turnR.ub· 48,597 bytes40757749d3c18dbca51ad312571dfc5f9d668629a21aa171197ebbc46193292bedpieces.cag / balltex.TGA· 49,196 bytesfe9e4e5dc7c23621f2aff0331fe09503824e443c56adebae385c3ce18800f985edpieces.cag / golftex2.TGA· 49,196 bytes148f5b5f1a0f7b5835083c0389571fa6ddb2b1deed2c0cda74f4e5a8becbfd4bedpieces.cag / hijump.TGA· 12,332 bytesf459ebfaa8dbd9e464663dc8466b549ea0febfc5fbee790d1cae340ceb6f14efedpieces.cag / pspbrwse.jbf· 185,605 byteseaf8637d9344ed0129a93a447de359719afe46a9a767bb00e844393c480fa7cdedpieces.cag / STREET.TGA· 49,196 bytes1eed07f00b70206fb0abf26b39c12f3d8d0e57215894d3686d6dff91991fa8afuedit.cag / but_hijump.tga· 12,332 bytes0dd79282f4b0573c7284690ee4ee501fd072f7bd4af151d10f0b5544b1e6d34euedit.cag / hijumpbut.tga· 12,332 bytes94fe6d993a751a2df82318b8437cc6d7abe97f4c35f1b18b901570b5637ece03
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Leaf texture pair
Link to this discovery ↗LeafYellow128.tga depicts a yellow leaf, with Leafo128.tga providing an aligned grayscale silhouette.
What remains unknown: The grayscale image is likely a mask, but its intended operation is unverified.
Read about how this was found: Leaf texture pair
Both are 128 by 128 and lack recovered model/UV/scene references. The silhouette is likely a companion mask, but its intended operation is unverified.
Recorded check
All 8,751 nonzero silhouette pixels overlap nonblack leaf pixels; the color image has another 531 nonblack pixels. The silhouette includes intermediate grayscale values.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare LeafYellow128.tga and Leafo128.tga at their original 128×128 coordinates, counting nonblack color pixels and nonzero silhouette pixels.
- Aligned support suggests a companion mask, but no material binding or mask operation was recovered. The 885-image equality scan does not test cropped or transformed reuse.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / Leafo128.tga· 17,196 bytes8678984a686ce34f53562ae7233d544c1848469c2aa5a812fe7e4c1577b9a4c8edpieces.cag / LeafYellow128.tga· 49,196 bytes57425643307176176fd7be33522a5f8a937eace14a3b20d92415e8b004f9adb0edpieces.cag / pspbrwse.jbf· 185,605 byteseaf8637d9344ed0129a93a447de359719afe46a9a767bb00e844393c480fa7cd
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Blue-and-flame Utrack imagery
Link to this discovery ↗A stored editor image shows a blue U-shaped structure decorated with red-and-yellow flames, and a matching-looking texture sheet remains in edpieces.
What remains unknown: The pictured blue-and-flame geometry has not been recovered; chronology is unknown.
Read about how this was found: Blue-and-flame Utrack imagery
Normal Utrack selection instead loads the small blue soda can bearing the Semi Logic studio logo with set1/set4 textures and a can-specific button image. The pictured design's geometry and chronology are not established.
Recorded check
The selected utrack.lws uses Utrack.lwo with set1.tga and set4.tga, and a button material names but_slecan.tga. The selected model has 249 vertices / 460 triangles with 460 matching UV records.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Distinguish edpieces/Utrack.tga (256×256 sheet) from uedit/Utrack.tga (640×480 stored render). Follow UI record 0x4BCD60, piece ID 19, into the parsed scene list.
- The selected structure contains the blue Semi Logic can. The blue/flame illustration is preserved imagery, not recovered playable geometry or proof that Utrack as a whole was unused.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / set1.tga· 196,652 bytes8421fabf78c07c34fa103be8ce95a057448c4f662a84a9b294c6ba719e7bf9b9edpieces.cag / set4.tga· 196,652 bytes9fc9e8f9034a6a6af829526011fee2523acf8d5f47b3456c8cfec7bd6b00b114edpieces.cag / Utrack.lwo· 11,310 bytesc780e86f62312209f17e41d8a06ee25dec0abb658dfd02dbaa69e1b0e0929957edpieces.cag / Utrack.lws· 1,405 bytes32d1fb4ed2e62e3bf2fa796ddc72cb5bfff135f6b0ec7abda695ffe1ed9a8375edpieces.cag / Utrack.tga· 196,652 bytes92bbf5ab4c31b33cff000c8d49a2f59b0a87c9f78d1bd5a9970ff9288ff71e83uedit.cag / but_18.lwo· 286 bytes8ef686b43a03f39026c375b1732a9035f2c83336da5e4df900539e4ee25ddb55uedit.cag / Utrack.tga· 921,644 bytes0f16a6b3453bdb576f319539eb2267c46b67d886ee4e0faebde3ebff74d6ee48
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Likely earlier terrain sheet
Link to this discovery ↗set1OLD.tga is a likely earlier terrain sheet, with rougher-looking grass and dirt arranged differently from referenced set1.tga.
What remains unknown: Earlier-version wording is an inference from the name and appearance, not a proved sequence.
Read about how this was found: Likely earlier terrain sheet
No recovered model/UV/scene references it. Earlier-version wording is a labeled inference from the name and appearance, not a proved sequence.
Recorded check
The loose sheet is 128×128; referenced set1.tga is 256×256. The recorded 2,032-file / 885-image audit found no consumer or full-image alias for set1OLD.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare set1OLD.tga and set1.tga’s dimensions/pixels, then inspect exact material and UV references.
- Any earlier-version interpretation comes from filename and appearance. No date or revision sequence is established, and partial/resampled reuse was not excluded.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / set1.tga· 196,652 bytes8421fabf78c07c34fa103be8ce95a057448c4f662a84a9b294c6ba719e7bf9b9edpieces.cag / set1OLD.tga· 49,196 bytes4ac8729de626ef8e907f32112015e046a008a93b98dd720bf7429ae11dc8d526
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Alternate main-menu background
Link to this discovery ↗main.cag contains an unused alternate main-menu background, mainbk.jpg.
What remains unknown: Chronology and the reason for retaining the alternate background are unknown.
Read about how this was found: Alternate main-menu background
It has different Get 'N Dirty lettering in the upper-right corner and a different truck composition. The normal menu explicitly loads main.jpg; both stored menu scenes also name main.jpg. No reference to the alternate image was identified in the examined executable or recovered asset contents.
Chronology and removal reason are unknown.
Recorded check
Three recorded isolated x86 cases request main/main.lws and main.jpg, including release modes 1 and 0. Both scene files themselves name main.jpg, not mainbk.jpg.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Inspect initializer 0x473DC0 and its background load at 0x473E44. Compare BackgroundImage names inside main.lws and mainbk.lws.
- The 800×600 mainbk.jpg is an alternate image. Do not pair it with mainbk.lws as a demonstrated working menu; loader helpers were stubbed and every input route was not explored.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
main.cag / main.jpg· 471,094 bytes7e2a87b93cbc41b2fb0e3dcd2d9fc69fff63954b584747829d0a6f21fbed41bdmain.cag / mainbk.jpg· 476,792 bytesbb09bcc42769592b2b669416f3cabde3fca5ced40f214a0497ebeec8ae85e9c2main.cag / main.lws· 14,840 bytes21ca522790c7b0c6840036c8aa94a51bcad74c8784725395dd234978fe24d83dmain.cag / mainbk.lws· 6,614 bytes0754c214d02297c4f54fcf064dad4c1a6afb3c9189ce9d249a6889d1e5c439d7
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Unused exit icon
Link to this discovery ↗main.cag contains MNexit.lwo, a red prohibition-symbol model assigned to the exit control in mainbk.lws.
What remains unknown: The backup scene establishes an exit-control association, not a live-tested alternate menu.
Read about how this was found: Unused exit icon
The normal menu loads main.lws, which does not include this model. Its only identified asset reference is in the unselected backup scene.
Recorded check
The model is parented through Exit NULL to Exit Position Null. A 2,008-file content scan found MNexit only in mainbk.lws; selected main.lws omits it.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read MNexit.lwo’s parent chain inside mainbk.lws and compare the object list with selected main.lws.
- The exit association follows the hierarchy as well as the name. The reused initializer tests establish the normal scene choice, not live activation of the backup.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
main.cag / main.lws· 14,840 bytes21ca522790c7b0c6840036c8aa94a51bcad74c8784725395dd234978fe24d83dmain.cag / MNexit.lwo· 3,930 bytes129656c5a2c3784f5dd663b0c6adcd70809f61c3ac1744a73157b6e97c69c7cc
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Unused pond menu images
Link to this discovery ↗seltrack.cag contains template.tga and pond0634.tga, showing an overview of the pond. template.tga is formatted as a track-selection portrait.
What remains unknown: This concerns image selection, not absence of the pond from shipped movie footage.
Read about how this was found: Unused pond menu images
The selected pond portrait instead uses track2.tga, a close-up of a frog. No references to the two overview files were identified in the examined executable or recovered asset contents. This concerns the image files, not unused course footage.
Recorded check
The selected image is the frog close-up. The 2,008-file content search found no consumer reference for either stored overview image.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Inspect the selected seltrack.lws → seltrack/pond.lwo → track2.tga material chain, then search template.tga and pond0634.tga references.
- This classifies image files in the examined selection path, not unused movie frames. The numeric filename does not prove a movie-frame index.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / POND.lwo· 9,502 bytesfd5a85005a957ef9b7830f98dbc688fbd4354d1307b088fd5d55e37fe8e794d3seltrack.cag / pond0634.tga· 162,044 bytes0eac28d5929ea329e2bc5bd82b8f4db89e4510cb79a9f20897b711c720bf4c4cseltrack.cag / track2.tga· 196,652 bytesdf929f0823cc53f2ffaafd0614a4a55b17dd84460a9bffd3e6184c9972c65420seltrack.cag / template.tga· 196,652 bytesc8c31df3ce44836408b2b62841d545e6e94845b85a98fae85bb5df8f9cc1bddcseltrack.cag / seltrack.lws· 6,336 bytes0546e7ac0dabd1b5ceaf53d4a3bdecc424339f947f5dd07057ab35a6662a82b1seltrack.cag / pond.lwo· 518 bytesf62b0990cd50a71513f24461b6510cc39c72bd8935db5e78d6469a175b056c9e
Examined release and shared evidence scope · Back to section
Course authoring remnants
Terrain and animation data survive for courses seen in the finished game. These are authoring remnants, not a claim that the courses themselves were cut.
Browse the 4 findings in this section
Retained authoring data
Pond development scene
Link to this discovery ↗game.cag contains Copy of pond.lws, an unreferenced pond authoring scene with camera motion and car animation.
What remains unknown: Chronology, full production scenery and an alternate playable course are not established.
Read about how this was found: Pond development scene
At an offset of 80 frames, 102 of its 111 car keys match the selected pond scene in pitch and bank within 0.0001 degrees. It also references a grass mesh, PNgrassA.lwo. The file does not contain the complete pond scenery. It is likely a development version of the pond setup, although its chronological relationship to the selected scene is unproved. No consumer reference to the copy was identified. This does not establish an alternate course or unused movie footage.
Recorded check
102 of 111 keys agree within 0.0001 degrees. Of nine unmatched keys, six have no key at the shifted time and three differ in pitch/bank.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Match Copy of pond.lws carnull1 key times to pond.lws at selected frame = copy frame − 80. Compare pitch and bank only, without interpolation.
- The copy has only five mesh dependencies, including PNgrassA. Two-channel agreement does not establish full transform identity, exact movie camera alignment or a complete production scene.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
edpieces.cag / POND.lws· 1,418 bytes61e0a295858bef508f1babbb9066db76544a15496849e5b1158a469223c0a35egame.cag / Copy of pond.lws· 30,382 bytesb543527031386d8a7c326d4b150df4cacdec076a0cb7dae2b80121318e00269dgame.cag / pond.lws· 29,207 bytes503120a305d354529d253773ff0cc2c84edb7be569fb79f23d1d69e91fa526d2
Examined release and shared evidence scope · Back to section
Retained authoring data
Garden authoring terrain
Link to this discovery ↗HRDtrak.lwo contains Garden terrain, including irrigation rows, tomatoes and curved track sections. gardenbk.lws retains a camera path that follows this geometry.
What remains unknown: Access through trkride.lws is unresolved. This is not proof of a cut course or complete production scene.
Read about how this was found: Garden authoring terrain
Its 162 position-key times match the selected Garden scene, whose coordinate values are reduced by fixed per-axis factors. The model is also referenced by trkride.lws; access through that scene remains unresolved. This does not establish a cut course or a complete final movie-production scene.
Recorded check
All 486 components pass rtol=2e−6 and atol=2e−6 in the recorded reconstructed-coordinate comparison. HRDtrak is named by gardenbk.lws and trkride.lws, not selected garden.lws.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Match the 162 camera-position key times in gardenbk.lws and garden.lws; relate selected coordinates to backup coordinates using per-axis factors 1e−10, 1e−18 and 1e−12.
- The factors describe stored data, not a recovered runtime scaling instruction. trkride access remains unresolved; the terrain is not wholly unreferenced.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
game.cag / HRDtrak.lwo· 261,704 bytesb9dadc21d334f6b05b833aa960a4b2cb6c57af6c667cb6830b319e2c6d38ec11game.cag / trkride.lws· 72,755 bytes8306ef0639e074a2116bbcdf6d305cec3b80183b9369eea1ef0211edcdfbb9acgame.cag / gardenbk.lws· 50,587 bytese321945e209f6155f9d7dc480ad4ea0b51a23545d996f0ceffa5f86191c23a9c
Examined release and shared evidence scope · Back to section
Retained authoring data
Disabled Beach terrain geometry
Link to this discovery ↗hrdtrak2.lwo contains Beach terrain.
What remains unknown: Exact final movie-source geometry and a complete production scene are not established.
Read about how this was found: Disabled Beach terrain geometry
It is referenced by beach.lws, beachbk.lws and ugroundbk.lws, but all three entries specify ShowObject 0 3. The original scene handler skips the mesh loader for a zero first value, retaining an entry without loaded mesh geometry. The selected and backup Beach camera paths follow this terrain in unchanged coordinates. This does not establish a cut course or exact final movie-source geometry.
Recorded check
All three identified scenes store ShowObject 0 3. Five isolated x86 cases establish that zero skips mesh loading, writes mesh index −1 and flags 0x88; nonzero controls enter the load branch.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Find all hrdtrak2 references and inspect their ShowObject values. Follow handler 0x45E410 through branch 0x45E46C to mesh-loader call 0x4A5970.
- The executed branch used stubbed token/name/file helpers. This proves more than hidden geometry, but does not constitute a complete live scene-load test or final FMV-source identity.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
game.cag / hrdtrak2.lwo· 329,130 bytes1e1a2cc0840bfee1b1d17ec76999788d92a5bb8560c848c532c4a8bcff3fc566game.cag / beach.lws· 52,619 bytes848d7ad67750ab1cf69d10bccbda38df6d2d0ac9892fd8d306263999dcfae3fcgame.cag / beachbk.lws· 48,119 bytesbba5e78e827632e1fe1b92d057af9fea772e66e3b3e25323331cb42d1df955af
Examined release and shared evidence scope · Back to section
Retained authoring data
Disabled Creek terrain geometry
Link to this discovery ↗CRKhrdtrack.lwo contains Creek scenery, including a boat and hollow logs.
What remains unknown: The landmarks support retained authoring scenery, but exact final production-mesh identity remains unproved.
Read about how this was found: Disabled Creek terrain geometry
Both creek.lws and creekbk.lws reference it with ShowObject 0 7, which skips geometry loading in the original scene handler. All 140 camera-position keys match at identical times after accounting for the selected scene’s threefold coordinate and terrain scale. The recovered path crosses the boat and a hollow log during the corresponding movie sequences. This supports retained course-authoring scenery; it does not establish a complete production scene or exact final movie-source geometry.
Recorded check
Both scene records store ShowObject 0 7. Key times match and coordinate comparisons pass rtol/atol 2e−6; terrain scales are three and one. The shared zero-value handler skips mesh loading.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read CRKhrdtrack’s records in creek.lws and creekbk.lws, then compare their 140 camera-position keys after dividing selected coordinates by three.
- Boat/log film frames provide visual context. Camera-path agreement and recognizable landmarks do not establish exact final production meshes or a recovered salamander model.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
game.cag / CRKhrdtrack.lwo· 1,372,718 bytes4a4512450ca5a2410af6a8aaa2ed55071e5d221aa59a04561c9a7b2bbc80c3begame.cag / creek.lws· 42,362 bytesfd5e32d13b0097116bd6d2056f6c6882b8826c6f7ca2cbf83edb8074217632bagame.cag / creekbk.lws· 41,641 bytesc31a6b3c42d49179e8dd1c71f8608063785afc79b2684a79b05e2a76775a5622
Examined release and shared evidence scope · Back to section
Developer controls
The executable retains developer tools. Static analysis and isolated execution are distinguished from controls actually replicated in runtime.
Browse the 1 findings in this section
Static analysis · Isolated code tests
Developer-variable and state controls
Link to this discovery ↗The executable retains a developer-variable display and editor, with 510 static table entries including headings and separators.
What remains unknown: Isolated code tests are not a live-tested activation procedure or proof that every destination works.
Read about how this was found: Developer-variable and state controls
Controls cover physics, cameras, rendering and animation. The Enter toggle requires releasemode to be zero and uses enabledebprint to change the display state; the shipped configuration sets releasemode to 1 and does not enable enabledebprint. Isolated execution confirms camera-position calculations, timer-countdown suppression and bone rest-transform copying. A numbered state selector also survives, gated by enabledebprint; its isolated tests record state requests rather than proving every destination is usable. State 16 contains a course-data editor with per-frame DAT/SND editing, sound audition and file-writing paths. Its diagnostic display includes the literal heading "!!!!!! -> BILLS AUDIO SECTION <- !!!!!!". State 14 requests testworld scenes whose required filenames were not found in the examined disc, cabinet or decoded archives; failed scene loading reaches an error dialog and exit. These are code findings, not a live-tested activation procedure or a recovered playable test level.
Recorded check
There are 510 table rows, including 69 type-7 headings/separators. Enter requires releasemode zero. The recorded tests exercise original x86 branches with external operations stubbed.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Inspect the developer table, shipped releasemode setting, Enter activation gate and state-selector dispatch separately.
- State 16 contains course DAT/SND editing and writer paths; state 14 requests missing testworld dependencies. These are not a live-tested activation recipe or 510 independently verified settings.
Examined release and shared evidence scope · Back to section
Car variants and effects
Alternative car geometry, a packed texture variant and an effect-authoring scene survive in the shipped archives.
Browse the 2 findings in this section
Static asset and reference evidence
Unused car body variants
Link to this discovery ↗Unused car body variants remain in cars.cag.
What remains unknown: Development order, complete original materials and the intended mirroring workflow remain uncertain.
Read about how this was found: Unused car body variants
The Treadator and Sting Rod examples below have fewer polygons than their selected counterparts. OLDtread.lwo has 387 polygons, compared with tread.lwo's 856; purpluv4.lwo has 499, compared with stingrod.lwo's 522. stingrodbk.lwo duplicates purpluv4.lwo's point and polygon data. The campaign and developer course tool select the standard car scenes, which load tread.lwo and stingrod.lwo; none of these variant names was found in the executable or decoded asset references. Their chronology is unknown. OLDtread's UV data references tread.tga, absent from the decoded inventory. Applying purpluv4's saved mapping to the surviving stingrod.tga does not produce a cleanly aligned texture, so its original appearance remains uncertain.
Further unused Commando variants include truckUV8.lwo (324 polygons, compared with the selected commando.lwo's 501) and shawn05.lwo (35 polygons). shawn05 is one-sided: 29 vertices lie on negative X and 14 on the center plane, with none on positive X, consistent with a half-model intended for mirroring. Direct visual comparison identifies both as Commando variants. The selected Commando scene loads commando.lwo; the candidate names have no references in the inspected executable or decoded asset contents. Their development order and the intended mirroring workflow are unproved.
Additional unused body variants are shockUV5.lwo, rollcage4.lwo, flameUV5.lwo, Monster7.lwo and Boonyn6.lwo, corresponding to Shocker, Roll Cage, Flame, Enforcer and Boonyn. Their geometry differs from the bodies selected by the shipped car scenes. They are not uniformly lower-detail: shockUV5 and Monster7 contain more polygons than their selected counterparts. No candidate-name references were found in the inspected executable or decoded asset contents. Development order remains unknown.
The cars archive also contains an extensionless file named rollcage, holding two packed 256x256 images. Its first image is a distinct Roll Cage texture variant. The traced campaign path instead requests rollcage.tsp, whose first image matches rollcage.tga exactly. The original archive filename comparison distinguishes these names, and no standalone extensionless rollcage reference was found in the decoded asset contents or executable. This supports an unused packed texture variant outside the inspected loading path. Its development order is unknown; visual polish alone does not establish chronology.
Recorded check
The campaign call at 0x469C10 and course-tool call at 0x4639EE use the same scene field. OLDtread has 387 polygons versus 856 selected; purpluv4 has 499 versus 522. Other pairs are not uniformly lower detail.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Follow the selected car index at 0x4C0CF4 through 0x10C-byte records and scene names at 0x4C1CA8, then inspect each selected scene’s model reference.
- Compare PNTS/POLS and UV topology per named variant. Keep extensionless packed rollcage distinct from rollcage.tsp; case-insensitive comparison must still preserve the extension. Counts do not prove an LOD system or chronology.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
cars.cag / commando.lws· 11,302 bytesb74d328595b8be38f77dec9ce36a147a642b33548e8d4a4fd1312c5947a6ca7ecars.cag / enforcer.lws· 10,840 bytes3bd928e4f2188e062aeee352932bb84f737f88ecdb1623c73e216749e8b32451cars.cag / tread.lws· 10,779 bytes9cb583d3e5ae9990f1be2e8392320cae7f2bafe1fc6412aa3e57862e5ca4d698cars.cag / stingrod.lws· 11,145 bytesd44b3aa1f2401633166858b2899765d476342421db2b76bcbd5a8641c6eb17dbcars.cag / stingrod.tga· 196,652 bytesadd5cfd91de5c70739764c21a66814f3032f6a659d8e027981e8165cef9b1995cars.cag / tread.lwo· 16,652 bytes2ef825cf1dd0ab12085644964e22fcf4b61a5ca319cfdacf2137d1ca438fa0cdcars.cag / rollcage· 393,244 bytes25228ac969b2dd0556639b3e471f25814763deeee68b74014b38aa449936a42ccars.cag / stingrod.lwo· 11,002 bytes86d57b4a7d82aa4c4c4167b7c350516258048457aaea279d5fc06da1d97f98bbcars.cag / OLDtread.lwo· 7,770 bytesce63b8c18b800111f7df97d4eab5db37f00c518b705e7284cf662baf12be1e47cars.cag / purpluv4.lwo· 9,626 bytes2cb6a9cd492e1f0fd2534d4356ac3a71c4151fed23273dbd28ecdf30de421b8ecars.cag / stingrodbk.lwo· 9,626 bytes8cd6969e4d418e8db2a4975b8afa4e4eeb81affd7fe33d234b843edfaca73598cars.cag / shockUV5.lwo· 11,180 bytes3c76a4ef2828e0e3dc2c50443c6c965fa0938318a077fac40f5cac38dae6c119cars.cag / shawn05.lwo· 976 bytesa86728fa1747181ebfc32d79894e05804fc9022794219703bb3abf164b0c658ecars.cag / treadUV5.lwo· 7,768 bytes8cb9a1de0ebb10bdc88ec8d5b656ed4660c7f7491546ad4d7f5776a759477d4bcars.cag / truckUV8.lwo· 6,588 bytesdb5b8c0282bbbc6c41f474f26a0a72e05ddab9505825146b1a3e0af6a96426d2
Examined release and shared evidence scope · Back to section
Static asset and reference evidence
Orb effect authoring scene
Link to this discovery ↗An unreferenced scene named powup.lws contains an orange orb, two curved pieces rotating on different axes, and a pulsing translucent outer sphere.
What remains unknown: Finished appearance and possible rendered derivatives are unresolved. A removed pickup mechanic is not established.
Read about how this was found: Orb effect authoring scene
It declares RGB and alpha-image output paths under models/powerup/animation, supporting an effect-authoring role. No literal scene or component filenames were found in the executable; the components' inspected scene references are confined to this arrangement. Four referenced ring textures are absent from the decoded inventory. No convincing match to the inspected shipped effect frames was identified, but its exact finished appearance and possible rendered derivatives remain unresolved. The filename does not establish a removed pickup mechanic or an origin in another game.
Recorded check
ring1 heading is 0/179.8/360.9001 degrees at frames 0/5/10; ring2 pitch is 0/178.6/359.1. Four named ring images are absent from the decoded inventory. ball and ball2 share PNTS/POLS bytes.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Read powup.lws’s object keys/material dependencies and search component references separately from rendered sprite comparisons.
- RGB/alpha output metadata supports an effect-authoring context. The visual comparison found no convincing derivative, but does not exclude all rendered reuse or prove a removed pickup mechanic.
Examined source files and SHA-256 hashes
Files named in the supporting research record. Hashes identify examined bytes; they do not independently establish whether a file was used.
game.cag / powup.lws· 2,595 bytesaa27b6ca3ae7e2ab812dfbca6cb0ce4ed664f42d06c51b9aace66355417a033fhiscrline.cag / HANDLFT.uv· 1,021,332 bytes55e56655cd79faf5a5afc758830a7cb9b9c737765bb7ace46bebb19483a1342dscore320.cag / HANDLFT.uv· 1,021,332 bytes55e56655cd79faf5a5afc758830a7cb9b9c737765bb7ace46bebb19483a1342dscrline.cag / HANDLFT.uv· 1,021,332 bytes55e56655cd79faf5a5afc758830a7cb9b9c737765bb7ace46bebb19483a1342d
Examined release and shared evidence scope · Back to section
Related editor variants
Section titled “Related editor variants”Explore six variants of familiar editor content
Tire-loop model and icon
Section titled “Tire-loop model and icon”An unreferenced tireloop.lwo has additional terrain and upright strips compared with selected loop.lwo. loopbk is a close relative. The actual loop button icon depicts extra grassy entrance detail, but its exact source mesh is unproved.
Bubble bottle
Section titled “Bubble bottle”Standalone bubblebottle.lwo has different geometry and mapping, including a smaller label area, than the bottle embedded in selected bubbles.lwo. No recovered scene references the standalone model.
Bubble terrain and disc
Section titled “Bubble terrain and disc”bubflat.lwo differs in terrain height from selected bubbles even after removing the bottle and wand analytically. bubblc.lwo is a small octagonal fan; a wand-film role is plausible but unproved. Neither is referenced by a recovered scene.
Book/flashlight turn variants
Section titled “Book/flashlight turn variants”90turnAD has a different book topology but reuses the compared flashlight after a quarter-turn. Its contents.obv occurrence is an unresolved auxiliary reference, not a demonstrated scene-load route. No chronology follows from backup-style names.
Turn components
Section titled “Turn components”90turn_1 includes the bookflash geometry and terrain close to the selected turn; 90turn_Part1 is a two-triangle patch. Their analytic combination still differs by one quad diagonal and is not a recovered authored assembly.
Puddle2 variant
Section titled “Puddle2 variant”puddle2 contains all tested selected t4way triangle geometry plus 49 additional unique triangles forming upright strips. This is a variant of used terrain, not a wholly unused depression.
Sound controls and trailing data
Section titled “Sound controls and trailing data”Replicated in runtime · Static executable analysis
Undocumented sound controls
Link to this discovery ↗While driving a custom track, pressing A cycles through sounds from the Garden sound bank. M mutes music in the menu and track editor.
What remains unknown: Full-cycle and reset behavior were not separately reported in the live test. Neither control establishes that the sounds themselves are unused.
Read about how this was found: Undocumented sound controls
The sound table has 60 entries, with wrapping and silence in its first entry. Cycling was replicated with the source-matching executable and source-matching configuration. The M handler toggles between two music-volume values. Neither control is described in the examined shipped text manual or ReadMe.
The adjacent H coordinate-write handler is disabled by shipped releasemode 1. It is not presented as a normally enabled retail control or a runtime-confirmed effect.
Recorded check
The A branch at 0x4885FD–0x488645 requires a fresh event and held state at input index 0x1E. Recorded isolated tests verify increment and 59→0 wrapping for a 60-entry bank. Live observation separately confirms cycling with the source-matching executable and configuration.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Follow state 10’s initialization to the garden.tag load and its update to the A handler. Separate the isolated playback stub’s logged index from actual audible playback.
- Inspect the M handler at 0x455A25–0x455A7F: it toggles storage at 0x575EE1C and passes −10000 or 0 to 0x4577D0. Menu/editor muting was observed; a full sound-cycle and reset-lifetime test was not reported.
File comparison · Original loader and writer analysis
Trailing ratings data
Link to this discovery ↗The loose ratings.dat is 1,980 bytes long, but the examined ratings loader and writer each process only 660 bytes.
What remains unknown: The origin of the 1,320 surplus bytes is unknown. Their presence does not establish how they were produced.
Read about how this was found: Trailing ratings data
The copy inside ratings.cag is 660 bytes. The first 660 bytes of the loose and archived copies also differ. The loose file’s tail contains additional rating-like rows and a historical development-path fragment at file offset 0x7B0.
These observations identify a surplus outside the examined routines’ data span. They do not establish a memory-dump or serialization-error explanation.
Recorded check
The successful writer at 0x478230 performs 33 sequential writes of 20 bytes. Recorded isolated runs with both source prefixes each wrote 660 bytes; filesystem calls were stubbed. A fresh file comparison confirms the 1,980/660-byte lengths and differing active prefixes.
How to check this finding
- Use the evidence record to identify the examined files and their hashes. Begin with the source-checking procedure.
- Compare the cabinet’s loose ratings/ratings.dat with ratings.cag’s ratings.dat. Hash both, compare bytes 0–659, and measure the loose file’s remaining bytes. The evidence record includes separate full-file, prefix and tail hashes.
- Trace the fixed reader span and writer loop separately from the file-resolution routine. The inspected resolver prefers an available loose file over the archive fallback. Do not infer which file a historical live session opened or which tool produced the surplus.
Examined release
Section titled “Examined release”The shipped SETUP/README.TXT identifies CD-ROM version 1.0 and Windows 95/98 support. SETUP/MANUAL.TXT credits Mattel Interactive and Semi Logic Entertainments; both texts carry a 2000 copyright notice. The exact regional packaging edition has not yet been established. The cover shown above is a separately sourced THQ-branded package, not proof of the examined disc’s edition.
Examined stunt2.exe SHA-256
2aefb46e94db8b5c05435b2bb7267956a1f9ba9157b91c34aa32bf01a73ed53aEditor selection evidence
Section titled “Editor selection evidence”The original editor initialization passes uedit.txt to the parser at virtual address 0x47B730. The parser stores scene handles in 0x150-byte records. A second consumer uses the deferred parser at 0x480BB0. Recorded isolated execution of the original parser bytes requests the same 27 scene names; token supply and external calls are stubbed, so this is not an observation of a live game loading all scenes.
Independent inspection of the placement records identifies 25 selectable IDs, 2–26. The remaining two scene-list entries are the grid and base. The selectable count is also supported by in-game observation. Saved tracks resolve numeric IDs through this same list.
Examined placement records and executable hash
Checking the source files
Section titled “Checking the source files”The downloadable checks require Python 3.10 or newer and already decoded CAG members from your own copy. Archive extraction is a prerequisite; these scripts do not extract a disc or run the game. They identify files by SHA-256, so extraction filenames can differ.
Save the source checker, relationship checker and source manifest together. From that folder, substitute your decoded-member directory below. Choose unused report filenames; the scripts refuse to overwrite existing reports.
python -B check_sources.py "path/to/decoded-members" source-manifest.json source-report.jsonpython -B check_relationships.py "path/to/decoded-members" source-manifest.json relationship-report.jsonThe source-audit result verifies all 1,960 member identities and records 683 LWOB mesh summaries plus 158 scene object lists. Polygon records, fan-triangulated faces and unique coordinate triangles are different measurements; the report labels its counts explicitly. Model basenames in scene lists do not by themselves resolve archive paths or prove runtime use.
The relationship-audit result repeats 11 bounded checks, including geometry aliases, mirrored turns, the published Bjump-to-olly transform, Bunker/Odip vertices, Garden and Creek camera positions, and pond pitch/bank keys. It also inspects the editor-list text, including its extra model token; this text check does not execute the original parsers or establish selectable IDs.
Each finding’s evidence record separates these fresh source observations from the recorded excavation experiments. The scripts do not rerun every geometry search, image/UV comparison or isolated x86 harness. Those earlier experiments retain their stated scope and limits; none is silently presented as a new live game test.
Reading the evidence
Section titled “Reading the evidence”Original scene text, mesh structure, image data and executable references support the static findings. Where original code was executed in an isolated harness, that is labeled separately from runtime replication. Reconstructed inspection images retain the limitations stated in their captions. No abandoned asset has been restored to playable retail use in this investigation.