VenturaGuy101

The Steam options only work if you installed Steam to the default path. I am glad Real Traffic is not on Steam as I can control the install and use custom terminals and schedules that are not over written by Steam updates.

Test #1 Started at 18:00 and had AAL758 waiting to cross runway 27R at K3. PTD4922 landed. I gave "Vacate runway right onto taxiway N" just as the plane appeared on the ADIRS but before landing. The plane exited left onto M. Test #2: AAL2049 landed just behind PDT4922. I gave "Vacate runway left onto taxiway N" but got a runway too short message. I gave "Vacate runway left onto taxiway T" and the plane decided to exit right onto K4. So yes it is repeatable. output_log.txt

I can try another session and see.

I gave the instruction while the aircraft was still on the DBrite for some aircraft or after touching down but before the successful landing message. The Vacate Runway message used to work before the "runway not long enough" bug started. I was unsuccessful to get the cargo planes to exit left toward the cargo terminal and the odd exit left down taxiway M instead of continuing to exit right at N. I have not had the time to test with other airports. I only know it occurred at KPHL.

I have discovered an issue with "Vacate Runway Left/Right" with the last update to the SP. I was at KPHL around 16:00 (Custom Schedule from ATC Joe). I was using 27R for arrivals and 27L for departures. I attempted to get the FedEx and UPS flight to Vacate Runway Left. Each time the planes exited to the right. I then tried to have an AAL plane continue down runway 27R and exit at taxiway N instead of K3. I used the command "Vacate Runway Right onto Taxiway N" The plane exited left onto taxiway M. Both issues occurred with multiple aircraft during the run. Log is attached. --- UPS2072 Log --- COMMAND: UPS2072 VACATE RUNWAY LEFT ONTO TAXIWAY N 17:39:21 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => PARSE CMD: VACATE RUNWAY LEFT ONTO TAXIWAY N 17:39:21 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => TAXIWAY roadcut: VACATE RUNWAY LEFT ONTO TAXIWAY NOVEMBER 17:39:21 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => RUNWAY roadcut: VACATE RUNWAY LEFT ONTO TAXIWAY NOVEMBER 17:39:21 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => SAY: VACATE RUNWAY LEFT ONTO TAXIWAY NOVEMBER UPS TWO ZERO SEVEN TWO 17:39:21 * UPS2072 => ADD HISTORY: UPS2072: VACATE RUNWAY LEFT ONTO TAXIWAY N UPS2072 ... 17:39:43 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => STATE CHANGE from STATE_LAND to STATE_ESCAPE_RUNWAY 17:39:43 * UPS2072 => ADD HISTORY: UPS2072 Successful landing. +10 pts 17:39:43 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => escape cross: N ... 17:40:00 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => stop gate at: (209.1, 1749.2, 0.0) takeoffgate: null ... 17:40:12 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => STATE CHANGE from STATE_ESCAPE_RUNWAY to STATE_WAITING ... COMMAND: UPS2072 TAXI TO TERMINAL VIA K T P U 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * UPS2072 => PARSE CMD: TAXI TO TERMINAL VIA K T P U 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => STATE CHANGE from STATE_WAITING to STATE_TO_TERMINAL 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => VIA roadcut: TAXI TO TERMINAL VIA KILO TANGO PAPA UNIFORM 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => SAY: TAXI TO TERMINAL VIA KILO TANGO PAPA UNIFORM UPS TWO ZERO SEVEN TWO 17:40:22 * UPS2072 => ADD HISTORY: UPS2072: TAXI TO TERMINAL VIA K T P U UPS2072 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => Start calc route from: N start idx: 57 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => Calc from: N 17:40:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: cargo2 r: 27R * UPS2072 => Route is: N, K, T, P, U, apron-cargo, cargo2, calculate time: 0.04858398s highest count: 11396 --- AAL1262 Log --- 17:49:13 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => STATE CHANGE from STATE_INCOMING to STATE_INCOMING ... 17:49:25 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => STATE CHANGE from STATE_INCOMING to STATE_INCOMING 17:49:25 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => Activate incoming plane. ... 17:49:55 * AAL1262 => ADD HISTORY: AAL1262: Philadelphia Tower, AMERICAN 1262 with you Runway 27R. ... COMMAND: AAL1262 RUNWAY 27R CLEARED TO LAND 17:50:03 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => PARSE CMD: RUNWAY 27R CLEARED TO LAND 17:50:03 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => RUNWAY roadcut: RUNWAY TWO SEVEN RIGHT CLEARED TO LAND 17:50:03 alt: 3000 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => SAY: RUNWAY TWO SEVEN RIGHT CLEARED TO LAND AMERICAN ONE TWO SIX TWO 17:50:03 * AAL1262 => ADD HISTORY: AAL1262: RUNWAY 27R CLEARED TO LAND AAL1262 ... COMMAND: AAL1262 VACATE RUNWAY RIGHT ONTO TAXIWAY N 17:55:30 alt: 134 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => PARSE CMD: VACATE RUNWAY RIGHT ONTO TAXIWAY N 17:55:30 alt: 134 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => TAXIWAY roadcut: VACATE RUNWAY RIGHT ONTO TAXIWAY NOVEMBER 17:55:30 alt: 134 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => RUNWAY roadcut: VACATE RUNWAY RIGHT ONTO TAXIWAY NOVEMBER 17:55:30 alt: 134 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => SAY: VACATE RUNWAY RIGHT ONTO TAXIWAY NOVEMBER AMERICAN ONE TWO SIX TWO 17:55:30 * AAL1262 => ADD HISTORY: AAL1262: VACATE RUNWAY RIGHT ONTO TAXIWAY N AAL1262 ... 17:55:33 alt: 99 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => STATE CHANGE from STATE_INCOMING to STATE_LAND ... 17:56:11 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => STATE CHANGE from STATE_LAND to STATE_ESCAPE_RUNWAY 17:56:11 * AAL1262 => ADD HISTORY: AAL1262 Successful landing. +10 pts 17:56:11 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => escape cross: M ... 17:56:22 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => stop gate at: (988.4, 2267.3, 0.0) takeoffgate: null ... Store stat: True COMMAND: AAL1262 TAXI TO TERMINAL VIA P T J 17:56:28 alt: 0 takeoff: False/False/-2 OWNER_TOWER r: 27R * AAL1262 => PARSE CMD: TAXI TO TERMINAL VIA P T J 17:56:28 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: A8 r: 27R * AAL1262 => VIA roadcut: TAXI TO TERMINAL VIA PAPA TANGO JULIET 17:56:28 alt: 0 takeoff: False/False/-2 OWNER_TOWER t: A8 r: 27R * AAL1262 => SAY: TAXI TO TERMINAL VIA PAPA TANGO JULIET AMERICAN ONE TWO SIX TWO 17:56:28 * AAL1262 => ADD HISTORY: AAL1262: TAXI TO TERMINAL VIA P T J AAL1262 COMMAND: ... output_log.txt

Dang...It appears this flight was delayed. At least it wasn't canceled.

It also appears it fixes the beacon and aircraft light remaining on after parking at the terminal.

I saw the update this morning but I also have not seen any information if its a Tower!3D Pro update or if it is one of the add-on airports. It appears that it was the Tower3d.exe that was updated.

Try training Microsoft speech program to improve accuracy.

Craig, I think I was successful because I copied files over from my Tracon!2012 file after I installed Tracon!2012:SE. So I cannot confirm or deny this issue. There has been quite a few people having issues so it should be looked into.

I am in progress of fixing the Tracon myself. The issue is the Mag-True was set negative when it should have been positive. I discovered when the local features and departure paths were not aligned with the runways. When I tried to add a couple of approach waypoints, they were intersecting the runways at 50 degrees. I discovered the Mag-True and corrected that value and it actually created a complete mess with the runways, departures, and some waypoints. I started to edit each runway and entered data available from AirNav and things started to come together so I know that I am on the right track. The sad part is I will not be able to share the sector since it is published by a vendor and the changes are so numerous, not many people will attempt to fix it them selves even if I have a complete set of notes.

A quick question regarding editing a Tracon Sector. * When editing an item like the runway there is an elevation tag. The manual does not state if the elevation is metric (meters) or imperial (feet)? I don't see any place to indicate units. * Is there any contact information for Simulated Designs? I don't see them on this forum and I cannot find any contact information so far on the internet. I found some significant errors in one of their Tracon Products and I would like to let them know. A PM with this information is fine.

@FeelThere - I also have an issue with the profile button missing so I cannot add a new profile. Tracon!2012:SE with all addons purchased from feelthere.com. @wsuch - What tracon sector are you running? Are you having issues with the other sectors? I am able to run KLAX so far. I have installed NorCal, New York, Atlanta, and Philly all regular versions and not from Steam but I have not tested those yet.

Texpack1 = TIST Texpack2 = KPHL Texpack3 = KLAX Texpack9 = KLGA Texpack10 = KPHX @lgvdbroek What airport are you running? Have you tried one of the other airports to see if you still have the same issue on all 3?

When do you give the vacate runway command? I sometime noticed that giving the command too early caused that kind of issue but that was a few patches back when we were getting the "runway too short" issue. I have not reported anything since as I hope that the current issue with the path calculation gets fixed first so I can do more complicated testing. I have only been playing KPHL ans KSAN as the other airports are having real issues with complicated taxi instructions with wrong order or not calculation of routes at all.

All files are compatible with Tower!3D and Tower!3D Pro as long as you have Real Traffic and Real Colors. The only difference is you have voice recognition in Pro.

You can add some additional lines in the Tower3d.rec file that allows for taxi instructions at pushback. It helps to get planes going in the right direction.

Thanks Gabor for updating the terminal file for KLGA to include the terminal assignments.

I believe there was an issue with the terminal files that caused loading issues at KLGA and TIST. Joe created a good terminal file using the new terminal assignments that did not contain the issue that was in the original RT.

Turn off the antivirus.

I am finding some issues with the path calculation with the latest SP3.1d. It is faster but at more complex airport taxiway, it calculates a path out of order. At KBOS: JBU2369 located at gate: Term_C18 (near taxiway A and A1) and wanted to take off on runway 9. It calculates convoluted winding paths and does not respect the order of taxiways given. First Command: JBU2369 PUSHBACK APPROVED, EXPECT RUNWAY 9 TAXI VIA B K M Path: JBU2369 => Route is: Term_C18, A, K, B, E, M, M, calculate time: 0.0234375s Why did it pull K before B? To get it off taxiway A I tried this command once it was ready to taxi: JBU2369 RUNWAY 9 TAXI VIA B E M Path: JBU2369 => Route is: A, E, B, M, M, calculate time: 0.04760742s So once again the path does not repect first taxiway B before deciding to go all the way down to E before using B. I thought that I need to give path of every taxiway from A to runway 9 so I tried: JBU2369 RUNWAY 9 TAXI VIA A F B E M Path: JBU2369 => Route is: A, E, B, F, M, M, calculate time: 0.09545898s I gave A then F then B then E so why does the pathing calculation puts E and the next taxiway? So tried first crossing taxiway: JBU2369 RUNWAY 9 TAXI VIA F B E M Path: JBU2369 => Route is: A, E, B, F, M, M, calculate time: 0.1096191s So once again why is it not using my order and put the first taxiway a F? Why is the pathing prioritizing E? I noticed similar issues at KLGA and KLAX. I end up burning so much time trying to get one plane on the correct taxiway that everything gets stacked up. I understand if I gave the command to taxi ECHO, BRAVO, FOXTROT, MIKE I should get the path above but I did not issue that command. I know FeelThere is on vacation this week so I will probably bump this when Vic and crew return. Anyone else running into this issue? once again output_log.txt

The arrow is facing the correct direction as it shows the direction that the wind is moving. The issue is airplanes need to fly into the wind when taking off and landing. Most commercial weather displays either use a dot or the arrow points inward. Here is an example wind at 266 degrees:

Dang, you gave away my secret...and I forgot KMCO... :)

Let me throw out some nonsense: KSFO, KMIA, KEWR...

hartleecub, You need to get our more. ATControl-Joe is a great Youtuber who is taking his own free time to create some new schedules and he is making them available to the community for free. The developers of the game (FeelThere) and associate Companies (Nyerges Designs and Sim Smith Design) have their name in official developer posts. ...And a thank you to ATControl - Joe for the schedules. I have enjoyed them.