[Hamza97]

Hii everybody.....
I am currently making some broad gauge (1676mm) track for use on Indian Routes. With the help of @inflammable I successfully learnt about the entries in tsection.dat file. I made some track section, exported them, made entries in tsection.dat everything was okay till that and I had three entries in tsection.dat file.

Next I decided to try some double track section and so exported it, made entry in tsection.dat and opened up RE but the track section didn't show up on list I fiddled up with tsection.dat file wondering what I had done wrong, but couldn't find anything wrong in it. Then I decided to move the entry up the third place and replaced the entry that was on third pplace to fourth place, fired up the RE and EUREKA......!!!! The track section was showing up, but the entry which was moved to fourth place now didn't showed up in RE.

I am just wondering that is there some rule that only three track sections could be there :wall_bash:

If someone can help me with problem, I do be gratefull.... :p :)

[Genma Saotome]

Look at other 2track shapes and study how they're done.

It is very, very easy to screw up something while editing the tsection.dat file so be careful and test everything you do.

[Hamza97]

I have checked ALL the params 3-4 times, also testsd the track shape by adding it as scenery object and it appeared so .s file being screwed is also not the case. I actually copied the default 10m shape file entry of tsection and modified it. Still trying to figure out..... :p

[captain_bazza]

Welcome to the train sim "What the.......!? Club.

Cheers Bazza.

[inflammable]

Post your tsection, and let others help you look.

If you're making a completely new tsection, then ensure that you've accounted for the total number of entries.

James

[Hamza97]

SIMISA@@@@@@@@@@JINX0F0t______

Tracksections ( 4

TrackSection ( 0
SectionSize ( 1.676 8 )
)

TrackSection ( 1
SectionSize ( 1.676 48 )
)

TrackSection ( 2
SectionSize ( 1.676 0 )
SectionCurve ( 250 -30 )
)
TrackSection ( 3
SectionSize ( 1.676 0 )
SectionCurve ( 250 30 )
)

Trackshapes ( 4

TrackShape ( 0
FileName ( a1t8m.s )
NumPaths ( 1 )
SectionIdx ( 1 0 0.0 -4.002 0 0 )
)

TrackShape ( 1
FileName ( A1t48m.s )
NumPaths ( 1 )
SectionIdx ( 1 0.0 0.0 0.002 0 1 )
)

TrackShape ( 2
FileName ( A1250r15d.s )
NumPaths ( 1 )
SectionIdx ( 1 0.0 0.0 0.002 0 2 )
)

TrackShape ( 3
FileName ( A2t48m.s )
NumPaths ( 2 )
SectionIdx ( 1 0.0 0.0 0.0 0 1 )
SectionIdx ( 1 5.3 0.0 0.0 0 1 )
)

Hiii everybody...
Here's the tsection file..... If somebody can find an error in it

[DRelyea]

Hi,

The multiple path trackshapes appear to need to be centered, at least from what I've seen in the other Tsections. For example:

TrackShape ( 8
FileName ( A2t250mStrt.s )
NumPaths ( 2 )
SectionIdx ( 1 -2.4925 0 0 0 3 )
SectionIdx ( 1 2.4925 0 0 0 3 )
)

odd number of tracks like such:

TrackShape ( 14
FileName ( A3t500mStrt.s )
NumPaths ( 3 )
SectionIdx ( 1 -4.985 0 0 0 4 )
SectionIdx ( 1 0 0 0 0 4 )
SectionIdx ( 1 4.985 0 0 0 4 )
)

If I remember correctly, the multiple trackshape Shape origin must also be centered on the end of the shape in the modelling program, so that it rotates correctly (at least, as much as it can rotate correctly)

make the first SectionIdx (1 -2.65 ...), and the second (1 2.65...) and it should work.

Doug Relyea

[StevenMasters]

SIMISA@@@@@@@@@@JINX0F0t______

Tracksections ( 40000
 TrackSection ( 0
  SectionSize ( 1.676 8 )
 )
 TrackSection ( 1
  SectionSize ( 1.676 48 )
 )
 TrackSection ( 2
  SectionSize ( 1.676 0 )
  SectionCurve ( 250 -30 )
 )
 TrackSection ( 3
  SectionSize ( 1.676 0 )
  SectionCurve ( 250 30 )
 )
)

Trackshapes ( 40000
 TrackShape ( 0
  FileName ( A1t008m.s )
  NumPaths ( 1 )
  SectionIdx ( 1 0 0 0 0 0 )
 )
 TrackShape ( 1
  FileName ( A1t048m.s )
  NumPaths ( 1 )
  SectionIdx ( 1 0 0 0 0 1 )
 )
 TrackShape ( 2
  FileName ( A1t0250r30d.s )
  NumPaths ( 1 )
  SectionIdx ( 1 0 0 0 0 2 )
 ) 
 TrackShape ( 3
  FileName ( A2t048m.s )
  NumPaths ( 2 )
  SectionIdx ( 1 0 0 0 0 1 )
  SectionIdx ( 1 5.3 0 0 0 1 )
 )
)

1) Use 40000 for the number of track sections/shapes. Any dynamic track that you use in your route starts at these numbers. The 40000 gives you lots of room for expansion.
2) You are missing the closing ')' for the track section/shape blocks.
3) Missing the 't' in the A1250r15d.s shape file name. Also it should be 30d according to the track section definition. You may want to 'zero' fill the file names as shown to better list them in the RE.
4) Offset values - Your asking for allot of pain in creating a new track set with different offsets for each section. Set the origin of the shape to match the origin of the track shape definition. To fix the s-file see the track making page here.

[Hamza97]

@DRelyea, StevenMasters

Nope..... :) :( None of the advises worked..... I going MAD at this.... Everything is okay, then to RE is not showing. If this gets worked out, I will claim for a rocket science degree.... :bigboss:


EDIT - Okay, this is overwhelming... in frustation I just added a 0 in front of last TrackShape. I.e. like this
FROM --- TrackShape( 3
TO ---- TrackShape( 30

And it WORKED..... !!!!!! The track piece is showing...

[Simon E]

Me is thinking there should be an Editor written for Tsection.dat , Especially when this world has quite many different track gauges... Narrow, Medium - Narrow, Standard and Broad (Like eg Indian, Irish, Iberian, And other odd sizes that I have left out, That are used in Europe , Inside mines, Or timber tramways)

I specifically need to create full-on complete Irish gauge (1,600 mm) Track for Melbourne Australia layouts, And Adelaide. They are the only places outside Ireland that uses an Irish gauge track... Argentina also uses Indian gauge track, I also think Chile And a few other Latino American countries do so too. So a lot of route builders from those places will be very happy with you for creating this track!.

This is also a good time to figure all this stuff out for OpenRails, A new clean easy to understand track system, with all the right gauges, track sections and track components, Dual gauges, 3rd and 4th rails for older Electric British and USA Subway lines) etc. Street Tramways, Rack Railways blah blah... will become easy.

They (Kuju) could have at least created 1,067 mm Cape guage for the 2 Japanese routes that came with MSTS out of the box... That is really bad work. I think Japanese routes done with standard track out of the route editor looks rubbish, Unless it is a Shinkansen route, The MSTS 1,500 mm they use is not even right for that!!! (what in the world were thinking??)

So I am glad that im not just one out of two people talking about track gauges and making new proper tracks for their country, in Train Sims.

So Conclusion is: We definitely need a Manual about how tracks and paths work in a simulator like MSTS/OR, and of course an editor for the Tsection.dat and other relevant parts of tracks, like the sms files and ttype files for the sounds of these tracks... http://www.elvastower.com/forums/public/style_emoticons/default/sign_thank_you.gif

Bring it on!!

[Lutz_s]

Why do you need an editor for the tsection.dat? This file has less than 30 different parameters. (I did not count them though)
What you are writing sounds more like you want an editor which lets you create the trackshapes. The tsection.dat only contains values which shapes should be displayed and how the path for the trains runs through the shape. There is a value for the track gauge, but it makes no difference to the sims if the gauge is 2ft, 1.4m or anything else. Maybe this will be added sometime, but the few parameters needed in the tsection.dat don't call for an editor.

If you have problems defining your track, copy an existing one and change the parameters one after another.

Cheers Lutz

[copperpen]

I think that the concept of a dedicated track section editor is good if one includes the ability to write the required entries to a form of tsection.dat file. This could lead to tsections dedicated to a single track gauge which could in turn lead to making life easier for builders and users alike. Right now however, we do not know what method of track laying will be used moving forward, sectional or procedural or even if a tsection style file will be required in the future.

[Simon E]

Lutz_s, on 22 June 2015 - 01:00 AM, said:

Why do you need an editor for the tsection.dat? This file has less than 30 different parameters. (I did not count them though)
What you are writing sounds more like you want an editor which lets you create the trackshapes. The tsection.dat only contains values which shapes should be displayed and how the path for the trains runs through the shape. There is a value for the track gauge, but it makes no difference to the sims if the gauge is 2ft, 1.4m or anything else. Maybe this will be added sometime, but the few parameters needed in the tsection.dat don't call for an editor.

If you have problems defining your track, copy an existing one and change the parameters one after another.

Cheers Lutz

Why an Editor?, Because as we have read in this thread, and from experience, it is a delicate and VERY important part of the sim and can really screw things up (Like every route you have installed as a consequence) if someone gets it wrong. Which does, and has happened in the past.

Its interesting that you mention "trackshapes" we do need new track components, Like check-rails, Closures, Certain types of diamonds, Slab Tracks (Bare naked Track on Concrete slabs, with special clips), different ballast mound heights, ballast shoulders and of course textures. Did you know that Overhead wire is also attached to them?? (I have just found out something new!)

The gauge is important, because if you lay track in a route using the wrong width, Your route can really get off by quite a bit pretty fast, by quite many meters. (Think about it, Add it all up... you will see that this effect is accumulative over the route, And it makes that dreaded Goode-Homosoline effect worse as well), It is also what makes paths mysteriously break, With unclosed track sections. (dreaded blue poles), With TDB's And RDB's that don't rebuild cleanly. And crashes in the Sim.

So an editor is a great thing to have. It helps to get all this stuff right. You will see a lot more nicer tracks and roads coming up for download. An Editor helps you to get everything right, All the right shapes, Curves and lengths needed.... And them submit them to train-sim.co.uk, (Or it may be submitted to the Open Rails team in the future, Who knows?) So there are many reasons to have an editor... Its not just a little fancy Text Editor that I am talking about, now that would be a real waste of programming time...

Simon. :sign_thanks:

[Simon E]

copperpen, on 22 June 2015 - 01:11 AM, said:

I think that the concept of a dedicated track section editor is good if one includes the ability to write the required entries to a form of tsection.dat file. This could lead to tsections dedicated to a single track gauge which could in turn lead to making life easier for builders and users alike. Right now however, we do not know what method of track laying will be used moving forward, sectional or procedural or even if a tsection style file will be required in the future.

Yeah, The track laying method may become more different when we really get going with the Route Editor (Which looks like it is already underway!) The Tsection may become XML Which I think is a good way to go, Or as you say It might be totally unnecessary in the future... Who knows until we figure it all out. But this editor, would be a good "in the mean-time" thing to do to make peoples lives more easier (And routes more prototypical)..

And it is all about getting the right entries in the file, and associate them with the right shapes and textures... (And to make it more clear what is Rail, and what is ballast, Or whatever else the Rails maybe laid upon (Ballast-less on a Slab in a metro or bridge, or on the middle of a Street with a tram going down it, And some of those European Streets with trams, as you very probably well know are not just plain old cement) acleantrack1.ace, acleantrack2.ace and whatever is just cryptic and confusing to some people.. And Editor would help a lot in putting all these elements together properly and correctly. And even attaching the correct sounds to them too.

So I am not just talking about a quickly programmed, and sexed up "little text editor" here

Simon :)

[Lutz_s]

If I understand it correct you want a tsection.dat which can define every type of track, though you have in it a definition for a 10m shape with lets say 10 different types of ballast, and each of them with and without overhead wire. You can do it this way, but if you want to edit a current route, you run into the same problem you have, when you edit an old route with standard tracks and now use xtracks. Your tsection.dat for dynamic tracks will blow away, since the total amount of shapes will easily rise above of 40000, which is the maximum defined with xtracks today. So this must be redefined someway.

I can have a look if an editor can be programmed if you define what you want it to do.

Lutz