[Montana DLC] Glasgow, railway crossing is not working [193060]

Post Reply
30maes
Posts: 183
Joined: 20 Jun 2022 08:05
Location: Shanghai, China
Contact:

[Montana DLC] Glasgow, railway crossing is not working [193060]

#1 Post by 30maes » 02 Feb 2023 06:16

The railway crossing is not working in Glasgow, Montana. You can see there is a train but the road is not blocked.

Game.log:
game.log.txt
(131.51 KiB) Downloaded 10 times
Map co-ordinate: railway crossing is not working ;[02/02/2023 13:57:05] (sec-0011-0014);-40493.4;34.9524;-54641.9;-2.91946;-0.030381
Screenshot:
20230202135704_1.jpg
Version: 1.46.2.13s
PC: Win10 x64
Reproducibility: Always
ProMods Senior Beta-tester since January, 2023.
ProMods Moderator since July, 2023
User avatar
KrysEmlyn
Posts: 477
Joined: 17 Mar 2017 12:32
Contact:

Re: [Montana DLC] Glasgow, railway crossing is not working [193060]

#2 Post by KrysEmlyn » 02 Feb 2023 22:56

This is due to how the semaphore profile "crossing" is configured.
Here is what SCS Software has defined for this semaphore profile:

Code: Select all

tr_semaphore_profile : tr_sem_prof.crossing
{

	name: "road crossing - country"

	# Distances in [m]:
	#
	# crossing <-> object rear (green)
	# object front <-> crossing (orange-to-red)
	# object front <-> crossing (red)
	# crossing <-> object rear (orange-to-green)
	#
	interval[]: (50.0, 550.0, 350.0, 20.0)

	# Minimum delay after orange-to-green distance before barriers go up
	cycle[]: 4.0

	type[]: barrier_distance
	type[]: model_only

	id_map: 13
	id_map[0]: 0
	id_map[1]: 0
	id_map[2]: 0
	id_map[3]: 0
	id_map[4]: 0
	id_map[5]: 0
	id_map[6]: 0
	id_map[7]: 0
	id_map[8]: 0
	id_map[9]: 0
	id_map[10]: 0
	id_map[11]: 0
	id_map[12]: 0
	id_map[13]: 0

	model: 13
	model[0]: ""

	# 1-road x 1-rail
	model[1]: "crossing_r"
	model[2]: "crossing_l"

	# 1-road x 2-rail
	model[3]: "crossing2_r"
	model[4]: "crossing2_l"

	# 1-road x 2-rail
	model[5]: "cr1_r_2ln"
	model[6]: "cr1_l_2ln"

	# 2-road x 2-rail
	model[7]: "cr2_r_2ln"
	model[8]: "cr2_l_2ln"

	model[9]: ""
	model[10]: ""
	model[11]: "cr1_r_2ln"
	model[12]: "cr2_r_2ln"

	model[13]: "cr2_l_2ln"
	
	model[14]: ""
	model[15]: ""
	model[16]: ""
	model[17]: ""
	model[18]: ""
	model[19]: ""
	model[20]: ""
	model[21]: ""
	model[22]: ""
	
	model[23]: "crossing4_r"
	model[24]: "crossing4_l"
}
This is what it should be:

Code: Select all

tr_semaphore_profile : tr_sem_prof.crossing
{

	name: "road crossing - country"

	# Distances in [m]:
	#
	# crossing <-> object rear (green)
	# object front <-> crossing (orange-to-red)
	# object front <-> crossing (red)
	# crossing <-> object rear (orange-to-green)
	#
	interval[]: (50.0, 550.0, 350.0, 20.0)

	# Minimum delay after orange-to-green distance before barriers go up
	cycle[]: 4.0

	type[]: barrier_distance
	type[]: model_only

	id_map: 25
	id_map[0]: 0
	id_map[1]: 0
	id_map[2]: 0
	id_map[3]: 0
	id_map[4]: 0
	id_map[5]: 0
	id_map[6]: 0
	id_map[7]: 0
	id_map[8]: 0
	id_map[9]: 0
	id_map[10]: 0
	id_map[11]: 0
	id_map[12]: 0
	id_map[13]: 0
	id_map[14]: 0
	id_map[15]: 0
	id_map[16]: 0
	id_map[17]: 0
	id_map[18]: 0
	id_map[19]: 0
	id_map[20]: 0
	id_map[21]: 0
	id_map[22]: 0
	id_map[23]: 0
	id_map[24]: 0

	model: 25
	model[0]: ""

	# 1-road x 1-rail
	model[1]: "crossing_r"
	model[2]: "crossing_l"

	# 1-road x 2-rail
	model[3]: "crossing2_r"
	model[4]: "crossing2_l"

	# 1-road x 2-rail
	model[5]: "cr1_r_2ln"
	model[6]: "cr1_l_2ln"

	# 2-road x 2-rail
	model[7]: "cr2_r_2ln"
	model[8]: "cr2_l_2ln"

	model[9]: ""
	model[10]: ""
	model[11]: "cr1_r_2ln"
	model[12]: "cr2_r_2ln"
	
	model[13]: "cr2_l_2ln"
	
	model[14]: ""
	model[15]: ""
	model[16]: ""
	model[17]: ""
	model[18]: ""
	model[19]: ""
	model[20]: ""
	model[21]: ""
	model[22]: ""
	
	model[23]: "crossing4_r"
	model[24]: "crossing4_l"  	
}
Note the differences in the "id_map" section. SCS Software doesn't have enough entries defined to accommodate the 4-track crossing gate models in their version of the semaphore profile.
Post Reply

Return to “Bugs 1.46”

Who is online

Users browsing this forum: No registered users and 2 guests