[KMW]

Ursprungligen postat av svenolov

Ja, jag läste det och det ser ju ut som om dom tar AI-problemet det på allvar. Det är ju i alla fall en start i rätt riktning. Men fortfarande är AI-trafik och manuella förare isolerade från varandra, och förmodligen så kör inte AI efter signalbeskeden heller - ännu. Ser fram emot en test i September.

Mer om AI delen över hos Railworks America: http://railworksamerica.com/forum/vi...art=120#p24164

/æ

Dispatcher and Signalling information lacking from the TrainSim2012 release news? well it falls under a yes and no answer. Yes information isn't in the headlines, but this aspect of TrainSim2012 has not been left untouched.

So what do I mean? Well lets recap the current status of RailWorks2. There has been to date, one all powerful Dispatcher in the RailWorks world, born into Rail Simulator and expanded gently ever since. Why is it taking so long to address issues with the Dispatcher? Simply put, its dangerous. There are many hundreds of scenarios included in RailWorks, there are just as many again in all the official DLC, and there are thousands more in the freeware communities around the globe. Scenarios are the bread and butter of RailWorks, they combine all aspects of the simulator to create the experiences everyone is here to enjoy.

Imagine if you will, a time traveller going back to see the Dinosaurs. There is inherent risk that while walking about the forest 65million years ago, that traveller might accidentally step on a tiny creature, which could result in the entire evolution of species culminating in the birth of the human race being wiped out. Back in the RailWorks universe, the one overriding Dispatcher is at the heart of hundreds of thousands of hours of game play, and one tiny change could have awesome destructive power. Therefore the risk of any change has always far outweighed the desire to make the changes.

So how does TrainSim2012 address this situation? Two words > Dispatcher Versioning.

Put simply, progress will be made by cloning the Dispatcher, and then enhancing the clone. The original can then be left alone, and everything reliant on it will remain stable. TrainSim2012 lays the foundations to commence work on improving dispatching. Future updates could include a 2nd dispatcher, or a 3rd or 4th. Each update will see scenarios make use of these additional dispatchers as well as all the features of the ones before. Will this leave behind the older scenarios? Yes, for the very reason that we want them to remain stable and usable. We dont want updates to TrainSim2012 damaging the many hours spent creating that content. Will this mean those older scenarios will need to be recreated to use future Dispatcher enhancements? No. When a scenario is generated, it will record the level of the then current Dispatcher. When a new update is provided, the level of the Dispatcher will be incremented. Older scenarios will continue to use the previous level. However, if you open that scenario for edit on the new level, when saved, the new level is recorded, thus allowing scenarios themselves to be updated if so wished. Authors are then able to choose if they want to update their content, rather than being forced to because an update broke them.

RailWorks stablized the (then) present, RailWorks2 addressed the past, and TrainSim2012 is the future. !*cheers*!