New functions: ATC/ATS-SN/ATS-P, doppler effect sounds etc. Complete RB 1.4.2 review.

As a power RouteBuilder user, I can assume, that RouteBuilder routes are less 
powerful than manually built ones, 'cause RouteBuilder has some commands that 
are not considered while creating RouteBuilder. Maybe, it is because Western 
people don't understand Japanese. Me, as Japan lover and Japanese learner, I 
can assume that the command sense has been already discovered by some Japanese 
people or people who know Japanese, or otakus/weeaboos etc. Maybe it is a Jens 
Ruegenhagen, the Chashinai Dentetsu developer, or Takashi Kojima, the BVE 
author (who knows less English), or Dennis Lance, the author of BVE route 
coding tutorials, or somebody else etc. We'll call him Kaya. So, as a person 
who is almost like this Kaya, I can see that all command are same and nobody 
has mistaken. But, stories are the stories, it's not literature section, it is 
an issue report service. First, I will give you a tip that in RB, you can't 
make routes that are using ATC, ATS-SN or ATS-P. That's because for making the 
route safety system working, you have to add transponders on the track. This 
function still isn't realized in RouteBuilder. In manual coding, use of 
transponders is enacted in .Tr <type> command. For using ATC on route, you do 
so on stations, where you should write .Sta name;;;;;;1 type command to enable 
ATC equipment, or .Sta name;;;;;;0 type command to disable it.
Then, on Japanese routes, while driving through the crossing, you gonna hear 
the "ten-ten-ten-ten" sound, which volume is increasing when you drive to it, 
and decreasing when you drive off it. Or in Tokyo Metro Ginza line, when you 
enter the tunnel after driving off Shibuya station to Omotesandou station, you 
hear the buzzer, which intensivity is increasing while driving to and 
decreasing  while driving off. It is possible in manual coding, but impossible 
in RouteBuilder. It is called doppler sounds. In manual coding, doppler sound 
use is enacted in .Doppler <name> command.
Then, platforms, roofs, walls, dikes (TSO), and everything other in 
RouteBuilder is considered as free objects. This indeedly makes the platforms 
etc untransformable. When trying to make gradients in RB with some walls, walls 
do not follow the pitch: they are repeating each 25 meters as steps. When you 
are making an island platform on the two-track line, and you are trying to make 
platform ends narrowing to the lines, the narrowing effect doesn't work. Cracks 
are impossible at all. While making a connection, that is entirely longer than 
25 meters, while creating the announcements sounds, they repeat every 25 
meters. Even rails lug sometimes, when you build complex trackwork  (While 
making a Samara Metro line bound from Yungorodok to Rossiyskaya, you can see 
the lug in trackwork of the cross-connection). Some TSO/dikes and walls 
disappear sometimes. Route always should contain the stopsign, without it I 
experienced some crashes while building Kiev Metro line 2 (KChL). Platforms can 
be placed only on the left or on the right, both platforms are impossible. 
Signals on the track that is longer than 25 meters are repeating every 25 
meters. Grids often lug.
I DO NOT force anyone to hate routebuilder and code manually. I just list all 
the problems that should be solved as fast as possible to make RouteBuilder 
really powerful.
Original issue reported on code.google.com by oleg5...@yandex.ru on 4 Nov 2011 at 8:12
Giovi802 / routebuilder

New functions: ATC/ATS-SN/ATS-P, doppler effect sounds etc. Complete RB 1.4.2 review. #2
