[ATW]

I think the old way most are use to is the word tab options clicked on a engine wagon rather then getting use to the symbols. Maybe it needs to be optional, symbols need wording or the in-game option needs it to be like the Train Driving Hud or DPU operation of having the option to minimize/maximize character abbreviations.

I like the vertical option more as it feels like reading an actual train list rather doing so much horizontal scrolling. So less scrolling, click a engine wagon show symbol or side click to show the old wording way of what to do to that engine or wagon. There's still some advanced features missing such as certain valves or breakers that will someday need to be implemented.

[Laci1959]

Traindude, on 27 January 2024 - 05:26 PM, said:

Thinking out loud here, if we wanna eventually implement permanent "bar" couplings (exmaple: The Original Acela Express, steam locomotives and their tenders, etc.), which cannot be uncoupled by the player in-game, how do we communicate to the player that the coupling cannot be uncoupled?

Like this?...:
Open Rails 2024-01-27 05-13-31_Cropped_Gray.jpg

...or like this?:
nocouple.jpg

Obviously, these images are demonstrations. These would need to be updated when the new Train Ops graphics are created.

Hello.

This is a sorely missed feature. I've missed you since the beginning. In Europe, there are trains where the ends of the two cars rest on a common bogie. This is the so-called Jacobs bogie. It cannot be disassembled only in a suitable workshop with many hours of work. I like the lower red marking better. More attention grabbing.

Sincerely, Laci1959

[Weter]

Hello.
I think, some special symbol, like = would look more logical, than striked-out auto-coupler symbol(which could mean/be understood as failed coupling, or so).
Permanent coupling is neither automatic, nor hook by it's design, so why mess symbols.
Excuse me, if it sounds too straightforward - haven't intention to offend anyone.

[Genma Saotome]

I've not yet used this but it sure looks like it adds a lot of utility. THANK YOU!


I do have a few thoughts about future improvements, should there be any.

In North America, and perhaps elsewhere, cars are identified by the owner's initials and the car's own serial number (e.g., B&O 123654), both of which are painted on the car, clearly visible to any of the crew working on the ground. I would love to see Initials() and CarNbr() in .wags and made visible somewhere in-game. My question is to ask if there is anything like this in other countries? Surely there must be some aid to help the people on the ground do the right thing besides counting to the 37th car and hoping you got it right.

Second, I noticed someone mentioned Lading. Again, another longed for add: LadingName() and LadingMass(). The later really needs EmptyMass() too so ALL .wags have EmptyMass() and the value of the official parameter, Mass() is handled by OR.

Last, this too may be specific to North America (but I rather doubt it); The conductor is in charge of the train and when it comes to the retail side of train operations (a.k.a switching) he has the information for exactly where the switching will occur and I would expect that includes the name of the shipper (for dropping empties) or consignee (for receiving loads) as well as the car(s) initial(s) and number(s).

When you put it all together the parametric data might look like this:

StationName(Oak Park) TrackID(123) Action(Drop) Initials(ATSF) CarNbr(12754) Consignee(Nabisco) LadingName(Empty) LadingMass(0t-us)
StationName(Oak Park) TrackID(123) Action(Pickup) Initials(ATSF) CarNbr(63962) Shipper(Nabisco) LadingName(Biscuits) LadingMass(28t-us) and somewhere else:
StationName(Stockton) TrackID(789) Action(Drop) Initials(ATSF) CarNbr(63962) Consignee(Safeway) LadingName(Biscuits) LadingMass(28t-us)

How that should be presented (and how much of it) is a different (and harder) question. Some/all in the sprites above cars? Some in the brakeman's window you've created?

So the above is just food for thought; I do hope some of it has enough value to be coded.

[Weter]

8-digits numeration for rolling-stock units is used.
For locomotives it contains type, for freight - type, for passenger - owner and purpose.
These are first two digits. Next five is number itself.
8-th digit is verification symbol, like we have on bar-codes. That's because automatic recognition facilities are used on bid station throats.
There are electronic marks, attached to stock, for rf-scanning instead of optical.

[Weter]

Hello.
New train operation winoow is indeed eye candy, but it seems, code isn't perfect yet.
With 1.5.1-1192 testing version I got crash to desctop, after clicking on consist unit's number in F9 window.
details are below:

Information: At 0 secs, advanced adhesion model switched to low precision after low frame rate 12,6 below limit 30

Error: System.NullReferenceException: Ссылка на объект не указывает на экземпляр объекта.
   в Orts.Viewer3D.Popups.TrainCarOperationsViewerWindow.buttonTogglePower.locomotiveStatus1(Int32 CarPosition)
   в Orts.Viewer3D.Popups.TrainCarOperationsViewerWindow.buttonTogglePower..ctor(Int32 x, Int32 y, Int32 size, Viewer viewer, Int32 carPosition)
   в Orts.Viewer3D.Popups.TrainCarOperationsViewerWindow.Layout(ControlLayout layout)
   в Orts.Viewer3D.Popups.Window.Layout()
   в Orts.Viewer3D.Popups.TrainCarOperationsViewerWindow.PrepareFrame(ElapsedTime elapsedTime, Boolean updateFull)
   в Orts.Viewer3D.Popups.Window.VisibilityChanged()
   в Orts.Viewer3D.Popups.buttonLoco.buttonLabel_Click(Control arg1, Point arg2)
   в System.Action`2.Invoke(T1 arg1, T2 arg2)
   в Orts.Viewer3D.Popups.Control.OnClick(Point mouseControlLocation)
   в Orts.Viewer3D.Popups.Control.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.WindowControlLayout.HandleMouseUp(WindowMouseEvent e)
   в Orts.Viewer3D.Popups.WindowManager.HandleUserInput(ElapsedTime elapsedTime)
   в Orts.Viewer3D.Viewer.HandleUserInput(ElapsedTime elapsedTime)
   в Orts.Viewer3D.Viewer.Update(RenderFrame frame, Single elapsedRealTime)
   в Orts.Viewer3D.Processes.UpdaterProcess.Update()
   в Orts.Viewer3D.Processes.UpdaterProcess.DoUpdate()
   в Orts.Viewer3D.Processes.UpdaterProcess.UpdaterThread()
   в System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   в System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   в System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   в System.Threading.ThreadHelper.ThreadStart()

No problem for cars - above is about diesel locomotive.
Power On icon is not being shown.
Battery icon occasionally not being too for electric loco.
White squares for both cases instead.
By the way, cab for that locomotive is not being installed (not sure, can that affect, or no), though, other locos with cab installed crash the game as well.
Very front/rear angle cocks is impossible to operate (it can be done with old menu Ctrl+Alt+F9, but no indication on new window).
Can't open cocks completely (that's being done automatically somehow, after hoses connection)

All that happens if different language is being choosen - not default English.

[mbm_OR]

Hi Weter,

Quote

All that happens if different language is being choosen - not default English.

It seems to point to outdated locales files. I'll take a look.

Regards,
Mauricio

[Weter]

Thanks, Mauricio.
What could I do from my side (locales) to assist You?

[mbm_OR]

Hi Weter,

Weter, on 16 September 2024 - 02:02 PM, said:

What could I do from my side (locales) to assist You?

Could you please test these files for the unstable version?


Unzip to the /Program folder.


The RunActivity.Messages.resources.dll file to the /Program/ru folder.

Regards,
Mauricio

*** Updated : Fix available since unstable build U2024.10.10-2053.

[mbm_OR]

Hi,

About this bug, here is a fix for the Unstable version.

You need to unzip all the files in the program folder.

Regards,
Mauricio

*** Updated : Fix available since unstable build U2024.10.14-1322.

[mbm_OR]

Hi,

Since the release of this feature, the TrainCarOperations window and the TrainOperationsViewer window overlap when the TrainCarOperations window is moved or resized. This is annoying for users.

A fix is available in build U2024.10.19-0852.
The TrainOperationsViewer window will now automatically placed around the TrainCarOperations window, depending on where it is located on the screen.

This feature now appears to be more user friendly.

Regards,
Mauricio

[mbm_OR]

Hi Weter,

Weter, on 19 October 2024 - 03:12 AM, said:

Do You mean brake parameters string clipping?

Perhaps you are referring to the string brake parameters from the TrainDrivingInfo window, which are not related to this feature.
You can check that the string brake parameters, are now correctly aligned for all languages, a PR#990 was generated a week ago to fix this.

Regards,
Mauricio

[Weter]

Hello.
Sorry, my guilt: I indeed have messed these two different windows: called by F9 and F5.

[Genma Saotome]

Traindude, on 28 January 2024 - 09:21 PM, said:

While ORTS doesn't yet have the ability to differentiate between different types of freight/passenger cars yet (just "Passenger", "Freight", "Steam", "Diesel", "Electric" and "Tender"), ....

Late to the party by 10 months....

IMO a solution is pretty simple: Add a couple of new fields in .wag files and display them where they would be useful.

CAR TYPES
In the US the industry group AAR has, for at least a century, used two and three letter codes to signify what each car is used for. Oftent he codes would be unchanged for many decades. A few examples from before 1960:

XM -- Box, merchandise (i.e., an ordinary boxcar)
TA -- Tankcar, Acid
HT -- Hopper, twin
HM -- Hopper, general purpose
XAP -- Box, autoparts

A similar set of codes was used for passenger cars.

As cars designs changed obsolete codes were dropped, new codes added. At some point in recent years they were all scratched and a new set of codes were created, largely to address the need to identify special equipment and load limits.

IMO a set of codes like these could be created to cover freight cars world-wide. Many could be taken right from the AAR list, car types not used in North America could have codes created by us, or by the countries where they are used. If there is to be a worldwide list then there should not be multiple codes for the same kind of car; OTOH it might make more sense to make use of other countries car codes, in full; This would require a country code in .wags as well as the route's .TRK file (so OR would know which country code to use). There are several sources of worldwide country codes so these can be found and copied.

Car identification
Add these to the .wag and display them when useful:

CountryCode() -- CAN
Owner() -- CP
SerialNumber() -- 34612
CarType () -- XM

[Traindude]

Is anyone else having this issue with re-connecting the brake hoses after re-coupling to their train?

Whenever I try to connect the rear brake hose of the front car, then connect the front hose of the rear car, the front hose appears to disconnect (and vice versa). What am I doing wrong?