A browser-based 3D track viewer for classic Terminal Reality games.
JSTrackViewer opens the archives of Monster Truck Madness, Monster Truck Madness 2, CART Precision Racing, Terminal Velocity, Fury3/F-Zone, Hellbender, 4x4 Evolution, 4x4 Evolution 2 and Fly!, and renders their levels in 3D: terrain, textures, objects, courses, skies and game-specific data. Everything runs locally in the browser.
Live application: Open JSTrackViewer on GitHub Pages
Changes since 1.3.0:
- A track's own ambience (track format version 6, section 9.6): the TXV's sky gradient and sky picture, haze and light tint. In Clear weather the sky dome shows the track's sky and the haze fades the scene into its colour, its start and end laid over the view distance; the light tint applies in every weather. Any MTM2 track may carry the keys (the Motorhead conversions do); the Track Data panel lists them.
- OpenPhotex 1.7.4.
Changes since 1.2.0:
- Track format version 6 tracks (.SI3, https://openmtm2.github.io/proposals/track-format-v6): worlds of 512 cells (16,384 ft a side), the height step and base its TXV sets (heights below zero or thousands of feet up), 16-bit ground boxes, and version 2 lakes and waterfalls. The Track Data panel shows the world's size, height step and height range; a TXV or grid file that does not fit refuses the track with the reason.
- Tracks that share one level, such as the 22 Midtown Madness Chicago races, find the level's TXV, lakes, vegetation and waterfalls by the level's name first, then their own: their water now shows.
- Community Patch 4 beta 0.53 waterfalls (.WFL): each built at load as the game builds it, by walking the water from its crest over the terrain into the lakes or the track's water, then drawn flowing in the game's Original look with its foam strip, ragged edges and mist box, with a Waterfalls toggle and a Stats row.
- OpenPhotex 1.7.3.
Changes since 1.1.0:
- Community Patch 4 and Traxx 1.7 tracks: 16-bit heightmaps, 16-bit Spline and 16-bit Full Map terrain (drawn on its 8 ft grid), and height PNGs.
- Lakes drawn at their own heights; Test Drive treats them as water.
- Fog volumes shown as translucent boxes in the weathers they belong to, listed in the Stats panel.
- Traxx 1.7 vegetation: trees and grass drawn instanced, with far cards, and a Vegetation toggle.
- Surface types from a model's .SRF file shown in the Models window.
- A new document comparing the June 1996 MTM1 beta (Build #41) with the retail game.
- OpenPhotex 1.7.0.
Changes since 1.0.0:
- Added a Models window with 3D previews, model statistics, and controls to find and step through placed objects.
- Added a Textures window with adjustable thumbnails, texture dimensions, ground types and depths, and road surface details.
- Test Drive now uses the OpenPhotex MTM2 simulation shared with OpenMTM2, including solid axles, suspension, tire grip, gearing, and air and water drag.
- Improved truck wheel and axle animation, tire sizing, ground-box and scenery collisions, analog gamepad input, and truck switching.
- Added explorable Terminal Velocity and Fury3 tunnel interiors, listed separately after surface levels, with the camera starting inside the entrance.
- Added Terminal Velocity and Fury3 chamber ceilings and a Rock tops toggle for viewing rooms inside solid terrain.
- Corrected terrain proportions, triangle sampling, and object placement in Terminal Velocity, Fury3, and Hellbender.
- Fixed Hellbender cavern heights, surface openings, underground visibility and lighting, and texture palette selection.
- Added Hellbender moving-terrain markers with height ranges, named powerups, automatic navigation-point labels, and warnings for missing tunnel levels. Moving terrain is marked but not animated.
- Updated the shared OpenPhotex library and expanded regression tests and documentation for driving physics and game-specific level behavior.
- Opens archives from disk, URL or a whole folder: POD, EPD and ZIP files, with every track of every archive in one list.
- Nine games: Monster Truck Madness 1 and 2, CART Precision Racing, Terminal Velocity, Fury3, Hellbender, 4x4 Evolution 1 and 2, and Fly! scenery.
- Complete levels: terrain, ground boxes, objects, animated and moving models, water, backdrops and skies.
- Courses and markers: checkpoints, AI lines, navigation points, powerups and tunnels, each toggled on its own.
- Lighting and weather: the game's sun position, cascaded shadows, Clear, Cloudy, Dusk and Night skies, lens flare and truck lights.
- Test Drive: drive a Monster Truck Madness truck on any loaded level, with collisions, surfaces and lap timing.
- Fly! cities: 250 km of satellite-textured terrain with skylines and bridges, streamed at full resolution near the camera.
- Inspection tools: Models and Textures windows, wireframes, a terrain grid, hitboxes, texture filtering and track statistics.
- Free camera: fly anywhere, zoom with the mouse wheel, and jump around with the minimap.
Each feature is described in detail under Feature details.
| Content | Games | Support |
|---|---|---|
| POD1 | MTM1, MTM2, CPR, Terminal Velocity, Fury3, Hellbender | The original archive layout, 32-byte directory names |
| POD2 | 4x4 Evolution 1 and 2 | Indexed archive layout |
| EPD | Fly! | Fly!'s archive layout |
| ZIP | All | ZIP files holding one or more POD archives |
| Content | Games | Support |
|---|---|---|
| LVL | All | The level manifest: heightfield, texture grid, palette, texture list, sky, music, lighting and water. A positional list in MTM, CPR and the Terminal Velocity family; labelled fields in 4x4 Evolution |
| SIT, SI2 | MTM1, MTM2, CPR | Scene script: objects, ramps, ground boxes, starting grid and courses (SI2 is the Community Patch 3 spelling) |
| SI3 | MTM2 (track format version 6) | The same scene script for a track format version 6 track, listed as its own track even beside a SIT or SI2 of the same name. Its TXV sets the world's size (256 or 512 cells, up to 16,384 ft a side) and the height step and base, so heights may be negative or thousands of feet tall; a TXV or grid file that does not fit is refused with the reason. Its TXV, lakes (WTR), vegetation (VEG) and waterfalls (WFL) are found by its level's name first, then its own, so several tracks can share one level (as the Midtown Madness Chicago races do) |
| SIT v6 / v7 | 4x4 Evolution 1 and 2 | Scene script: placements, starting grid and course centrelines |
| RAW (heightfield) | All but Fly! | Terrain height per grid point: one byte in MTM and the Terminal Velocity family, 16-bit fixed point in CPR and 4x4 Evolution |
| CLR | All but Fly! | Terrain texture per cell: a 16-bit word (texture index, mirror and rotation) in MTM1, MTM2, CPR, Hellbender and 4x4 Evolution; one byte (texture index and rotation) in Terminal Velocity and Fury3 |
| TEX | All but Fly! | The level's terrain texture list |
| TTY | MTM1, MTM2 | Ground type and depth for each terrain texture, used by Test Drive |
| LTE | MTM1, MTM2 | Baked terrain light |
| RA0 | MTM1, MTM2, Hellbender | Ground boxes: lower height of the box in each cell, 1 byte per cell (1 or 2 bytes on an SI3 track, on its step and base) |
| RA1 | MTM1, MTM2, Hellbender | Ground boxes: upper height of the box in each cell, 1 byte per cell; 0 means the cell has no box |
| CL0 | MTM1, MTM2, Hellbender | Ground boxes: the six face textures of each cell's box (south, north, east, west, top, bottom), one texture word each, 12 bytes per cell |
| RA2 | Hellbender | Underground: cavern floor height, 1 byte per cell, biased so that byte 255 is altitude 0 (the surface datum) |
| RA3 | Hellbender | Underground: cavern ceiling height, 1 byte per cell; where it equals the floor, the cell is solid rock |
| CL1 | Hellbender | Underground: cavern floor texture, then ceiling texture, one texture word each, 4 bytes per cell |
| RA4 | Hellbender | Underground ground boxes: lower height, encoded as RA0 on the cavern's heights |
| RA5 | Hellbender | Underground ground boxes: upper height, encoded as RA1 |
| CL2 | Hellbender | Underground ground boxes: face textures, encoded as CL0 |
| DEF | Terminal Velocity, Fury3, Hellbender | Object definitions and placements |
| NAV, PUP, TDF, ANI | Terminal Velocity, Fury3, Hellbender | Navigation points, powerups, tunnel definitions and animated textures |
| TNL | Terminal Velocity, Fury3 | A tunnel level's tube: segments of two elliptical rings, one terrain square long |
| QKE | Hellbender | Moving terrain: cells and ground boxes that rise and fall (doors, lifts, crushers, switches) |
| TXT (briefing) | Hellbender | Planet, location and mission text |
| Sky RAW + ACT, VOX | MTM1, Terminal Velocity, Fury3, Hellbender | Sky texture, recolouring palette and horizon colour; STARS.VOX star field |
| TRK + TTX | CPR | The road layer: surfaces, curbs, walls and their textures |
| WAT, VEG | 4x4 Evolution 2 | Water material and vegetation |
| RAW (16-bit), height PNG | MTM2 (Community Patch 4) | 16-bit heights at 1/128 ft: 256 x 256 (131,072 bytes, drawn as is or expanded to an 8 ft Spline grid when the TXV says terrainGrid=spline), a 1024 x 1024 Full Map at 8 ft (2,097,152 bytes), or the grey PNG the TXV names with terrainHeights |
| TXV | MTM2 (Community Patches 3 and 4, track format version 6) | The track's version record: format version, tool, and Community Patch 4's terrain grid and height file; for an SI3 track also worldCells, terrainHeightMap (a 16-bit RAW or grey PNG of N or 4N square), terrainHeightStep and terrainHeightBase; on any track the ambience keys skyTopColor, skyBottomColor, skyHorizon, skyImage, fogColor, fogStartFt, fogEndFt and lightTint |
| WTR | MTM2 (Community Patch 4, track format version 6) | Lakes above the track's own water: a height each and a 256 x 256 map of their tiles (version 1), or 512 x 512 with signed heights across the terrain's range (version 2, 512-cell SI3 tracks only). The world's size picks the version, and any other pairing is refused with a warning |
| WFL | MTM2 (Community Patch 4 beta 0.53, track format version 6) | Waterfalls: up to 64 crests of 2 to 8 points, each fed by a lake or a spring at its own height, with its flow speed, opacity, mist, splash, sound and texture. The file holds no geometry; the sheet is built at load from the crest, the terrain and the water. Version 1 is a 256-cell world's (SIT, SI2, or a 256-cell SI3) and version 2 a 512-cell SI3's, with signed heights across the terrain's range and crests anywhere in the world; any other pairing is refused with a warning |
| VEG (binary, MVEG) | MTM2 (Community Patch 4) | Placed trees and grass clumps, with each species' model and far card |
| SRF | MTM2 (Community Patch 4) | A model's surface types, one per texture, making it drivable scenery |
| AI_*.TXT | 4x4 Evolution | The computer drivers' recorded laps |
MTM1 and MTM2 levels carry all nine RA and CL grids, but only RA0, RA1 and CL0 hold anything; the six underground grids are present and empty. CPR, Terminal Velocity, Fury3 and 4x4 Evolution levels have none of them.
| Content | Games | Support |
|---|---|---|
| BIN | All but 4x4 Evolution | Textured models, with each game's scale, materials and animated keyframes |
| SMF | 4x4 Evolution 1 and 2 | Models, versions 2 to 4, including bump materials |
| BSP | Fly! | Large structures such as bridges |
| RAW + ACT | All | Paletted textures, with fallback palette resolution |
| RAW + ACT + OPA | 4x4 Evolution 1 and 2 | Paletted textures with an 8-bit opacity plane |
| TIFF | 4x4 Evolution 2 | Palette-indexed art with an optional alpha sample |
| PNG, TGA | MTM2 (Community Patch 3) | High-definition textures |
| TRK (truck) | MTM1, MTM2 | Truck manifests for Test Drive |
| Content | Support |
|---|---|
| SCF | A city's manifest: its name, coverage area and archives |
| ALT, TYP, REF, TEX, AL2 | Each globe tile's heights, cell types, texture references, texture list and finer relief |
| SCENERY.Sxx + BIN, BSP | Buildings, landmarks and bridges, placed by latitude and longitude |
| *NIGHT.EPD | City lights for dusk and night |
- A modern browser with JavaScript modules, Web Workers, WebGL, and Origin Private File System support
- An HTTP or HTTPS origin; the application cannot run correctly from
file:// - Network access to the Three.js and fflate CDN modules
- Open JSTrackViewer on GitHub Pages.
- Choose Open from Disk for a POD, EPD or ZIP file, Open from URL to fetch one, or Open from Folder for a whole folder of them.
- Select a track when there is more than one.
- Use the keyboard, mouse, and view controls to explore the level.
- Use the Markers and View Options panels to choose what is drawn. Every panel collapses from its heading, and controls appear only where the loaded track has that content.
Note
Remote archives must be served over HTTP or HTTPS. Cross-origin servers must also allow the browser request through CORS.
Clone the repository and serve its root directory with any static HTTP server:
git clone https://github.com/juanputrerasm/JSTrackViewer.git
cd JSTrackViewer
python3 -m http.server 8080Then open http://localhost:8080/. There is no build step and no package installation.
| Control | Action |
|---|---|
| Up / Down Arrow | Move forward / backward |
| Left / Right Arrow | Turn the camera |
| Page Up / Page Down | Pitch the camera |
| A / Z | Raise / lower the camera |
| Mouse drag | Look around |
| Mouse wheel | Zoom in and out, 0.5× to 8×; the Zoom slider under Distance follows it and sets it |
| Home | Reset near course segment 0 |
| Minimap click | Move to the selected map position while preserving camera orientation |
| Minimap double-click (Test Drive) | Move the truck to the selected map position, keeping its heading |
| Speed slider (under the minimap) | Scale arrow-key and A/Z travel speed, 5% to 100%; defaults to 25% and is remembered per browser |
Test Drive puts a truck on the level you are viewing and lets you drive it. The truck comes from its own archive, so a track POD and a truck POD are open at the same time.
- Load a track as usual.
- In the Test Drive panel, choose Load truck POD and open a Monster Truck Madness or Monster Truck Madness 2 truck archive. The Drive button appears once a truck archive is open.
- Pick a truck from the list.
- Choose Drive. The truck starts at the first starting grid slot, or where the level starts the player; on Fly! scenery it starts on the ground under the camera, facing the same way.
While driving, the panel reports speed in mph and km/h, the selected gear, whether the gearbox is automatic or manual, engine rpm, the surface under the tires and the active camera. On a track with checkpoints it also reports the lap number, the next checkpoint, the current lap time and the best lap.
| Control | Action |
|---|---|
| Up Arrow / W | Throttle |
| Down Arrow / S | Brake and reverse |
| Left / Right Arrow, or A / D | Steer (arrows only in manual) |
| M | Toggle the manual gearbox |
| L | Toggle the truck's lights (headlights, roof light bar and beacons) |
| A / Z | Shift up / down in manual; Z from first selects reverse at a standstill, and the throttle drives it |
| Space | Handbrake |
| V | Cycle the cameras: chase near, chase far, cockpit, free orbit |
| R | Return to the start |
| Mouse drag and wheel | Swing and zoom the free orbit camera |
| Gamepad | Sticks and triggers, where the browser reports one |
Note
Drive mode borrows the arrow keys while it is active, so the free-flight camera stands down until you stop driving.
- Open from Disk takes a POD, EPD or ZIP file. A ZIP holding several PODs offers every track of every POD, grouped by POD.
- Open from URL fetches the same kinds of file from an absolute, root-relative or page-relative address, such as
https://example.com/tracks/circuit.pod,/downloads/track-pack.zipor../archives/track.pod. Relative addresses are resolved against the viewer page. A ZIP fetched by URL opens its first POD. - Open from Folder offers every track of every POD and EPD under the chosen folder, at any depth, in one list grouped by archive, along with any Fly! scenery sets in it. The archives are read where they are, never copied, and only their directories are read until a track is chosen. ZIPs inside a folder are not opened.
- An archive with more than one track opens a chooser over the viewport, and the picker in the top bar switches between tracks without reopening anything, across archives too.
- The heightfield is drawn with its texture grid, each cell's texture mirrored and rotated as its CLR entry says. CPR, Terminal Velocity, Fury3 and Hellbender split their cells along alternating diagonals, as the games do, and markers sit on those triangles.
- Terminal Velocity, Fury3 and Hellbender terrain is drawn in its true proportions against the objects on it (one height step is 1/32 of a square in Terminal Velocity and Fury3, 1/16 in Hellbender).
- MTM1 and MTM2 terrain is drawn at the brightness its LTE file bakes in.
- Community Patch 4 terrain: 16-bit heights are read at their full precision, and Spline and Full Map tracks are drawn on their 8 ft grid, each 32 ft cell's texture stretched over its 16 finer quads, split on the same alternating diagonals the game drives on. The Track Data panel names the grid. Test Drive and the markers stand on the same 8 ft triangles.
- Ground boxes are the solid blocks that stand on single cells, each face textured from CL0. Hellbender's underground is a second layer under the surface: cavern floor and ceiling meshes covering only the hollow cells, plus the cavern's own ground boxes. The surface opens into it where the game opens it, at every point whose surface height is 0 above a cavern ceiling at 0: almost all of the floating levels, and the shafts and pits of levels such as JURASIC and KREASH3.
- Terminal Velocity and Fury3 chambers, the rooms inside the solid rock at altitude 255, get the ceiling the game generates: the floor mirrored about 255, textured from ten squares along. The Rock tops toggle hides the rock the game never draws, to look down into them.
- Texture presentation: smooth or sharp (pixelated) filtering, and the two-pixel tile overlap that hides seams between terrain tiles, on by default where a game's tile sets need it.
- Models are placed and turned as each game does it, at each game's own scale and height stretch.
- Tracks that name more than one background model show all of them. The Backdrop toggle hides that scenery and keeps the sky.
- Animated BIN models play their keyframes, blending each frame smoothly into the next. Animated textures play where the level's ANI file names them.
- Moving objects: MTM2 and 4x4 Evolution trains travel along their velocity, following the terrain and ground boxes, and 4x4 Evolution 2's banked flying objects circle overhead with whatever is attached to them, such as a plane's banner. The Moving objects toggle stops them and puts them back.
- 4x4 Evolution 2 vegetation is drawn with instancing.
- Community Patch 4 vegetation is drawn with instancing too: every tree and grass clump of the track's VEG, placed, turned and scaled as the file says. Trees change to their far card beyond 950 ft and grass is drawn to 1,000 ft, as the game's defaults do, decided per 256 ft square. The Vegetation toggle hides both games' vegetation.
- Community Patch 4 lakes are drawn as flat water at their own heights over their tiles, with the track's water, and Test Drive sinks into them. A lake the game would refuse (out of range, below the track's water, or on a bed that touches it) is left out and named in the warnings.
- Community Patch 4 fog volumes (type 14 boxes) are drawn as translucent boxes in their colour, their opacity from their visibility distance, and shown only in the weathers they name. The Stats panel lists each with its settings; a click flies the camera to it and outlines it. The Fog volumes toggle hides them, and Test Drive drives through them.
- Community Patch 4 beta 0.53 waterfalls (
WORLD\<stem>.WFL) are built with the game's rules (OpenPhotexbuildFallMeshes): the record checks and refusals, the walk of each column over the terrain in the mode the track is drawn in, the spacing and vertex budget, the foam strip and the mist. Refused, dropped and skipped falls are listed as warnings. The sheet is drawn in the game's Original look: the fall's texture scrolling down at its crest speed with a second layer mixed in, a ragged mask on its edges and end, and the foam strip where the water lands when the fall has SPLASH. A fall without its own texture uses the retail ripple (RIPPL100 to RIPPL800) when the opened archive carries it (the game keeps it in STARTUP.POD and FIXMORE4.POD), and is drawn in the water colour otherwise. Each mist is a fog volume box. The Waterfalls toggle hides them; Test Drive drives through them, as the game does. - A model with a Community Patch 4 SRF shows each of its textures' surface type in the Models box.
- MTM, MTM2 and 4x4 Evolution tracks show the main course and each AI line, every course with its own checkbox, label and colour. A Style choice draws them three ways: Smooth, with the joins rounded off the way a truck turns; Joined, the runs as stored joined straight; or Traxx, each segment on its own and numbered at its start.
- 4x4 Evolution stores only the straight runs of a course, so the corners and hairpin legs between them are drawn back in along the roads. A rally is a one-way run, so its course ends at the finish. When a track ships its computer drivers' recorded laps, each distinct lap is its own AI line.
- CPR's five courses are named and coloured by purpose: three AI racing lines, the pit road lap and pit row. Its checkpoints are labelled pit entry, pit speed limit start and end, start/finish, then the lap's gates.
- Numbered checkpoint markers for MTM, MTM2, CPR and 4x4 Evolution. MTM1 checkpoint banners are ordinary scenery; only the invisible trigger boxes wait behind the Checkpoints toggle.
- Terminal Velocity, Fury3 and Hellbender show navigation points with their objective text, tunnels and powerups. Powerups are named (Laser, Shield Restore, AfterBurner and so on, and Hellbender's own 31 types), and objects that always drop one are marked. Hellbender's sync points that the game inserted itself are marked "auto", and a tunnel whose level is not in the archive says so.
- Hellbender's moving terrain (doors, lifts, crushers and switches) is marked from its QKE, with each one's height range.
- Objects stand where the game puts them: Terminal Velocity and Fury3 set every surface object on the ground at its exact position, add its definition's offset and lift flyers by half their size; Hellbender keeps the stored height but raises an object to the floor or onto the ground box it is inside. Both at the size and proportions the game draws them, turned about their own origin.
- Terminal Velocity and Fury3 tunnel levels open as their tube, built from the level's TNL and textured from its texture list, with the level's objects and powerups inside. They are listed after the surface levels, marked "(tunnel)", and open with the camera inside the tube's mouth, looking along it.
- The sky is the game's flat textured ceiling above the world, recoloured for each level through its sky palette, or a star field on space levels. Fog fades the world into the level's horizon colour and follows the Distance slider. Sky and Fog have their own toggles.
- Hellbender shows each world's planet and mission names.
- The road layer is built from its TRK and TTX files: surfaces, curbs, walls and catch fencing, with wireframe overlays. Closed circuits are joined across the start/finish line, the layer stops at its walls, and the road is always drawn over the terrain.
- In Test Drive the road carries the truck and the walls stop it.
- Sun position: every game states where its sun is, and the viewer reads it, names its compass point and lets you move it.
- Shadows: objects, vegetation and the driven truck cast shadows onto the terrain and the road surface, out to the full view distance, through cascaded shadow maps that are redrawn only when the camera has moved far enough to need it. Sun light and shadows are separate toggles.
- Weather: MTM1, MTM2, CPR, 4x4 Evolution and Fly! offer Clear, Cloudy, Dusk and Night, each with its own sky and light. Cloudy greys the backdrop scenery, Dusk and Night darken it, and at Night the moon casts faint shadows. The choice is remembered between tracks.
- Sky style: the weather's textured sky, or the plain Gradient sky MTM1 and MTM2 draw with their textured sky switched off. MTM1 tracks also offer Classic, the game's own flat sky from its LVL, kept at a fixed height above the camera, with its horizon haze.
- Sun, moon and lens flare: in a Clear or Dusk sky the sun is drawn with MTM2's lens flare, fading as terrain or objects cover it; Night shows the moon.
- Truck lights: MTM2 trucks carry their own lamps, with flares and beam cones. The headlights and roof light bar light the terrain and objects ahead, and switch on by themselves at Dusk and Night. Brake and reverse lights follow the pedals.
See the physics integration notes for the shared simulation boundary and validation.
- Vehicle simulation: Test Drive uses the same OpenPhotex MTM2 simulation as OpenMTM2: solid-axle articulation, spring and damper suspension, load-dependent tire forces, four-wheel steering, the engine torque curve, three-speed gearing, hull contacts, and air/water drag. It advances at a fixed 120 Hz.
- Surfaces: terrain and ground-box texture types feed MTM2's friction and tire-cut tables. Surface depth is tire sink in inches; submerged tires and bodywork add water drag. The viewer's terrain samplers also support its other game formats and preserve holes in Hellbender terrain.
- Collisions: objects with a model collide against the model itself, so a truck can pull up against a tree trunk and drive under its foliage. Ground boxes and the steep sides of fixed scenery are met through the same OpenPhotex collision as OpenMTM2, and each truck rolls on its own tires' size. Light objects with a mass, such as cones, are knocked aside; CPR's cones and signs, which carry no mass, get Monster Truck Madness 2's weights. Camera-facing billboards are not solid, except MTM2's "Collide (facing)" objects. MTM1 and MTM2 Top Crush cars flatten gradually under the truck.
- Show hitboxes draws a wireframe around everything the simulation can collide with.
- Picking another truck swaps it in where you are, keeping speed, heading, gearbox and camera. Loading a different track parks the truck, which stays loaded for the next one.
- A city (San Francisco, Los Angeles, New York, Chicago or Dallas) opens from its folder: four globe tiles of terrain, about 250 km across, draped in the game's satellite imagery, with the city's buildings, airports, stadiums and bridges standing on it. A single numbered scenery EPD opened from disk shows its one globe tile.
- Terrain near the camera streams in at the imagery's full resolution, about 15 m a pixel, with the airports' finer detail textures, over the finer relief the scenery stores for rugged cells.
- The camera opens over downtown. Weather applies, and at dusk and night the cities light up.
- Test Drive works on the scenery: the truck starts under the camera, and buildings and bridges are solid.
- The free camera uses MTM2's field of view, about 70 degrees vertically; the mouse wheel and the Zoom slider narrow or widen it from 0.5× to 8×.
- The minimap shows the heightfield (or, for Fly!, the satellite imagery) and moves the camera where you click.
- The Markers and View Options panels toggle each layer: terrain, textures, grid, wireframes, objects, vegetation, ground boxes, collision boxes, water, fog volumes, waterfalls, backdrop, sky, fog and markers. Distance, sunlight and gamma have sliders. Panels collapse from their headings, and only the controls the loaded track uses appear.
- Track Data and Stats list the track's metadata and statistics: textures, objects, courses, ground boxes, and CPR surface and wall types.
- The Models and Textures buttons under Track Data open two floating boxes, after JSTraxx's (and Traxx's) boxes of the same names. Models lists every model in the track with how many objects place it, a 3D preview with turn, tilt and zoom, and its vertex and triangle counts; picking one flies the camera to the front of the first object using it and outlines that object in wireframe, and the arrows step through the others. Textures shows every terrain, CART road, model and sky texture in a grid of small tiles (24 to 128 px, 48 by default; a larger box shows more), and a click shows the texture's name, slot and size, and its ground type where the game gives one: Grass, Cement, Dirt and so on, with depth, from the .TTY in Monster Truck Madness and CART, Evo's .TEX (with its vegetation class), and CART's road surface types. Terminal Velocity, Fury3 and Hellbender store none. Both boxes can be moved and resized, and remember where they were.
| Component | Role |
|---|---|
| ES modules | Application controller, archive staging, navigation, and scene management |
| Module Web Worker | Archive indexing, track parsing, model decoding, and terrain construction |
| OPFS | Isolated temporary storage for archives opened from disk or URL |
| Three.js r169 | Terrain, model, water, backdrop, lighting, and overlay rendering |
| fflate | ZIP extraction |
| OpenPhotex | Terminal Reality format parsing and MTM2 vehicle simulation, vendored as plain ES modules in src/vendor/openphotex/ |
src/
├── app.js User-interface controller and track-loading flow
├── scene.js Three.js scene, terrain, objects, and overlays
├── nav.js Free-flight camera navigation
├── worker-client.js Promise wrapper for the module worker
├── zip-utils.js POD-in-ZIP extraction
├── folder-contents.js What a picked folder holds: archives and Fly! scenery sets
├── drive/ Test Drive: truck simulation, colliders, cameras, and input
├── shared/ OPFS, path, palette, and CPR schema helpers
├── vendor/openphotex/ OpenPhotex build: the format parsers (do not edit)
└── worker/ SIT, LVL, TRK, BIN, texture, and terrain decoders; fly/ assembles Fly! scenery
Archives are read by OpenPhotex, the shared Terminal Reality format library; src/worker/pod-format.js only feeds it bytes. The vendored copy is generated, never edited here: change OpenPhotex, then refresh it from the OpenPhotex checkout with npm run build && npm run vendor -- ../JSTrackViewer/src/vendor/openphotex. src/vendor/openphotex/VERSION records the version and commit it was built from.
- Rendering is intended for inspection. Apart from Test Drive, the viewer does not emulate the games: no AI, audio, weapons, enemies, or game scripting.
- Test Drive reads Monster Truck Madness and Monster Truck Madness 2 truck archives. 4x4 Evolution trucks use a different manifest and are refused rather than misread.
- Test Drive handling is a feel-alike, not the original. Monster Truck Madness 2 keeps its mass, spring rates, gearing and tire grip in the executable rather than in track or truck files, so those values are approximated; see the physics notes.
- Test Drive does not simulate other trucks, damage, or race rules beyond checkpoint order and lap timing.
- CART Precision Racing absolute wall height is approximate.
- CART Precision Racing catch fencing falls back to a synthesized panel unless
ART/CATCH3D.RAWis reachable, since it ships inSTARTUP.PODrather than in a track POD. - CART Precision Racing tree walls (
wallType7) are drawn as a tall textured panel, not as billboarded foliage. - Terminal Velocity and Fury3 tunnel segment types (doors, blockers) are not drawn; a door segment is drawn as plain tube. Hellbender ships no tunnel levels.
- Terminal Velocity and Fury3 chambers are found per square (solid rock within seven squares in all four directions), which can also take in a deep enclosed pit open to the sky; the game decides from the camera's position instead.
- Hellbender's moving terrain is marked, not animated.
- Terminal Velocity and Fury3 fog distance is not read from the game; it follows the Distance slider.
- Terminal Velocity and Fury3 powerup models ship in
STARTUP.POD, not in a level archive, so loose powerups are drawn as named markers unless the opened archive carries the models. - 4x4 Evolution
.SDWbaked shadow overlays and.RTDgrids are read but not drawn. - 4x4 Evolution 2 material stages beyond diffuse and alpha (bump, cubic reflection, gloss and projected shadows) are not reproduced.
- Community Patch 4: lake reflections, the fog volumes' soft edges, height falloff and wisps (their shader lives in the game's renderer, which is not available), vegetation tint, the far card cross-fade band, scenery detail tiers (every tier is drawn) and tree collision are not reproduced. SRF surface types are shown, not driven on: a model's collision is the same with or without one.
- Community Patch 4 waterfalls: no sound, droplets, foam zones or landing rings; only the Original look is drawn (not CP4's Enhanced and Realistic water looks, nor the ice look of a frozen fall in snow); the mist is a plain translucent box, like the fog volumes; a custom texture that names one of the track's animations is drawn still; and every fall is drawn whatever its distance, without the game's draw range.
- Track format version 6 (SI3) tracks: waterfalls are built in the track's own world: crests wrapped at its width, the N x N lake map, heights checked against the terrain's range and the walk on its terrainHeightMap heights at full precision. A 256-cell track (SIT, SI2 or SI3) reads WTR and WFL version 1 only and a 512-cell SI3 version 2 only; a file of the other version is a warning and is not drawn. The viewer draws the whole world without wrapping it, as it does every track, and a 512-cell Spline or Full Map track's 8 ft mesh is four times a Community Patch 4 one's.
- 4x4 Evolution vegetation stands on the drawn terrain and is turned by a viewer convention, because a
.VEGrecord carries no orientation;treeBiasYis read but not applied. - Standalone downloadable 4x4 Evolution
.LTEtracks are not supported; they are a compressed format that reuses assets the track does not carry. - Fly! scenery does not draw its beacons and windsocks, whose models ship with the game rather than the scenery, or the sectional charts in
Maps\. Cells outside a city's photographed area use generic textures that also ship with the game, so they are drawn in flat land and water colours. - Assets referenced by a track but absent from its archive cannot be rendered.
- 4x4 Evolution 1/2 track rendering analysis
- CART Precision Racing track layer analysis
- Terminal Velocity/Fury3 level format analysis
- Hellbender level format analysis
- Terminal Velocity executable analysis, Fury3 executable analysis and Hellbender executable analysis: engine rules, cheat codes and lineage
- CPREdit guide
- CART Precision Racing racetrack layer implementation guide
- Monster Truck Madness 2 physics notes
- JSPod: browser-based POD archive and individual-asset viewer.
- JSMTM2Converter: browser-based 4x4 Evolution to MTM2 track and truck converter.
- JSTruckViewer: browser-based MTM1 and MTM2 truck viewer.
JSTrackViewer follows the lineage of JTraxx and the original Traxx track editor for Monster Truck Madness and Monster Truck Madness 2.
Developed by Juan Pablo Utreras for the Monster Truck Madness Guild.
Released under the Apache License 2.0.
The game names and Terminal Reality are trademarks of their respective owners. This project is an independent community tool and is not affiliated with or endorsed by their owners.
