BINGO!
You are right! Tracks now works fine!
Thanks ZaZ, waiting for official fix now :P
BTW, how's growing up CSM 2.0? =)
ZaZ Wrote:
-------------------------------------------------------
> I think your .tmd file got corrupted due to a bug
> in the TSM gui.
> If you once imported a track into your tmd file of
> your track and it has too many bumptable entries
> for the track you want to play, then it will never
> delete the excess entries.
>
> So imagine this scenario where the .dat file you
> are using supports up to 14 bumptable entries:
> You start creating a tmd file by loading some
> magic data file for your track
> It will import the 14 bumptable entries and track
> track works. You can tweak the values in TSM and
> it will keep working.
> Then you will try another md3 file or a default
> track from the exe as base, but the amount of
> entries is not supported by this track.
> TSM writes down, let's say, 21 entries (could be
> anything of course)
> When you play GP4 will crash.
> You decide to import the 'old' magic data but it
> still crashes, so you think your track got
> corrupted.
> In fact, your track is still fine, but the tmd
> file got corrupted, because it did import the good
> 14 values, but also left the remaining 7 in the
> file.
>
> So, can you check your tmd file to see if it has
> more than 14 bumptables? You can open the file in
> notepad.
> In your case you could simply delete the excess
> entries from the tmd file and save the file again,
> or you could simply delete the whole tmd and
> import it again from a md3 file.
> If that solves your issue then I will create a
> update which fixes this problem.
Samuele
32BOBO32