BVEStation

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - R36 #9346

Pages: 1 [2]
16
BVEStation Network News / Re: The new R46 has been released.
« on: July 02, 2012, 05:03:10 pm »
Nice. I drove it in oBVE on my Linux install.

17
Other Projects / Re: R142B 7 LCL StripMap Testing
« on: June 23, 2012, 10:06:01 am »
Interesting...

18
BVE/OpenBVE Support / Re: Running into another train
« on: November 18, 2011, 10:51:08 pm »
Be careful though, the signaling on many routes is such that only one red signal is behind the train in front of you: the signal that train just passed. On real NYC subway lines, there are at least two red signals behind a train.

19
NYCTA Projects / Re: New NYCT Objects Pack
« on: September 22, 2011, 05:02:37 pm »
Can you make a video how to Install your new Signals because i try.
 :-[

Just put the folder of the signals in the Objects folder
It's not just that, but the route needs to be modified to use them. You can't just pop a group of objects into a folder and expect the objects to appear on the route unless the route is looking for them.

And depending on your filesystem, case sensitivity may be an issue.

20
Art & Graphic Design / Re: Bus Timetable Cover Design
« on: September 19, 2011, 05:26:17 pm »
I guess the Metropolitan Avenue stop could be in the extreme far east portion if Glendale.

21
BVE/OpenBVE Support / Re: OpenBVE + Steam = ???
« on: September 03, 2011, 12:10:09 pm »
If only we could introduce portals into BVE routes. Not the elevated-to-tunnel kind, but build a fictional route where an elevated line runs into a portal placed on the wall of a building in Manhattan, and instantly emerges from that portal somewhere in Brooklyn.

If you haven't played Portal or Portal 2, try them. I recommend them both.

22
BVEStation Network News / Re: The D Line has been released!
« on: August 19, 2011, 04:35:52 pm »
I just drove a train on that route (specifically, the file NTCT-D2.csv), and I noticed a couple of things that, well, got me taking notes on the things that can be improved.

Graphical Improvements
While the route in general looks great, there are a few cosmetic issues that need to be taken care of. For instance, at the Rockefeller Center station, there are no diagonal bits connecting the wall and horizontal beams.

Next, at 103rd Street, there's an F train on the uptown express track.

Announcements
At Fordham Road, there's no announcement of the Bx12 Select Bus Service. I don't know for certain how it's treated in the B division, but it's always announced on the A division stations where the line crosses. This is probably due to the automated announcements, but I think the R160s already announce the M15 where it crosses the lines with R160s running on them.

I would suggest updating either the scenery and marker bitmaps or the announcements to be consistent with the period being depicted. "Franken-forties" running on the B and announcements of the availability of the M train on Sixth Avenue? When is this route set, 2009 or 2011?

Stations
I noticed that at stations where the platform is on the train's left, the doors on the train's right side opened. I'm sure a conductor would get written up for opening the doors on the wrong side once, but doing it ten times (at 205, BPB, KB, Fordham, Tremont, 145th, RockCenter, 9th Av, 62nd St, Bay Pkwy)… well, if it happened on a real D train and it didn't make the news, I would be surprised. There is a fix for this, which I will explain below.

I also noticed that at places where the signal at the departing end of the station is an automatic or other single-headed signal, the signal shows red as the train approaches, but turns green as the train approaches the stopping point. I've seen this bug on many of the other BVE routes depicting the subway system, and there is a fix, which I will also explain.

The fix for these two issues. It all has to do with the Track.sta command. In the file, an example station command is:

Code: [Select]
.sta 205th Street;5.0130;5.0200;0;1;1;ats;;10;50;D2\205_Dep.wav
Parsing this command, we get the following:
Name: 205th Street
ArrivalTime: 5.0130
DepartureTime: 5.0200
PassAlarm: NO
Doors: RIGHT
ForcedRedSignal: YES
System: ATS
ArrivalSound: <NULL>
StopDuration: 10
PassengerRatio: 50
DepartureSound: D2\205_Dep.wav
TimetableIndex: <NULL>

The values in bold are what need to be fixed. For stations with platforms on the left, change the Doors parameter (the first one bolded in the example above) to −1. For stations with red signals as you approach the stopping point of stations (practically all of them), change the Stop or ForcedRedSignal parameter to 0. Setting this parameter to 0 will not make the program think the train is not supposed to stop at the station. That effect is done by setting the ArrivalTime parameter to P.

However, the effect could be retained (with an appropriate tweak to the StopDuration parameter) at stations where the motorman is required to "punch for line-up" (e.g. 36th Street).

As for the schedule, I think it would be nice to see how late or early you are at other stations along the route. This can be achieved by supplying the ArrivalTime parameter for each station, and leaving the DepartureTime blank. You can get this information using Scott's Transit Playground.  While there is no trip leaving 205th Street at 05:02, there is one leaving at 05:04, operating express in Manhattan, local in The Bronx and Brooklyn. Then again, if 5:02 PM is intended, the correct schedule starts at 17:02. Assuming that this is the case, here's the schedule for this trip:

Code: [Select]
17:02:00 Norwood - 205 St
17:04:00 Bedford Park Blvd
17:07:48 Kingsbridge Rd
17:09:24 Fordham Rd
17:10:54 182 - 183 Sts
17:12:30 Tremont Av
17:14:24 174 - 175 Sts
17:16:30 170 St
17:18:36 167 St
17:21:00 161 St - Yankee Stadium
17:22:30 155 St
17:24:00 145 St
17:27:30 125 St
17:35:30 59 St - Columbus Circle
17:39:06 7 Av
17:41:00 47 - 50 Sts - Rockefeller Ctr
17:42:30 42 St - Bryant Pk
17:44:30 34 St - Herald Sq
17:47:30 W 4 St
17:49:30 Broadway - Lafayette St
17:51:30 Grand St
18:02:30 Atlantic Av - Pacific St
18:08:00 36 St
18:12:00 9 Av
18:14:00 Fort Hamilton Pkwy
18:15:48 50 St
18:17:36 55 St
18:19:30 62 St
18:21:18 71 St
18:23:00 79 St
18:24:36 18 Av
18:26:06 20 Av
18:27:30 Bay Pkwy
18:29:18 25 Av
18:31:30 Bay 50 St
18:35:30 Coney Island - Stillwell Av

Signalling
Finally, I start with a bit of a story. After crossing the Manhattan Bridge and passing DeKalb, I approach Pacific Street, and to my surprise, I see the train in front of me, with two signals behind it: the one immediately behind showing red, and the one behind that showing yellow. I hit the brakes, waited for the train to go well ahead of me, then proceeded into the station.

This leads me to pose a question: Is there anyone working on the Track.Section + Track.SigF method of placing signals? Because that would be really nice, especially when you consider repeater signals. What's cool about Track.Section is that you can make it so that there can be two blocks of red behind a train.
Code: [Select]
with track
1435,.section 0;0;2;4,.sigF 3;0;-3;-1

Yeah, it only works with OpenBVE, but who still uses older versions of Mackoy's BVE Trainsim? (I suppose that could be a poll question.)

23
BVEStation Network News / Re: New Train Sim in development
« on: March 03, 2011, 12:18:14 am »
You will be driving fictional trains on a fictional track.

The train actually exists. It it part of the Rotterdam Metro rolling stock in the Netherlands. Here are two pictures:

http://sp7.fotolog.com/photo/55/29/32/metro/1081790967_f.jpg

http://www.ovinnederland.nl/RRMetro.jpg
Here's a third picture of the 5500 series cars that are also used in the simulation.
http://commons.wikimedia.org/wiki/File:Randstadrail_Nootdorp_2.jpg

Pages: 1 [2]