[Kapitaen13]

Quote

UID (217) is a simple exit-signal in the station Sattledt. Only one black cube shows up with "View" "TrackDBItems".

And the red signal pyramide? If it is not there, delete the entry about the black cube. Then reposition the signal and your error is fixed.

Greeting..

[Csantucci]

Woodfyr, on 23 June 2019 - 06:03 AM, said:

There may be problems with MG Rev. #26.

Program: OR NewYear MG Rev. # 26 with Reshade
Interface: Raildriver/keyboard
Route: Train Simulations - Ruel
Activity: Summer Maintenance
Start Time !0:15:00

Player train arriving Capreol from south, A1-201 arriving from east for crew change. Arrival: 10:17:00.
Player stops for red signal (30 yds). Player Arrival:10:17:

Accoding to HUD (Dispatcher Info) Train A1-201 (15 F) is due to depart at 10:20:04.
At the A1 departure time, the entire train begins to Rock & Roll, engines increase revs but do not
move. In addition the wheels of All cars disappear. HUD Dispatcher shows Speed for F15 as 'NaN'. ??

WEIRD !!!!

Further exploration of this phenomena has determined that this can occur on all activities on the Ruel
and Seligman routes rtunning MG Rev. #26.

All run fine on MG Rev. #19.

https://youtu.be/-5IbZI5iQV4

Yes, there is such problem in Rev. #26 and it has already been solved in Rev. #27.

[Woodfyr]

Csantucci, on 23 June 2019 - 07:21 AM, said:

Yes, there is such problem in Rev. #26 and it has already been solved in Rev. #27.

Upgraded to Rev 27. All is well. Hope I can keep up with you folks. :oldstry:

Thanks :sign_thanks: - This group is Amazing. :sign_rockon: :thumbup3:

[Csantucci]

Hannes44, on 23 June 2019 - 02:27 AM, said:

With MG 64 Rev.25 I get a load of these warnings in the OpenRailsLog: I can't figure out what the problem is to repair. Thank you for some information.




Warning: System.IO.FileLoadException: {TileX:-5589 TileZ:14762 X:707.799 Y:269.885 Z:-327.347} scenery object 217 failed to load ---> System.ArgumentException: An item with the same key has already been added.

Hi Hannes,
first of all I'd like to know if you get the same warning messages with the standard version of OR.
If yes, please attach here (or send to me) file sigcfg.dat and tell me the shape name of the signal generating the error, and attach also the .w file entry for scenery object with UiD 217 in file w-005589+014762.w .

[Hannes44]

Sorry, I obviously used the wrong thread, the same happens with the standard version of OR. sigcfg.dat ist attached. The signal shape is "mzb_ausfahrt_ns" the entry in the .w file is:

Signal (
UiD ( 217 )
FileName ( mzb_bhf_ausfahrt.s )
Position ( 707.799 269.885 -327.347 )
QDirection ( 0 -0.383065 0 0.923721 )
VDbId ( 4294967295 )
SignalSubObj ( 00000001 )
SignalUnits ( 1
SignalUnit ( 0
TrItemId ( 0 1355 )
)
)
)

Thanks for your help!

Attached File(s)

•  sigcfg.zip (3.13K)
  Number of downloads: 1
•  sigscr.zip (872bytes)
  Number of downloads: 0

[Csantucci]

The problem is in file sigcfg.dat within the block of SignalType mzb_ausfahrt_ns .
Starting from line 107 you have

	SignalDrawStates ( 2
			SignalDrawState ( 0
				"Red"
				DrawLights ( 1
					DrawLight ( 0 )
				)
				SemaphorePos ( 0 )
			)
				SignalDrawState ( 0
				"Green"
				DrawLights ( 1
					DrawLight ( 0 )
				)
				SemaphorePos ( 0 )
			)
		)

As you can see, both SignalDrawStates have as index 0. This is incorrect, and leads to the warning, because OR uses such index to point to the desired draw state. So such block must be corrected to

	SignalDrawStates ( 2
			SignalDrawState ( 0
				"Red"
				DrawLights ( 1
					DrawLight ( 0 )
				)
				SemaphorePos ( 0 )
			)
				SignalDrawState ( 1
				"Green"
				DrawLights ( 1
					DrawLight ( 0 )
				)
				SemaphorePos ( 0 )
			)
		)

that is, the second SignalDrawState must have index 1.

[Hannes44]

Thank you for your help and your extensive work to improve OR. Much appreciated!

[Brace_2011]

Hello. I have encountered a problem with recent ORMG versions. I have noticed it in versions 25 and 27, but only when trying to load the route MONON-2 v17. I have not been able to reproduce the fault with other routes (although I haven't tried them all), and the problem does not manifest itself with ORMG v22 (I only have these three versions on my machine). For information, I used 7-zip to unpack the *.zip files.

The load process stalls soon after trying to load, and the only way to get out of the 'loop' is to close the program via Task Manager. The log file is attached. If I leave the loading process to run for longer the only effect is to lengthen the log file with multiple iterations of the final block (starting Warning: Orts.Viewer3D.Processes.ThreadHangException: Thread 'Loader Process' has hung; the consistent stack trace is shown below: )

I don't use MONON very often, but this seems to be symptomatic of a problem in the ORMG code somewhere, so I hope it helps you to debug it.

Regards

Martin

[Csantucci]

I just tried starting the default activity of Monon - 2, and got no problems, see attached logfile
 OpenRailsLog.zip (3.49K)
Number of downloads: 7
At the moment I don't know what is happening here. It seems only that you get all those messages when OR tries to parse file sigscr.dat.

[Brace_2011]

Hi Carlo

Thanks for looking at this. I wasn't expecting this outcome. It seems that there are now 2 questions.

1 Something in the code must have changed between v22 and v25 for my system to hang up in the way it does (ie. under v25 and v27, but not v22).

2 The fact that your setup properly loads MONON-2 and mine doesn't seems to suggest a difference between our MONON-2 installations. Mine is set up as a miniroute, with no other routes in the installation. If I read the log file correctly the hangup seems to be caused by my sigscr.dat file. Mine is as supplied with the route with no alterations, although I have installed the Monon-2_OR_Update-SEP_2017. My sigscr.dat file is 101kb and dated 14/6/2011.

I don't believe that I can be the only person experiencing this issue. Can anyone else add anything that may shed light on the problem?

Martin

PS. Experimental version 68 (ie not MG) works properly, so it seems to be something in the MG version only. Hope this helps