F3 handling in shunting operations

[King OfLions]

When decoupling a part of a train, the rear cam (F3) is moved to the new end of the train. When coupling to a new set of cars, the rear cam remains in the same position (is not repositioned to the end of the train). What makes it nearly impossible to position the end of the train correctly, especially on track ends.
This is an old bug which already existed in the MSTS.

The error ist not route or train dependent.

[Carlo Santucci (carlosanit1)]

I assume that, by pressing Alt+1(Numkey) after coupling, the rear cam (3) jumps to the new end of train.

[King OfLions (kol01)]

Thanks for your mail!

Not <Numkey> but ALT <END>. However, this is an inconsistent behaviour, as the other switching of the cam occurs automatically (and it should not be necessary to remember a 4 or 5 Level keyboard (combinations with <ALT><CTRL> etc. would be also possible ;-) for easy play).

Btw.: is there an easy way to place CR's in the system? The Version tracking board is locked for "normal" users. Can/should CR's also be posted as errors? I have a big one, and a few minor issues.

Kind regards
Alfred

-----Ursprüngliche Nachricht-----
Von: <email address hidden> [mailto:<email address hidden>] Im Auftrag von Carlo Santucci
Gesendet: Freitag, 1. Februar 2019 09:01
An: <email address hidden>
Betreff: [Bug 1814100] Re: F3 handling in shunting operations

I assume that, by pressing Alt+1(Numkey) after coupling, the rear cam
(3) jumps to the new end of train.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1814100

Title:
  F3 handling in shunting operations

Status in Open Rails:
  New

Bug description:
  When decoupling a part of a train, the rear cam (F3) is moved to the new end of the train. When coupling to a new set of cars, the rear cam remains in the same position (is not repositioned to the end of the train). What makes it nearly impossible to position the end of the train correctly, especially on track ends.
  This is an old bug which already existed in the MSTS.

  The error ist not route or train dependent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1814100/+subscriptions

[Carlo Santucci (carlosanit1)]

By CR you mean change requests? And do you mean only the request itself or also the related code changes?

[King OfLions (kol01)]

Only the request itself. The major request is regarding shunting operations, that have been implemented in the MSTS (due to performance and resource limitations) only partially (at least ... only the signal type "SHUNTING", that causes the MSTS to crash sometimes.
In difference so DE, where the "Sperrsignal" can be treated as main signal (affects shunting and train), the former k&k states (AT, SK, CZ, HU, partially PL, IT with associated private lines, and CH) distinguish between shunting an train signals. Clean shunting would be a major benefit for interesting scenarios. I do not know the state in the US, but UK has also shunting signals on some lines, an i think some lines in the USA also.

The problem today is, that shunting is a fake, and is neither signalled correctly, nor really possible in many cases (e.g. shuntig out of a station on the main line cannot distinguish between shunting and train operation.

It seems to be easily implementable, but should be discussed in advance, if there is any interest.

And, as i said, some other more or less minor issues, like stop points on platforms to avoid these incorrect stops centered to the platform etc.

-----Ursprüngliche Nachricht-----
Von: <email address hidden> [mailto:<email address hidden>] Im Auftrag von Carlo Santucci
Gesendet: Samstag, 2. Februar 2019 09:22
An: <email address hidden>
Betreff: [Bug 1814100] Re: F3 handling in shunting operations

By CR you mean change requests? And do you mean only the request itself or also the related code changes?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1814100

Title:
  F3 handling in shunting operations

Status in Open Rails:
  New

Bug description:
  When decoupling a part of a train, the rear cam (F3) is moved to the new end of the train. When coupling to a new set of cars, the rear cam remains in the same position (is not repositioned to the end of the train). What makes it nearly impossible to position the end of the train correctly, especially on track ends.
  This is an old bug which already existed in the MSTS.

  The error ist not route or train dependent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1814100/+subscriptions

[Carlo Santucci (carlosanit1)]

Here http://www.elvastower.com/forums/index.php?/topic/28517-open-rails-12-planning/page__view__findpost__p__201634 you can read how to propose new features for OR.