tilted train if the consist file name has "tilted"

[Komachi]

This feature doesn't seem to work. My consist is as follows
SIMISA@@@@@@@@@@JINX0D0t______

Train (
TrainCfg ( "M-ETR450 Tilted"
Name ( "Tilted" )


Yet it doesn't do it. Only if I change the filename/trainCFG to just 'Tilted' too. Think this ain't workin right, thoughts?

[rrroberttt]

After you go to the experimental tab, and, change the ( 0 ) to an 1 or greater up to an max of 10, then go into the consists folder in the trains folder, and change the consist name for whatever consist you want as follows. Example: "Acela.con" original name, to "Acela-tilted.con". Be warned, however, as Superelevation now stands, for what I have gathered, if an route use an mixture of track, like (x-traks, and some other like, MSTS original tracks), then, whenever the track pieces connect with one another, that area of track will disappear, leaving the train running on the textures only. When an route is using like one track source, (MSTS tracks), that route will run, with Superelevation perfectly. I have filed an bug report with ORTS about this.

[Komachi]

This tilting feature is very selective whether it wants to work or not, something the OR Team should look at. the following works: Train (
TrainCfg ( M-ETR450-Tilted
Name ( "ETR 450Tilted" )

This doesn't: Train (
TrainCfg ( Fs-Etr500-Tilted
Name ( ETR500-Tilted )

[jjtang]

It should be "tilted", not "Tilted".

[jjtang]

Be warned, however, as Superelevation now stands, for what I have gathered, if an route use an mixture of track, like (x-traks, and some other like, MSTS original tracks), then, whenever the track pieces connect with one another, that area of track will disappear, leaving the train running on the textures only. When an route is using like one track source, (MSTS tracks), that route will run, with Superelevation perfectly.

Not sure about this though. Which route has the problem? Could you please try the newest code?

[neyland]

I have experienced the same thing with UKFS track and x-tracks, bug reports were submitted a few days ago.

[jjtang]

Please give me a route (and where I can get it) so I can take a look.

[Komachi]

3DTrains Feather River, and one where it disappears completely is the PRR Eastern.




Also I tried 'tilted' instead of 'Tilted' and it's STILL not working...

[eric]

Are your quote marks the issue?

The one which works has the name in quotes. The one that doesn't work doesn't have the name in quotes...

I ran into the reverse of that once with my own app, which hadn't counted on quoted names.

[rrroberttt]

I can confirm that with the latest experimental version, 1498, it is now working. I used the PRR Eastern, which had major problems with this uprgade, the PRR, using many different track types, is now working as expected. Thanks to JJtang, and team ORTS. I will amend my bug report on this issue over at the bug report forum.

[csantucci]

I had no problems in renaming consists to have them tilting. For the M-ETR450 I did so:
Filename: M-ETR450-tilted.con
Within the file
TrainCfg ( M-ETR450-tilted

For the FS-ETR460 I did so:
Filename: Fs_Etr460_Pendolino_It-tilted.con
Within the file
TrainCfg ( "Fs_Etr460_Pendolino_It-tilted"

while the ETR500 is not a tilting train...

This is what happens now with superelevation on the Bernina route on release 1498

Bernina_superelevation1.jpg

[rrroberttt]

Well it is not working 100%. However, it is an whole lot better. With the PRR route, using an path from Philadelphia 30th Street station, heading towards NYC, I found an couple of spots, that had missing track pieces. Approaching Linden, NJ, on the right hand side, there was a small patch of tracks missing. Also an couple of spots before that. Overall, I would say that it is identifying and displaying about 90-95% of all the track pieces useds on that path. I will at some time later on today, try a couple of other paths.

[jjtang]

This is what happens now with superelevation on the Bernina route on release 1498

[ATTACH=CONFIG]57518[/ATTACH]

There is a choice of track gauge, make it 945mm. There is no way to recover the correct gauge at this time, so you have to specify it.

Track sections have a width value, but most put it as 1.5 for standard, or 0.9 for narrow gauge. Using these values will not give us correct drawing of the tracks.

[neyland]

Making Tracks Great Eastern is the worse, the UKFS track appearance is completely corrupted. SE sections are drawn as the original msts track sections would appear.

But any route using UKFS is affected in how the track looks on the SE curves.

Bug reports were made, accompanied by screenshot attachments.

EDIT: https://www.trainsim.com/vbts/showth...22#post1799922

[jjtang]

Making Tracks Great Eastern is the worse, the UKFS track appearance is completely corrupted. SE sections are drawn as the original msts track sections would appear.

But any route using UKFS is affected in how the track looks on the SE curves.

Bug reports were made, accompanied by screenshot attachments.

EDIT: https://www.trainsim.com/vbts/showth...22#post1799922

I am not familiar with these track systems, please tell me a free route I can download, so that I can try to figure out the problems.

It uses a default track profile, thus resembles the MSTS standard tracks. If you can supply a TrProfile in the route folder, it will use that to generate the tracks.