[Weter]

and/or it's animation

[Laci1959]

Hello.

In the ORTSSuperElevation block, what determines the MinimumSpeed ​​( ), MaximumSpeed ​​( ) speeds?
1. The actual speed of the train.
2. The last speedpost left.
3a. The speed determined by the last marker touched, if Max.
3b. The speed determined by the last marker touched, if reduced speed ( 40km/h, 80km/h ) is allowed.

With best regards, Laci 1959

[pschlik]

Laci1959, on 27 May 2025 - 08:14 AM, said:

Hello.

In the ORTSSuperElevation block, what determines the MinimumSpeed ​​( ), MaximumSpeed ​​( ) speeds?
1. The actual speed of the train.
2. The last speedpost left.
3a. The speed determined by the last marker touched, if Max.
3b. The speed determined by the last marker touched, if reduced speed ( 40km/h, 80km/h ) is allowed.

With best regards, Laci 1959

The values of MinimumSpeed and MaximumSpeed are manually defined and are determined by how (or even if) a railroad handles superelevation across wide speed ranges. It's up to you to figure that out (does the railroad use different superelevation for regional lines than for high speed lines? If it's different you'll need to use the speed parameters to make sure the high speed line gets one type of superelevation while the regional line gets a different type) and sometimes it won't be needed at all. If you don't give any values, MinimumSpeed will be 25 kph or 15 mph depending on route units, and MaximumSpeed will be infinity.

As for this 'speed' we want the min and max of, this is referring to permanent track speed limits, not actual train speeds, not signal speeds, not temporary speeds (at least, I think it ignores activity speed limits?) Each section of track checks the freight and passenger speed limits in both directions (by looking for speed limit signs protecting that track section) and the largest of those 4 limits (usually the passenger speed limit) is compared to the MinimumSpeed and MaximumSpeed. If the track speed limit is below the minimum or above the maximum given in ORTSSuperElevation, then that superelevation won't be applied to that particular track section, though it can still apply to other track sections on the route that do have the right speed limit.

The current speed of a train does not matter for this decision; this is all done before any trains are put on the map.

FS.E652 091, on 05 March 2025 - 09:07 AM, said:

At this point all I have to do is do some tests with a rolling stock with normal, i.e. standard, bogies... and see if it works...

Returning to the discussion of the rolling stock with intercommunicating bogies, is the solution therefore to act on the 3D model?

Oh yeah, by the way, I'm guessing your problem was the same as this bug. The way that train was assembled with the bogies as their own wagons makes it behave just like 2 axle rolling stock, so if the route had superelevation but the option in settings was disabled then you'd get no superelevation. You can check that again since the bug is fixed.

[FS.E652 091]

pschlik, on 27 May 2025 - 10:38 AM, said:

The values of MinimumSpeed and MaximumSpeed are manually defined and are determined by how (or even if) a railroad handles superelevation across wide speed ranges. It's up to you to figure that out (does the railroad use different superelevation for regional lines than for high speed lines? If it's different you'll need to use the speed parameters to make sure the high speed line gets one type of superelevation while the regional line gets a different type) and sometimes it won't be needed at all. If you don't give any values, MinimumSpeed will be 25 kph or 15 mph depending on route units, and MaximumSpeed will be infinity.

As for this 'speed' we want the min and max of, this is referring to permanent track speed limits, not actual train speeds, not signal speeds, not temporary speeds (at least, I think it ignores activity speed limits?) Each section of track checks the freight and passenger speed limits in both directions (by looking for speed limit signs protecting that track section) and the largest of those 4 limits (usually the passenger speed limit) is compared to the MinimumSpeed and MaximumSpeed. If the track speed limit is below the minimum or above the maximum given in ORTSSuperElevation, then that superelevation won't be applied to that particular track section, though it can still apply to other track sections on the route that do have the right speed limit.

The current speed of a train does not matter for this decision; this is all done before any trains are put on the map.


Oh yeah, by the way, I'm guessing your problem was the same as this bug. The way that train was assembled with the bogies as their own wagons makes it behave just like 2 axle rolling stock, so if the route had superelevation but the option in settings was disabled then you'd get no superelevation. You can check that again since the bug is fixed.

Thank you for the response!! that type of bogie is particular, so, by the way, since ORTS_MG has been updated, with the superelevation sistem too, the problem is gone and it's works normally!
I hope that in future you will perform the superelevation sistem with new improvements too!

[Albertosaurio65]

Hi, I have encountered a "bug" that has made me very dizzy trying to find what it was.

The train stops suddenly at the beginning of a curve, regardless of speed, and neither forwards and backwards, after doing everything and seeing that it didn't work, I suddenly remembered that I didn't put ORTSTrackGauge on it because it was a variable gauge train, I put it on and the problem was solved.

This creates doubts for me about how to proceed with the configuration of variable gauge trains, since there are routes with the Iberian gauge of 1668mm, others with the UIC gauge of 1435mm, and routes in which both are present. Currently, as this cannot be simulated, it is decided to put the most coherent one in the TRK due to its use, whether AV (1435) or CONV (1668), and I cannot decide which section uses one trackprofile or another, where the track gauge is also specified.

I suppose that by putting a gauge on the train, whether it corresponds to the track or not, the train will not stop as it does if it is not specified, right?

Saludoss

[pschlik]

The ORTSTrackGauge is exclusively used to determine the curve resistance, derailment risk, and the max comfortable curve speed. If a train stops on a curve, that sounds like a curve resistance problem. I would encourage you to grab a screenshot of the "forces" Alt + F5 debug screen when this issue happens, but after looking at the curve resistance code for a minute I think there might be a very simple mistake (missing parenthesis) causing faulty calculations.

Now, all that said, ORTSTrackGauge should be set automatically, so perhaps that's wrong as well. I guess I needed something to do with my Saturday night...