System.ArgumentException at Orts.MultiPlayer.MSGSignalStatus..ctor (X4249, Campania2018)

[Davide Conte]

As soon as I open the scenario in MP it suddenly crashas.

[Carlo Santucci (carlosanit1)]

Providing the full logfile is always better. This crash seems be caused by the particular route tdb file, and concerns signals. Can you tell me in which route this occurs, and if possible can you attach the full logfile?

[Davide Conte (davide3262)]

sorry, I express myself better: when I use the scenario in question in Single Player it works correctly, when in MP crasha giving me the error that I sent in the picture .. I would like to understand what is due. Thanks for the support.

[Carlo Santucci (carlosanit1)]

If I have time I'll download the route and check why it fails in MP.

[Carlo Santucci (carlosanit1)]

Where can I download that route?

[Davide Conte (davide3262)]

http://www.mediafire.com/file/yzewa3dhgsbv1rd/Campania_2018.rar/file this
is the link for the download..Thank you for the work you are doing!!

Il giorno mar 16 ott 2018 alle ore 18:41 Carlo Santucci <
<email address hidden>> ha scritto:

> Where can I download that route?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796408
>
> Title:
> System.ArgumentException at Orts.MultiPlayer.MSGSignalStatus..ctor
> (X4249, Campania2018)
>
> Status in Open Rails:
> New
>
> Bug description:
> As soon as I open the scenario in MP it suddenly crashas.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/or/+bug/1796408/+subscriptions
>

[Carlo Santucci (carlosanit1)]

I'm checking the route.
First thing I noticed (which has nothing to do with the crash, which I also have) is that the logfile has many warning lines of type:
Warning: Cannot parse the constant number nan in J:\Program Files\Train Simulator\ROUTES\Campania2018_352gts\Campania2018.rdb:line 18500
In fact if you check line 18500 of the .rdb file it is as follows
   UiD ( -5633 14367 12031 3 -5633 14367 nan nan nan 0 1.5402702 0 )
This is clearly a faulty line. The route author should check such faulty lines and correct them.

[Carlo Santucci (carlosanit1)]

I've found the cause of the error. I'm sorry, but there is a mess in the signal data of the route, which causes the problem. In file w-005626+014367.w there is this block
 Signal (
  UiD ( 12919 )
  FileName ( FSSignal_1C_2VQ.s )
  Position ( -841.867 0.994007 143.205 )
  QDirection ( 0 0.505806 0 0.862647 )
  VDbId ( 4294967295 )
  SignalSubObj ( 00004013 )
  SignalUnits ( 2
   SignalUnit ( 0
    TrItemId ( 0 938 )
   )
   SignalUnit ( 1
    TrItemId ( 0 939 )
   )
  )
 )

and in file w-005627+014367.w there is this block
 Signal (
  UiD ( 11451 )
  FileName ( FSSignal_1C_2V.s )
  Position ( -84.3275 1 911.661 )
  QDirection ( 0 -0.891052 0 0.453902 )
  VDbId ( 4294967295 )
  StaticDetailLevel ( 0 )
  SignalSubObj ( 0000040f )
  SignalUnits ( 2
   SignalUnit ( 0
    TrItemId ( 0 938 )
   )
   SignalUnit ( 1
    TrItemId ( 0 939 )
   )
  )
 )

As you can see, both blocks refer to the same TrItemId's, that is 938 and 939, which is wrong.
By the way in the logfile of OR there are warnings about a good number of other incoherences within the signal data. So, such data should be corrected by the route author.