Traxx 1.7.3 and the new features
Traxx 1.7.3 and the new features
https://mtm2.com/%7Etraxx/downloads/traxx_173.zip <--- updated 11/14/26
I am going to have to consolidate in the traxx tutorial all these new features that I have been adding because at this point they are spread over various threads. lol. And this one is significant enough that it warrants its own thread rather than adding it to the previous one.
For reference: viewtopic.php?t=7534
Ok so this update has a big amount of changes that goes together with the new engine update. First to get out of the way:
- updated the UI so that MOST windows now can be resized. This is purely a QoL update.
- the track picture, info photo and track icon (in the track list) can now be of .png but it still needs to be of the restricted size.
- you can now import heightmaps in .raw, .png and .tga format. they have to be grayscale. PNG is most likely the best choice here as it is the most versatile both in file size, resolution and color grading wise.
- updated the random terrain generator to allow the new 16bit heightmaps
Vegetation
Traxx (and the game) can now take two additional masks. A VEGETATION_V.PNG mask and a VEGETATION_G.PNG mask. You can name them any way you want, the _V and _G part is important. For the most part, they both work identically except for some small important differences.
What they both share:
Both masks need to be done on a square image, 256x256, 512x512, 1024x1024 or 2048x2048. The higher resolution the more finer the placement. These file sizes will be small anyway due to the fact that they will be just a few solid colours. I would recommend using the mask export that the game supports and that I pointed out in the detail mask work. Start a new layer in photoshop (or whatever program you are using) and create an image with a fully black background (zeroes all the way), then load the image exported from the game so that it gives you an idea where to paint and then do new layers and paint away. When you save at the end, make sure to remove the image exported by the game because it is necessary that you only have BLACK (which the game will ignore) and a few solid colours. Paint brush should be 100% harshness here, the smother the edges the worse it is (unlike the normal mask work which smooth edges were fine and the game reacted to them).
When you load these masks, traxx will automatically detect the colours. Now for each colour you can add one model (.bin file) or even multiple ones. If you add multiple ones, then traxx will mix and match. Traxx is the authoring tool here, so traxx places the models and the engine honors what traxx does.
The reason there are two of them is that obviously, these colors on a single mask cannot overlap. So the idea is to have a mask that can have trees and whatever else you want and then a different mask that has grass/shrubs etc that can go in the same place as where the trees are. That is why there are two options. The small grass/shrubs are ALWAYS non-collide and they do not produce shadows. So keep this in mind.
So let's go ahead and explain what each button does:
Seed
The starting number for the random planting. Same masks, same rules and same seed always give exactly the same forest, so a re-plant never reshuffles anything unless you change something. A different seed gives a different but equally valid scatter of the same layout.
Default 1. Any whole number
New Seed
Picks a fresh seed for you. Use it when the forest’s layout is right but the exact scatter isn’t: a clump in an awkward spot, or a gap you don’t like. Re-plant afterwards to see the new result.
AI course corridor (ft)
A clear strip kept free of trees around the AI driving line, the start grid and every checkpoint gate. The game’s AI doesn’t know about trees yet, so this setting is the only thing stopping AI trucks driving into them. It’s measured from the course line outwards on each side, so 40 means an 80 ft wide clear lane. Grass ignores it, because grass never collides.
Default 40 ft. Range 0–500.
Object margin (ft)
Extra clear space kept around every scenery object, so trees don’t grow through buildings, ramps or other models. It’s added to the size of each object. Checkpoint gates use the corridor setting instead. Grass ignores it too.
Default 8 ft. Range 0–200.
_V mask:
Trees and bushes: solid plants that can collide, placed individually with a minimum spacing.
_G mas:
Grass and scrub: ground cover scattered in clumps per 32 ft tile. It never collides and has no spacing.
The same colour can mean different things on each mask.
Let's move on to what do you do with the colors:
Name
A label for your own use, such as “pine forest” or “dry grass”. It only appears in Traxx.
Spacing (ft), trees layer only (_V mask only)
The minimum distance between two tree trunks in this colour. It’s also checked against trees of other colours, so forests meeting at a colour border don’t overlap. Small numbers make a dense forest; large numbers make an open woodland.
Default 18 ft. Range 2–500.
Density (%), trees layer only (_V mask only)
How full to pack the area, as a percentage of what the spacing allows. 100% packs as tightly as the spacing permits, and lower values thin it out at random for a more natural look.
Default 70%. Range 0–100.
Clumps per tile, grass layer only (_G mask only)
How many grass clumps go on a fully painted 32 × 32 ft tile. A tile that’s only half covered by the colour gets about half as many, and they land only on the painted pixels.
Default 300. Range 0–1024. A tile holds 1024 clumps at most, counting all grass colours together.
Then when you select a color, for each of these colours you can add one or multiple objects. Btw... these can be any objects, you can add tractors if you want for both _V and _G but the point is that these multiply a lot and they are not part of the object cap limit, so if you load heavy objects you can tank the FPS badly. Each color can hold up to 8 objects.
Status line
Shows the current counts: trees, grass clumps and species. It also warns you when:
The rules have changed since planting: re-plant to apply them.
The masks have changed since planting: re-plant to update.
Nothing is planted yet: there are rules but no plants.
The vegetation came from another tool: it’s read-only, and Clear All lets you author your own.
Buttons:
Re-plant
Plants everything from the masks and rules, and replaces the previous plant. Afterwards a report lists the counts per colour, plus anything that went wrong:
a model that isn’t in the track;
a limit reached (30,000 trees, 131,072 clumps, 60 species of which at most 16 are grass);
an anti-aliased mask;
a model the game can’t instance. As a tree it would draw only the nearest ~128 copies; as grass it wouldn’t draw at all.
Trees are never planted:
on raised ground boxes;
near objects (Object margin);
in the AI corridor;
under water;
on slopes steeper than the model’s Max slope.
Grass is only kept off raised ground boxes and out of water.
Make Far Cards
For each tree model, Traxx renders a flat stand-in seen from far away: two pictures crossed at 90°, one from the front and one from the side. Beyond about 950 ft the game draws this card instead of the full 3D tree, which is much cheaper to draw. The card’s name is filled into each model’s “Far card model”.
Skipped: grass, facing models, models that already have a far card you typed in, models that are already flat cards, and animated models.
Where it writes: card models go to your Models folder and card art to your ART folder.
Game folder protection: if a protected game folder is set in Options > Folders and the box allowing writes there is unticked, it refuses to write into that folder.
Afterwards: Re-plant, so the far cards reach the saved vegetation.
If you cancel: cards made in a session you then cancel stay in the model list until you use Purge Unused Models.
NOTE: The Far Cards only make sense if you are loading a 3D tree like the evo conversion trees. If you are using a MTM2 2D tree, it is pointless to make far cards.
Ok, so now let's talk what happens when you select a model and hit edit, it brings up the vegetation model which allows you to select properties for that specific model of how to behave.
Far card model (optional)
The stand-in model drawn beyond about 950 ft. Make Far Cards fills this in for you, but you can type the name of your own card instead. Leave it empty for no card: the full tree then draws at every distance. Greyed out when Facing is ticked.
Weight (1–1000)
This model’s share of the plants within its colour, relative to the colour’s other models. Pine at 3 and oak at 1 gives about 75% pines. Only the ratio matters, and with one model in the colour it has no effect.
Default 1.
Scale min / Scale max
Every plant gets its own random size between these two values, which makes one model look like many different trees. 1.0 is the model’s own size.
Default 0.8–1.25. Range 0.0625–16.
This scale min/max is like the 4x4 Evo, where you can have the same exact tree/model (and thus only one copy in memory) and it gets rendered at different sizes. It's the cheapest way to give the illusion of multiple models when it's really just one.
Random rotation
On: each plant faces a random direction. Off: they all face the same way, heading 0.
Default on.
Collide (trees only; grass is always None)
None: trucks drive straight through it. Use it for bushes and decorative plants.
Trunk: a solid trunk at the base of the tree. You hit the trunk, not the branches. The default for trees. (best used for those evo trees)
Model: uses the model’s own collision shape.
Trunk diameter / Trunk height (ft, 0 = auto), only with Collide = Trunk
The size of the solid trunk at scale 1.0. It grows and shrinks with each plant’s scale. 0 lets the engine work it out from the model’s base.
Default 0 (auto).
Sink (ft, 0–50)
Lowers each plant by a random amount between 0 and this value, so tree heights vary more naturally and roots stay buried on uneven ground.
Default 0.
Scenery detail (you know, the old school way of saving FPS) - also, this setting is ignored by grass.
Sparse (always shown), the default.
Normal.
Complex.
Cast shadow
Whether the plant casts a sun shadow in the game.
Default on for trees, off for grass.
Facing (always turns to the camera)
For flat 2D models such as grass cards, ferns, reeds or sprite trees, which look like thin slivers when seen edge-on. Every plant turns to face the camera, like a facing scenery object, and Random rotation no longer matters. A facing model needs no far card. Flat facing cards don’t cast sun shadows unless the player turns on “Facing Obj. Shadows” in the game, and facing grass never casts one.
Default off.
Cross-fade into the far card, trees only, needs a far card
On: the tree gradually dithers into its far card between 900 and 1000 ft. Off: it swaps all at once at 950 ft, which you can see as a pop. Greyed out when Facing is ticked.
Default on.
Note: this cross fade is VERY pleasant and if it's far enough, you don't even notice it.
Max slope (degrees, 0 = no limit), trees only
Trees of this model aren’t planted on ground steeper than this, for example to keep pines off cliffs.
Default 0, meaning no limit. Range 0–90.
Stay tuned for more
I am going to have to consolidate in the traxx tutorial all these new features that I have been adding because at this point they are spread over various threads. lol. And this one is significant enough that it warrants its own thread rather than adding it to the previous one.
For reference: viewtopic.php?t=7534
Ok so this update has a big amount of changes that goes together with the new engine update. First to get out of the way:
- updated the UI so that MOST windows now can be resized. This is purely a QoL update.
- the track picture, info photo and track icon (in the track list) can now be of .png but it still needs to be of the restricted size.
- you can now import heightmaps in .raw, .png and .tga format. they have to be grayscale. PNG is most likely the best choice here as it is the most versatile both in file size, resolution and color grading wise.
- updated the random terrain generator to allow the new 16bit heightmaps
Vegetation
Traxx (and the game) can now take two additional masks. A VEGETATION_V.PNG mask and a VEGETATION_G.PNG mask. You can name them any way you want, the _V and _G part is important. For the most part, they both work identically except for some small important differences.
What they both share:
Both masks need to be done on a square image, 256x256, 512x512, 1024x1024 or 2048x2048. The higher resolution the more finer the placement. These file sizes will be small anyway due to the fact that they will be just a few solid colours. I would recommend using the mask export that the game supports and that I pointed out in the detail mask work. Start a new layer in photoshop (or whatever program you are using) and create an image with a fully black background (zeroes all the way), then load the image exported from the game so that it gives you an idea where to paint and then do new layers and paint away. When you save at the end, make sure to remove the image exported by the game because it is necessary that you only have BLACK (which the game will ignore) and a few solid colours. Paint brush should be 100% harshness here, the smother the edges the worse it is (unlike the normal mask work which smooth edges were fine and the game reacted to them).
When you load these masks, traxx will automatically detect the colours. Now for each colour you can add one model (.bin file) or even multiple ones. If you add multiple ones, then traxx will mix and match. Traxx is the authoring tool here, so traxx places the models and the engine honors what traxx does.
The reason there are two of them is that obviously, these colors on a single mask cannot overlap. So the idea is to have a mask that can have trees and whatever else you want and then a different mask that has grass/shrubs etc that can go in the same place as where the trees are. That is why there are two options. The small grass/shrubs are ALWAYS non-collide and they do not produce shadows. So keep this in mind.
So let's go ahead and explain what each button does:
Seed
The starting number for the random planting. Same masks, same rules and same seed always give exactly the same forest, so a re-plant never reshuffles anything unless you change something. A different seed gives a different but equally valid scatter of the same layout.
Default 1. Any whole number
New Seed
Picks a fresh seed for you. Use it when the forest’s layout is right but the exact scatter isn’t: a clump in an awkward spot, or a gap you don’t like. Re-plant afterwards to see the new result.
AI course corridor (ft)
A clear strip kept free of trees around the AI driving line, the start grid and every checkpoint gate. The game’s AI doesn’t know about trees yet, so this setting is the only thing stopping AI trucks driving into them. It’s measured from the course line outwards on each side, so 40 means an 80 ft wide clear lane. Grass ignores it, because grass never collides.
Default 40 ft. Range 0–500.
Object margin (ft)
Extra clear space kept around every scenery object, so trees don’t grow through buildings, ramps or other models. It’s added to the size of each object. Checkpoint gates use the corridor setting instead. Grass ignores it too.
Default 8 ft. Range 0–200.
_V mask:
Trees and bushes: solid plants that can collide, placed individually with a minimum spacing.
_G mas:
Grass and scrub: ground cover scattered in clumps per 32 ft tile. It never collides and has no spacing.
The same colour can mean different things on each mask.
Let's move on to what do you do with the colors:
Name
A label for your own use, such as “pine forest” or “dry grass”. It only appears in Traxx.
Spacing (ft), trees layer only (_V mask only)
The minimum distance between two tree trunks in this colour. It’s also checked against trees of other colours, so forests meeting at a colour border don’t overlap. Small numbers make a dense forest; large numbers make an open woodland.
Default 18 ft. Range 2–500.
Density (%), trees layer only (_V mask only)
How full to pack the area, as a percentage of what the spacing allows. 100% packs as tightly as the spacing permits, and lower values thin it out at random for a more natural look.
Default 70%. Range 0–100.
Clumps per tile, grass layer only (_G mask only)
How many grass clumps go on a fully painted 32 × 32 ft tile. A tile that’s only half covered by the colour gets about half as many, and they land only on the painted pixels.
Default 300. Range 0–1024. A tile holds 1024 clumps at most, counting all grass colours together.
Then when you select a color, for each of these colours you can add one or multiple objects. Btw... these can be any objects, you can add tractors if you want for both _V and _G but the point is that these multiply a lot and they are not part of the object cap limit, so if you load heavy objects you can tank the FPS badly. Each color can hold up to 8 objects.
Status line
Shows the current counts: trees, grass clumps and species. It also warns you when:
The rules have changed since planting: re-plant to apply them.
The masks have changed since planting: re-plant to update.
Nothing is planted yet: there are rules but no plants.
The vegetation came from another tool: it’s read-only, and Clear All lets you author your own.
Buttons:
Re-plant
Plants everything from the masks and rules, and replaces the previous plant. Afterwards a report lists the counts per colour, plus anything that went wrong:
a model that isn’t in the track;
a limit reached (30,000 trees, 131,072 clumps, 60 species of which at most 16 are grass);
an anti-aliased mask;
a model the game can’t instance. As a tree it would draw only the nearest ~128 copies; as grass it wouldn’t draw at all.
Trees are never planted:
on raised ground boxes;
near objects (Object margin);
in the AI corridor;
under water;
on slopes steeper than the model’s Max slope.
Grass is only kept off raised ground boxes and out of water.
Make Far Cards
For each tree model, Traxx renders a flat stand-in seen from far away: two pictures crossed at 90°, one from the front and one from the side. Beyond about 950 ft the game draws this card instead of the full 3D tree, which is much cheaper to draw. The card’s name is filled into each model’s “Far card model”.
Skipped: grass, facing models, models that already have a far card you typed in, models that are already flat cards, and animated models.
Where it writes: card models go to your Models folder and card art to your ART folder.
Game folder protection: if a protected game folder is set in Options > Folders and the box allowing writes there is unticked, it refuses to write into that folder.
Afterwards: Re-plant, so the far cards reach the saved vegetation.
If you cancel: cards made in a session you then cancel stay in the model list until you use Purge Unused Models.
NOTE: The Far Cards only make sense if you are loading a 3D tree like the evo conversion trees. If you are using a MTM2 2D tree, it is pointless to make far cards.
Ok, so now let's talk what happens when you select a model and hit edit, it brings up the vegetation model which allows you to select properties for that specific model of how to behave.
Far card model (optional)
The stand-in model drawn beyond about 950 ft. Make Far Cards fills this in for you, but you can type the name of your own card instead. Leave it empty for no card: the full tree then draws at every distance. Greyed out when Facing is ticked.
Weight (1–1000)
This model’s share of the plants within its colour, relative to the colour’s other models. Pine at 3 and oak at 1 gives about 75% pines. Only the ratio matters, and with one model in the colour it has no effect.
Default 1.
Scale min / Scale max
Every plant gets its own random size between these two values, which makes one model look like many different trees. 1.0 is the model’s own size.
Default 0.8–1.25. Range 0.0625–16.
This scale min/max is like the 4x4 Evo, where you can have the same exact tree/model (and thus only one copy in memory) and it gets rendered at different sizes. It's the cheapest way to give the illusion of multiple models when it's really just one.
Random rotation
On: each plant faces a random direction. Off: they all face the same way, heading 0.
Default on.
Collide (trees only; grass is always None)
None: trucks drive straight through it. Use it for bushes and decorative plants.
Trunk: a solid trunk at the base of the tree. You hit the trunk, not the branches. The default for trees. (best used for those evo trees)
Model: uses the model’s own collision shape.
Trunk diameter / Trunk height (ft, 0 = auto), only with Collide = Trunk
The size of the solid trunk at scale 1.0. It grows and shrinks with each plant’s scale. 0 lets the engine work it out from the model’s base.
Default 0 (auto).
Sink (ft, 0–50)
Lowers each plant by a random amount between 0 and this value, so tree heights vary more naturally and roots stay buried on uneven ground.
Default 0.
Scenery detail (you know, the old school way of saving FPS) - also, this setting is ignored by grass.
Sparse (always shown), the default.
Normal.
Complex.
Cast shadow
Whether the plant casts a sun shadow in the game.
Default on for trees, off for grass.
Facing (always turns to the camera)
For flat 2D models such as grass cards, ferns, reeds or sprite trees, which look like thin slivers when seen edge-on. Every plant turns to face the camera, like a facing scenery object, and Random rotation no longer matters. A facing model needs no far card. Flat facing cards don’t cast sun shadows unless the player turns on “Facing Obj. Shadows” in the game, and facing grass never casts one.
Default off.
Cross-fade into the far card, trees only, needs a far card
On: the tree gradually dithers into its far card between 900 and 1000 ft. Off: it swaps all at once at 950 ft, which you can see as a pop. Greyed out when Facing is ticked.
Default on.
Note: this cross fade is VERY pleasant and if it's far enough, you don't even notice it.
Max slope (degrees, 0 = no limit), trees only
Trees of this model aren’t planted on ground steeper than this, for example to keep pines off cliffs.
Default 0, meaning no limit. Range 0–90.
Stay tuned for more
Re: Traxx 1.7.0 and the new features
Terrain Grids
When you start a new track now, you have 4 modes to chose from:
8 bit classic
16 bit (classic... it doesn't mention classic but it's basically identical to the old school 8bit but with 16bit accuracy)
16 bit spline - this is the 4x4 evo rounded terrain
16 bit Full Map - this is basically full control over the terrain, there's no automatic spline (btw, a full map is a 1024x1024 greyscale map)
And to further clarify
8bit classic - 32foot square tiles, integer terrain height
16bit (classic) - 32foot square tiles, floating point terrain height (10.4, 123.7 etc)
16bit spline - 32foot square tiles, floating point terrain height BUT with automatic subdivision of the 32foot square into 8ft square, the game uses this extra space within the 32foot square to curve the terrain (cannot achieve MTM2 sharp edges, will automatically round them up Evo style)
16bit Full Map - full control over the square tile. So while applying textures is still done based on a 32foot square tile, the terrain editing is actually done on a 8ft square tile now. So this is giving the user complete control over the terrain and the only way to achieve 4x4 Evo rounded terrain AND MTM2 sharp edges
Using the Special>Terrain Grid option you can kinda convert between them. Going from lower to higher is easy but going from higher to lower will inevitably lead to a loss in detail as terrain gets rounded to the nearest value that it can hold.
The special>terrain grid>store heights as PNG is mostly to be used if you are using a full map because traxx will do a 1024x1024 .raw greyscale file which ends up at 2mb. with this activated, it CAN compress it but not necessarily, this will depend on the composition of the map but the 2mb can go fro 35k to the full 2mb. The .raw file is 2mb no matter what. As a general rule I would say to leave this on all the time.
Fog objects
When you give an generic box the FOG property it becomes a cloud that is directly created by the video card's pixel shader. The visual size (edges) of it are going to be based on the size that you give the box. So imagine the generic box now suddenly having fog inside it, that's what it is. And you can freely make it biger, smaller, narrower, higher above ground etc. Traxx changes the shape a little bit to make it easier to tell apart.
Floor offset from object (ft) 0 Moves the fog’s floor up or down from the object’s height. The top is then floor + Height. The line under it shows the result as real heights (“Floor 96 ft, top 136 ft”).
But they also have specific properties you can change:
And you can control in what types of weathers it appears.
Limit of 50 fogs per track (for now)
Lakes
Ok so lakes are a body of water that are in addition to the traditional water. The lake can NEVER be lower than the baseline water that is set in the track components. Also a lake has no tide, so it stays fixed (for now). Otherwise it has all the same properties as the regular water. The reflection might be finnicky... this is a work in progress and it's going to depend on performance too. Up to 3 lakes have perfect reflection but more than that it might be a little off depending on specific circumstances.
The way to make a lake, you make a hole in the ground (as in, you make a crater), using the terrain editing tool, whichever one helps you the most with accurate placement, aim inside the crater, right click and select Create Lake! Now you have the option of how high or low you want the lake to be. Traxx will automatically detect the crater edge where if you go above, the water would spill out and it will not allow you to go higher than that amount. Lower, you can go as far as you want. You can also chose whether it's reflective or not.
Traxx itself draws the body of water with different colours just to help you differentiate, the water itself for now will not look different inside the game.
When you start a new track now, you have 4 modes to chose from:
8 bit classic
16 bit (classic... it doesn't mention classic but it's basically identical to the old school 8bit but with 16bit accuracy)
16 bit spline - this is the 4x4 evo rounded terrain
16 bit Full Map - this is basically full control over the terrain, there's no automatic spline (btw, a full map is a 1024x1024 greyscale map)
And to further clarify
8bit classic - 32foot square tiles, integer terrain height
16bit (classic) - 32foot square tiles, floating point terrain height (10.4, 123.7 etc)
16bit spline - 32foot square tiles, floating point terrain height BUT with automatic subdivision of the 32foot square into 8ft square, the game uses this extra space within the 32foot square to curve the terrain (cannot achieve MTM2 sharp edges, will automatically round them up Evo style)
16bit Full Map - full control over the square tile. So while applying textures is still done based on a 32foot square tile, the terrain editing is actually done on a 8ft square tile now. So this is giving the user complete control over the terrain and the only way to achieve 4x4 Evo rounded terrain AND MTM2 sharp edges
Using the Special>Terrain Grid option you can kinda convert between them. Going from lower to higher is easy but going from higher to lower will inevitably lead to a loss in detail as terrain gets rounded to the nearest value that it can hold.
The special>terrain grid>store heights as PNG is mostly to be used if you are using a full map because traxx will do a 1024x1024 .raw greyscale file which ends up at 2mb. with this activated, it CAN compress it but not necessarily, this will depend on the composition of the map but the 2mb can go fro 35k to the full 2mb. The .raw file is 2mb no matter what. As a general rule I would say to leave this on all the time.
Fog objects
When you give an generic box the FOG property it becomes a cloud that is directly created by the video card's pixel shader. The visual size (edges) of it are going to be based on the size that you give the box. So imagine the generic box now suddenly having fog inside it, that's what it is. And you can freely make it biger, smaller, narrower, higher above ground etc. Traxx changes the shape a little bit to make it easier to tell apart.
Floor offset from object (ft) 0 Moves the fog’s floor up or down from the object’s height. The top is then floor + Height. The line under it shows the result as real heights (“Floor 96 ft, top 136 ft”).
But they also have specific properties you can change:
Code: Select all
Thickness
Property Default What it does
Visibility into it (ft) 300 How far you can see into the fog at its floor, the distance at which it’s about 95% opaque. Smaller is thicker. About 30 is a wall, 150 thick mist, 1000 a light haze. The minimum is 1.
Thins by half every (ft) 8 The fog is thickest at the floor and halves in thickness every this many feet going up, so it pools low. A small value makes a thin layer hugging the ground. 0 makes it uniform from bottom to top.
Softness: hiding the box shape
Property Default What it does
Soft sides (ft) 20 The fog fades to nothing over this distance inside each side wall. It is capped at half the footprint. Make it bigger if you can see a straight wall of fog.
Soft top (ft) 5 The same fade, under the top face. It is capped at the height.
Soft bottom (ft) 0 The fade going up from the floor. 0 means full thickness right at the floor, which is right when the floor is sunk under water or ground. Raise it for fog that floats, so its underside blends instead of ending in a flat line.
Roundness 100% The shape of the footprint: 0% is a rectangle, and 100% is an ellipse filling width × length (a circle if they’re equal). The soft sides follow the rounded outline, so there are no corners.
Colour and opacity
Property Default What it does
Colour pale blue-grey The fog’s colour in full daylight. The game darkens it to match the weather’s light, so one setting works in every weather: Rain ×0.3, Dusk ×0.375, Night ×0.25, Pitch black ×0.05.
Opacity cap (%) 100 The most opaque the fog can ever get, however much of it you look through. At 60 you can always see 40% through it, even across a huge bank. Use it for haze that should never fully hide things.
Wisps: breaking it up
Property Default What it does
Wisps (%) 50 Drifting 3D noise that breaks the fog into patches and frays its edges. 0 is smooth, even fog, which also costs nothing extra to draw.
Wisp size (ft) 40 How big the patches are. Small values give fine streaks; large values give big rolling banks.
Drift (ft/s) 3 How fast the wisps move, along the object’s heading. To change the drift direction, rotate the object. 0 means still.Limit of 50 fogs per track (for now)
Lakes
Ok so lakes are a body of water that are in addition to the traditional water. The lake can NEVER be lower than the baseline water that is set in the track components. Also a lake has no tide, so it stays fixed (for now). Otherwise it has all the same properties as the regular water. The reflection might be finnicky... this is a work in progress and it's going to depend on performance too. Up to 3 lakes have perfect reflection but more than that it might be a little off depending on specific circumstances.
The way to make a lake, you make a hole in the ground (as in, you make a crater), using the terrain editing tool, whichever one helps you the most with accurate placement, aim inside the crater, right click and select Create Lake! Now you have the option of how high or low you want the lake to be. Traxx will automatically detect the crater edge where if you go above, the water would spill out and it will not allow you to go higher than that amount. Lower, you can go as far as you want. You can also chose whether it's reflective or not.
Traxx itself draws the body of water with different colours just to help you differentiate, the water itself for now will not look different inside the game.
Re: Traxx 1.7.0 and the new features
https://www.mtm2.com/~mtmg/downloads/mt ... andbox.zip
This was the sandbox that I was using to test the features out. it has both the .txx and the .pod file
You will also note that I used horses as grass for the grass mask
This was simply out of curiosity to see how it works exactly. And yes, you can basically add whatever you want. So the only limit to whatever you want to add is performance wise really.
This was the sandbox that I was using to test the features out. it has both the .txx and the .pod file
You will also note that I used horses as grass for the grass mask
Re: Traxx 1.7.0 and the new features
What I'm presented with whenever I run Traxx in full window. :\

WAIT! Scratch that! The 1920X1080 resolution setting in the Options cured it!

WAIT! Scratch that! The 1920X1080 resolution setting in the Options cured it!
Re: Traxx 1.7.0 and the new features
I've updated JSTraxx to bring it up to feature parity with version 1.7.
https://juanputrerasm.github.io/JSTraxx/
You do not have the required permissions to view the files attached to this post.
Re: Traxx 1.7.0 and the new features
By the way, the executable is missing 32bit MSVCP140.dll, you should include it in the zip file
i had to install this thing to get it https://aka.ms/vs/17/release/VC_redist.x86.exe
i had to install this thing to get it https://aka.ms/vs/17/release/VC_redist.x86.exe
Re: Traxx 1.7.1 and the new features
https://mtm2.com/%7Etraxx/downloads/traxx_172.zip <--- updated 11/13/26
https://www.mtm2.com/~mtmg/misc/fog_test_sandbox.zip <--- updated sandbox track with both .txx and .pod
- Before I move on to the main feature I wanna point something out. The edges of the world inside traxx, when using OpenGL renderer, now copy 3 tiles from the opposite side. These tiles are not editable. This is just a visual help for you to align the terrain/textures/water for a perfect wrap around. These copies are live, so when you edit the terrain at the other side of the world, the copies will be updated immediately.
- there's now a visual hint when creating course 0, it shows you how the segments connect to each other to give you a rough idea of how the map will be created
- this new segment connection is also wrap-around aware and it will correctly connect in a wrap around style
The libraries are now included in the .exe so Traxx is independent now.
Traxx 1.7.1 is the authoring tool for Waterfalls. It has some pretty robust checks to ensure that the waterfalls work correctly + it has a very handy dandy and pretty accurate visual guide for you to see how the water flows and where it lands!
The waterfalls are compatible with both traditional water look and the enhanced/realistic water. And the traditional water look also comes out pretty decently I might add, surprisingly decent I would add.
Waterfalls are created when in the terrain editing mode. I strongly recommend using the Single-point direct edit (The hand icon) for an easier time knowing where your mouse is pointing but you can do whatever you are comfortable with. There are two ways of creating a waterfall.
1. Having it start from nowhere.
2. Have it start from a body of water (let's call it lake) and land either on terrain or another body of water.
In both cases the way it works you right click and select Draw Waterfall. I know I said earlier you wanna use the hand icon but actually when you draw a waterfall, it automatically switches to the hand icon. So here is how it works.
1. For starting out of nowhere.
Right click Draw Waterfall. It will switch into single edit mode and now you click where the beginning of your waterfall mesh starts. All you get to do is draw a line where the water begins and the rest is physics depending on parameters. The line that you draw can have up to 8 points, so you don't have to draw a perfect line for a perfect even waterfall. Important to remember: you are not drawing the path the waterfall goes. Only the starting point and can be a pretty long line. The line will be immediately highlighted by a yellow line. Once you are happy, hit enter (or right click again to enter properties and you can either confirm or cancel the waterfall). There's an arrow to show you which direction the water goes (but can be flipped).
Traxx will draw the origin line as LIGHT BLUE when everything checks out and it's valid, yellow when you are editing it and RED when there are problems. Traxx won't even write the pod when that happens. There's a comment box which will try to explain what the issues are. Warnings are not fatal (example warning that it lands on dry ground is just a reminder)
In the properties you have a bunch of options. Select the origin (either a lake or none, the case in point).
- You have flow speed which will show how fast the water is moving (both traditional and enhanced) at ORIGIN. The steeper the terrain, the faster the water accelerates including free fall. The flatter the terrain and the water slows down. This original original flow speed also works as the launcher and will contribute to how long the waterfall gets to be. Traxx draws a live visual guide of where the waterfall goes and how long it is.
Then you have opacity.
Then you have 3 options controlling Mist. This only appears inside the game if the waterfall lands into another body of water. In that case you can have the option to have mist, to create a nice visual effect. You can control how dense the mist is and how tall and the depth (starting from the landing moving outwards). The width is automatically calculated based on the landing size. Traxx will again draw a visual guide of roughly where the mist will be inside the game.
Then you can attach a sound file to it so that you can play a waterfall sound. It plays on loop. You can control volume or just disable it.
By default the game uses the original water texture modified a little bit and it works surprisingly well but if you want, you can add your own texture instead. You can either add a single texture and let the game try to do its magic OR you can add an .ani file for an animation.
Then you have flip direction in case you want it to go the other way... not sure how this works if you are driving to have it go upstream. lol
2. Water to water waterfall.
The overall control of the waterfall works exactly as above EXCEPT for the following.
In source you select which water (Lake) acts as the source. Here is where the tricky part comes in. The lakes themselves, they are not allowed to reach the same height as the terrain around them that holds them in. This is to prevent overflow of the entire map. Designating a waterfall to a Lake allows for that rule to be broken for the length of the waterfall line. So let's say you have a lake at 100 height and the surrounding terrain is 120 height to keep it in. You can draw the waterfall on one of those edges, as long as you want it. Then assign it to the lake. Then for the distance of that waterfall line, you can actually lower the terrain to the exact height of the lake (and technically the snap to lip should help you with aligning). With the terrain you cannot go lower than the height of the lake and traxx won't let you but you can go at the exact height. Now you are free the edit the exterior part of the terrain (as in where the water will flow) and guess what, when you shape your terrain around, traxx will update the visual guide of where the waterfall goes. Important to know: Editing the terrain on the side of the lake, the terrain that is close to the waterfall will also affect the way the waterfall behaves. Again all this is shown by traxx visually so you can edit and see real time what you are getting.
And that's all there is to it. The sandbox has both versions of the waterfall as reference, so you can check it out if it's confusing you.
https://www.mtm2.com/~mtmg/misc/fog_test_sandbox.zip <--- updated sandbox track with both .txx and .pod
- Before I move on to the main feature I wanna point something out. The edges of the world inside traxx, when using OpenGL renderer, now copy 3 tiles from the opposite side. These tiles are not editable. This is just a visual help for you to align the terrain/textures/water for a perfect wrap around. These copies are live, so when you edit the terrain at the other side of the world, the copies will be updated immediately.
- there's now a visual hint when creating course 0, it shows you how the segments connect to each other to give you a rough idea of how the map will be created
- this new segment connection is also wrap-around aware and it will correctly connect in a wrap around style
The libraries are now included in the .exe so Traxx is independent now.
Traxx 1.7.1 is the authoring tool for Waterfalls. It has some pretty robust checks to ensure that the waterfalls work correctly + it has a very handy dandy and pretty accurate visual guide for you to see how the water flows and where it lands!
The waterfalls are compatible with both traditional water look and the enhanced/realistic water. And the traditional water look also comes out pretty decently I might add, surprisingly decent I would add.
Waterfalls are created when in the terrain editing mode. I strongly recommend using the Single-point direct edit (The hand icon) for an easier time knowing where your mouse is pointing but you can do whatever you are comfortable with. There are two ways of creating a waterfall.
1. Having it start from nowhere.
2. Have it start from a body of water (let's call it lake) and land either on terrain or another body of water.
In both cases the way it works you right click and select Draw Waterfall. I know I said earlier you wanna use the hand icon but actually when you draw a waterfall, it automatically switches to the hand icon. So here is how it works.
1. For starting out of nowhere.
Right click Draw Waterfall. It will switch into single edit mode and now you click where the beginning of your waterfall mesh starts. All you get to do is draw a line where the water begins and the rest is physics depending on parameters. The line that you draw can have up to 8 points, so you don't have to draw a perfect line for a perfect even waterfall. Important to remember: you are not drawing the path the waterfall goes. Only the starting point and can be a pretty long line. The line will be immediately highlighted by a yellow line. Once you are happy, hit enter (or right click again to enter properties and you can either confirm or cancel the waterfall). There's an arrow to show you which direction the water goes (but can be flipped).
Traxx will draw the origin line as LIGHT BLUE when everything checks out and it's valid, yellow when you are editing it and RED when there are problems. Traxx won't even write the pod when that happens. There's a comment box which will try to explain what the issues are. Warnings are not fatal (example warning that it lands on dry ground is just a reminder)
In the properties you have a bunch of options. Select the origin (either a lake or none, the case in point).
- You have flow speed which will show how fast the water is moving (both traditional and enhanced) at ORIGIN. The steeper the terrain, the faster the water accelerates including free fall. The flatter the terrain and the water slows down. This original original flow speed also works as the launcher and will contribute to how long the waterfall gets to be. Traxx draws a live visual guide of where the waterfall goes and how long it is.
Then you have opacity.
Then you have 3 options controlling Mist. This only appears inside the game if the waterfall lands into another body of water. In that case you can have the option to have mist, to create a nice visual effect. You can control how dense the mist is and how tall and the depth (starting from the landing moving outwards). The width is automatically calculated based on the landing size. Traxx will again draw a visual guide of roughly where the mist will be inside the game.
Then you can attach a sound file to it so that you can play a waterfall sound. It plays on loop. You can control volume or just disable it.
By default the game uses the original water texture modified a little bit and it works surprisingly well but if you want, you can add your own texture instead. You can either add a single texture and let the game try to do its magic OR you can add an .ani file for an animation.
Then you have flip direction in case you want it to go the other way... not sure how this works if you are driving to have it go upstream. lol
2. Water to water waterfall.
The overall control of the waterfall works exactly as above EXCEPT for the following.
In source you select which water (Lake) acts as the source. Here is where the tricky part comes in. The lakes themselves, they are not allowed to reach the same height as the terrain around them that holds them in. This is to prevent overflow of the entire map. Designating a waterfall to a Lake allows for that rule to be broken for the length of the waterfall line. So let's say you have a lake at 100 height and the surrounding terrain is 120 height to keep it in. You can draw the waterfall on one of those edges, as long as you want it. Then assign it to the lake. Then for the distance of that waterfall line, you can actually lower the terrain to the exact height of the lake (and technically the snap to lip should help you with aligning). With the terrain you cannot go lower than the height of the lake and traxx won't let you but you can go at the exact height. Now you are free the edit the exterior part of the terrain (as in where the water will flow) and guess what, when you shape your terrain around, traxx will update the visual guide of where the waterfall goes. Important to know: Editing the terrain on the side of the lake, the terrain that is close to the waterfall will also affect the way the waterfall behaves. Again all this is shown by traxx visually so you can edit and see real time what you are getting.
And that's all there is to it. The sandbox has both versions of the waterfall as reference, so you can check it out if it's confusing you.
Re: Traxx 1.7.2 and the new features
I was hoping to continue work on the AI today but this traxx shortcoming was significant enough that it needed immediate attention, especially since traxx can control all the engine features.
- the Special>Lighting window got a complete redesign. Since the discovery that the game already allows the sun to be placed at any angle, this has now been translated into traxx. It turns out the sun is controlled by the X,Y,Z positions and they do the following:
X, Z work as the placement in the sky and thus the direction the sun hits you from (and casts the fancy shadows). They do contribute to the sun intensity.
Y, in addition to the position (whether it is higher or lower in the sky and thus directly contributes to the length of the shadow) it also contributes to the intensity of the shadows. It turns out that the crappy shadow map that everyone hates (that takes a bit to cache on the first run) is actually much more detailed than I realized. And the reason it was never dark enough was not because the shadow map was wrong but because it was never fed the correct information (Kmaster always complained the terrain is not dark enough for him). Well, now we can finally fix this. The Y position is also directly responsible for how strong the sun is aka how bright the track gets. X,Z are positioning, shadow direction and a bit of strength, Y controls shadow length and light intensity/shadow intensity with some positioning too.
The last editable parameter is the ambient, which is the overall look and whether you want more or less brightness overall. You can manually edit all these numbers with the exact numbers that go in the .lte file. Or you can drag sliders around, numbers update in real time. It has two visual guides, one is the actual heightmap and you get a rough idea of how lighting changes the map look and a cube to give you an idea of which sides get shaded and which direction the shadows are pointed at.
Of course, this sun position is also directly responsible for how weak or strong the normals look. This is a pretty big change for how RuDeE gets to play with normals.
One thing to note: I added the option of "Keep Strength" when you slide the sun around. So if you want to keep a specific level of brightness/darkness when you look for the ideal sun placement, if you enable Keep Strength it will automatically move the sun around on the Y axis.
- the second feature is in track components where traxx is now aware of the water normal/mask. It behaves identical to the terrain normal/mask.
- the Special>Lighting window got a complete redesign. Since the discovery that the game already allows the sun to be placed at any angle, this has now been translated into traxx. It turns out the sun is controlled by the X,Y,Z positions and they do the following:
X, Z work as the placement in the sky and thus the direction the sun hits you from (and casts the fancy shadows). They do contribute to the sun intensity.
Y, in addition to the position (whether it is higher or lower in the sky and thus directly contributes to the length of the shadow) it also contributes to the intensity of the shadows. It turns out that the crappy shadow map that everyone hates (that takes a bit to cache on the first run) is actually much more detailed than I realized. And the reason it was never dark enough was not because the shadow map was wrong but because it was never fed the correct information (Kmaster always complained the terrain is not dark enough for him). Well, now we can finally fix this. The Y position is also directly responsible for how strong the sun is aka how bright the track gets. X,Z are positioning, shadow direction and a bit of strength, Y controls shadow length and light intensity/shadow intensity with some positioning too.
The last editable parameter is the ambient, which is the overall look and whether you want more or less brightness overall. You can manually edit all these numbers with the exact numbers that go in the .lte file. Or you can drag sliders around, numbers update in real time. It has two visual guides, one is the actual heightmap and you get a rough idea of how lighting changes the map look and a cube to give you an idea of which sides get shaded and which direction the shadows are pointed at.
Of course, this sun position is also directly responsible for how weak or strong the normals look. This is a pretty big change for how RuDeE gets to play with normals.
One thing to note: I added the option of "Keep Strength" when you slide the sun around. So if you want to keep a specific level of brightness/darkness when you look for the ideal sun placement, if you enable Keep Strength it will automatically move the sun around on the Y axis.
- the second feature is in track components where traxx is now aware of the water normal/mask. It behaves identical to the terrain normal/mask.
Re: Traxx 1.7.3 and the new features
https://mtm2.com/%7Etraxx/downloads/traxx_173.zip <--- updated 11/14/26
Another round of improvements.
- Added FOV that users can chose from. I realized that since we went openGL with higher resolutions, traxx was running with extreme fish eye which distorted world and placing objects
- the performance improvements from previous round made smaller objects disappear. They were still there but traxx couldn't render them. This has now been fixed
- piggybacking on the previous fix, Traxx should now accurately display the model's outlines with the model.
- added more control for the waterfalls
- tweaked how the lakes work. Basically, if you get a warning that the lake can't go past a certain height, check the boundaries. What you need to check is the blue line that the additional square that is outside of the drawn water. Not just the visual water itself. The reason for this is because the game renders water in full tiles, the edge of the lake will always have a tile or two that is partially over the water.
- tweaked how lakes and waterfalls interact. Basically the waterfall is the one that allows the lake the break the rule of "can't go at terrain height". It was supposed to work the same in the previous version but traxx had some extra safeguards that made connecting harder than it should have been.
Another round of improvements.
- Added FOV that users can chose from. I realized that since we went openGL with higher resolutions, traxx was running with extreme fish eye which distorted world and placing objects
- the performance improvements from previous round made smaller objects disappear. They were still there but traxx couldn't render them. This has now been fixed
- piggybacking on the previous fix, Traxx should now accurately display the model's outlines with the model.
- added more control for the waterfalls
- tweaked how the lakes work. Basically, if you get a warning that the lake can't go past a certain height, check the boundaries. What you need to check is the blue line that the additional square that is outside of the drawn water. Not just the visual water itself. The reason for this is because the game renders water in full tiles, the edge of the lake will always have a tile or two that is partially over the water.
- tweaked how lakes and waterfalls interact. Basically the waterfall is the one that allows the lake the break the rule of "can't go at terrain height". It was supposed to work the same in the previous version but traxx had some extra safeguards that made connecting harder than it should have been.
Re: Traxx 1.7.3 and the new features
Not sure what I'm messing up with the grass, but nothing's showing up either in Traxx or in game when I plant a bunch of it despite Traxx saying it planted over 100k grass objects. Trees work fine.
Pod with planted grass: https://drive.google.com/file/d/1wvodpl ... sp=sharing
Pod with planted grass: https://drive.google.com/file/d/1wvodpl ... sp=sharing
Re: Traxx 1.7.3 and the new features
RuDeE - i did a silent update for both MTM and traxx, so redownload them both.
In short... you are pushing the limits again and traxx did not know how to deal with it (since the engine follows what traxx told it to follow). There was a limit of 130k grass objects but because you spread the mask over the whole map with a high enough density, Traxx needed to put down 1mil objects of grass. It never had a failsafe what to do in this situation so it started laying them down as per your instructions and when it hit the limit, it stopped. So the grass was actually there at the edge of the map. If you wanna see yourself, open it before you apply the updates.
So with the update, both traxx and engine can now support up to 2mil grass objects but give you a heads up, 1mil clumps of grass on my system gave me about 10% fps hit... although that means i went from 580fps to 480fps which for me doesn't mean much, lol.
I did a few more changes too
Traxx:
- it gives a warning when placing over 500k. It's not a blocker, just a warning that hey maybe you wanna reconsider this.
- if you go over the limit again (this time 2 mil), traxx will work on spreading them out evenly instead of just stopping, despite what your density setting is.
- moved the vegetation mask and detail mask toggles to be in the same areas instead of having detail mask in options>advanced. Now they can be toggled either from the panel on the right or View menu
- added a toggle for water mask too, just like the one for terrain in case as a visual guide.
MTM2: since these are so specifically targeted at you, i'll just post them here, lol
- supports the new 2mil grass
- added strength sliders for the default always on terrain and water normals
- reworked the terrain details strength so that hopefully it matches more to what you were hoping for. This is actually a "cheat" and doesn't follow "real" (so to say) logic. So the whole game reacts based on where the sun position is but now the terrain details get their own "cheat" position of the sun (aka it takes wherever the sun is right now and lowers it) so that it bumps up the details. Nothing else is affected by this... or in theory nothing should be affected by this other than the terrain normal detail.
- top down sun (such as some of mal's tracks) do not get this cheat sun because the sun being on top, it doesn't know where to cheat place it. Plus realistically speaking, when the sun is top down you don't get any details anyway in real life either (film makers and photographers HATE filming with a top down sun).
In short... you are pushing the limits again and traxx did not know how to deal with it (since the engine follows what traxx told it to follow). There was a limit of 130k grass objects but because you spread the mask over the whole map with a high enough density, Traxx needed to put down 1mil objects of grass. It never had a failsafe what to do in this situation so it started laying them down as per your instructions and when it hit the limit, it stopped. So the grass was actually there at the edge of the map. If you wanna see yourself, open it before you apply the updates.
So with the update, both traxx and engine can now support up to 2mil grass objects but give you a heads up, 1mil clumps of grass on my system gave me about 10% fps hit... although that means i went from 580fps to 480fps which for me doesn't mean much, lol.
I did a few more changes too
Traxx:
- it gives a warning when placing over 500k. It's not a blocker, just a warning that hey maybe you wanna reconsider this.
- if you go over the limit again (this time 2 mil), traxx will work on spreading them out evenly instead of just stopping, despite what your density setting is.
- moved the vegetation mask and detail mask toggles to be in the same areas instead of having detail mask in options>advanced. Now they can be toggled either from the panel on the right or View menu
- added a toggle for water mask too, just like the one for terrain in case as a visual guide.
MTM2: since these are so specifically targeted at you, i'll just post them here, lol
- supports the new 2mil grass
- added strength sliders for the default always on terrain and water normals
- reworked the terrain details strength so that hopefully it matches more to what you were hoping for. This is actually a "cheat" and doesn't follow "real" (so to say) logic. So the whole game reacts based on where the sun position is but now the terrain details get their own "cheat" position of the sun (aka it takes wherever the sun is right now and lowers it) so that it bumps up the details. Nothing else is affected by this... or in theory nothing should be affected by this other than the terrain normal detail.
- top down sun (such as some of mal's tracks) do not get this cheat sun because the sun being on top, it doesn't know where to cheat place it. Plus realistically speaking, when the sun is top down you don't get any details anyway in real life either (film makers and photographers HATE filming with a top down sun).
Re: Traxx 1.7.3 and the new features
Side note: The waterfall work has lead me to discover a new work pipeline for the coding. I am now implementing this new work pipeline between traxx and the engine which will result in traxx being able to show things closer to how the engine does. The side effect of this is that it's very scary because at this point the AI is talking to the other AI and are side stepping me me. lol
Re: Traxx 1.7.3 and the new features
Beautiful stuff! Thanks, Fila.
Since I didn't know how it worked, I went with the full green mask, but now I understand it's more like Wreckfest and something like this is better: PS: In WF1, only RGB channel info is taken into account and only 3 types of clutter are allowed (one per channel). There's much more flexibility in your color approach, which is nice, but I can't imagine anyone using more than two or three colors. Look forward to seeing someone prove me wrong!
Got everything working: normal mask, lake, waterfall, surfaces, trees, and ground clutter. Really cool stuff! I'm wondering, can vegetation trees be made non-collide for AI, similar to how collide-able purple boxes work currently? Even with a 40ft radius for trees away from the AI routes, I'm getting some trees placed in the path --- I think in between the red main paths in Traxx. In this particular track, I think it's fine for players, but I keep passing AI stuck on trees. Several solutions come to mind.: taking the blue connecting paths into account on tree planting, AI don't collide with trees (suggested above), and / or adding a tree section to the top bar where you can select and move trees in the veg file (this is how it's done in Evo 2).
Another question: does the face / material type of a grass type clutter matter? I tried 0x33 and 0x40 foliage and didn't notice a difference. Ended up having to darken the clutter textures to better match the track and stuck with 0x40 foliage face / material type.
My grass / ground cover models are unreasonably complex (3d models with 30-50 faces each), but I didn't see any difference in performance with 500k vs 1mil. So, that's pretty impressive to me! I think things are running really well. They could probably all be replaced by cards with no visual difference, but it's cool nonetheless.
Since I didn't know how it worked, I went with the full green mask, but now I understand it's more like Wreckfest and something like this is better: PS: In WF1, only RGB channel info is taken into account and only 3 types of clutter are allowed (one per channel). There's much more flexibility in your color approach, which is nice, but I can't imagine anyone using more than two or three colors. Look forward to seeing someone prove me wrong!
Got everything working: normal mask, lake, waterfall, surfaces, trees, and ground clutter. Really cool stuff! I'm wondering, can vegetation trees be made non-collide for AI, similar to how collide-able purple boxes work currently? Even with a 40ft radius for trees away from the AI routes, I'm getting some trees placed in the path --- I think in between the red main paths in Traxx. In this particular track, I think it's fine for players, but I keep passing AI stuck on trees. Several solutions come to mind.: taking the blue connecting paths into account on tree planting, AI don't collide with trees (suggested above), and / or adding a tree section to the top bar where you can select and move trees in the veg file (this is how it's done in Evo 2).
Another question: does the face / material type of a grass type clutter matter? I tried 0x33 and 0x40 foliage and didn't notice a difference. Ended up having to darken the clutter textures to better match the track and stuck with 0x40 foliage face / material type.
My grass / ground cover models are unreasonably complex (3d models with 30-50 faces each), but I didn't see any difference in performance with 500k vs 1mil. So, that's pretty impressive to me! I think things are running really well. They could probably all be replaced by cards with no visual difference, but it's cool nonetheless.
You do not have the required permissions to view the files attached to this post.
Re: Traxx 1.7.3 and the new features
For the grass it doesn't matter. That's the tradeoff to allowing to have so many and the difference between vegetation and shrubs. Vegetation gets the full shadow/render treatement. The grass gets non-collide, no casting shadows, no materials, no different faces etc.
I doubt anyone is going to make use of having multiple options... unless ZooN or Oops come out of retirement
For the AI... the new AI will be aware of the trees, so we'll wait on that first
That definitely does not look like the MTM2 that we know. lol
I doubt anyone is going to make use of having multiple options... unless ZooN or Oops come out of retirement
For the AI... the new AI will be aware of the trees, so we'll wait on that first
That definitely does not look like the MTM2 that we know. lol
Re: Traxx 1.7.3 and the new features
I wish, no better time to return to content making with what we're doing now.
Re: Traxx 1.7.3 and the new features
cmon guys, let me finish my 4x maps & conversion tracks
this one took a while... let's just pray to the higher powers (My small voodoo dolls of Phin and Mal ) so you BOTH dont get more creative lol
jokes aside, keep up the good work.
jokes aside, keep up the good work.
You do not have the required permissions to view the files attached to this post.
Re: Traxx 1.7.3 and the new features
Oh crud. I realized I've had my game set up as 220 normal strength this whole time whereas the shipped default is 120. I'm bumping it up to 220 for next hotfix, let me know if it changes stuff or you wanna move it back to 120.
And KMaster, next round of hotfix is really a bunch of mtm2 under the hood fixes.
And KMaster, next round of hotfix is really a bunch of mtm2 under the hood fixes.
Re: Traxx 1.7.3 and the new features
a .md of the CP4 changes until now would be nice, no code of course.Fila wrote: Mon Nov 16, 2026 1:40 am Oh crud. I realized I've had my game set up as 220 normal strength this whole time whereas the shipped default is 120. I'm bumping it up to 220 for next hotfix, let me know if it changes stuff or you wanna move it back to 120.
And KMaster, next round of hotfix is really a bunch of mtm2 under the hood fixes.