[BB22210]

Hello,
Thank you for your reply.
I just discovered the existence of the version 88 of Monogame, and yes Json datas can be captured and interfaced with our Train console.
/BUG ON /
I discovered a small issue on signal light that are not aligned at the right position in the signal, did you encounter this trouble (bug) ? I do not want to chnage configuration in sigcfg.dat file since all is ok into OpenRails.
/BUG OFF/

Do you know if source code of Monogame v88 is available for developpers ?

Thanks & Rgds
Christophe

[Csantucci]

The source code is available under the GNU license at the site shown in my signature.

[scottb613]

bennycdn, on 22 January 2021 - 07:24 AM, said:

Scott,I tried doing this with my IP with the:2120 and couldn't get it to work or load. I tried the manual,there was nothing about it.
Could you possibly do a step by step about the process. Thanks Benny

Did you get it working ?

Regards,
Scott

[Sid P.]

Hi Carlo, I may have missed something, but I find that when I run release version 1.3.1.275, I can keep the Dispatch viewer open in the same window as my cab, and operate the train controls; but when I run the MG .86 or .88 version, I cannot keep the dispatch viewer alive in the same window. To operate my train controls I have to close the dispatch viewer or move it to another display window. Is that the intended mode for the MG version, or have I missed an option?

[Csantucci]

Hi Sid,
maybe the addition of the timetable tab in the Dispatch Window has caused a different behaviour. However it is enough to click on the main game window to get back control of the train.

[Sid P.]

Hi Carlo,
Yes, but that puts the Dispatch window behind the full screen OR window - so I still can't have both visible in the same window.
The important difference is that in the release version, the keyboard controls are still alive when the Dispatch window is visible (but not selected) ; in the MG version, the keyboard is locked out when the Dispatch window is visible.

Sid.

[Csantucci]

If users prefer to have your issue solved and to renounce to the timetable tab, I can revert the change. Having both (issue solved and timetable tab) is not possible, at least for me, because I'm not the author of the timetable tab addition.
When I use the dispatcher window, I usually open it on a secondary screen, but I understand that that's not possible for everyone.

[cjakeman]

Hi Carlo,

Csantucci, on 01 February 2021 - 11:49 PM, said:

Having both (issue solved and timetable tab) is not possible, at least for me, because I'm not the author of the timetable tab addition.

The addition of the Timetable Tab was not intended to affect the train controls.

As the author of this feature, I'm willing to look into this to see why it has this effect in the Monogame version - especially as we will be dropping XNA for Monogame soon.

Sid P.
Is it keyboard controls, mouse controls or both that are affected?

[Sid P.]

Hi Carlo,
Thanks for the explanation. I can get around the problem by putting the dispatcher window on another screen page.

[Sid P.]

Chris,
The keyboard is disabled on my system when the dispatch display is visible in the same window as the cab, for example. The mouse is active - if I click outside the dispatch window, it hides the dispatch window.

[Csantucci]

Chris,
thank you for your interest in trying to solve this.

[Csantucci]

Revision 89.1 of OR NewYear MG is available here http://www.interazio...loads/index.php .

This unofficial version has been derived from the latest official OpenRails testing revision X1.3.1-290.
Moreover it includes the fix to enable tapping on the OR icon on touch screen web clients, which is already present in the OR master branch.

No Unstable releases are used to preserve the Monogame version of OR NewYear MG.

The list of additional features to the testing official OR release present in OR NewYear MG is as follows:

- Monogame, OR NewYear MG version
- 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
- 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
- faster loading of Raildriver options page, by perpetualKid
- bug fix for https://bugs.launchp...or/+bug/1895391 Calculation of reversal point distance failing, see also http://www.elvastowe...point-set-to-1/
- support for inclined gauges in 2Dcabs, see http://www.elvastowe...ges-in-2d-cabs/
- bug fix for http://www.elvastowe...-brakes-in-hud/
- bug fix for http://www.elvastowe...w-train-player/
- support for animation of wipers in 2D cabs, see http://www.elvastowe...post__p__265101 ,
with the contribution of Paolo
- bug fix for http://www.elvastowe...post__p__265463 , by mbm_OR
- extended support for ETCS L2 planning area, for braking distance and text area, and initial support for menus by césarBL, see http://www.elvastowe...f-the-etcs-dmi/
- removed trace of wait processes when enable watchdog option deselected
- tentative support for RAIN textures for objects, terrain and transfers
- dynamic terrain and scenery loading strategy (useful for slower computers)
- American horn blow sequence for AI trains, see http://www.elvastowe...american-style/
- bug fix for https://bugs.launchp...or/+bug/1910684 Crash selecting height entry in altitude file
- NEW: using webserver code of official OR testing version, as improved by Ryan
- NEW: enable customized tooltips for cabview controls, by adding a

       Label ( "string" )

line in the cabview control block in the .cvf file, by Jindrich

Moreover some features present in the Unstable Monogame version by James Ross have been inserted.


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.

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

[scottb613]

Hi Carlos,

Well thank you kindly - sir.
;)

Regards,
Scott

[scottb613]

Csantucci, on 02 February 2021 - 07:24 AM, said:

Revision 89 of OR NewYear MG is available here http://www.interazio...loads/index.php .

Hi Carlos,

RE: Web Server

Just a heads up - v89 appears to include the little ORTS Logo at the bottom of the "Train Driving Info" - which is the [Toggle] to switch between the abbreviated and full text version of the HUD.

It appears to be the code that does not work well on iPads - I worked offline with Mauricio a week or so ago and I believe he fixed it - that fix appears to be missing.

I'm not saying it needs to be included if for some reason it's not ready for production - just an observation - FYI.

Thanks.

Regards,
Scott

[cjakeman]

Hi Sid P.

Sid P., on 02 February 2021 - 07:18 AM, said:

The keyboard is disabled on my system when the dispatch display is visible in the same window as the cab, for example. The mouse is active - if I click outside the dispatch window, it hides the dispatch window.

Forgive me if I'm a bit confused by all these windows.

I am thinking that when you write
"The keyboard is disabled on my system when the dispatch display is visible in the same window as the cab",
I should understand that as
"The keyboard is disabled on my system when the dispatch window is visible in the same monitor/display/screen as the cab".