[Weter]

OR.org site said:

T1.5.1-1462-g1fe38c637 Merge pull request #936 from rwf-rr/contentmanager-add-to-consist-info
ContentManager Enhancement: show more info for consists
(and so on...)

Could we know more about this new-looking thing, please.

[C44-9W]

Quote

Could we know more about this new-looking thing, please.

The ContentManager is a contributed feature (under Tools) that shows info about installed content: Routes, Activities, Consists, etc.

This enhancements adds more data for consists. Here is an example:

• The attributes Num Engines to TOPB are new. The last two, HP per Ton and Tons per Operative Brake are North America specific. There may be equivalents for other regions.
• The Weight column in the Car list is new. It is a crude bar-graph of the car weight. This helps to see where the loads and empties are.

I find this useful to select a train to practice specific train handling scenarios (on mountain grades).

Roger

[Weter]

Hello, Roger and thanks for answer.
I didn't see it yet alive, but on screenshot, it's clear: additional information is very useful and representative.
Before, length and tonnage were evaluated only via TSRE, what is not always handy.
Could parameter num axles be fetched too? That's also specific characteristic, important for brakes handling.

My gratitude for improvement.
Is localization capability via GetText planned for this program?

[C44-9W]

Weter, on 19 January 2025 - 01:34 PM, said:

Could parameter num axles be fetched too? That's also specific characteristic, important for brakes handling.

NumAxles could be added easily. However, there are some MSTS work-arounds that result in odd NumWheels values. I believe it mostly affects locomotives and articulated cars.

Quote

Is localization capability via GetText planned for this program?

No. The original implementation (done way back) did not include localization. The enhancement minimized the impact on existing code.

Roger

[Weter]

Axles number primary important for long freight trains.
Articulated freight cars and locomotives are not used here usually, so I don't expect much trouble.

[C44-9W]

I have PR 1052 up to add the Axle count. Consist shows total count, engines powered plus unpowered, cars show axles.

It was not entirely trivial. Some rolling stock mixes ORTS (Axles) and MSTS (Wheels) config. And a lot of the legacy-MSTS NumWheels config is tweeked to get good physics. This explains some unexpected counts.

[pschlik]

Worth noting that OR physics handles the inconsistencies of "NumWheels" by assuming that value is the number of axles unless that number is 6 or larger, in which case it could be anything (I've seen content where the number was obviously neither axles nor wheels and had some arbitrary value set to convince MSTS to do...something?) so the number of axles gets set to 4. Whatever the content manager does aught to reflect that.

ORTSNumberAxles completely bypasses anything from NumWheels, and there's no limitation on the NumberAxles value...so everyone out there should use ORTSNumberAxles.

[C44-9W]

pschlik, on 03 March 2025 - 12:28 PM, said:

Whatever the content manager does aught to reflect that.

It does. I looked at MSTSLocomotive.Initialize() and TrainCar.UpdateTrainDerailmentRisk() to see what the simulation does.

[Weter]

Quote

I have PR 1052 up to add the Axle count.

Thanks, dash9, a lot.
As I always correct Num wheels data to actual in files, I got, I expect, that would be accurate for my trains.