Hi Carlo,
Yes it occurs on MG1.3E and latest version v88, but not for all signals
Rgds
Christophe
Incorrect display of the light texture of the signal SignalLightGlow
#12
Posted 23 January 2021 - 12:28 AM
This occurs also on some Italian signals, and if I remember well, it occurs also in the official OR releases. I have no clue for that, and we here have OR-specific versions of sigcfg.dat, which we put in the route's Openrails subfolder.
#13
Posted 23 January 2021 - 12:52 AM
Csantucci, on 23 January 2021 - 12:28 AM, said:
This occurs also on some Italian signals, and if I remember well, it occurs also in the official OR releases. I have no clue for that, and we here have OR-specific versions of sigcfg.dat, which we put in the route's Openrails subfolder.
I would like not to change sigcfg.dat configuration file since it works perfectly for Openrail 1.31.
Is it possible to set a switch on config signal file among ORTS or MG usage ?
#15
Posted 23 January 2021 - 03:22 AM
I use :
OR1.31 and before signals are Ok
MG1.3E : not Ok
New Year MG X285 unofficial Rev 88 (downloaded yesterday) : not Ok
OR1.31 and before signals are Ok
MG1.3E : not Ok
New Year MG X285 unofficial Rev 88 (downloaded yesterday) : not Ok
#16
Posted 23 January 2021 - 07:38 AM
Christophe,
I understand that, but I need to know if the malfunction is there also with the Unstable release. Do you know how to get it? You can download it from here https://james-ross.c...jects/or/builds .
I avoid having flags that let a program run differently under OR NewYear MG and official versions. The behaviour should be the same.
I understand that, but I need to know if the malfunction is there also with the Unstable release. Do you know how to get it? You can download it from here https://james-ross.c...jects/or/builds .
I avoid having flags that let a program run differently under OR NewYear MG and official versions. The behaviour should be the same.