Draconisaurus wrote:machf wrote:remember, TresEd doesn't save proper WTD files.
Even when they are modified/resaved retail WTDs?...
I'm not quite sure since we don't have TresEd's source code... but it definitely doesn't save .WTD files in the (100%) proper format. Remember, back then, we were all guessing how it was done, basically attempting to reverse engineer the formats, and one or two things may have been wrong. But they were enough to generate the sort of errors we know.
tatu wrote:So this method is only good for retail WTD's then I guess, not fan made ones. Or unedit GUIApp WTD generated ones.
Maybe at the time I wrote the first post on this topic I should have been more careful... but it was quite a long time after I first wrote those scripts, and I didn't remember too well what it was like with GUIapp. It's better to use a terrain TRI file instead of a TPM one to import Trespasser terrains into MAX whenever possible, but when you have a user-edited terrain, you may have no other option that to use a TPM one in the first place, and later re-import the terrain into MAX using a TRI file after having fixed it with GUIapp. And maybe it's better to make any further edits to the terrain mesh in MAX to prevent having to repeat the process again.