OR NewYear MG
#81
Posted 21 March 2019 - 02:07 AM
In the Monogame version, a horizontal transfer becomes very prominent, depending on the viewing position, whereas in the 'standard' OpenRails, transfers seem to blend fairly well. A half-minute video clip illustrates the difference:
https://youtu.be/LBqVID-IFsg
Is there anything I can do to produce a better transfer texture which will not appear so unsightly under Monogame? It's not a major problem - in my real route most transfers are either not flat and horizontal or are in a more forgiving, gritty texture to suit a loco yard for example and they do not stand out so prominently. The clip from my 'Sandbox' route is really to show an extreme example.
On a more positive note, it also shows how much smoother it is under Monogame and woohoo, at the end of the rotation, the loco no longer does a celebratory skip!
#82
Posted 25 March 2019 - 03:57 AM
It is aligned with rel. 1.3.1-41 of the standard OR, plus
- addition of track sounds in the sound debug window (by dennisat)
- change of the font family and dimension for the digital displays in 2D cabs
- F5 HUD scrolling (by mbm_or)
- checkbox in General Options tab to enable or disable watchdog
- experimental increase of remote horn sound volume level
- enable/disable on screen control confirmations with Ctrl-Alt-F10
- removal of on screen notification of camera change
- dynamic management of trough refill (by steamer_ctn), see here http://www.elvastowe...-water-troughs/ .
#83
Posted 28 March 2019 - 09:20 AM
GreenRiver.JPG (99K)
Number of downloads: 26
#84
Posted 28 March 2019 - 09:47 AM
Csantucci, on 25 March 2019 - 03:57 AM, said:
It is aligned with rel. 1.3.1-41 of the standard OR, plus
- addition of track sounds in the sound debug window (by dennisat)
- change of the font family and dimension for the digital displays in 2D cabs
- F5 HUD scrolling (by mbm_or)
- checkbox in General Options tab to enable or disable watchdog
- experimental increase of remote horn sound volume level
- enable/disable on screen control confirmations with Ctrl-Alt-F10
- removal of on screen notification of camera change
- dynamic management of trough refill (by steamer_ctn).
Great stuff buddy, many thanks as always for the updated release.
Mike.
#85
Posted 28 March 2019 - 09:53 AM
jdgremsjr, on 28 March 2019 - 09:20 AM, said:
GreenRiver.JPG
I would have thought that the reason for the warning is self evident. It is telling you that the save you are about to load may not work in the current version of OR.
#86
Posted 28 March 2019 - 10:55 AM
copperpen, on 28 March 2019 - 09:53 AM, said:
I get that. but it was saved in the current version so why would a save in the current version may not work in the current version?
#87
Posted 28 March 2019 - 11:10 AM
copperpen, on 28 March 2019 - 09:53 AM, said:
The purpose of the message is to warn (but not prevent) resuming from a Save made in an earlier version.
However in this case it looks like the message is saying that the Save and the current version are the same.
This was an old bug. James fixed it (5 Jan 2017) so either this MG version is out of step with the official one or the code has since been broken.
#88
Posted 28 March 2019 - 11:13 AM
jdgremsjr, on 28 March 2019 - 10:55 AM, said:
Need an error message when there is a problem, not when there might be one.
It's not like it's going to damage anything.
Steve
#89
Posted 28 March 2019 - 01:37 PM
#90
Posted 28 March 2019 - 01:40 PM
Choosing Yes will start the saved activity with no further problems. The bug is back.
Attached File(s)
-
bandicam 2019-03-28 14-38-03-676.jpg (458.09K)
Number of downloads: 25