crbascott

They may suggest it, but I have never found it be be necessary.

Nice, looks like that second look did some good! Thanks again Vic!

In both schedule files I've created, I've provided a header record showing the schedule file format: // Depart,Arrive,Type,Airline,Flight,Arrival,Departure,Duration,Codeshare The arrival time (19:31) in your example is actually the time the flight appears on the DBRITE The 12:00 you question is the departure time (pushback request). In the LAS arrival example you provided, the departure time is irrelevant to the sim so 12:00 is plugged in. You'll see something similar for a departing flight where the arrival time is 12:00. Duration is not used by the sim so the number 1 is being plugged in. The last field (BA in your example) is codeshare and is also not being used by the sim. ======================= You can have flights with the same time - depending on the situation the sytem handles them differently. You can have an arrival and a departure with the same time, no issue at all. You can have two or more departures with the same time. Here's how it works:. Let's say you have 3 departures all at 08:00. The first pushback request will come in at 08:00:00, the second at 08:00:15, and the third at 08:00:30. Two arrivals at the same time will definitely cause one of the flights to be delayed. When the delayed flight appears depends on the number of runways, other inbound traffic, and a minimum separation of 5 nm. Happy scheduling!

Where has this lighting problem been mentioned? I think you've been around long enough to know that a post without details, without a log and/or screenshot, and in a thread not read by the developers is like a tree falling in a forest where no one is around.

Didn't realize one post on Steam carried that much weight. I'll guess I'll start posting there. ;)

Vic, I don't have a life and follow this forum and Steam pretty closely and obviously missed the requests to expand the 6 hours. Who was asking for this and who plays this for 8 hours straight? Insanity! I actually create snippet schedules because the 6 (and now 8 apparently) hours of optimization causes too many no free terminal issues. If you look at my KJFK custom schedule post, you can see the difference between playing with a full schedule and a snippet. I think going up to 8 hours is going in the wrong direction. Personally I think a user configurable option of how many hours of schedule to load would be more of a benefit. Also, I'm unclear as to the ultimate benefit of making planes disappear. Wouldn't this ultimately just sacrifice departures for the sake of arrivals? And the fact that all of a sudden planes disappear from gates - what were you saying about "absolutely unrealistic"? Craig

I'm sorry to be blunt but Martin is incorrect and needs to look closer at the logs (see excerpts from the log below) - all incoming planes landed. I agree that I had 12 restarter planes that worked, but these 3 didn't and that is what is baffling. All three incoming planes made it to the gate (including NKS1105) and disappeared from the strip. Unfortunately, there is nothing in the log that actually indicates when a plane reaches a gate (see proof below), so I think Martin is making an incorrect assumption saying that NKS never reached the gate.The only way to know for sure is to actually simulate the session - let me know if I need to send you a schedule file. This is from the session 1 log file - the incoming planes definitely did land. COMMAND: UAL284 EXIT AT TAXIWAY B10 08:20:57 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * UAL284 => PARSE CMD: EXIT AT TAXIWAY B10 08:20:57 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * UAL284 => TAXIWAY roadcut: EXIT AT TAXIWAY BRAVO ONE ZERO 08:20:57 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * UAL284 => AT roadcut: EXIT AT TAXIWAY BRAVO ONE ZERO 08:20:57 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * UAL284 => SAY: EXIT AT TAXIWAY BRAVO ONE ZERO UNITED TWO EIGHT FOUR 08:20:57 * UAL284 => ADD HISTORY: UAL284: EXIT AT TAXIWAY B10 UAL284 selcmd: #SELECT*NKS858% SET PlANE: NKS858 CMDTREE: tree_ground_outgoing 08:21:13 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * UAL284 => STATE CHANGE from STATE_LAND to STATE_ESCAPE_RUNWAY 08:21:13 * UAL284 => ADD HISTORY: UAL284 Successful landing. +10 pts COMMAND: VRD950 RUNWAY 27 CLEARED TO LAND 08:54:19 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => PARSE CMD: RUNWAY 27 CLEARED TO LAND 08:54:19 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => RUNWAY roadcut: RUNWAY TWO SEVEN CLEARED TO LAND 08:54:19 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => SAY: RUNWAY TWO SEVEN CLEARED TO LAND REDWOOD NINER FIVE ZERO 08:54:19 * VRD950 => ADD HISTORY: VRD950: RUNWAY 27 CLEARED TO LAND VRD950 08:58:43 alt: 99 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => STATE CHANGE from STATE_INCOMING to STATE_LAND 08:58:52 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => Landing cnt on runway: 27 cnt: 4 08:59:16 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * VRD950 => STATE CHANGE from STATE_LAND to STATE_ESCAPE_RUNWAY 08:59:16 * VRD950 => ADD HISTORY: VRD950 Successful landing. +10 pts Below are excerpts from the session 1 log file showing that the final log entries for incoming planes. The fist plane (DAL2838) is not a restarter and you can see there is nothing that indicates it reached the gate. The second plane (SCX401) is a restarter that worked. Very similar log entries, nothing that actually says it reached the gate, but there is a final message stating to start the outgoing plane. 10:48:42 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * DAL2838 => stop gate at: (-2275.9, 1459.8, 0.0) takeoffgate: null COMMAND: DAL2838 TAXI TO RAMP 10:48:44 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * DAL2838 => PARSE CMD: TAXI TO RAMP 10:48:44 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_36 r: 27 * DAL2838 => SAY: TAXI TO RAMP DELTA TWO EIGHT THREE EIGHT 10:48:44 * DAL2838 => ADD HISTORY: DAL2838: TAXI TO RAMP DAL2838 10:48:56 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_36 r: 27 * DAL2838 => STATE CHANGE from STATE_ESCAPE_RUNWAY to STATE_TO_TERMINAL !10:48:56 alt: 0 takeoff: False/False/-2 t: T2_36 r: 27 * DAL2838 => I try to go to terminal! DAL2838 10:48:56 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_36 r: 27 * DAL2838 => Start calc route from: B7 start idx: 4 10:48:56 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_36 r: 27 * DAL2838 => Calc from: B7 DAL2838 => Route is: B7, B, apron_t2, T2_36, 11:54:39 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * SCX401 => stop gate at: (-2275.9, 1459.8, 0.0) takeoffgate: null 11:54:53 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * SCX401 => STATE CHANGE from STATE_ESCAPE_RUNWAY to STATE_WAITING COMMAND: SCX401 TAXI TO RAMP 11:55:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27 * SCX401 => PARSE CMD: TAXI TO RAMP 11:55:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => STATE CHANGE from STATE_WAITING to STATE_TO_TERMINAL 11:55:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => SAY: TAXI TO RAMP SUN COUNTRY FOUR ZERO ONE 11:55:06 * SCX401 => ADD HISTORY: SCX401: TAXI TO RAMP SCX401 11:55:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => Start calc route from: B7 start idx: 4 11:55:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => Calc from: B7 SCX401 => Route is: B7, B, B10, X, T2_44, 11:58:06 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => start outgoing: SCX401

Just wanting to make sure this hasn't fallen off the radar (so to speak). Not getting any inbound flights for a terminal (especially international flights) very much kills traffic volume and spoils what should be a really fun airport to control. Thanks, Craig

Vic, I can confirm that the above issue is a multi-monitor issue only. It worked fine when using a single screen. Just for grins, I tried it with the ADIRS inside the main window and an ADIRS on a second screen. The ADIRS within the main screen worked fine, the ADIRS on the second screen had issues. Thanks, Craig

Yes - in both sessions the incoming planes successfully landed. The attached log for session 1 indicates it landed at 8:22:35 and the log for session 2 has it landing at 08:22:49. Below are a couple of log items for a successful triggering of an outgoing plane: 11:57:51 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX401 => start outgoing: SCX401 11:57:51 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: T2_44 r: 27 * SCX402 => STATE CHANGE from STATE_TO_TERMINAL to STATE_WAITING Obviously, the above didn't happen for the three restarter combos I have shared with you. Thanks!

I assume you mean 25L. I assume these are smaller planes exiting here. You can always issue an EXIT AT TAXIWAY or VACATE RUNWAY command to have them exit farther down - which is probably more realistic anyway.

In testing a custom KSAN schedule I noticed a departure never spawned. Looking at the log I noticed in the restarter section that an incoming plane came in but it never triggered the outgoing plane. The same thing happened tonight when playing the Pro Challenge schedule for JFK - an incoming plane did not trigger an outgoing plane ruining our attempt at a perfect score. :( As a result, I performed a small test at KSAN using an extract of the RT schedule including only airlines using Terminal_2W. This is the terminal where I noticed the issue and thought it could possibly be a gate issue. I ran the same schedule twice and in both sessions the below incoming restarter airplanes never triggered their outgoing counterpart - while other incoming/outgoing planes worked fine. Also, in both sessions different gates were used by the incoming planes so I don't think it is a gate issue. There doesn't appear to be anything in the log indicating an issue with the incoming planes - they landed plenty early and taxied to the gate without a problem. Restarter airplanes / parent incoming: NKS1105 - 08:06:00 outgoing: NKS308 - 12:59:00 Restarter airplanes / parent incoming: UAL284 - 07:48:00 outgoing: UAL555 - 10:21:00 Restarter airplanes / parent incoming: VRD950 - 08:52:00 outgoing: VRD953 - 10:03:00 Open gates are precious commodities, so these planes not departing just clogs up more gates adding to the no free terminal woes. I appreciate FT looking into this. I've attached the logs for both sessions. Thanks! Craig PS - I also attached the log from JFK. It is using a custom schedule with the following plane combo having the issue: incoming: BAW2273 - 19:33:00 outgoing: BAW172 - 20:50:00. output_log_san1.txt output_log_san2.txt output_log_jfk_e46_2.txt

Feel free to post a log file (output_log.txt from your tower3d_data folder) if you are still having taxi issues. Should be a simple fix. This also might help if your syntax is not quite right. http://forum.simflight.com/topic/84559-tower3d-pro-user-manual-annotated/

Vic, I always have my ADIRS on a second monitor so I'm not sure if this happens on a single screen or not. Thanks, Craig

Bummer - thanks for the feedback.

Highly unlikely in this case, but you're the moderator ... so what you say goes and what posts you decide to delete goes too apparently

Posted it only a couple of weeks ago and it has already pushed to page 4. Busy forum!

http://forum.simflight.com/topic/84644-tower3d-pro-exit-at-taxiway-strangeness-ft-andor-nd/

LOL - "This probably has been brought up somewhere" - yes, it has ... by you ... six days prior to this post ... http://forum.simflight.com/topic/84558-career-mode/?tab=comments#comment-512018 Keep fighting the good fight! :)

It means Real Traffic (RT) didn't get installed at the correct location. Make sure to point the installer to your root Tower!3D folder. After installing RT you should see an Extensions folder under your Pro root folder. Underneath the Extensions folders you''ll see Airfields and Airplanes. Under the Airfields folder you should see all the airports and within those folders will be several text files - including the schedules. Keep in mind RT gives you real world airlines, planes, and schedules. It does not give you liveries - that is where Real Color comes into play.

To elaborate: Sometimes :) In the case of LGA, some airplane mods were made that affected several airplanes used at several different airports. In the case of PHX, only new aircraft to PHX were added along with the new traffic. So, yes I would recommend downloading and installing the latest RT version now and when a new airport is released. RT will overwrite any custom files you have saved that are named as the real traffic name. So, I'd recommend copying those files and save them in a folder or make a backup with a new name. To this point I have not seen a need to re-download and/or reinstall any of the airports when a main SP is released.

Good point VenturaGuy101. The lighting system is the same as in Tower!2011. Having that knowledge and expectation level is why I specifically didn't see runway 9 at KBOS as an issue.

SK -No argument about KPHX, but Joe's last post was about KBOS and that is where the screenshots are from. So, runway light issue at KBOS or not?

Joe, you're screenshot only shows the end of the runway. If you follow the lights for the entire length of the runway at KBOS you'll see that it is "not covered in red lights" but seems to follow the standards for RCLS. I've included the description below from the link SK provided and also screenshots from runway 9 showing the light configuration. Runway Centerline Lighting System (RCLS) - On some precision runways, a runway centerline light system is installed, with white lights spaced at 50-ft intervals on the centerline of the runway. With 3,000 feet remaining, the white lights change to alternating white and red, and then all red during last 1,000 feet. Red lights the last 1000 feet. Alternating red and white White lights

RT and RC (developed by Nyerges Design) prompt the version in order to supply a default folder. Unfortunately, the airports developed by FeelThere do not do this.