Author Topic: pakset mismatch with crossings  (Read 511 times)

0 Members and 1 Guest are viewing this topic.

Offline Vladki

pakset mismatch with crossings
« on: April 13, 2017, 11:16:54 PM »
I have compiled fresh pak128.britain-ex and put it on the server. But when I try to connect to a server game, it says that the paksets do not match. I have cleaned , rsynced, checked  many times - everything is absolutely identical.
Lengthy in-game compare of paksets said that the problem is with objects:
Code: [Select]
Name=CrossingAFB
Name=CrossingT
Name=CrossingNarrowAHB
all of them have defined
Code: [Select]
sound=level-crossing.wavbut that file does not exist - there is a misnamed "evel-crossing.wav"
But even after renaming the file, cleaning and rsyncing again, the network connection still says that these three objects do not match

Offline jamespetts

  • Simitrans-Extended project coordinator
  • Moderator
  • *
  • Posts: 16126
  • Total likes: 444
  • Helpful: 177
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: pakset mismatch with crossings
« Reply #1 on: April 14, 2017, 12:40:15 AM »
This is very odd - I am currently staying with my parents and away from my development computer, so cannot do any complex debugging. Can you check to see which commit introduced this error? That would help me greatly. Thank you.
Download Simutrans-Extended.

Want to help with development? See here for things to do for coding, and here for information on how to make graphics/objects.

Follow Simutrans-Extended on Facebook.

Offline Vladki

Re: pakset mismatch with crossings
« Reply #2 on: April 14, 2017, 05:15:42 AM »
I am going away too, but I suspect that adding sound to crossing might have done tge damage. No other crossings have sound.




Offline Vladki

Re: pakset mismatch with crossings
« Reply #3 on: April 23, 2017, 11:57:09 PM »
I still have problem with pakset mismatch. Could someone try connecting with the pak from http://server.exp.simutrans.com to confirm?

So, I have commented the sound= lines in ways/new-crossing.dat and  ways/narrow-crossing.dat and now the pakset matches. There are no other corssings with sound, so this must be the root of the bug.
« Last Edit: April 24, 2017, 09:51:39 PM by Vladki »

Offline Vladki

Re: pakset mismatch with crossings
« Reply #4 on: April 30, 2017, 10:30:45 AM »
Fixed