I am having issues with routes that use Yelland's semaphore signals. The arms are misplaced for signals with a lot of arms. Does anyone know the cause? Examples from Bacup Branch and JetGriff's Bromsgrove Manchester Sheffield:
I too had this on JetGriffs BromsManSheff a couple of years back, I never did get it resolved, not really tried or played it since tbh.
I have a feeling somewhen someone did alter the original files and we all have the tampered with Yelland asset folder, can't imagine the signals looked like that when the route was built. I've downloaded Bacup and got a different common signal script than what I already had in my Yelland folder. Basically you would need to edit the signal arm child object matrices in the signal blueprints.... trial and error.
Somebody also reported similar issues with Yelland signals on my route......he resolved it by deleting the Yelland folder and replaced it with an older version from a few months ago. Andy
Do you have any more details? It would be good to be able to track down the specific folder in question.
I seem to remember I had the same issue with the Yelland signals on the "Steaming over Shap "route. I think I just reinstalled the Yelland signal kit that was on UKTS to fix the issue. Will have a look and see if I can find anything .
I have found 3 packs, UKTS_27751_BR-LMS_Signal_Kit_V3-0.zip, UKTS_37266_BR-LMS_Signal_Kit_V3.0_Supplement_01, UKTS_37396_BRS-LMS_Signal_Kit_V3.0_-_Supplement_02 To be honest I cant remember which one I reinstalled, probably all three ! It seemed to work though. I have the Bacup branch and it was ok for me, since then I have rebuilt my PC and started with a clean install of TSC and have only reinstalled a couple of 3rd party routes, Bacup wasn't one of them. I don't know why as I only live a few miles from Bacup. Will have a go and reinstall tomorrow see if I have the same issues as you have. Keith
For anybody who might be having issues with the Yelland Signals on my route ( South Lancs & North Cheshire - BR Blue ) you should be able to re-download from one of the host sites......the Yelland signals are bundled into the asset pack so you can grab them from there. These were specific for Slancs though, Nick did work with the creator to have some custom buillt for Slancs which we use in addition to some of the other Yelland signals. Andy
Yep, copying over the Assets/Yelland/Addon/RailNetwork/Signals/UK Semaphore/BRS_LAT_Arms, BRS_LAT_Posts, BRS_TU_Arms, and BRS_TU_Posts folders from those original UKTS uploads into my TS install fixed the issue, the signal arms are now all in their proper places. Guess it's another reason not to use big asset .rwp bundles...
Great find. From now on, when installing any UKTS asset pack, I will click "Yes" when it asks me to overwrite because I got some of the assets already, mostly from big route rwp's. Always bad when somebody tampers with other people's assets (though be it in good intention) A lot of the signal scripts in my Yelland folder have compiled (.out) signal scripts which are not present in the UKTS files, best to delete them (or move them to a backup folder), just to make sure as they will override any .lua if present with the same name. (And are there more to obfuscate things than increasing performance, as the script interpreting is not anything considered to be hard work for the CPU). I've installed all three packs using eldomtom2 's archive org link and clicked "Yes" to overwrite, issue fixed. Bac(k)up signals working Thanks again, KeithG !
I have looked at my Yelland folder and there are 13 .out files, all have a corresponding .lua file, although the file size is different. for example. "New Common Signal Script.lua" at 22kb and "New Common Signal Script.out at 9kb Are you saying I am best to move these files "out of the way" to keep everything running ok. Keith
Hello Keith. The point is, after the signal arms issue, it's clear someone messed with Yelland's assets and spread these files. In the three original packs, there's no .out files. They might work, but this is what I don't know and have removed them if the corresponding .lua is present. These compiled scripts might be based on changed .luas. So if you have signalscriptA.lua signalscriptA.out in your folder and overwrite the lua (because you found the original pack), TSC will still use the .out file as these have higher priority. Might be no issue at all keeping these, but I want to have the original files by the author if available to avoid the issues we've seen. And whether a signal script is in readable lua format or in binary compiled .out format makes no difference in the game. People compile their scripts to prevent others from stealing their code.
Got it now. Thanks for clarifying the issue and explaining the priority between the .lua and .out files and the reason for file size difference. Keith
