[wushin]

I have noticed on several routes, 3DTrains WP 3rd. division and TPII with Scalerail there is quite a difference in how the rails and ballast appear at the junctions of one type to another. I have attached a screenshot that will help to display what I am referring to. Hopefully this is an easily remedied problem and will push Open Rails even closer to perfection. I am really enjoying the stability of the Open Rails platform and eagerly await each weeks update.

Donald
Other sizes available here if needed
http://www.flickr.co...in/photostream/

Attached thumbnail(s)

• 

[Csantucci]

Maybe this is caused by superelevation. Could you pls. make a test with superelevation off? Pls. check also that in "Experimental" options Gauge is set to 1435.

[wushin]

Csantucci, on 07 June 2013 - 12:55 AM, said:

Maybe this is caused by superelevation. Could you pls. make a test with superelevation off? Pls. check also that in "Experimental" options Gauge is set to 1435.

I will try your suggestions this evening and report back.
Thanks for taking the time to respond.

Donald

[wushin]

Yes, after turning super elevation off the track and ballast displays normally now. The options gauge was already at 1435.
I hope this helps to solve this minor distraction.


Donald

[JTang]

You need to have the track profile from here: http://www.elvastowe...303#entry115303

You need to extract the file into the TrackProfiles folder of your route. If this folder does not exist, please create one first.

[wushin]

JTang, on 07 June 2013 - 03:01 PM, said:

You need to have the track profile from here: http://www.elvastowe...303#entry115303

You need to extract the file into the TrackProfiles folder of your route. If this folder does not exist, please create one first.

I downloaded the file and placed it in a folder I created named TrackProfiles which is in my WP3 folder. I ran the WP route and still notice some differences although not as bad. I hope I followed the directions correctly.

First picture with the Super elevation set to 1.

Second picture no Super elevation.

Thanks for the input and help.

Donald

Attached thumbnail(s)

• 
• 

[Mike B]

Sorry to dredge up an old topic, but I have noticed the same problem in other routes (such as FPM's Pac Surfliner) that use Scalerail. Would the same profile fix work there? Basically, it seems like with superelevation on, even at just 1, the curves have a completely different texture and color than they do on the straights. Will download & try it, anyway; also on WP3, which I have but haven't tried in OR with super on, yet.

[That Genset Foamer]

Superelevation appears to support only one texture, not sure if it can be changed but in theory ORTS could detect which TrackProfile.stf to use based on a parser that checks the string for the section prefix, and pulls the relevant trackprofile.stf. SR_w_ going to the SR_w_trackprofile.stf, SR_c_ going to the SR_c_trackprofile.stf, and so on.

[burgerbern]

Could this be linked to the last post above, this is on the Sherman hill beta route and any setting on Super Elevation produces no ballast texture showing (have tried settings of 1,2 &5) all come out the same as pic below shows, on the NEC4 route it works with no probs. This is with the latest stable V1 release of OR

http://i26.photobucket.com/albums/c103/burgerbern/Open%20Rails%202015-06-06%2008-19-50.jpg

[Hack]

That would indeed be strange, as there is no dynamic track on the route. Isn't SE applied only to dynamic sections? :)