This is the "Default Dynatrack profile" I managed to create from reading the source code.
Pull the .stf file out of the archive and put it file in a new folder named TrackProfiles under your route folder.
Like in the picture below:
The .stf file will be parsed without errors by the RunActivity.exe. It passes by with a TRP(.stf) entry in the log.
Feel free to experiment, putting different shapes, sizes and positions in the values. Have the source code at hand to get an idea of what goes where.
This .stf uses the default A1CleanTrack textures and is only valid for 1435mm standard gauge.
There is only one LOD, but the "canned response" in the source code also has a 1200 meters LOD and a dynamically rendered value LOD.
I think that for ScaleRail to work one needs 2 more LODItems but since I don't know how to disassemble .ace files, I don't know what they are called and how the textures are oriented. Also the LOD's are different.
DB Tracks is more complicated still, with yet other LOD's and still more LODItems.
I also think there is only one profile at a time per route possible, so one is currently unable to differentiate between mainline and spurs for superelevation.
Perhaps in a future release more definitions could be possible and an extra variable added to the TrackObj definitions in the .w files will choose the appropriate definition, or the textures needed could be read dynamically from the track piece the train currently travels over.