Birmingham 2 route

[jamesphh]

After trying OTR on the Feather River and the L&HR 1940 I decided to run the Birmingham 2 route. Ran into a number of issues. Tele wires are about 100 ft above poles. Most telegraph poles are misplaced. Some signals are incorrectly rendered. Dwarf signal are misplaced. Some reed colors do not render correctly. Water is flat. Street light light-cones give a greenish cast. Some milemarker signs are blank. Other light cone make track, railcars etc dissappear. However, building are more vibrant and seem to have more detail, and the shrubery is even better than is MSTS. Also some shrubery is misplaced. I know this is a beta but thought I would report what issues I have found. Good start.

[longiron]

After trying OTR on the Feather River and the L&HR 1940 I decided to run the Birmingham 2 route. Ran into a number of issues. Tele wires are about 100 ft above poles. Most telegraph poles are misplaced. Some signals are incorrectly rendered. Dwarf signal are misplaced. Some reed colors do not render correctly. Water is flat. Street light light-cones give a greenish cast. Some milemarker signs are blank. Other light cone make track, railcars etc dissappear. I know this is a beta but thought I would report what issues I have found. Good start.

Thanks for noting the issues. The Open Rails team is aware of many of them, but keep the comments coming:
1. Signals do not work in v128 and may be misplaced or duplicated as OR is just dumping a shape where a signal is called for. We're working thru an exciting new approach to signaling.
2. Mile markers and speed posts are not implemented in v128. This is still on our TO DO list
3. v128 has a temporary solution for water, we're working on a total new approach to water
4. We are aware of the lighting and transparency issues and they have been fixed.
5. We're aware of floating objects and have pretty much fixed the issue.
Please check the documentation to see if the OR team is aware and working on the issue.

[jamesphh]

I had forgotten some of the future updates, but what I had meant was that the tele poles in the middle of the track were misplaced. The dwarf signal in the middle of the track was misplaced. The custom signal showing in the MSTS version shows the primary head and a secondary head on the left of the mast. OR shows the secondary head on both the right and left of the mast. In other routes tried the signal shapes are correctly rendered.
One good point is that both the L&HR and Birmingham are very intensive routes with jerkyness in MSTS, there being less of this in OR.

[longiron]

the tele poles in the middle of the track were misplaced. The dwarf signal in the middle of the track was misplaced. The custom signal showing in the MSTS version shows the primary head and a secondary head on the left of the mast. OR shows the secondary head on both the right and left of the mast. In other routes tried the signal shapes are correctly rendered.

Since OR has yet to implement signals, there are misplacements and duplicates when double or triple signals are used in MSTS. The code is just dropping a similar shape wherever a real signal is called in MSTS. There still are mysteries as to how MSTS places shapes on tiles - they don't always end up visually where the coordinates say they should go.