|
|
Post by exdistrictdriver on Aug 31, 2020 1:26:45 GMT
Greetings all,
I know there was a problem a while ago where the mainline signals weren't showing for some reason, but the post says that has been solved... Any ideas why I still can't see the mainline signals?
I know they're from the London to Brighton route, so I have tried uninstalling and reinstalling that add-on but still no luck.
The other problem I have is really weird! It only seems to happen on the EC scenarios where every single signal I pass is at danger! The fog / repeaters show green, but the signal is showing a red aspect! Makes it really difficult to enjoy driving my old line! Pressing Tab always says permission granted but there must be something I've done wrong for both of the above!
I have all of the requirements and everything was installed as admin.
If anyone could suggest anything, I'd be very grateful!
Thanks,
Alan (Former District Line Driver, Acton Town)
|
|
|
|
Post by Jimi on Aug 31, 2020 1:52:06 GMT
Hi Alan! I strongly suspect we remember you from the DD forum. Solidbond is occasionally around here too :-)
We haven't seen this bug with the LUL signals before and as you note the missing mainline sigs issue was solved. There is likely a very simple solution and we'll work with you to figure it.
That a signal is red usually means the signal in rear is not sending it a message saying "train coming" which triggers the receiving signal to re-evaluate its state and either stay red or clear. You should normally be seeing signals clearing ahead of you in sequence. If that isn't happening than the first suspect is the pseudo trainstop gadget (Looks like a TPSS magnet in the 4 foot alongside the signal) which for unknown reason is blocking the messages. That *all* signals are misbehaving suggests something fundamental is in error. Are auto signals at red or just the semis? As you know the autos ought to default to green so that may be a clue. If it's only the EC scenarios causing an issue, then that suggests a version mis-match somehow. You've likely checked these, but I'll ask anyway...
Make sure you have the latest build or rolling update of the VDL. The EC scenarios are based off our V2.2 build.
Make sure you have the JT Met line. That you're missing the NR signals suggests there's an issue with the RSC LED signals, which Lon-Bri uses. Please check in <TS>/Assets/RSC and make sure there's a UKLEDsignals01 folder in there with some content. As you say, someone previously had this issue and we thought it had been solved. I'd bet this is similar.
This may take a few back/forth discussions, but we will figure it out and get you running correctly.
Best, Jimi
|
|
|
|
Post by exdistrictdriver on Aug 31, 2020 20:37:09 GMT
Hi Jimi, Indeed I was part of the DD forum! I have made a very quick, lo-res, no sound video so you can see the issue with the red signals. I have checked everything you suggest and the required routes and folders (like the UKLEDsignals01 folder) are all present and have contents! Sorry, it's typical of me to be the awkward one!! Any problems seeing the video, let me know and I'll put it on Youtube or something. www.dropbox.com/s/rdf03yk4uhx68ez/DistrictDriver_VDL1.mp4?dl=0 |
|
|
|
Post by Jimi on Aug 31, 2020 22:14:52 GMT
Thanks Alan! I got a look at your video and I'm still puzzled. Never seen this behavior, except when running a scenario from the editor instead of the main menu. Running from the Editor doesn't do a full Initialize, especially the signals.
I'll run that scenario here and verify a few things. I don't think the 2nd shunt out of the depot road should be on. There is one scenario where it is, for a good reason - main is occupied with an approaching EB, but I don't think it's this one.
As to the rest, again not seen that happen. It feels like something fundamental in the collection of JT stuff is wrong.
One further idea to collect info. If you approach a red,please check the "9" view (map) and see if there is traffic anywhere near you that might cause the signal to be red/on (e.g. exiting the depot). That you're seeing green repeaters and then red signals is a mystery, but we will figure it. It has to be a signals "asset" issue on your system, else everyone would see the same error - and with due humility we're not aware of any errors right now that we haven't fixed and documented on here.
Are you still missing the NR signals also?
We are discussing this among the team and are testing ideas...
|
|
|
|
Post by Jimi on Sept 1, 2020 0:06:29 GMT
I ran the same scenario and compared details to your video. We both leave at or about 9:33 when cleared to the exit by the East shunter. I see both shunts clear. There's nothing coming on the slow Ealing, or the Fast Northfields roads, to cause the shunt to be on, and in both our cases points are set from the Depot road to the EB main. In my case WL90 on the gantry is green/yellow, as the ACT4 home is currently red as the train ahead of me is just leaving ACT4. I keep to about 20 approaching the slow road and the home (WL109) clears to green/green and thus starter (WL106) is green. It is possible to get a brief red starter as the train ahead leaves the section, but then you'd see a green/yellow home, which I do initially on approach. So by the time I berth I'm maybe 2 blocks behind the train ahead (as we intended as part of the scenario design). That's what you should be seeing (which I'm sure you know from significant experience :-) so I'm left believing there's a glitch or conflict in your JT signals (both the LUL color lights and the disc shunts are from the JT pack. All that stuff lives in the Assets/Just Trains/LULibrary folder tree, and should be installed as part of either the Chitern L-A add-on (IIRC, if not someone will correct me) or the Met package. We have the JT Met as a pre-requisite as we're leveraging a lot of their LUL assets (and even more in VDL Phase III upcoming). So (more info gather)... What Just Trains routes or other assets do you have installed? (I'm suspecting a conflict somewhere, or something installed after something else doing an overwrite). What other routes (RSC, Kuju, etc.) are installed? Any 3rd party assets? And (final check) please make sure you have VDL v2.2 installed. When you did so, did you use the full v2.2 installer, or use a previous version (2.0, 2.1) and then the v2.2 cumulative updater? Sorry for all the questions, but we're turning over rocks until we find the issue :-) I'm also going to go back in the bugs thread and re-read the NR signals issue that came up, and recall how it was resolved.
EDIT: And another thought - please make sure TS2020 is up to date. v68.2c is current. I only ask as a while ago there was a glitch that caused the UKLED signals to go missing, which was fixed in a subsequent update :-)
MORE EDIT: Do you have the S7+1 or the S8 or both? The route uses the S7+1 trigger points under the track alongside the S:S boards to trigger the train monitors. If you don't have the S7+1 this may not be present (apparently JT produced an S8 version and an S7+1 version of the gadget and boards); and the lengthy bug thread about a rogue shunt disc failing because of a missing trigger asset may be relevant. Or not at all. But worth asking. This is so weird. For the video we see the signals in place so you DO have the assets. Which leaves us thinking the signal-to-signal message system is messed up as was the case with the Shunt disc bug. Which turned out to be an S-stock issue.
|
|
|
|
Post by exdistrictdriver on Sept 1, 2020 17:03:42 GMT
Hi Jimi,
Thanks for the ongoing support! Told you I was awkward!
I can confirm that the signals clear as they should if I run the route in QD. Only the scenario's cause the red signal issue. The NR signals are indeed still missing, which is a mystery! I opened the route in the editor and as an example I looked at W375 (the Wimbledon home signal). This shows as a milk bottle, however on looking up the referenced asset (RailNetwork~Signals~Pro Signals~Pro Signal Posts~G Pro L4A TH6.xml) I do indeed have this within my UKLEDSignals01 folder.
I am going to try a complete re-install of my train simulator as I have a lot of stuff installed on there which I very rarely use. I'll get back to you tomorrow (or once the reinstall is complete - I have a ton of AP/JT stuff to reinstall too!) and let you know how I get on as the fault is most likely at this end!
|
|
|
|
Post by Xavier on Sept 1, 2020 17:49:57 GMT
There was a problem with London to Brighton recently whereby the Steam DRM failed and everyone's signals disappeared. You might fix it if you go to the installed DLC list for TS2020 in the Steam client, untick it and retick it, and allow it to redownload.
|
|
|
|
Post by exdistrictdriver on Sept 2, 2020 1:43:46 GMT
OK guys, just so you know, after a complete fresh install (I'd forgotten the amount of add-on's I had) I can run all of the VDL scenario's perfectly well - all signals clear as they should and I have signals on the NR areas!
You can relax again! Thanks!
|
|
|
|
Post by Jimi on Sept 2, 2020 17:50:29 GMT
Great to hear Alan! We will of course be very interested in your critique, or to hear of any tweaks or fixes you feel we should do.
Phase III (Gloucester Rd to Aldgate East) is in development, so there will be even more scope for scenarios. Plus you might get held at OB31 waiting for a Circle out of Aldgate to go ahead of you. I believe that happens once in a while :-)
|
|
