DBTracks with superelevation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pgroenbaek
    Member
    • Jan 2024
    • 98
    • Denmark
    • ORTS

    #46
    Originally posted by StormerDSR
    Hello,
    I started to use US1 dynatrax profiles with high ballast and embankment to create own shapes. As for me this is the best visual experience for dbtracks I had ever seen(I do not found something similar in standard DB profiles). Now I realized that superelevation profiles are not created yet for such dynatraxs. Is there a possibility to include US1 dynatrax profiles in future plans for superelevation? Or maybe such superelevation profiles already exist somehow? Thank you for an answer.


    image.png
    There are profiles for USTracks available in the file library, including for US1he.

    If you created these shapes from the US1he Dynatrax profile and then changed textures in the shapes you can easily create a super-elevation profile for your custom shapes by taking TrProfile_US1he.stf and changing the textures within that in the same way.

    Make sure to also adjust the IncludedShapes to fit the naming of your custom shapes.
    - Peter

    Route Projects: DK24
    Utilities and Tools: ShapeIO, ShapeEdit, TrackshapeUtils

    Comment

    • StormerDSR
      Member
      • Feb 2024
      • 33
      • Poland

      #47
      Thank you very much, works like a charm These us2he profiles with superelevation support are big step ahead in route development

      Comment

      • StormerDSR
        Member
        • Feb 2024
        • 33
        • Poland

        #48
        Originally posted by pgroenbaek
        I have a suggestion for an improvement to the dynamic track flex functionality.

        Quite often when using it the first straight track section is left enabled with length 0.00, like this:

        Screenshot 2025-04-19 130502.png

        This actually causes a problem with the new super-elevation functionality in Open Rails, because Open Rails thinks there is a straight section in the middle of the curve if that 0.00 straight section sits between two curved track sections.

        You can of course just make sure to disable it manually, but I sometimes forget to do that. It's easily missed.

        It would be nice if it was disabled by default if the length is 0.00 after using flex.
        For me this will be a huge problem because I already had a lot of created dynatraxes using flex with first straight section =0. Reverting this to dynatraxes without 0 section is not an option for me(too much tracks and interactives to put again) . I hope there will be a fix for this situation in Openrails code.

        Comment

        • pgroenbaek
          Member
          • Jan 2024
          • 98
          • Denmark
          • ORTS

          #49
          Originally posted by StormerDSR

          For me this will be a huge problem because I already had a lot of created dynatraxes using flex with first straight section =0. Reverting this to dynatraxes without 0 section is not an option for me(too much tracks and interactives to put again) . I hope there will be a fix for this situation in Openrails code.
          Don't worry about it. It only causes the train to visually de-superelevate in the middle of curves if they sit within the curve. I very often use short dynatrax sections to change track elevation in curves, and that is why that if I forget to remove them then I get that behaviour.

          Most of the time the length=0.0 straight sections don't cause any issues at all.

          This was just a quality of life suggestion from me because it is something that I do so often and I sometimes miss that they are there.

          Even if you see this in your own route, the dynatrax sections don't need to be created again. The length=0.0 straight sections can just be edited away manually in the local tsection.dat. This is what I usually do if I already created the dynatrax track.
          - Peter

          Route Projects: DK24
          Utilities and Tools: ShapeIO, ShapeEdit, TrackshapeUtils

          Comment

          Working...