[BenDragon1337]

Hey there

I was wondering if it was possible to implement some sort of variable pantograph heights to the animation.

The problem is this: currently the way MSTS / Open Rails works the pantograph raises till the end of its animation stroke independent of the actual wire height for the route.

What I was thinking is that if a route's wire height is below the maximum pantograph height for the locomotive, then the animation would raise the pantograph until it met with the wire, if it was too low then it would reach the animation stroke and work normally like it currently does.

It would enable players to drive electric locomotives from a much wider variety of countries without looking awkward because the pantograph is too high for the wire.

[Mike B]

Like it! :thumbup3:

It would also be good to have if we ever get to the stage of realism where the wire sags a bit between suspension points (OK, probably only in simple suspension) and the pan/trolley pole can be seen to follow it in outside views. Yes, that's probably about version 4 or 5, after MSTS compatibility becomes fully optional ...

[BenDragon1337]

I only said it because I am sick and tired of the inability to drive the Uk class 77 on the Japanese Tokyo route with the BR MK1 coaches because the Japanese wires are lower then UK's wires. ^_^

As for the raising and lowering of catenary wires, I think that will have to happen after this is implemented. Not to mention the new editor would have to be capable enough to actually handle the new feature as well because the MSTS editor would not really have the capability to handle such a feature.

But think of the possibilities if it was ever implemented.

[Hamza97]

+1 to this suggestion...... :) :)

[copperpen]

What you are actually asking for is a mechanism whereby the code reads the route wire height and controls the animation to suit. While it would be a nice thing to have, I am not so sure that it is actually something that can be done within the normal animation methods. It would require the shape file to be read, and assume that it conforms to the proper naming conventions, and then make changes on the fly to the shape file as it loads.

[roeter]

To make it worse, some pantographs are made up of multiple parts, which only come together at the proper positions at the end of the animation, with some parts rotating (the lower support parts), some translating (the pantograph top), and some doing both (the top support part). Stopping the animation somewhere inbetween would require complex calculations for the required position of each individual part.

Regards,
Rob Roeterdink

[Kazareh]

Wouldn't it be easy enough to through definitions to 'define' part of the Pantograph as the 'top' of it, and then basically input code into ORS taht says 'When Defined PantoTop reaches Wireheight, stop animation.'?

[vince]

Kazareh, on 12 August 2015 - 04:51 AM, said:

Wouldn't it be easy enough to through definitions to 'define' part of the Pantograph as the 'top' of it, and then basically input code into ORS taht says 'When Defined PantoTop reaches Wireheight, stop animation.'?

As I understand the problem is as Rob states is the animation states of some pantographs (remember there are hundreds of folks making models) the 'in between up and down states are not useable so your suggestion to "stop when the right height is reached" is not workable.
best,
vince

[eric from trainsim]

I also don't see this as workable either within the current bounds of the shapefile. Animations have a starting point, and an ending point. Stopping halfway in between isn't feasible. You'd need to have a different animation model that has stops at pre-defined wire heights, and then you'd need some form of definition within the route and/or track section that says which ending stop is used for pans up/poles up.

What some shape creators have done is have different shapes for different wire heights. That seems to be the better bad choice.

[disc]

eolesen, on 12 August 2015 - 10:01 AM, said:

I also don't see this as workable either within the current bounds of the shapefile. Animations have a starting point, and an ending point. Stopping halfway in between isn't feasible. You'd need to have a different animation model that has stops at pre-defined wire heights, and then you'd need some form of definition within the route and/or track section that says which ending stop is used for pans up/poles up.

What some shape creators have done is have different shapes for different wire heights. That seems to be the better bad choice.

Animations can be stopped/reversed anytime, if it's implemented in the "player". Cab control animations work like that. If parts of a pantograph visible fall apart during the animation, then the animation is simply isn't good enough.