jmm
Station Staff
Posts: 21
|
Post by jmm on Sept 12, 2019 18:46:40 GMT
Hi! Good evening!
Just another issue I've discovered: the roof between West Brompton and Earl's Court is too low for the S7.
I don't know if it has been posted before. If so, sorry!
jmm
|
|
|
Post by Jimi on Sept 12, 2019 19:19:23 GMT
Hi Jorge, We were aware of it to be honest. Fixing that means a bunch of terrain/track/scenery twiddles that has potential to break the track and signals if the slightest thing goes wrong during editing. So we were reluctant to address it so close to release. We will put this on the wish list, but likely won't address it right now as it's high risk - and there's other stuff we're working on.
Our experience says, if you want to create a tracks.bin corruption of biblical proportions, try gradient changes. But we will take a look at it when able.
Thanks!
|
|
jmm
Station Staff
Posts: 21
|
Post by jmm on Sept 12, 2019 19:44:42 GMT
Ok, no problem, just in case you had not noticed it (although I thought that was unlikely Greetings!
|
|
|
Post by Jimi on Sept 12, 2019 23:12:07 GMT
Another request guys, although we have asked this before - refer back to the original post.
We try and solve issues as fast as we can, but without specific information it is almost impossible. And if we have to go through multiple Q/A posts to get it, it takes forever. Case in point (not to pick on anyone, but...) on the FP page. Someone has reported "...the S8 getting tripped by a shunt signal". No details about scenario (if relevant), location, direction of travel, signal number, etc.
We asked for more detail. it's apparently "...a Shunt going from ACT towards ECT approaching one of the HSK platforms".
Unfortunately, there aren't any shunt signals controlling approach to HSK - it's done by signal ED23 with an RI (Route Guide P32), and we still don't know the signal number so we still can't help. The only shunt signals any where near there are going the other direction controlling access to Triangle, or exit from the Yard at ECT. I'm sure we'll figure it al in the end...
We will bend over backwards to help you, or solve a bug, but please give us enough info to go on - and preferably all in the first message. :-)
Scenario (if relevant), location and direction, what were you doing? What happened? Signal number (if relevant), etc.
NOTE: Almost all signals have a number plate with a unique (real life) signal number. On some shunt signals, especially the old disc type, the plate may not be visible. In that case look at the "9" view to see the route map. All signals are visible with their number, so grab it from there.
Thanks!
|
|
|
Post by smproductions on Sept 17, 2019 16:06:01 GMT
In regard to signals, I seem to be having an issue with signals that have an associated shunt disc - the game treats passing the signal as a SPAD regardless of what aspect is shown. In Career scenarios it's an immediate Game Over, in Timetable or Standard it does not cause a Game Over but it is shown in the debrief upon exiting the scenario along with any other offences like lateness, speeding etc. From what I have experienced the following signals seem to have this problem:
EALING COMMON
Platform 2 WM5 eastbound
ACTON TOWN
WL16 on the eastern approach to platform 1 westbound local
WL32 platform 2 westbound fast WL87 platform 3 eastbound fast
WL106 platform 4 eastbound local
In a test scenario that I have attached to this post I am unable to pass signal WM5 at Ealing Common even though the signal and its co-acting signal are both displaying a proceed aspect and the points are correctly set for the eastbound line.
The route is as follows:
Leave Ealing Common as soon as the signal is clear (no need to open the doors etc), then
WAYPOINT ECM EB Slow Road
PICK UP PASSENGERS Acton Town Platform 4 DESTINATION Acton Town Platform 4
I have tried using CTRL+TAB but the dispatcher refuses the request, I have also tried adding a TAB Trigger before the signal but this does not work either (I removed this again prior to uploading the scenario).
I am running the latest public version of VDL Phase II including the patch released today.
Attachments:Testing1.rwp (16.15 KB)
|
|
|
Post by Jimi on Sept 17, 2019 16:10:06 GMT
Thank you for a very detailed bug report.
That should not happen, as there's no tripcock there to trip the train. Same at ACT, and WKN/Lillie. We did that deliberately in locations where there's a shunt disc, as the player has to pass a mainline signal at danger in order to deviate via the Shunt.
EDIT:
If you turn off the TS option that says "passing signal at danger = game over" what happens? I just realized that that's how I have always had that option set, and I've never seen a SPAD at the locations you cite. In locations like these where the player MUST pass one signal or the other (main line or shunt) at danger, that may be the only option.
EDIT 2:
And I see Xavier echoed my thoughts as I was replying.
|
|
|
Post by Xavier on Sept 17, 2019 16:11:59 GMT
Go to your Gameplay settings in your Train Simulator options in-game and untick the box next to "Passing a signal at danger ends game."
|
|
|
Post by catsrcool on Sept 19, 2019 11:23:22 GMT
I swapped the D78 stock player train for a JT S8 in the Second Half Phase II Timetabled scenario. I get to the first station and load the passengers. I then move off with the signal showing a double green aspect and as soon as I pass the signal the Tripcock activates. Is this me doing something wrong? Or is there a problem using the S8 stock on the VDL?
|
|
|
Post by Jimi on Sept 19, 2019 11:48:49 GMT
That first station would be Acton Town EB, and there's a shunt signal there that will be red. It *is* possible that JT have coded something into the S8 that trips the train when passing *any* signal at red. We will check this out, but I'll first ask did you check the TS setting noted above regarding "SPAD = game over"? Others have noted the S8 trips out when passing ECM EB also (again, there's a shunt disc present there). So not a problem using the S8 on VDL per se, but maybe a problem passing UKpro shunt disc signals at red. We will investigate more...
|
|
|
Post by catsrcool on Sept 19, 2019 12:32:25 GMT
Thanks. Not got SPAD ends game ticked.
|
|
|
Post by Jimi on Sept 20, 2019 0:16:58 GMT
We have confirmed that the S7/S8 does not get tripped by JT color light shunt signals at red, but does get tripped by JT shunt discs like those at ECM EB, ACT EB, WKN EB, etc. (JTLU_Sem_1T_Disc). We'd prefer to leave the shunt discs in place, as they represent the real in situ signals at those locations, rather than swap them for the color light versions. We have emailed the folks at Just Trains with a request that they enhance the S8 code to not trip on these shunt signals. it is very likely that they have put none of that type on the Met, and so never encountered this in their testing. We will keep you informed as to progress.
|
|
|
Post by smproductions on Sept 21, 2019 16:22:20 GMT
I have unticked the 'passing signal at danger ends game' and sure enough that allows me to run and finish scenarios involving those areas.
I've noticed that the signals with associated shunt discs around the Ealing and Acton areas are fully seperate signals unlike others which have a position light attached to them (UKpro, JTMS etc) - if main colour light signals and shunt discs could be merged into one custom signal it would eliminate the issue of the sim reporting passing it as a SPAD every time as the shunt disc would simply be an extra route from the main signal, although I'm not sure if its possible to have two parts of the same signal moveable individually to reflect how they are positioned in real life.
|
|
|
Post by Jimi on Sept 26, 2019 18:11:04 GMT
The issue is not the signal, but the train. The signals talk to each other and are aware of trains in their vicinity, and (99%) show the correct aspect reflecting track circuit occupancy and route set/clear just fine.
The JT S8 responds correctly to the UKpro and JTLU signals - with one exception we are aware of. The JTLU_Sem_1T_Disc shunt disc. When, for example, running past the (green) starter at ECM EB the shunt must logically be ON as the points path is set to main line, not depot. The S8 (incorrectly) detects this as passing a signal at danger and trips. It does not do so with the color light shunt variant used in other locations, so JT must be aware of the general issue of passing by a shunt signal that is ON.
The fix belongs in the S8. Our LU trains don't trip as we special-case VDL locations where there is a co-located shunt and do not cause the (simulated) tripcock to trip the train. We have made JT aware of the issue and are hopeful they will address it.
|
|
|
Post by nigelbpool on Sept 27, 2019 20:37:10 GMT
hi folks got a problem with the c69 stock with the windscreen wipers working outside ok bur inside they are not moving. any ideas
|
|
|
Post by Eddie on Sept 27, 2019 22:18:08 GMT
If the train fails to initialise, none of the animations visible inside the cab work. Wipers is one of them. Easiest way to get it fixed is to hit ESC and restart the scenario. In the cab the clue all is well is if the red, orange and green mini lights on the desk console in front of you are lit. This is a known issue that we have made some progress in improving.
|
|
|
Post by catsrcool on Nov 14, 2019 14:20:59 GMT
Just Trains have now got the updated version of the S8 on their site. Unfortunately I have to report that they have not changed the scripting and it still trips the tripcock going past some shunt signals. On last nights Train Sim stream Tom said the size of the collision boxes have been reduced. I have not tried it as there does not seem to be any point.
|
|
|
Post by Jimi on Nov 14, 2019 17:35:47 GMT
Yup - we spotted that too. We will continue to approach JT with suggestions. At least they fixed the collision boxes, so we shouldn't get any more issues near Fulham Broadway and others. Likely worth the free update just for that.
Here's the release notes for S8 v1.03:
v1.03
- Collision boxes reduced in size to allow tight bends to be driven without collision.
- Poly reduction in models to help increase frame rates in Driver and Ai versions.
- SCAT icon visual quality improved.
- Pneumatic sound added to Tripcock reset function.
- Added Metropolitan Line destinations to TCMS station name display.
- Scenarios for Metropolitan line route included.
- Johnston font replaces previous font internally and externally.
- Two additional camera views in passenger view, now three in total.
- Fixed loss of train numbers after a save and resume.
- Reduced brightness and angle of headlights to be more authentic in tunnels.
|
|
|
Post by Larwood on Nov 20, 2019 16:21:04 GMT
Setting the destination on the 73 stock in scenario creation isn't working for me at all. No matter what number and letter I change it to (or even if I just leave the auto-generated one) it always shows Heathrow, and 255 for the train number.
|
|
|
Post by Xavier on Nov 20, 2019 17:21:41 GMT
Setting the destination on the 73 stock in scenario creation isn't working for me at all. No matter what number and letter I change it to (or even if I just leave the auto-generated one) it always shows Heathrow, and 255 for the train number. There isn't interchangeable destinations on the 73 stock. It wasn't discovered at the time why it was the case that only one texture was being used for the destinations but we decided to leave trying to figure it out until later so that it wouldn't hold up release.
|
|
|
Post by bigjacko on Jan 8, 2020 17:50:04 GMT
Hello again! I hope this is the right place to decant all this - I have a few minor bits of feedback, and a possible problem report (which will most likely turn out to be my fault, but I'll mention it in any case, because I could do with the pointers, if so!) So far, since getting VDL Phase II last week, I've started at the beginning, and only delved into the Standard scenario called "01. Training - D78 - Entering service and stabling at ECMDT". In case it matters, I have all specified requirements per your page at backdated weebly whatnots, with the exception of the S8 - I have the JT bundled S7+1. I am assuming neither is being used in this scenario though of course, it's possible you are using invisible components, and that may be the root cause of my problem. First, the problem... Some - but not all - of the shunt discs don't seem to rotate. Specifically, the disc at the exit of ECMDT on the ECM side, and the entry-to-depot disc on the platform at ECM. I've lost track of how many times I've tried this scenario and failed it - at the beginning it was a bit of a learning cliff, but I can at least get through it now, but I am having to 'cheat' somewhat (TAB to get an authorised SPAD on the way out of the depot, and on the way back in, my authed SPAD request was denied, but I went in all the same - I don't have the 'end game on SPAD' option set). I have tried all kinds of positioning on the depot exit - close to the disc, far away, stopping at the dwarf, waiting before starting, starting like a bat out of hell... all to no avail. I've got to the point where I can get all of the initial messages correctly - about waiting for traffic on the 'manline' (note spelling typo - you might want to tweak that minor error), about waiting for the 73TS and watching the disc. Nothing ever happens with the disc. The D78 that comes into ECM (ACTS23, I think) seems to be certain death, if it closes its doors and pulls forward - it'll always stop on the greens, never proceeds, and I am left waiting at the depot exit with a non-rotating disc, for ages (I've left it 10 mins plus, and no dice). That's where I found the only way out was to get dispatcher SPAD authorisation (after the 73TS has left, and as the D78 ACTS23 has just arrived, but before it shuts its doors). From there on, everything goes fine, until... Coming back into ECM, I do the non-service stop wait time, and get the message about waiting for the depot entry disc... but once again, it never spins. Here, a dispatcher SPAD request will be refused, but meh... I got in. Thereafter, everything fine and dandy. I must say even with these little glitches, I am loving the experience, really enjoying the feel of the stock, and think the scenery is amazingly good quality. Really impressed. But a less appreciative person might not be so forgiving, and I'd hate for them to give up on the first 'trainee' scenario, simply because they couldn't leave the depot - hence my posting it here. I hope I've done the right thing; the intention is constructive, not complaint, okay? I wondered (looking at the scenario in the editor for a moment) whether perhaps the depot exit scenario destination point was partly a cause. Its marker didn't seem to go around the 'slip' and it formed a tight angle, and overlaps with a route marker - perhaps that is causing confusion with the dispatcher system? Or maybe it's the presence of that D78 ACTS23 - I've noticed the timing of when the 73TS leaves and the D78 arrives is not split-second timed, so perhaps the D78 can arrive a tad too early and get into a 'race' condition where it holds the junction, even though the junction is already cleared against it? Not sure. But maybe worth a look. Finally, I did notice one tiny clipping error in the ECMDT 20 road, on the Acton side. One of the dwarf light signals clips into the car bodies as they make that corner. Very minor, but I was half-expecting to hear graunching metal and paint sounds, such was my immersion at that point! Hope this helps. By all means, quiz me for more detail if you need it. Very grateful for your work, and have nothing but praise, and a desire to make it perfect. Thanks very much indeed!
|
|
|
Post by Eddie on Jan 8, 2020 18:18:44 GMT
OK, there actually is nothing wrong with the scenario, we tested it to death. There are You Tube videos by people such as Alex The Mole of Molehill who ran this on a live stream, so in order to correct what appears to be something in your scenario database which is being cached by the game, I want you to do this :
Navigate to your Railworks folder, using Windows Explorer. It is under Drive: /Steam/Steamapps/Common/Railworks. Now open your Railworks folder and look for the Content folder. With me so far ?
OK open the Content folder and look for a file SDBCache.bin , select it, and delete it. Don't worry , TS will rebuild it next time you run the game and reset all parameters cleanly. Then try the scenario again and report back.
|
|
|
Post by Eddie on Jan 8, 2020 18:57:49 GMT
|
|
|
Post by bigjacko on Jan 8, 2020 23:53:00 GMT
OK, there actually is nothing wrong with the scenario, we tested it to death. There are You Tube videos by people such as Alex The Mole of Molehill who ran this on a live stream, so in order to correct what appears to be something in your scenario database which is being cached by the game, I want you to do this : Navigate to your Railworks folder, using Windows Explorer. It is under Drive: /Steam/Steamapps/Common/Railworks. Now open your Railworks folder and look for the Content folder. With me so far ? OK open the Content folder and look for a file SDBCache.bin , select it, and delete it. Don't worry , TS will rebuild it next time you run the game and reset all parameters cleanly. Then try the scenario again and report back. Eddie, thanks so much for taking the time to look into this, and to replay the scenario yourself. I do appreciate it. OK, I followed the steps above, and deleted SDBCache.bin (not the MD5) and re-ran the 64-bit TS2020. It spent a bit longer than usual rebuilding the cache, as expected. Sadly, same dice. I progressed through all the screens you've shown above, and got all the same (positive) indications, including the one about keeping an eye on the disc, watched the 73TS depart and the D78 arrive a few moments later - sadly all with the disc at caution. This was my stop-point at the depot-exit: Reading your other comments, I double-checked the files in my VDL Routes and Scenarios folder, just to make sure nothing had changed. I was very careful when in the editor, to make sure that I did not quit by returning to drive mode, and did not approve any changes. I exited the editor using Task Manager and killed the program. Just to prove, though, here's the timestamps on the relevant files: and the scenario folder itself: I'll keep trying, just in case. In case it matters, my Metropolitan and S7+1 JT files were downloaded and sized as follows: And my VDL files and supporting tweak files are these: Worst case, I'll uninstall the whole VDL/Met/S7+1 caboodle and start again, but I'll persist a bit more with the scenario just in case. Might even make a video if I can find somewhere private to host it temporarily. Thanks again for your help, Eddie.
|
|
|
Post by bigjacko on Jan 9, 2020 0:14:43 GMT
And in case this is important too:
|
|
|
Post by Eddie on Jan 9, 2020 0:29:44 GMT
OK, so two more things to try now. Right click on TS in the Steam library, select properties and then on the box that opens select the Tools tab. From the drop down list select File Integrity Check. This may take quite a while to run to 100%. When it finishes it will tell you if any files failed to validate. I'd bet money you have over a 1,000 files corrupted. TS will re-acquire the correct files. So now you should have a clean TS installation. Now reinstall the District Line 2.02 version, use the complete installer, and disable any anti-virus programs before doing this, Norton in particular WILL remove critical files. If you have Windows 10 up to date, you do not need any antivirus, Windows Defender is perfectly capable of protecting your PC from all known threats. Uninstall, and then reinstall all the JT stuff. I have a feeling crashing out of the Editor with Task Manager killed the scenario. Stay well out of the Editor in future.
Now once you have installed VDL Phase 2 ( over the top of your existing install ) delete the SDBCache.bin file again and then restart TS. Before you try again, now go into settings/tools and clear the cache. Ts will restart clean and try again. If that doesn't work, I'm outta ideas.................. good luck.
Saw your post above, the S7+1 won't affect this one , the signals from JT's Met line are very important though, so reinstall that at least.
|
|