Generic question about AI trains

[Machinist]

AH! RS age... I started with scenarios with RW2 one year ago and then (couple months later) I continued with RW3. In Trainz, the portals emmit trainz (pun intendend) which is good once whilst not launched yet they do not impact performance (is just take care of don't emmit more then one at same time) and they don't disturb the traffic (don't block the path for other trains).

[OldProf]

Well, that didn't take as long as I thought it would! My demonstration scenario, Portal_Test_01, is on its way to the file library.

I decided to use the Castle Rock Railroad route and standard RW3 stock. The scenario includes a player train and two AI trains that spawn from a portal. The basic steps I took are as follows:

1) Placed an engine near a convenient portal, added a driver and a couple of commands, then double-clicked the portal to open its properties box. This includes two buttons: ADD and REMOVE. Clicked the ADD button, then clicked the AI engine, which immediately disappeared into the portal.

2) Set up a player engine and assigned it some tasks.

3) Tested the scenario, which worked as it should have.

4) Never satisfied with something simple, assigned some tasks to the AI train. To do so, used the REMOVE button to extract the train from the portal, placed it on a track, and edited it. Returned the train to the portal, as in step 1.

5) Tested the scenario: no problems.

6) Still not satisfied, added a second AI train, giving it a later starting time and some tasks. To place this train into the portal, I had to remove the other train, because it had to leave the portal first. Used the ADD button to assign the 2 trains to the portal (Service 3 first, Service 1 second -- the player train is Service 2).

7) Tested again: no problems.

In my opinion, after this initial test, RW3 handles AI trains spawned from portals better than RS did. That a train can be placed into a portal, removed, and placed again multiple times is quite impressive! I'm inspired to make additional tests.

Note: As stated above, this scenario runs on my RW3 installation without problems. If it does not run on your system, please don't scream at RSC or at me.

[artimrj]

Thanks Tom! That will make things different.

[Machinist]

Great Tom! As RSC stated on wiki that Portal doesn't spawn AI train, I never realised (how) to try!

@Bob, NERW is plenty of Portals, anywhere, so it will be really great for scenarios designers!

I changed the name of my post to make the it easier to find further.

Cheers,
Doc.

[harryadkins]

Excellent work Tom. Can't wait to try it out.

Harry

[Chacal]

I guess the wiki needs an update.

[Machinist]

I guess the wiki needs an update.

In fact, needs to be redone... a lot of missing information letting us blind when scripting.

[OldProf]

I guess the wiki needs an update.

In fact, needs to be redone... a lot of missing information letting us blind when scripting.

Indeed! Here, here! At the Support tab of RSC's website, this statement appears: "The Official RailWorks3 Train Simulator 2012 FAQ can be found as part of the Developer Wiki.", but as far as I can see, all of the FAQs relate to RW2. Moreover, the sections dedicated to scenarios do not even mention the Timetable Editor. RSC does provide a Timetable Editor Manual, but it hasn't been updated since it first appeared in 2010, along with RW2. Since then, AI deliveries and pick-ups have been added, as have those mysterious new "cinematic" scenario openings and the possibility of adding graphics to instructions, but RSC has not revealed the secrets behind these novelties. I very much respect RSC's production of new routes and rolling stock, but leaving those who enjoy making routes and writing scenarios groping in the darkness is really disappointing. On several occasions. members of various forums have attempted to put together a new wiki, but those efforts have usually produced more dissension and confusion than anything else. Besides, none of us really knows the facts behind RW's programming or the possibilities and limits that result from than programming. Thus, only RSC can actually create a worthwhile wiki. As we say in Italian, "magari!"

I'd appreciate feedback from anyone who tries my scenario, as well as suggestions about further experiments.