Transition Curves for Radius and Superelevation
2 posters
Page 1 of 1
Transition Curves for Radius and Superelevation
Currently openBVE doesn't seem to support transition curves, where the curve radii changes dynamically to allow the train to ease into the curve. Hope to see this feature someday where the train banks gently and eases itself into curves.
SMB142J- Posts : 4
Join date : 2021-02-26
Age : 25
Location : Singapore
Re: Transition Curves for Radius and Superelevation
I am pretty sure superelevation is already a feature. (And it will ease in from one block to another as well)
Track.Curve Radius; CantInMillimeters
Where the CantInMillimeters represents the superelevation (or cant) in millimeters.
As for transition curve, I hope this will be a thing as well. Right now it's kinda annoying to add it
(When I mean add it, I just means using an larger radius curve, then slowly reduce the radius)
Track.Curve Radius; CantInMillimeters
Where the CantInMillimeters represents the superelevation (or cant) in millimeters.
As for transition curve, I hope this will be a thing as well. Right now it's kinda annoying to add it
(When I mean add it, I just means using an larger radius curve, then slowly reduce the radius)
Re: Transition Curves for Radius and Superelevation
Yes the built-in cant is functional but the way it is triggered is extremely sudden and would be uncomfortable in real life. Was hoping it can be integrated with the transition rail so the rail will rise/lower along the length of the transition rail.
SMB142J- Posts : 4
Join date : 2021-02-26
Age : 25
Location : Singapore
Re: Transition Curves for Radius and Superelevation
Is the program suppose to bend a rail object automatically depending on the curve, or would the user require to generate the curve?
An shorter block length would've probably solve this question, but I found the performance hurt a lot.
What I see other developers are doing now is to make an Excel tools to calculate the radius of the transition curve, then slowly increase the cant each 25m block. But then again I think it's more like a workaround(??)
An shorter block length would've probably solve this question, but I found the performance hurt a lot.
What I see other developers are doing now is to make an Excel tools to calculate the radius of the transition curve, then slowly increase the cant each 25m block. But then again I think it's more like a workaround(??)
Similar topics
» Transition curve
» Dexter: Radius calculations in your developer document
» curves
» Points & Curves
» Building Curves for openBVE
» Dexter: Radius calculations in your developer document
» curves
» Points & Curves
» Building Curves for openBVE
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum