Post by danny252 on Oct 24, 2018 7:59:55 GMT
In V5.5.3, some maps have started showing errors about Exit mismatches when opened, suggesting that a new map update exists when one does not. It appears these cases are due to errors in the FYM configuration files, which refer to map exits that do not exist.
Please report any such maps, so that we can investigate further and make fixes as required.
The configuration files have been updated to fix the issues reported at Mon Valley Works, PA and Birmingham Sloss Coke, AL.
(I'm currently at a complete loss to explain why the original FYM track display code didn't give errors in these cases in the past)
Please report any such maps, so that we can investigate further and make fixes as required.
The configuration files have been updated to fix the issues reported at Mon Valley Works, PA and Birmingham Sloss Coke, AL.
(I'm currently at a complete loss to explain why the original FYM track display code didn't give errors in these cases in the past)