Das ganze ist ein aufwendiger gestalteter Quickdrive, KI-Verkehr in beide Richtungen, fest im Szenario eingebautes statisches Rollmaterial, das ging ja bisher schon, hat nur fast keiner gemacht. (Angst vor dem 32bit Dump?)
Was ich noch nicht rausbekommen habe, ist am KI-Startabstand gedreht worden? ich hab da 2000m in Erinnerung, um rote Signale wirksam zu provozieren, müsste der kürzer sein, sonst haut der blockierende KI zu früh ab. Was wurde da wie eingestellt?
Wäre schön wenn das "verraten" würde, da könnten auch andere diese interessanten Szenarien bauen.
For those who want to try their hand doing this here are some tips.
First: you will need MUCH time. A Real Drive for just one direction on a route takes me 3-4 FULL working days to build!!! Yes that is 7 hours a day for 3 or 4 days.
Running AI traffic in front of the player train while running it in the opposite direction you will run into the following problems: If you do not tell the trains exactly where to go they will crash. You will have to put in destinations in the scenario editor after each switch point. That means 40-50 extra destinations in a scenario. You can not leave any routing of an AI train or the player train up to the TS code. Where it can go wrong, it will go wrong.
Using the AI trains to make red lights and making use of the 2000m perimeter: Place the AI train with the back end of the train 50 meters after the hauptsignal. That will work.
Every time you add an AI train, close the editor, clear the cache(!) and start the drive from the quick drive menu. Even if your route for the player train and AI train routes are correctly laid sometimes TS crashes. I don’t know why. So if you do it all at once you will never know why TS throws an error message or what AI train is causing it. The TS crash log is not reliable unfortunately.
Sometimes the signal system is just too badly coded for it to work. This is why there is a Lübeck Hamburg Real Drive but no Hamburg Lübeck Real Drive. The signal coding in direction north aren’t good enough. I had huge problems on stretches of the Mittenwaldbahn (DTG version) that took me a whole day to solve.
Sometimes spawn points go corrupt when saving. Be prepared for that.
Sometimes destination points go corrupt when saving. Be prepared for that.
Write EVERYTHING down you do. Every position of every AI train, where it starts, where it goes etc etc etc... Without good notes you will not be able to resolve errors. And you will get errors!!!!!
I have done 11 Real Drives so far (and yes they will all be released for free) and none of them have not been extremely frustrating to make.
Do not change the spawn probabilities to less than 100% untill you have testdriven the drive 2 or 3 times. And then when changing probabilities for spawning test drive again. Changing probabilities can make TS think that the AI trains will crash even if their routes are many kilometers apart!!!
Stationary material can make TS think an AI will crash even if the route is correct. You will have to deal with that too.
Have a betatester that you trust. Sometimes scenarios can go corrupt when using the Utillity app to make the rwp file. You will not know this untill it has been opened on another computer. All my Real Drives have been test driven by someone else.
Everytime you make a change, save the scenario under a new name so you can always revert to a working version. Unfortunately the (clone scenario) can also corrupt the scenario. So you have to save, but the save might ruin your work....
There has to be trains that are tagged in the blueprint folder. Quick Drives can only have AI traffic if there are consists with locomotives in the blueprint folder. This is why i can’t make one for the Dreiländereck. It is one of my favorite toutes but has no trains in the blueprint folder. (To the creators of that route: PLEASE PLEASE PLEASE update the steam version with train consists in the blueprint folde so i can make Real Drives for your beautiful route)
Sehr gut.
[scallout][/scallout]
