Sorry for the delay guys but I needed some time to answer all your questions/suggestions
First thanks for all the kind words once again
@Maverick: "low-poly" bin file is a known limitation because .gp4 file have high-poly track mesh but .dat file does not seem to mention how to subdivide and which sectors to subdivide.
That's why I provided .bin export from .dat or .gp4 (even if none works perfectly today).
@Shuttle:
- .dat track sector main properties (Position, Direction, pitch, track width) could be generated back to .dat eventualy in future, it's not that hard to do (maybe some troubles with other commands like banks...) but it's not really on my priority list for now.
- ZM import filter has been built around car .gp4 format which is a slight cut-down version of the track .gp4 format. So ZM is waiting to find 0 values for flag/unk values as they are for any car object and when it finds non-zero values like with track objects, it fails to load the object.
- Yes, these object properties are quite important for their in-game visibility even if their real effect is not well known so you should restore original values when reimporting this object from ZM.
When importing back an object and furthermore if you displaced or/and rotate this object, do not forget to hit the object window "update coords" button. These properties are really important for in-game visibility.
@Maverick and Shuttle:
Reimported back 3d file to .dat could easily update:
-Position command
-Direction command
-left and right width (both equal anyway)
-verges and banks shape when they could be exported to .3ds too first
-ccpitch and ccdir as they are dependant to known sector position/direction
-wall height which is always 1m
-other commands like kerbs settings and other could be let as is
All of this needs only to respect one condition : to not add or remove any sector in ZM else how will 3deditor knows which are new sectors and what old commands belong to what old sectors...
- Yep, trackxx (with xx replace by a serial number) objects from .gp4 files are not displayed in game by default because .bin file is used for track tarmac ingame display.
To make any of these objects visible, simply add a CLASS markup before it as TRACK_ or NLAND_ (ie: TRACK_Track12 instead of Track12).
@Erwin: Hmm, surely
@Duffer and Maverick: check my last answer to Shuttle : using the update coords button is often sorting such trouble.