Page 1 of 1
| Possible bugs with simulation and 2011-10-23 TT 02/11/2023 at 19:30 #153862 | |
Coco-Banana-Man
17 posts |
Good evening, I've just finished a game with 2011-10-23 timetable and I might have found 2 possible bugs with the simulation and 2 bugs in the TT. I'd have liked to report it on the relevant threads here, but unfortunately it seems they are locked due to age. Simulation: 1. When setting a route from signal IJ24 to 102.24, from 102.24 to NH102.26 (both between Islington Jn and Hamilton) or from NH102.24 to NH102.26 (between Woodville Jn and Hamilton) and point P475B is at the wrong position, it immediately comes to the right position instead of taking a few seconds to move. It works correctly (taking a few seconds) when setting the point manually or when setting a route from N101.93 to NH102.24. 2. I don't know if it's really a bug or intended to work like this, but I had a TCF at Broadmeadow on section T260BT right behind shunt signal B 258. I tried setting a shunt route from signal B 258 to B 246, so I didn't have to tell the driver to pass at danger, which first worked and the signal showed shunt aspect, but when the train occupied section T260AT right before the signal B 258, it immediately reverted to danger and the train received an ACOA. I later had the same happening at Sulphide Junction too. (section T144AT behind S 144). The two saves are made after setting the shunt route for a second time. If you start them paused, you can see the signals showing the shunt aspect, which immediately reverts to danger after unpausing. Timetable (2011-10-23): 1. V454 should depart from Newcastle No. 1 Electric Siding to platform 3 at 15:18 while V787 is still sitting at P3 till 15:20. Setting a route from signal 13/19(B)/23 to 21/28 unfortunately doesn't help because 13/19(B)/23 stays at danger until 21/28 clears. 2. NN78 is timetabled to depart from Broadmeadow at 19:12, but its description says 19:21. As its next timetable location, Broadmeadow Up Relief, is timetabled to be passed at 19:26, I think 19:21 should be correct.  Post has attachments. Log in to view them. Log in to reply |
| Possible bugs with simulation and 2011-10-23 TT 04/12/2023 at 14:25 #154594 | |
|
Coco-Banana-Man
17 posts |
Hi there @flabberdecks: I just wanted to ask if you've seen this thread. Log in to reply |
| Possible bugs with simulation and 2011-10-23 TT 04/12/2023 at 15:51 #154595 | |
flabberdacks
579 posts |
Hello, I apologise, I did miss this thread. Thankyou for your reports. I'll look into it as soon as I'm able. I think V454 is an actual timetable error which we decided to leave in, but I'll make sure. Hope you've been otherwise enjoying the sim! Log in to reply The following user said thank you: Coco-Banana-Man |
| Possible bugs with simulation and 2011-10-23 TT 07/12/2023 at 23:57 #154654 | |
|
flabberdacks
579 posts |
Righto, some answers 1) Points 475 detecting instantly in some circumstances - Mantis 39929 - 'Swing time' value raised in the next sim version, should fix it 2) Signals going back to stop - this is a much tougher fix. Core code ticket already exists under Mantis 38857 after the same problem was discovered on a currently in-development sim. However this most likely affects most signals on the Australian sims. At this stage I can suggest the following: regardless of the circumstances, never trust a shunt signal to stay at proceed if both track circuits either side of it will become occupied at the same time. Plan to authorise them past it instead. 3) V454, unlikely to change if the error came from the actual timetable document, Mantis 39930 anyway to be sure 4) NN78, almost definitely a typo, Mantis 39931 Log in to reply The following users said thank you: Hap, Coco-Banana-Man |