[Weter]

@Dave
Reading my log-files I've already noticed, that handling obsolete MSTS models, ORTS uses "standard diesel tabs", taking in account present power of given model's diesel from *.eng-file, which doesn't contain specified engine tab. And the same is for steamers: program uses average parameters, if such can't be seen at steamer's *.eng-file.

[steamer_ctn]

cjakeman, on 11 January 2022 - 12:03 PM, said:

I wonder what others are thinking about your idea.

I think that this is a good idea, however as this thread suggests not may people will modify ENG/WAG files, so how and when will the INC file be triggered to be read into OR?

I think that the lead locomotive can be used to determine the relevant INC file to use. So for example, if the brake system type on the lead locomotive is a vacuum one, then a "standard" vacuum INC file should be imported into OR, similarly for air, etc.

However when should this actually happen suggests that a switch (dare I suggest it) such as Simple/Advanced is required that will read these files, and any other one feature parameters required to "stabilise" the performance of OR.

Whatever way is decided, this needs to be part of a documented "big picture" view that currently has a number of other threads being discussed at the moment.

[cjakeman]

I'm going to skip over these 2 controls because they were discussed in some detail here.




Instead, let's consider:




and the Manual entry is:




Is the text OK?


I think this checkbox could be removed and the web server permanently active. On my low-spec laptop, there is no drop in frame rate when I check this checkbox so I don't think performance is an issue.

[Genma Saotome]

Open always should be fine. Only thing that comes to mind WRT text is to wonder if a sentence is needed to describe what text is or is not displayed on the second device(e.g., the command line at the bottom of the screen vs. anything from function key use). If everything is shown then perhaps inserting the word all is enough.

[Aldarion]

If the port number box is to be maintained, wich i guess it will maybe you can define a number to be inserted and be interpreted has 'webser not enable' instead of the checkbox. so otherwise it is always enabled.

[Csantucci]

I'd prefer to keep the checkbox, as my guess is that this (welcome) feature is used only by a minority of palyers.

[Weter]

As more features enabled tend to increase bugs probability, I'd prefer to have disabled as many of not used options, as possible.
Again, for bug localizing, it's useful to turn options one by one to see, which of them causes this bug.

[Genma Saotome]

Weter, on 13 January 2022 - 06:42 AM, said:

As more features enabled tend to increase bugs probability, I'd prefer to have disabled as many of not used options, as possible.
Again, for bug localizing, it's useful to turn options one by one to see, which of them causes this bug.

Unless the OR team starts to capture player's metrics we'll never know what is or isn't being used. And does always on count as 1 when it is set or 1 for each time the game is launched? Or do they collect both?

Collecting metrics could be useful but only after some thought is given to what the numbers really mean.

[cjakeman]

Genma Saotome, on 12 January 2022 - 11:50 AM, said:

Only thing that comes to mind WRT text is to wonder if a sentence is needed to describe what text is or is not displayed on the second device (e.g., the command line at the bottom of the screen vs. anything from function key use). If everything is shown then perhaps inserting the word all is enough.

Is there a misunderstanding here?

The page or pages displayed on the second device are not under the control of Open Rails but can be whatever the user wants. We distribute some sample pages (see the Manual) but these can easily be amended or replaced. For example they might show maps or content about the route.

[cjakeman]

Genma Saotome, on 13 January 2022 - 11:26 AM, said:

Unless the OR team starts to capture player's metrics we'll never know what is or isn't being used. And does always on count as 1 when it is set or 1 for each time the game is launched? Or do they collect both?

Collecting metrics could be useful but only after some thought is given to what the numbers really mean.

Collecting some player metrics is definitely something that we want to do. I guess we'll make it opt-in though to avoid invading users' privacy.

For example, it will be very useful to discover how much each option is used.

And, yes, we'll need to be discuss what the data actually means before we try and collect it.