DWBennett55
Member
(Note: All this work has been done in T:ANE Build 78667)
Ok, I guess I have no idea whatsoever how the AI Driver works. I’ve been having problems with an AI Driver not correctly driving to a trackmark when the path to that trackmark is clear. The AI Driver will invariably attempt to take a path obstructed by a consist or a different path not blocked by a consist but not a direct path to the trackmark whatsoever.
I then decided to experiment with a path or routing rule (setting the junctions to the correct path) to see if I could get the AI Driver to go directly to the trackmark. No matter which rule I used, there was the same result; the AI Driver took control of the final junction to the trackmark, which the rule had set to the correct path, and switched it to a blocked or other incorrect path.
With those failures, I decided to set up a series of test session. I had noticed that there may have been problems with the AI and consists on the adjacent tracks. I had no idea why this may be but decided to test it. I shortened up the drive lengths and put a special trackmark on the correct track near the critical junction so the whole process would be shortened somewhat to speed up the testing.
I first tested the process with no consists on any of the adjacent tracks. Here’s a screenshot with the critical junction pointed out by the black line. The AI Driver chose the correct path and drove to the trackmark.
Here’s a screenshot a few seconds later with the engines entering the correct track headed to the trackmark:
Next, I added a consist on an adjacent track to see the result. Note that I changed nothing in the sessions but the route changed with the addition of a consist on an adjacent track to where the AI Driver is programmed to travel. Also, I removed all the path or route rules for this specific set of tests so that the only controlling command was one simple “Navigate To” command for the train to the specific trackmark.
Here’s a screenshot of the critical junction switched to the correct position by the AI some distance away from the critical junction. (The switch is pointed out by the black line.) :
A few seconds later, the AI switched the junction to the right and off the correct path to the trackmark as shown by this screenshot:
This situation happened every time a consist was placed on an adjacent track. I tested with a consist one track to the right and a consist two tracks to the right (as shown above) of the correct path track with similar results. As stated above, I also tried using both the path and route rules to set the junction correctly, with consists on adjacent tracks, and every time the rule(s) moved the critical junction to the correct state but when the train got to the point in the above screenshot, the AI reset the junction to the incorrect state. Invariably. I also tried the path and route rules without consists on adjacent tracks with success so it doesn’t seem that those rules have much to do with what’s going on. With the AI correctly sending the train down the correct track with no "interferring" consists, something like bad track work, track laid in the "wrong" direction, etc. don't seem to be the problem(s).
Ok, what am I doing wrong? Is there some simple solution to this; like a simple command (or rule) to straighten things out? Note tha this isn't the only point on the route where I have this type of problem so, again, it isn't just this set of track work.
Yeah, yeah, I know I can just leave consists off the adjacent tracks. But that really isn’t very realistic and will limit any session to a very simple one load and spot. After all, what yard has no consists in it when the AI Driver wants to go to a specific track?
Anyway, thanks in advance. I do appreciate all the help you guys give me.
Ok, I guess I have no idea whatsoever how the AI Driver works. I’ve been having problems with an AI Driver not correctly driving to a trackmark when the path to that trackmark is clear. The AI Driver will invariably attempt to take a path obstructed by a consist or a different path not blocked by a consist but not a direct path to the trackmark whatsoever.
I then decided to experiment with a path or routing rule (setting the junctions to the correct path) to see if I could get the AI Driver to go directly to the trackmark. No matter which rule I used, there was the same result; the AI Driver took control of the final junction to the trackmark, which the rule had set to the correct path, and switched it to a blocked or other incorrect path.
With those failures, I decided to set up a series of test session. I had noticed that there may have been problems with the AI and consists on the adjacent tracks. I had no idea why this may be but decided to test it. I shortened up the drive lengths and put a special trackmark on the correct track near the critical junction so the whole process would be shortened somewhat to speed up the testing.
I first tested the process with no consists on any of the adjacent tracks. Here’s a screenshot with the critical junction pointed out by the black line. The AI Driver chose the correct path and drove to the trackmark.
Here’s a screenshot a few seconds later with the engines entering the correct track headed to the trackmark:
Next, I added a consist on an adjacent track to see the result. Note that I changed nothing in the sessions but the route changed with the addition of a consist on an adjacent track to where the AI Driver is programmed to travel. Also, I removed all the path or route rules for this specific set of tests so that the only controlling command was one simple “Navigate To” command for the train to the specific trackmark.
Here’s a screenshot of the critical junction switched to the correct position by the AI some distance away from the critical junction. (The switch is pointed out by the black line.) :
A few seconds later, the AI switched the junction to the right and off the correct path to the trackmark as shown by this screenshot:
This situation happened every time a consist was placed on an adjacent track. I tested with a consist one track to the right and a consist two tracks to the right (as shown above) of the correct path track with similar results. As stated above, I also tried using both the path and route rules to set the junction correctly, with consists on adjacent tracks, and every time the rule(s) moved the critical junction to the correct state but when the train got to the point in the above screenshot, the AI reset the junction to the incorrect state. Invariably. I also tried the path and route rules without consists on adjacent tracks with success so it doesn’t seem that those rules have much to do with what’s going on. With the AI correctly sending the train down the correct track with no "interferring" consists, something like bad track work, track laid in the "wrong" direction, etc. don't seem to be the problem(s).
Ok, what am I doing wrong? Is there some simple solution to this; like a simple command (or rule) to straighten things out? Note tha this isn't the only point on the route where I have this type of problem so, again, it isn't just this set of track work.
Yeah, yeah, I know I can just leave consists off the adjacent tracks. But that really isn’t very realistic and will limit any session to a very simple one load and spot. After all, what yard has no consists in it when the AI Driver wants to go to a specific track?
Anyway, thanks in advance. I do appreciate all the help you guys give me.
