Sure will. My Crewe route to be posted soon uses the method but in a nutshell:
SCS2006 controls an engine that runs along a track lined with triggers (8 meters apart seems optimal), proceeding from one trigger to the next according to the timetable. Each trigger activates a CPC:Emit train on trigger which in turn triggers an unportal to release its train (alternatively SCS2006 sets a signal to green releasing a train waiting on Wait till not red). The trains proceed under path control and autodrive.
Would have preferred to use a library call from SCS but can't get it working at the moment.
This works great and the initial scenario for Crewe involves a train every two minutes or so entering the route from one of 7 different sources.
Currently running with over 30 trains and adding more each day to test the limits of this method - if any.
This has the advantage of overcoming the limit inherent in SCS2006 of between 20-30 trains due to thread restrictions.
Also experimenting with some trains under SCS2006 control also, basically use the former method for through trains and SCS2006 for yard operations.
SCS2006 and path control co-exist quite happily in the scenario if care is taken to ensure that both systems don't try and use the same routes simultaeously - they can use the same track, junctions, signals etc. but at different times. I believe it should be possible - although I haven't tried it yet - to assemble a train using SCS2006 then drive it away using path control - just to see if it can be done.
This methodology has brought a control method to Trainz that I've always wanted as it has a lot of flexibility and control. Still exploring all the possibilities
http://forums.auran.com/trainz/showthread.php?t=11778&highlight=crewe
Segy
P.S. needs PC power to do all this
SCS2006 - TRS2006 SP1
Core duo 6600 8800GTX 3DMark06 10,000+