Anyone knowledgeable about signals and signalling here? Help/Advice needed.

[HookitandBookit]

I am sorry for pestering the forums with all my questions, i find the learning curve quite steep and altough i like tinkering and finding stuff out on my own sometimes one needs help. So, are there anyone knowledgeable about the subject of signalling who can off some advice? Heres my starting point:
sigcfg_Checker v1.1 - Selected folder : E:\Norge ORTS\VBSR\Routes\Meråker


scr>> Duplicate Script entry - Pri3Light on lines 1045 & 57
scr>> Duplicate Script entry - Block5Light on lines 1162 & 118
scr>> Duplicate Script entry - Middle3Light on lines 1465 & 290
scr>> Duplicate Script entry - Middle2Light on lines 1496 & 473
scr>> Duplicate Script entry - Dwarf4Light on lines 1628 & 565

cfg>> No. of Signal Aspect Entries not equal to the number entered in SignalAspects.

Line Number : 254 SignalAspects ( 2

cfg>> Duplicate Signal Type - Pri3Light on lines 97 & 1020
cfg>> Duplicate Signal Type - Middle3Light on lines 147 & 2095
cfg>> Duplicate Signal Type - Middle2Light on lines 506 & 2146
cfg>> Duplicate Signal Type - Dwarf4Light on lines 199 & 2391

scr>> Signal Type : Block3LightNum from sigscr.dat [line 237] not listed in sigcfg.dat file
scr>> Signal Type : Middle3LightPrevious from sigscr.dat [line 361] not listed in sigcfg.dat file
scr>> Signal Type : Middle3LightOld from sigscr.dat [line 404] not listed in sigcfg.dat file


Signal Types used in .tdb file

Block3Light
Dwarf4Light
Middle2Light
Middle3Light
NorwSwArm2
PO2Light
POF2Light
Pri2Light
Pri2SimpLight
Pri3Light
PriDwarf7Light
Warn3Light

End of Report

Needless to say, running trains on this line is near impossible without manually changing signals, if not the trains despite beeing the only train on th eline just sits there waiting for green.

[slipperman]

Hi,
I don't profess to know much about the MSTS/ORTS signalling system so my utility, sigcfg_Checker, only reports inconsistencies/discrepancies between the sig.cfg.dat, sigscr.dat and the route's .tdb file. In many cases, they do not cause to problem for MSTS or ORTS, but might cause messages to be displayed the the log of the latter.

It needs somebody more knowledgeable on the subject to determine if the reported differences could cause problems and, if so, to suggest solutions.

Cheers,
Ged

[HookitandBookit]

I definately do need someone, i can't wrap my head around it. Here i am linking signals, making sure that they are properly linked. But when i examine the existing ones they are NOT linked to anything, yet they work?????!!!! Now i am really confused....does outbound signals not need to be linked? Only inbound signals?

[ZachBell4400]

On a route I'm building, for example, only the signals that protect switches (absolute signals) are linked to allow passing paths. The intermediate/bi-drectional signals can just be selected as "Check Next State" or something along that line, which shows the following signal status. A switch that diverges traffic will show Yellow-Yellow, or something like that. Make sure all signal heads allow for checking of next state if you are running a long-distance route.

[eric]

I definately do need someone, i can't wrap my head around it. Here i am linking signals, making sure that they are properly linked. But when i examine the existing ones they are NOT linked to anything, yet they work?????!!!! Now i am really confused....does outbound signals not need to be linked? Only inbound signals?

Not sure what you're calling inbound or outbound...

For a path converging (i.e. joining with another path) on a red pole, signals will automatically link the path beyond the red pole/junction automatically.

For a path diverging (i.e. splitting into two paths) at a red pole, you need to link the routes for it to work correctly.

[HookitandBookit]

Whatever i do with signals here, none of them will let my train trought this junction. Any ideas?