Quote from: pete9516 on May 22, 2024, 11:33 AMIt works, but with some issues still. Basically, there are some things to consider:
So you mean like when a nfs2 track is broken to open with T3ED, it is fixable using different COL and speed files?
1) VR data should be shorter than non-openable track (i.e. if track have, say, 200 blocks, it's better to replace VR data with something that is supposed to be lesser, like 64 blocks for example).
2) Some adjustments do not work, like automated adjustments for VR data, if, say, you want to adapt it for the track that was previously not opening, as T3ED will crash while attempting to do so,
3) Export/Import VR data doesn't seem to help with opening original troubled track (for example, I tried to rebuild VR data for Mediterraneo and replace the one that was provided as is, still it doesn't open).
So I think it's safe to say that with this workaround you can edit visual part, but not the VR part.
And then, I wonder if it is somehow possible to generate VR data based on polygons data (like passable-non-passable flags?) instead of loading the one that breaks the loading process.