Uploading New Route Specially for OR

[baldwin]

**************** don't know why the intermediates keep displaying approach and stop in OR, while the absolutes are fine, and there are no other trains or even consists on the route.

I think this is because of the way the signal system works in OR. It is very noticeable on the Surfliner2 where there are several signals grouped closer together. Far as I can make out it is due to the way OR sees the track ahead and allocates it in blocks.

[rdamurphy]

Fix for flashing water effect in MSTS:

http://msts.steam4me.net/tips.html#tip11

If anyone can give me some specifics, I'll be happy to look at the signal problems, also.

Robert

[flarrfan2]

The signal issue seems to be a bug in the latest version of OR. It was not an issue in MSTS or the previous version of OR, to my knowledge. There is also the issue that the 180 miles west from Tallahassee to P'cola is dark territory (DTC blocks), except for distant signals to the five passing sidings, four of which are controlled by visible absolutes and the fifth (Douglas City) by buried absolutes, all of which appear to function correctly. It may be that the distance between signals, as much as 30 miles in some cases, is confusing the OR code.

[rdamurphy]

That's helpful. Do you have a specific location of a signal that isn't functioning? One of the things we can do is open OR in the development environment and watch the code execute as the game is played. Very helpful for finding issues such as this.

I'll take a look and shoot an email to Rob, but it's much better if I can give him an "if A, then B happens, in C code...."

Robert

[flarrfan2]

Generally, across the whole route, the first signal encountered after a passing siding (as noted, that can be as much as 25 or 30 miles on the P&A, a more typical distance in the CTC territory east of Tallahassee) typically displays approach, and if there is another intermediate after it, a stop indication is displayed. The absolutes at the passing sidings generally display correctly. Bear in mind as well that there are buried signals at DTC block boundaries between Tallahassee and River Jct. I chose not to mark the many more block boundaries from there to Pensacola with signals when I scenicked the west end of the route, mainly because I didn't know well enough exactly where the block boundaries were, and I also decided against both mileposts and the prototype block boundary signs for the P&A. On that end of the route, the bad signals are the distants to each of the signaled sidings at Avalon, Floridale, Sellers and Chipley. Unfortunately, on the prototype, the distances between those signals and the respective sidings are widely varying, from ten miles or so east of Chipley, to less than a half mile east of Floridale. There are also buried absolutes, I think the only buried ones on the P&A, in downtown Pensacola where the double track from Goulding Yard ends just before the curve under I-110.

[apco25]

3 threads all on the same route? Can we get them merged?

Routes works just fine for me in OR v0.9 with 12gig ram Core I7 930