CL30

You can do this now. You have to give the plane a HOLD SHORT OF clearance for either a runway, or taxiway, that's on the OTHER side of the runway you want it to cross. At LAX, for example, the plane lands 25L. You want it to taxi across 25R without stopping. Give it the taxi routing you want it to take. THEN say "HOLD SHORT OF RUNWAY 24L" and it will cross 25R. It doesn't matter where on the airport the plane is going to, you just have to give a hold short command for some runway/taxiway off in the distance.

Lol! Nah, just a slow climb. Very, very slow climb! Had to burn a bit of fuel off to get up there.

Not really pics OF planes, but it's not every day you get to FL470. The winds were nasty yesterday, my friends. Only 99 knots yesterday up there....they were as high as 160+ knots during our climb to FL400. Went way up to get us home. I didn't fly this leg...I got the one going out with 160 knots straight on the tail!! lol My phone just did not do the sunset justice. It was beautiful! It's a bit wavy from distortion of the windscreen.

Since we're on the topic of aircraft performance, maybe someone could address the *cough* insanely slow *cough* acceleration of some of the corporate jets on takeoff. You'd think they were a 747, lol.

Sorry for not getting back to you quickly enough, but glad to see others have!

No problem, thanks!

No problem! Let me know if you need anything else, thanks!

Found it. I have SP1 for KPHX. @FeelThere Ariel

Thanks, will check...

Ariel, I don't know how to check which version of PHX I have, but I just bought that airport very recently (first or 2nd week of September, I think), so unless there were changes since then, it should be the latest version. Yes, I get weird things happening every time I play PHX, but usually only at the Southwest Airlines terminals. This morning I gave the same taxi routing as above (Delta Sierra Echo to 25R @ E12), and this time the plane never taxied down Delta, it just made a hard left turn onto D10 or D11, whichever it was sitting next to, and taxied to the runway. The problem has been present as long as I have owned PHX, which is only a few weeks.

Lol!

This is my first bug report; really hope I'm doing it right, lol. I ran the game using the .Bat file and have the Output_Log attached. It's a YUUUUGE log file though...and I don't see any of the planes I was working. The date of the file actually shows a few days ago, so maybe I'm not doing that part right. Game version is SP 3.3c PHX, RT and RC should be the latest releases. I just installed PHX a couple of weeks ago (updated RT the same day, and purchased RC even more recently) , but not sure how/where to find version info to check. Description of problem: I assigned SWA 1431 a departure from 25R at E12. Original taxi assignment is taxi via Delta Sierra Echo. I did this to accommodate AAL 460 and AAL 925, and allow them to pass. I then gave SWA 1431 a Hold Short of taxiway D11 command. Once the AAL flights passed, I gave a new clearance to taxi via D11 Echo to the runway. This is where problems happen. In this case, SWA did a series of turns (in reverse) through the end of the terminal. It then backed all the way up the alley between two terminals, stopped, and then taxied normally via D11 and Echo. In the past, I have seen various aircraft do so much as to back up all the way across runways! (Pics added below, but no Output Log from that day) These pics show SWA as it was backing up, and then turning onto Echo like normal. Pic #1 shows the plane inside a terminal (ADIRS) Pic #2 shows the plane backing up the alley Pic #3 shows it after taxing normally via D11 and left onto Echo. It seems to be a problem for the game if you taxi aircraft West on taxiway Delta, and then a left turn onto either D10 or D11 and onto Echo. I've had many, many problems of 360s, planes not making assigned turns, or weird reversing across the airport in various directions like these cases. Below you can see SWA 1684, which was given similar taxi routing, had done a 360 in reverse, and then backed itself across Delta, Echo, the dirt, Runway 25R, almost hit a departure aircraft, the dirt, and only stopped when I gave a Hold Position command. output_log.txt

Well, it goofed up again...

Ok thanks. Of course, now that I'm playing again and trying to re-create the bug, it's working fine...so far!

Did I read somewhere that I need to delete the Output_Log prior to initializing the game? I was going to post an Output Log for a bug report (KPHX), but it looks like it has TONS of data in it...data from planes not even controlled in the game I just played. Just it just keep a running tally of all the games I've played?

No problem at all, really! I know what you mean though, haha! I have to read, re-read, and re-re-read my posts anymore because I go off on the most random tangents sometimes. No harm, no foul, and I'm always happy to talk aviation! 😁

I think I get what you're saying now, and yeah, maybe it is controller preference?? I really don't know that side of it, unfortunately. You're right about the departure frequencies being split depending on direction/procedure though. It could be that they keep saying the frequency to contact as a means to "help" the pilots out and not get confused on which one they should contact. Hmmm...

Thought I'd throw this out as well since many of you like to listen into LiveATC! If you're listening to the Clearance frequency and you don't hear a lot of airlines, cargo operators, and some GA aircraft calling for their clearance, it's because the system is changing. Many aircraft are now capable of PDC (Pre-Departure Clearance) or CPDLC (Controller-Pilot Datalink Communication). I think I got my acronyms right, lol. Both of these allow pilots to receive their clearance, digitally, from ATC without ever needing to contact them....and tie up the frequency! You might simply hear "United 1234, information Alpha (ATIS), squawk 5521." With CPDLC, pilots and controllers can exchange information, flight plans, requests, etc. without having to verbally talk to each other. It's really only into effect (USA) for departure clearances right now. Starting next month, they'll begin to implement this stuff across the country for in-flight purposes. Really cool stuff, actually. CPDLC/FANS 1A is being used across oceans already, so planes flying across the pond don't really need to verbally talk to anyone unless the data stuff fails, or they just think a verbal request would be easier. So, back to my point, you may not hear a lot of clearances read for every aircraft. A lot of GA airplanes will still be getting their clearance verbally for sure.

Typically, most aircraft departing from a large airport like LAS will be flying a SID (Standard Instrument Departure procedure). On these SIDs all kinds of information is listed, and that often includes the Departure frequency for their route of flight. Aircraft receive their ATC Clearance ahead of time, prior to taxi. The clearance includes such things as the route, altitude, headings, frequencies (departure), and the "squawk code" for the transponder. Sometimes the clearance can be incredibly brief and may not include everything because a lot is given on the SID... For example, a clearance from LAS might be something like: "N123AF, cleared to Los Angeles International airport via the BOACH8 departure, Hector transition, Climb Via the SID, expect FL280 in 10 mins, squawk 5521." No initial altitude was given because a "Climb Via SID" clearance was given. The SID has a "Top Altitude" of FL190. The aircraft is cleared initially up to that altitude, but it must still comply with the altitudes listed during the climb out. No frequency was given because the frequency was listed on the SID. Clearances can be long, or they can be pretty brief. But to answer your question: if the tower is giving a departure freq, then it could have been a last-minute change; maybe a change in departure routing, or maybe the airspace is so congested they're opening up additional frequencies for workload management. Doesn't happen all the time, but it is certainly common for that to happen. Usually they'll give us the new frequency prior to takeoff, but it can happen both ways.

Oh dang, you're right- he sure did! Sorry, I was reading the link that Hexzed posted, which had pictures of how to break everything out in the directory. @Roger_H, thank you as well! 😁

Hexzed, you're da man! Thanks so much, working perfectly now!

Hey gang, So I just bought my first RealColor (PHX). Can't figure out where it needs to go. My game is installed to the Desktop...it's the only way I could get it to work right. As a result, I have to manually place the files where they need to go, but I can always get new airports, RT, and schedules to work fine. RC has me confused though. It appears RC has two files: - airplanes_texpack10 and airplanes_texpack10.manifest It looked like the installer wanted to place them in Extensions > Airplanes, so I copied and placed both in the Airplanes folder, but I still have white planes at PHX. I also tried placing the files in the PHX Airport folder with no results. Where do they go? 😵

There are often several "Ground" frequencies at large airports. Typically, there is a frequency for each side, say North and South (same with Tower freq's, often several), and there are also "Ramp Control" frequencies as well. During slow periods one controller may work a lot of the surface control, but it's definitely split when busy. I agree, it's not too realistic and VERY, very busy/tough to manage at peak periods at the large airports, but it is what it is. Still fun though!

A soggy day at KIAD:

I guess I stand corrected, lol! I didn't pay attention to who released it. 😯