Wake up
While TrackEd3 and TrackEd4 are nearly identical (I just saw TrackEd4 in operation for the first time the other day) the SIT files for Evo1 and Evo2 are written differently, which means the converter will only work with Evo1 SIT files created by TrackEd3. Scroll to the bottom of <a href=http://winterkill0.tripod.com/evo2to1.htm>this</a> page to see side by side SIT file "box" data comparisons from mtm, mtm2, evo1 and evo2.
I was especially chatty for a reason earlier, it gave me material for a readme as well as provide a basis for doing a TrackEd3 writeup. ;-)
But as it turns out, I was way off when writing of the scenery levels and the models in the beta. I was under the impression that every one of my models were set to "sparse" (seen in sparse, normal and complex modes), but a great many were set to normal, and since I hadn't switched out of complex mode I never noticed. So let it be known that complex was truly the setting to use for the beta (for performance testing), where everything was visible. As it stands the scenery level of the models was not set with any deliberate goal, and things turned out quite mismatched at lower settings.
But no matter, I've just cycled through the 400+ models and set them all to how they should be. Most buildings are invisible in sparse, as are all people, some trees, a lot of fences and some bits of wood. The beta linked above is obsolete, the next beta will be the final beta, and it will be out as soon as possible - I'm working steady on it right now.
But as it turns out, I was way off when writing of the scenery levels and the models in the beta. I was under the impression that every one of my models were set to "sparse" (seen in sparse, normal and complex modes), but a great many were set to normal, and since I hadn't switched out of complex mode I never noticed. So let it be known that complex was truly the setting to use for the beta (for performance testing), where everything was visible. As it stands the scenery level of the models was not set with any deliberate goal, and things turned out quite mismatched at lower settings.
But no matter, I've just cycled through the 400+ models and set them all to how they should be. Most buildings are invisible in sparse, as are all people, some trees, a lot of fences and some bits of wood. The beta linked above is obsolete, the next beta will be the final beta, and it will be out as soon as possible - I'm working steady on it right now.
- ZOtm_BigDOGGe
- Member
- Posts: 881
- Joined: Wed Nov 06, 2002 2:01 pm
- Location: Silicon Valley, California. USA
- Contact:
Looking forward to it. I saw the snapshots, and stopped dead in my tracks! That looks like it's going to be a new classic.....nice job bro.
I didn't get the previous version, but I'm patient enough to wait for the final beta.
------------------
- BigDOGGe's Boneyard ...The Best Custom Trucks in MTM2 -
I didn't get the previous version, but I'm patient enough to wait for the final beta.
------------------
- BigDOGGe's Boneyard ...The Best Custom Trucks in MTM2 -
Thanks BigDOGGe. By the way, what does the "tm" mean... team mascot? *<a href=http://www.hotink.com/wacky/mfiles/>laughs like Muttley</a>*
>> Can you also do fine tuning of the terrain in Tracked 3?
Practically: no. In fact: yes, but TrackEd3 turns the terrain into a 16-bit RAW, and in turning that back into an 8-bit image for MTM2 it will basically get messed up and need fixing in Traxx. Point for point, there is no better terrain tweaker for mtm terrains than Traxx.
>> Can you also do fine tuning of the terrain in Tracked 3?
Practically: no. In fact: yes, but TrackEd3 turns the terrain into a 16-bit RAW, and in turning that back into an 8-bit image for MTM2 it will basically get messed up and need fixing in Traxx. Point for point, there is no better terrain tweaker for mtm terrains than Traxx.
Darn it. The one thing i don't like about Traxx is the fact that it's not 3d accelerated and fine tuning the terrain can be a pain in the rear.... and i got so much to do in my new track (the horror!).Practically: no
------------------
"In my restless dreams, I see that town, Silent Hill..." - Mary, Silent Hill 2
- ZOtm_BigDOGGe
- Member
- Posts: 881
- Joined: Wed Nov 06, 2002 2:01 pm
- Location: Silicon Valley, California. USA
- Contact:
Muttley!!!!!! You quivering, sniveling hound!*laughs like Muttley*
<IMG SRC="http://mtm2.com/~bigdogge/temp_pics/dick&muttly.gif" border=0>
-----------------
"tm"? well, that's been debated:
team mechanic
team modeler
temporary maniac
total moron
tweaked mascot
But really, it just means "truck maker", bestowed by my team for all the trucks I made with the team name and/or logo on them, plus the official ZO team trucks..
------------------
- BigDOGGe's Boneyard ...The Best Custom Trucks in MTM2 -
<font size=1>Edited by ZOtm_BigDOGGe (09-02-2003)</font>
So like...when is this track going to be released again? LOL Come on WK!!! We got a spot for this baby reserved on the " Jump-Cope list already. Been sittin there for a while...waiting...waiting...waiting lol. You're making us look bad, bud - help us out and finish that track! 

While TrackEd3 and TrackEd4 are nearly identical (I just saw TrackEd4 in operation for the first time the other day) the SIT files for Evo1 and Evo2 are written differently, which means the converter will only work with Evo1 SIT files created by TrackEd3. Scroll to the bottom of this page to see side by side SIT file "box" data comparisons from mtm, mtm2, evo1 and evo2.
Dunno if this is still relevant but - I have found that you can use Tracked4 to edit MTM2 SIT files.
I had a problem with having MTM2, Evo1 and Evo2 running on the same 'pute - there seemed to be some conflict. The only reason I re-installed Evo1 was to try WK's model placing theory with the intention of using Phin's "box replacer" utility.
Since uninstalling Evo1 I have successfully imported an MTM2 sit into Tracked4 and have been able to work with it.
The way to go is use Podview to extract all files from your MTM2 track (POD) into your Evo2 folder (checkbox "keep original paths") then Tracked4 will recognise, read and load.
Even BINS are acceptable - dunno about groundboxes, probably not.
