BVEStation Forums
BVE => Other Projects => Topic started by: stump on May 29, 2013, 02:20:47 am
-
With all the commuter and mainline equipment development threads I see here, I thought I might try to create an OpenBVE train safety system plugin that implements NORAC cab signaling. This would also include defining conventions for placing NORAC-style signals in routes (including handling Rule 251/261-without-cab-signals, Rule 251/261-with-cab-signals, and Rule 562 territory appropriately), and I would also add an AI that obeys the relevant rules.
This is the set of rules used by (among others) Amtrak and just about every commuter railroad in the Northeast that isn't part of the MTA. (And the two that are aren't really too different from the others anyway, so you could probably end up adapting this to them too.)
I am not planning to use native code, so this will not be OS-specific.
I have not started yet. Updates will be posted here. Comments on the idea are appreciated.
-
I like the idea. Is there going to an Amtrak, LIRR or MNR routes and activites to go along with the signaling. I would love to see what everyone can come up with... SHould be pretty interesting .
-
Sounds like a great idea, I would love to help if you need it.
(textures, helping to equip trains, etc.)
-
I like the idea. Is there going to an Amtrak, LIRR or MNR routes and activites to go along with the signaling. I would love to see what everyone can come up with... SHould be pretty interesting .
I know that at some point someone was making a Northeast Corridor route, but I don't know what happened to that.
-
Development of cross-platform plugins is very sorely needed, so I applaud your efforts greatly. One of the things the developers here have been hoping for is a plugin that can be implemented in our routes and trains that works on all OS's, so this comes as great news to us!
-
I know that at some point someone was making a Northeast Corridor route, but I don't know what happened to that.
Perhaps we can revive these to go w/ the plugin.
http://forums.bvestation.com/index.php?topic=256.0 (http://forums.bvestation.com/index.php?topic=256.0)
http://forums.bvestation.com/index.php?topic=1299.msg16125#msg16125 (http://forums.bvestation.com/index.php?topic=1299.msg16125#msg16125)
-
A NE Corridor route is kind of ridiculous when you think about it... OpenBVE isn't nearly powerful enough for a route of that scale, and it's a massive project to attempt...
-
A NE Corridor route is kind of ridiculous when you think about it... OpenBVE isn't nearly powerful enough for a route of that scale, and it's a massive project to attempt...
Well that is not entirely true...there are pretty long British routes similar to the NEC, namely the Tyne Valley and ECML Northumberland routes.
-
An NEC route is definitely possible, but to make it even remotely realistic would require enormous amounts of time, work, and money.
-
Well that is not entirely true...there are pretty long British routes similar to the NEC, namely the Tyne Valley and ECML Northumberland routes.
Yes but those aren't 400 miles long.
BStyles
-
Wouldn't coding the NEC be like coding for the A from 207 to Far Rockaway and back to 207 at least 3 times?
-
Yes but those aren't 400 miles long.
BStyles
Nobody said we were making the entire NEC in one go, maybe just bit by bit.
-
Making the NEC in bits and pieces makes absolutely no sense in the long run, considering that most of the routes don't make short stops (In between, you have auxiliary routes like MARC and NJ Transit). The Acela Express is a single shot, and the AEM-7 and HHP-8 consists go as far as Miami.
BStyles
-
Building the NEC in sections is completely feasible. It just depends on how much painstaking detail you insist on adding into it.
http://web.ncf.ca/fb214/ (http://web.ncf.ca/fb214/)
^ Here is the perfect example of what I mean. The Maastricht route that you can download on this page is 300 kilometers (186.45 miles) long, making it about the length of a typical Keystone run between Harrisburg and NYP. Takes 3-4 hours to run depending on whether you're making every friggin stop on the local, or if you're express-ing. Honestly I'd have to disagree with Bstyles and say that building the NEC in segments is MUCH more logical. Realistically speaking, who is going to sit at their computer for literally 8 hours (http://www.amtrak.com/ccurl/774/528/Northeast-Corridor-Schedule-2-012813.pdf (http://www.amtrak.com/ccurl/774/528/Northeast-Corridor-Schedule-2-012813.pdf)) as they operate from Boston South to Union Station WAS? Segmenting the line like this -->
BOS-NH, NH-NYP, NYP-PHI, PHI-WAS
is much more realistic in the sense that you can play for 2-3 hours at a time on a segment of your choice, rather than waiting for the ENTIRE NEC to load with all those objects and then fumbling with the station jumper to get to the segment you want to operate. That's just my take.
-
As a Conductor for AMTRAK my craft and the Engineers would not work from Boston to Washington. We have several crew change locations. Boston, New Haven, New York City, Philadelphia and Washington. Philadelphia is used when a crew is running short on time from the hours of service law. Baltimore is another crew base because we supply the crews for the MARC local service to DC so we can grab crews from there in a pinch. But if you are going to try to create the NEC you will have to break it up..[1]Boston to New Haven...[2]New Haven to New York-on the Metro North...[3]New York to Philadelphia...[4]Philadelphia to Washington