Closed NicholasRB closed 10 months ago
the cause of this issue is the fact that i have only programmed the platform/ catchment area that leads to Cochran and Alarka. The intended route is ... <-> Hemingway <-> Alarka Jct <-> Cochran <-> Alarka <-> Almond <-> ... To be clear I WILL fix this but it may take a little bit
Thanks for getting back so fast. That makes perfect sense and is an easy workaround for now
yeah, as long as you stop at Cochran between Alarka Jct and Almond all should be golden. But you should be able to run a service that brings passengers going to all destinations from Alarka and Cochran to Alarka Jct so that the 'main line' service can bring them where they need to be. (assuming you can drop passengers at stations that are not their destination. Have not tried this yet). That being said the fix to this will likely be a feature update so it will likely take a bit as I've been programming non stop for like 3 weeks now XD also would like to make sure I have quashed all of the minor bugs first
This sounds like the issue I was having at Alarka, but I'm coming from Whittier <-> Ela <-> Bryson <-> Can't remember the station <-> Alarka. AI seems to not be able to handle a turn around at Alarka to head in reverse down the station list.
I personally have not gotten to Alarka just yet so if you could potentially get a video of the issue that would be great. Also I know I have been pushing out versions like a machine gun but if you could upgrade to the latest version to get that vid if you can, that would be fantastic
I picked up the beta 1.0.1.5 and it appears that Alarka functionality has improved dramatically!
Fantastic, I'll close this issue as solved with Beta 1.0.1.5
Alarka Junction seems to pose a problem for the pathing somehow in that the AI will attempt to find a place to stop at the station but continuously pass it. Then it will pull forward and try again and do this on repeat forever, never stopping in the right spot to load/unload.