Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] Pantograph height route command #1086

Open
hotdamndel opened this issue Nov 8, 2024 · 2 comments
Open

[Suggestion] Pantograph height route command #1086

hotdamndel opened this issue Nov 8, 2024 · 2 comments

Comments

@hotdamndel
Copy link

hotdamndel commented Nov 8, 2024

Many routes require catenary height variation (tunnels, etc) and pantographs on trains must react to that. However, currently it's either very difficult and route-specific via plugins, or just inachievable.
I can suggest a simple solution (or at least my vision on it) - CatenaryHeight command for Track section in routes and a corresponding function for .animated files.

Route side:

With Track,
1000,.CatenaryHeight 5.0, ;in meters above rail heads
1200,.CatenaryHeight 5.0,
1250,.CatenaryHeight 4.2, ;tunnel starts here
1500,.CatenaryHeight 4.2, ;tunnel ends
1550,.CatenaryHeight 5.0,
...

Heights are interpolated similarly to .Brightness command (i.e. there are 50m "ramps" before tunnels in this example)

Train side:

[object]
States = PantoTop.csv
TranslateYFunction = 5.0 - CatenaryHeight(-6.2)

-6.2 in this example is offset along the track from Car[i]'s model origin, since we need to receive catenary height from route position exactly matching Car[i]'s current position with some offset (pantos are rarely mounted in the middle of a car).

@leezer3
Copy link
Owner

leezer3 commented Nov 8, 2024

I actually wrote most of this several years ago:
#501

Trouble is that traction modelling (the logical follow-on) is nowhere near being done, and I just end up bodging bits badly into the existing code, which was never designed to do stuff....
That's one of the reasons I've mostly been re-writing things slowly over the last few years, so that stuff like this can be added in sensibly.

If that PR looks interesting, it'd probably be simple enough to revive.

@hotdamndel
Copy link
Author

Looks promising. I'd honestly contribute a lot of traction and related sound realism, but can't code, so can only suggest the parts of my overall vision on how to make train simulation more realistic but still configurable and flexible enough

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants