markyisri, on 06 December 2017 - 07:06 AM, said:
I'm trying to avoid re-signalling my route to ensure compatibility with the downloaded version. I'm only changing sigcfg and sigscr.
Is there another way to reset the limit for NORMAL signals?
Is there another way to reset the limit for NORMAL signals?
In MSTS there is no other Way, then to place a hidden Signal(NORMAL)
If You have on this Route such hidden Signals You can this replace for OR as follow:
Copy the Signalfiles in a Folder OpenRails
Modify this Hidden Signal as follow:
Example of a Hidden Signal for MSTS can show as this:
SignalType ( "CHLBahnhofende" SignalFnType ( NORMAL ) SignalLightTex ( "ltex" ) SignalDrawStates ( 2 SignalDrawState ( 0 "Red" ) SignalDrawState ( 1 "Green" ) ) SignalAspects ( 4 SignalAspect ( STOP "Red" ) SignalAspect ( STOP_AND_PROCEED "Red" ) SignalAspect ( CLEAR_2 "Green" ) SignalAspect ( CLEAR_1 "Green" ) ) SignalNumClearAhead ( 2 ) )
The same Signal in the Folder OpenRails
_(OR_Special CHLBahnhofende ist vom Typ SPEED statt Normal) SignalType ( "CHLBahnhofende" SignalFnType ( SPEED ) SignalLightTex ( "ltex" ) SignalDrawStates ( 1 SignalDrawState ( 0 "Red" )) SignalAspects ( 1 SignalAspect ( STOP "Red" signalflags (OR_SPEEDRESET) )) SignalNumClearAhead ( 2 ) ) _(OR_Special Ende)
And delete the corresponding Signalscript in sigscr.dat in the Folder OpenRails
Now in OpenRails the Signalspeed raise in Openrails, und there is no Signal to see in the Trackmomitor.