Notice to all visitors and members of the Train-Sim.Com message forums: If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.
Please note that RR will not make a good compact version of tsection.dat v0023 due to a change in the format of said file.RR was able to compact previous versions of the tsection.dat file so that they only contained references to files actually in your Global\Shapes folder.I have modified the program to deal with the problem I found and should post it within a few days.Mike
Mike,one of the problems in my 20+ years in Computing and Programming has been a certain lack in Communications between parties working on the same project ! Why did David Beach not inform you of changes he made in the format of the Tsection.dat ! Good question, isn't it ?O t t o
HI David,Not your fault, problem appears to be that in the earlier tsection.dat files where there was an _Info line within a TrackSection entry, it was preceded by a TAB character, but in some of the entries used in v0023 (those with the info line in German language), the _INFO is preceded by spaces.Due to my sloppy code, RR jumped from the _INFO to the next TrackSection entry and thus the tsection.dat so produced was invalid.I have posted a new version of RR on my site which works OK.This was not your fault (I suspect you cut/pasted these entries in any case), I should have made allowances for spaces at the beginning of a line being either tabs or spaces.You can not win them all.....Mike
David,Apologies for suggesting that there was a lack of communications between you two, at least not from your side ! But it is a problem sometimes. I get a lot of it, my Hardware partner not telling me that he is using equipment with different drivers for instance, making unexpected demands on lower Ram, affecting my programs ! Having your attention and learning a few more things about the Tsection.DAT, helping Jürgen Romanowski with his Y-Tracks, what is the connection between the TrackSection and the TrackShape entries ?How do the TrackSection entries know which TrackShape they refer to, if that is what they need to do or vice versa ?Thanks, O t t o.
Hi David,I must admit that there is a syntax error in my part of tsection.dat Thanks to Carlos bringing that to my attention. The function of the Sim i s n o t affected, but some tools ( tstools, routewriter ) will complain.Here is one of the questionable entries ( 31312, 315, 318, 320 are affected. They are all x-over shapes )TrackShape ( 31312 FileName ( Y1tXover1-9.s ) NumPaths ( 2 ) SectionIdx ( 2 0 0 0 0 32650 32650 ) SectionIdx ( 2 1.16202019 0 0.06435670 -6.34 32650 32650 ) CrossoverShape ( ) XoverPts ( 1 ) <------- here it is, that bracket is wrong XoverPt ( 0 0 10.52285734 ) ) And here is how it must be:TrackShape ( 31312 FileName ( Y1tXover1-9.s ) NumPaths ( 2 ) SectionIdx ( 2 0 0 0 0 32650 32650 ) SectionIdx ( 2 1.16202019 0 0.06435670 -6.34 32650 32650 ) CrossoverShape ( ) XoverPts ( 1 XoverPt ( 0 0 10.52285734 ) ) <--- bracket needs to enclose the whole xover definition ) Sorry for any inconvinience I apologize. But it is a hidden error, TS does not complain, only certain tools. In future i will take more care and crosscheck against tstools and route-writer.Regards Jürgen Romanowski aka Roman
Roman, there seems to be a line missing in your examples from the Tsection.dat 0023 which came with Xtracks-3.10 and the values in them are different to those in the copy you E-Mailed me last, shown below: TrackShape ( 31312 FileName ( Y1tXover1-9.s ) NumPaths ( 2 ) ClearanceDist ( 31.5 ) <<<<<<<<<<<<<< SectionIdx ( 1 0 0 0 0 32650 ) <<<<<<<<<<<<< SectionIdx ( 1 1.16209051 0 0.06436255 -6.340192 32650 ) <<<<<<<<<<<<<< CrossoverShape ( ) XoverPts ( 1 XoverPt ( 0 0 10.52317667 ) <<<<<<<<<<<<<< ) )Which is the correct version ?O t t o
If only kuju or MS had bothered with an SDK, or at least some thorough documentation, we'd all be better off.Spaces and tabs are used semi-interchangeably within the tsection.dat file. When parsing the file it would be advisable to convert all tabs to spaces, and all multiple spaces to single spaces. Then when writing out (would that be riting out?) the new version expand them back out based on some consistent pattern. The program is just as happy with the tsection.dat entries if the returns within a given TrackSection or TrackShape entry are replaced with spaces (up to some maximum line length?). The formatting is really just for us poor humans, the computer doesn't care.Yes, its all cut and paste with some modifications.David Beach.Palouse & Lewiston
Standardized \global\tsection.dat file now at build00023.
