Hi to all,
I have decided to get back into my next project and the one I have been working on lately is the Russian route Perm II. The 5 templates are finished but am having signal issues which I can't resolve, even with AG's permissive mode feature in testing the AG-generated activities. But before going any deeper with the signal issue, here are some details about the route and templates.
The Russian Perm II route is among the best Russian routes available out there. It is a 125 km route complex which covers from Mulyanka to Palniki with PermII in the middle. The city of PermII is close a million in population. The route, located near the Ural Mountains is very industrialized (mainly gas and energy) and is heavy in scenery, as you will see in the next screenshots.However, FPS is very good despite all this detail. I have rarely seen that many scenery and detail in any route. Despite the much smaller TDB file compared to some mega-routes, like the PRR-Eastern route this file is a 759MB single file to download and once installed it is about 1.5GB. It is mainly a double track electrified line with some single line trackage and have 130 serviceable sidings but about 25 of these sidings are only accessible by diesel locos. That is why the templates includes two NB and SB for each electric and diesel engines as the number of serviceable sidings are different for both tractions. The fifth template is a YARDS template with a TEM2, a Russian diesel shunter. The number of paths created for AI traffic and player engines is 75 paths for all templates. All templates have the same traffic pattern, NB & SB.
Now about the signal issue; many of the sidings are signalled and seem to be set to absolute, that means that even with a request (TAB) or trying to have AG change the mode to Permissive have been unsuccessfull. One solution found is that I had to reposition all possible markers in each of the 5 templates as close as possible to the signals, so when the player train hooks up with the cars, it will not cause the engine to find itself behind the signal.This took some time but this change is helping. So far, the WB and EB AG-Generated activities for all tractions were successfull while being careful at the same time when coupling or uncoupling in sidings close to signals.
The YARDS template is the one who is now causing a major concern, since I cannot enter in some remote areas from the mainline only accessible by diesel. In these locations the signal is near the mainline but cannot enter to do some work because of the absolute signal attribute of these signals.
If you wish Steve to send you a copy of the sigscr.dat file, let me know. Your help will be much appreciated.
In the meantime, I am working to upload the oncoming Dvoukolejka, pending the signal issue.
Will update later.
The screenshots will be posted in the next posts.