Trainz/route

sessions Lot's of other pages Sessions are the heart and soul of interactive Driving taskings... there is much to discuss! so... Promissary Note... someday soon I'm going to get started on this page!, says Fra nkB combined from Driver and Glossary and Notations Scenarios and sessions Driver Scenarios were modular interactive scripted software elements which acted as a adjunct to Trainz Driver, and provided the first game experience offering task challenges, scoring, and switching operations. Crude ability to load and load trains off-camera enabled distribution of cars and then picking up the same during the same gaming session. session Sessions supplanted use of scenarios as the TrainzScript module was not directly integrated into the game, whereas the session editor was part of Surveyor. Driver Scenarios were modular interactive scripted software elements which acted as a adjunct to Trainz Driver, and provided the first game experience offering task challenges, scoring, and switching operations. Crude ability to load and load trains off-camera enabled distribution of cars and then picking up the same during the same gaming session. Sessions supplanted use of scenarios as the TrainzScript module was not directly integrated into the game, whereas the session editor was part of Surveyor. Support for Scenarios will not be continued after TS12's service packs.   Trainz Driver Sessions are scripted Driver activities that create an interactive game play episode with tasks, conditions, and standards set by the Session creator. Sessions were introduced in Trainz 2004 as a better, easier user friendly replacement for scenarios. Sessions are written using the Session editor API in Surveyor, so were integrated into the game with map features visible, and so easier to make than scenarios which used a separate TrainzScript editor module.   Scenarios main topic coverage: scenarios Scenarios were available from Trainz 1.3 (Trainz updated to SP3) into TS12Scenarios were available from Trainz 1.3 (Trainz updated to SP3) into TS12... but based on personal experience, but some older scenarios were sometimes defeated (unrunnable, though CM was happy to import them) by changes (usu. mandatory values checks or defines not present in Trainz, UTC nor TRS2004—so had incurable faults) in the script libraries of newer Trainz releases. Unlike their functional replacement, Sessions, writing a Trainz scenario relied upon the external Auran application TrainzScript, and relied upon a much higher needed level of programming ability and knowledge.   Session sessions Sessions session Driver session Sessions main topic coverage: sessions Sessions came about because the Trainz of the day had trouble keeping context when switched back and forth from the Scenario editor and Surveyor modules, where one had to track what was to happen step by step. The solution was to incorporate the necessary scripts as other Rules configurable in the Session Editor API added to TRS2004 and up, along with an expansion of the standard script libraries made part of Trainz after Trainz 1.3A version by version differential comparison of these using freeware tool kdiff3 shows the script libraries have been astonishingly stable, Trainz release to Trainz release, with at worst, half a dozen script files showing changes. Explorations by computer engineer/author, Fabartus. This was not, and is still not an optimal solution, but it beats returning to Trainz Surveyor and only having a black screen displayed, or a disconnected mouse. Expand with some coverage of how routes are built, organized, signaled and use trackmarks, triggers, et. al.