[Csantucci]

engmod, on 01 August 2020 - 01:15 AM, said:

You should NEVER put an extra dot in a filename like E405.035.eng

The windows filemanager will expect that the extension to be ".035.eng" and the file will not load as expected.

Derek, that does not seem to correspond to reality. See here
https://en.wikipedia.org/wiki/Filename
In Windows a . in the filename is accepted, and the last one will be interpreted as the separator to the file extension.
So E405.035.eng should be accepted. After the last . the eng extension can be recognized.

[Haran Banjo]

Csantucci, on 01 August 2020 - 08:57 AM, said:

Derek, that does not seem to correspond to reality. See here
https://en.wikipedia.org/wiki/Filename
In Windows a . in the filename is accepted, and the last one will be interpreted as the separator to the file extension.
So E405.035.eng should be accepted. After the last . the eng extension can be recognized.

And then? What is the solution?

[YoRyan]

Haran Banjo, on 31 July 2020 - 04:33 AM, said:

There are some consists that don't work with the new version, an event that already occurred with the unstable version

the problem seems to lie in the name of the consist, those that have the dot (.), inside the consist itself and also in the rolling stock, in the .eng files both in the names and inside the file, for example try these rolling stock http://www.amicitren...a3cac622644a406

Thanks for the report. Fixed in U2020.08.01-1821.

[engmod]

>Derek, that does not seem to correspond to reality. See here
>https://en.wikipedia.org/wiki/Filename

Hi Carlo,

I will have to reserve judgement on this one.
I have been involved in two memorable filename issues in my work.
One involved email issues, where an extra dot in a username caused emails to fail sending. ( this does not happen any more )

The second issue was an inhouse written application ( written in VC ) that failed when using filenames with 2 dots.

[Csantucci]

After few time, revision 70 of OR NewYear MG is available here http://www.interazio...loads/index.php .
A new revision is already available, to incorporate the correction of the bug related to .eng filenames including periods.

This unofficial version has been derived from the latest official Open Rails unstable revision U2020.08.01-1821 (which does NOT include Monogame)
and from the latest official OpenRails testing revision X1.3.1-X1.3.1-195.
To see what the official unstable release includes, check here https://james-ross.c...&utm_medium=app .

The list of additional features to such unstable release present in OR NewYear MG is as follows:

- MONOGAME
- addition of track sounds in the sound debug window (by dennisat)
- F5 HUD scrolling (by mbm_or)
- checkbox in General Options tab to enable or disable watchdog
- increase of remote horn sound volume level
- when car is selected through the F9 window, the car's brake line in the extended brake HUD is highlighted in yellow (by mbm_or)
- improved distance management in roadcar camera
- signal script parser (by perpetualKid): reduces CPU time needed for signal management
- true 64-bit management, allowing to use more than 4 GB of memory, if available, in Win64 systems (mainly by perpetualKid)
- general options checkbox for optional run at 32 bit on Win64 (to avoid slight train shaking bug)
- translatable Train Driving Info window (see http://www.elvastowe...post__p__251671 and following posts), by mbm_OR
- extended Raildriver setup, as present in OR Ultimate (by perpetualKid)
- analog clocks showing game time, see http://www.elvastowe...station-clocks/ , by jonas
- bug fix for bad mouse pointing in full screen mode and for issues with Fast full screen-Alt-Tab mode
- Webserver operating also with IPv4 addresses, that is on external devices, by mbm_OR, cjakeman and BillC
- panto commands and animations now swapped when in rear cab
- improvements in Activity Evaluation of station stops, by mbm_OR
- correction to reduce transfer flickering at short distance
- allow passing a red signal for shunting through dispatcher window, see https://trello.com/c...spatcher-window , by césarbl
- Fix memory usage indication that was clamped to 4 GB, see http://www.elvastowe...post__p__257699
- option to skip saving commands (reduces save time on long activities), see http://www.elvastowe...post__p__257687
- skip warning messages related to ruler token, that is introduced by TSRE5
- General Option to reduce memory usage
- Bug fix for https://bugs.launchp...or/+bug/1877644 SPEED signals not being updated in multiplayer clients. By cesarbl
- Avoid 3D cab stuttering by a mutable shape primitive, by YoRyan
- bug fix for memory leak, see http://www.elvastowe...al-memory-leak/
- track gauge can be changed over the whole route, see http://www.elvastowe...ng-track-gauge/
- first edition of management of ORTS_POWERKEY and ORTS_BATTERY cab controls, by Paolo
- re-introduced advanced coupling, by steamer_ctn
- NEW: improvements to webserver, by mbm_OR




Instructions and additional files to use the AWS TCS are available here http://www.elvastowe...post__p__255510 .


Users having not more than 4 GB RAM are suggested to run selecting general options checkbox for optional run at 32 bit on Win64.

When running on Win64, the player can select if he prefers running at 64 bit or 32 bit. In this second case RunActivity32.exe is run, and only a maximum of 4 GB of RAM can be accessed by OR. If the computer has only 4 GB RAM, selecting the option to run at 32 bit on Win64 is recommended.
Note for developers: Runactivity32.exe is not generated by building the pack, but manually doing a copy of Runactivity.exe, renaming it Runactivity32.exe, and using on the Developer Command Prompt command corflags with the modifier -32BITPREF+


NOTE: ReShade 4.3.0 or older or ReShade later than 4.5.2 must be used. ReShade 4.4.2 doesn't work here. See here http://www.elvastowe...mg-and-reshade/ for an installation guide of ReShade.

When running on Win64, if you are running OR at 64 bit (option not checked) you must point ReShade to OpenRails64.exe; if you are running OR at 32 bit (option checked) you must point ReShade to OpenRails.exe.

It is suggested to unpack the .zip using 7zip, if other unpackers lead to problems.

Instructions for web server:
What you can do now to test it: check the general options checkbox Enable WebServer, and start OR. If you type
http://127.0.0.1:2150/index.html
in your browser of the same PC where OR runs, you'll get a web page with the OR HUD.
You can display the same page also on other PCs, or devices like an Android Smartphone or TV box, or an IPad. In this case however, within the Command prompt you must type ipconfig; you will get some lines as reply, and one of them is
IPv4 Address. . . . . . . . . . . : 192.168.1.114
So, in such case, on the browser of your external device (being in the same internal network of your PC) you will have to type
http://192.168.1.114:2150/index.html

Revision 68 can still be downloaded from here http://www.interazio...loads/index.php (click on OR_NewYear_MG_oldrecent.zip) .

[Haran Banjo]

Hi, I wanted to report that multiplayer with the monogame version 70 does not work. When a player tries to join in multiplayer he displays 1 player 1 train.
It is not a problem of Routes, UID in consist or of missing train, because the same trains have been used by all the players.
For the avoidance of misunderstandings it has also been tried with other trains.

[Csantucci]

Hi,
can you try also with the latest Unstable release?

[Haran Banjo]

Csantucci, on 05 August 2020 - 12:42 AM, said:

Hi,
can you try also with the latest Unstable release?

I tried the latest unstable U2020.08.04-2021 version, and the problem persists. also on the site http://www.tsimserve...ServerInfo.html when trying to access a door, only the number of accesses appears, but not the name of the route and those of the players

[YoRyan]

So, to be completely transparent, the reason tsimserver can no longer talk to OR unstable is because I've introduced a "tilting" boolean to the "PLAYER" message to indicate whether or not the player train tilts. Currently, we infer this from the presence of the "tilted" string in the consist filename, but for our native format I'd like to deprecate this and just use a dedicated "IsTilting" property instead, which can be independent of the filename.

I inserted the new flag into the middle of the message, so I think I might be able to restore backwards compatibility by moving it to the far end. I will look into this, as well as the broken multiplayer in general in the unstable release, so thanks for the reports, everyone.

However, what concerns me is that if the ability for the tsimserver to talk to Open Rails is indeed a "hard" requirement, then this needs to be spelled out somewhere for new developers, either somewhere in the code or in the developer documentation. As of now there is no indication that the multiplayer code needs to do anything except talk to identical versions of Open Rails. (A natural conclusion, since we don't worry about backwards compatibility for save games, do we?)

In my personal opinion we should add some kind of querying API for tsimserver to use that isn't so brittle and won't change between versions, but that's a decision for the management team.

[YoRyan]

Update: In my testing, unstable -> unstable multiplayer works. Beware that if you have the web server enabled, the second RunActivity.exe instance will crash, because EmbedIO cannot bind to the same port number twice! Perhaps that shouldn't be a fatal error.

I've come around on backwards compatibility and I have decided to preserve it, but I am still working on that patch. At the moment I am having trouble getting the public server to work.