DeltaVII

Another wish: Compile the different wishlists into one single list that by our replies (via quote) we can vote either in favor or against for each single item you think you can include in XX... 😉

I found a method for me to fit departures between arrivals. My rules are: (A1 = landing aircraft, D = departing aircraft, A2 = approaching aircraft) - The latest moment to issue LUAW is when A1 crosses the threshold and A2 is six miles out. - Better include another mile for safety. - For every Heavy or A321 in the equation, add 1 mile. - For every Super in the equation, add 2 miles. How it plays out: 1) B787 on 26L@M, A319 on 26L@A, A320 crossing the threshold, B738 on a 7-mile final: A319 is good to go, B787 is not. 2) B787 on 26L@M, A319 on 26L@A, A320 crossing the threshold, B738 on an 8-mile final, another aircraft on 13-mile final: B787 is good to go. 3) A321 on 26L@M, B738 on 26L@A, B777 crossing the threshold, A388 on a 9-mile final: B738 is good to go. 4) A321 on 26L@M, B738 on 26L@A, B777 crossing the threshold, A388 on a 10-mile final: B777 is good to go. 5) A321 on 26L@M, B738 on 26L@A, B777 crossing the threshold, A388 on an 8-mile final: no departure inbetween. 6) A319 on 26L@M, B738 on 26L@A, A320 crossing the threshold, A310 on a 13-mile-final: First B738, then A319 are good to go.

I knew I forgot something. Something important: CANCEL TAKEOFF CLEARANCE (and following procedures) This is for the rare cases when the pilot (of a plane spinning on the threshold ^^), the controller (or his speech recognition ...) messes up (or it is one of the intentional mistakes I mentioned earlier, like at Kennedy in 2017 or at Midway in 2015). One aircraft on short final, another one on the runway with takeoff clearance, and you think that this might not end well. So you instruct the landing aircraft to go around, but if the departing plane takes off, this will be a close call, so you need to be able to cancel the takeoff clearance to get the departing plane to abort the takeoff, if possible, leave the runway, probably have the brakes checked by the fire brigate (this could be one of the emergency scenarios mentioned by Craig and Andrew), and return to the gate or to the runway, depending on how fast they were already going.

CUSTOMIZABLE COMMANDS As progressive taxi will be included in XX, it would be nice to be able to customize the set of commands. While it makes sense for beginners to say the full command, the reality is a little different. So it would be nice to use "DELTA 2489, CROSS 22R, LEFT ALPHA, SHORT JULIET" instead of "DELTA2489, CROSS RUNWAY 22R, TURN LEFT ONTO ALPHA, HOLD SHORT OF JULIET". PUSHBACK ONTO TAXIWAY CLEARANCE If you've ever listened to Kennedy Ground, on terminals 1 and 7 there's the need for bigger jets to push back from the ramp onto Alpha. In the current version the tugs just pull them out of the alleyway onto the taxiway without clearance (for example at KLGA's Terminal_B_B - I've had a crash that way, and I don't like it; it happens at JFK on M, too). So this is a common occurrance. It is realistic. So when the push (and only the push itself, not pulling the aircraft after the push!) starts in a ramp and needs to enter a taxiway, the clearance should be explicitly contained in the request and directed at ground ("GROUND, DELTA 2489, REQUEST PUSHBACK ONTO ALPHA"). The clearance has to include it, too, of course ("DELTA 2489, PUSHBACK ON ALPHA APPROVED, FACE NORTHEAST"). AUTOMATIC RAMP CONTROL / CALL WHEN READY TO TAXI This is connected to @Avwriter's request for automatic position handling in single player mode. When playing ground (or in a combination with tower) it can be a pain in the prolongation of the back to handle push requests in the ramp and have the aircraft standing at the position in the ramp when ready. I would appreciate, if there was an option to handle the ramp automatically from the push to holding short of the first main taxiway. This would allow for a scenario like Kennedy where the planes ready for taxi call from the alleyway short of ALPHA (even in a row). Exception: when planes need to push onto a taxiway (see above). OPTIONAL BLOCKED RADIO At default, it could be off. When switched on, when two or more calls on the same frequency occur at the same time, you don't hear anything but beeping. In this version, you can still talk over another pilot's transmission. In reality, the one that you direct your call at doesn't hear much. CALLSIGNS WITH LETTERS In the recent version, when you have a callsign like "CLX45A", the A is dropped. So when there's another "CLX45K" in the schedule, the sim interprets it as "CLX45A" and can't find the correct plane. This should be fixed in XX. (The correct callsign then being "CARGOLUX FORTYFIVE ALPHA HEAVY".) INCLUDE MISTAKES Nobody is perfect. Not even pilots. As you can see here (with the A350 being configured to leave at R, but the ATC assigns them runway 33R, so they call "we missed that one"), the pilots can "miss" an exit from the runway etc. (In the video you can also see that the A350 is assigned runway 33L as a taxiway - @crbascott's number 15 item.) Things like that. REALISTIC APPROACH AND DEPARTURE FLIGHT PATHS Just one word: Canarsie. (This includes issueing the landing clearance while the aircraft is not on runway heading.) This also means for the controller to be able to issue certain departure routes (like "fly the Canarsie climb") and the aircraft to follow it (the departure routes have to be defined in the airport manifests). SHORT APPROACHES FOR GA In the current version, the GA aircraft follow the same approach path to the runway and often get "run over" by following jets. In reality, they often are assigned approach paths with short finals (even shorter than 5 miles) and might even get a long landing request by the ATC to speed up the taxiing process. WIND INFORMATION IN LANDING CLEARANCE Well, this is self-explanatory... That's it - for now. --- Oh, I forgot something: PRM/SOIA Parallel approaches like flown at KSFO in reality.

@Pierre Simon Look into the lfpg_schedule.txt and replace "B738" with 738. [Hint for future cases: If you see something like Custom plane found: B738 NullReferenceException: Object reference not set to an instance of an object in the logfile, that's the problem. If the plane type is 4 characters, you need to find the three-letter-code (3LC) for it in the ****_airplanes.txt and replace the faulty four-letter-code (4LC) in the ****_schedule.txt with the 3LC. In case it already is a 3LC, you probably don't have the aircraft model or it's an invalid one (for example in a custom schedule - mistakes happen). In that case what you want to do is replace it with a similar model you already have in-game; just look into a schedule from another airport for a similar aircraft type - that then might stay white, if you don't have the livery in the game. Or you can substitute it with a different model from the same airline that you already have in the game.]

Just a guess: It's EK123 (also on a 77W), because according to both the custom schedule and flightradar24 there's IndiGo flight 38 to Thiruvananthapuram (TRV) shortly afterwards.

Dubai is a (if not THE) hub to connect Eastern Asia and Europe. You have arrivals from Thailand, India, Japan, Vietnam, China, Korea, the Philippines, Singapore, as well as some destinations in Africa. On the other hand, you've got departures to the UK, Ukraine, Italy, Germany, France, Netherlands, as well as to destinations in Asia like Male, Jakarta, Mangalore, Seoul, Cochin, Taipei, Hanoi, Islamabad, Kuala Lumpur. Remember: When it's 3 a.m. in Dubai, it's midnight in Central Europe, 6 p.m. at the American East coast, and already morning in East Asia. Just recently, I've seen an Emirates A380 (EK226) departing KSFO to the north overflying Yukon, the North Pole, the Barents Sea, then "suddenly" to the south above Siberia, Kazakhstan, the Caspian Sea, Baku and Northern Iran to land in OMDB. Which is a pretty unusual (and not the most obvious) flight path considering that a flight from KBOS took the "regular" route over the Atlantic Ocean and half of the EU (which today's EK226, being over Iran right at this moment, also did, while the opposite direction EK225 into KSFO takes the North Pole route).

From left to right: V, TA, [T], R, Q

Counting peas again, huh? And I appreciate that. Believe me - I was even more surprised that our banking system was able to process the transfer within a day. In the past, this whole process took much longer...

It is off. I mean, it's not like you couldn't see it from the orientation of the field in ADIRS alone... UAL1193 lined-up and waiting on 26L with a recorded heading of 284 (see left corner): UAL1193 airborne after giving the instruction to fly the (according to you) true heading 261 (upper right corner): Bonus: This Korean 777 is also a little off the line after arriving at the gate... could that be 23° off?

Uhm, by the way... Why are the runways - although being not only named 08L/26R and 08R/26L, but also oriented at 080°/260° - oriented at 284° in-game? Because when I issue a go-around, my follow-up instruction is always 5 degrees to the outside of the airport, so they almost maintain runway heading (which is the normal procedure) until they passed the airport. But when you say: "XXX1234 turn right heading 265" they will almost make a 360, won't they? Because orientation-wise, 265° is LEFT of the runway... Or is 360° also turned 14 degrees clockwise?

I bought it this evening. And I just made the payment. That hopefully gets processed by my bank and by Commerzbank on Friday. Which means that BMT will have it on Monday, if I'm lucky (if not, it's Tuesday or Wednesday, and if I get f****d up the a**e by that partly state-owned mess that's called Commerzbank, the payment will be made next Friday, because next Thursday is a national holiday). And then I'll get the keys and download links. Believe it or not: When FeelThere publishes on Monday or Tuesday, I can start controlling the new airport on Wednesday or Thursday.

On a f***ing thursday again, so non-Steamers will have to wait a week for their payment to be processed... *sigh*

Thanks for letting me know to never ever fly with Southwest. It's frustrating how basically nothing was learnt from Colgan or ValuJet, but it also explains how the FAA could let Boeing basically self-issue the air-worthiness certificate for the Max 8... (Context)

I noticed that, too, but I thought it was somehow a feature. However, it occurred to me mostly with engine noise from aircraft parking next to the tower at any weather, like the Delta ramp at Kennedy or the Terminal 3 gates E15, E14, E12 at McCarran.

I pronounce it "Voo-a-ling". Although that's not how you pronounce it in Spanish, but this is an English engine, so...

The game automatically assigns flights from the schedule to terminals, if there's not assignment for that airline at all. So just distribute the airlines from 1B and 1C to other terminals. The game does read the data correctly - if all those data are correctly formatted by the one making them. However, it stops loading when the schedule contains an aircraft unknown to the engine, because it's not in the respective airplane file. Like the BCS3 missing from Joe's KBOS airplane file. Mistakes happen (especially when you provide FREE STUFF such as a schedule that took lots of UNPAID hours to make), and if you're able to read the log file, it's even easy to fix - and kindly leave a note in the thread so the maker can fix it.

They haven't even opened a wishlist by now. So my guess is Tower!3D II will take another three to four years from now.

To a certain extent, this is realistic. There definitely ARE stupid pilots out there missing their assigned exit, and it's the ATC's job to keep an eye on it. Unfortunately, I don't think this is an intended feature by FeelThere. I have yet to find out when a virtual pilot reads back "unable to land, the runway is too short" and when he/she accepts the exit and takes the next one (sometimes on the opposite side). Yup. When I'm ATC at LEBL, there are multiple occations where I have to issue a Go-Around. Mostly in Western flow operations on 7L with A321s exiting R1 after having completed their landing short of runway 2 and creeping up to the exit with another aircraft on short final. Same goes for middle and long-range jets following a CRJ at JFK's 4R/22L. Regional jets in general are problematic, including the Dash-8s, because of their landing speeds and distances which make especially the CRJs miss most exits by an inch and creep up to the next one at 19 kts (because braking action in Tower3D is fixed by aircraft type and not calculated for the best performance to the next reachable or assigned exit). That's what I love the A319 and B757 for. They are the easiest to handle on almost any airport.

Nah, I did it the easy way: After ending the Tower3D task I took a good look at the logfile (I always start the game through the batch file) and found the error message stating that this particular aircraft type was unknown. Then I tried again. And in terms of the "more aircraft models" - he doesn't. The A220 is in the game since (I think) LEBL came out. At least, airplane_texpack16.manifest is the earliest occurrence of a livery for this model that I could find (Air Baltic, Swiss).

@Kim @EliGrim Look up in the KBOS airplane file whether you have the CS3 (BCS3) aircraft in the list. Copying it in from another airport's aircraft file did the trick for me.

I already wanted to go home, but there were two guys I caught coming out of nowhere. The first one was one of two flights from the regional airport Heide Büsum (EDXB /HEI), a Cessna 172 with the registration D-EOSG (the other was D-EFLL), registered to an aviation club and flight school called "Hanseatischer Fliegerclub Hamburg e.V." which is residing at HAM and connected to Lufthansa. The other one was a Cessna Citation Latitude (C68A) flying for NetJets Europe (a Portugal-based subsidiary of Berkshire Hathaway and a sister company to NetJets - probably better known with their callsign "EXECJET", while this European airline's callsign is "FRACTION"). This one was registered "CS-LTA" and came from Bern (LSMB / BRN). The following aircraft were nothing out of the ordinary - two A319s from Austrian (OS173, OE-LDA from Vienna / VIE) and Swiss (LX1056, HB-IPU from Zurich / ZRH), a Eurowings B738 (EW7657, D-ABKN from Heraklion / HER) and a Lufthansa "Star Alliance" A321 from the Tower!3D world out of Munich (EDDM / MUC), flight LH2070, registration D-AIRW. The only reason for me to stay was this last one that I don't see too often when I'm away from the keyboard: An Embraer 190, registration "PH-EZN", this time in KLM Cityhopper livery (flight KL1781 from EHAM / AMS). After this one, I went home for an hour to relax, until I had to leave again. Because at 16:25 was the scheduled departure time for the A380... The first departure from runway 33, however, was this Ryanair Boeing 737-8 (EI-DYF) operating flight number FR7184 to Palma de Mallorca (LEPA / PMI). Another GA aircraft, a Cessna 525 Citation Jet CJ1 (D-ICEY) going somewhere in Swiss canton Ticino or northern Italy, as far as I could find, then a Eurowings A320 (D-AEWF) to Pristina (LYPR / PRN) and the Speedbird A320neo (G-TTNF) that I mentioned earlier (now back to Heathrow with flight number BA965) departed, before Emirates made their way back home to Dubai (EK60). It's quite something to see, hear and especially feel this fat baby take off. Because 30 seconds after it passed my position behind the fence about 50 or 60 meters from the runway, a storm caught me off-guard that went as quickly as it came. I couldn't believe that the wake turbulence from this beast was so strong! WOW!

So, I was at my home airport HAM / EDDH yesterday. I even refused to listen to the web radio broadcast of my home team (Hamburger SV) playing against Aue. What was so special? Well, not this Speedbird A320neo (BAW965 from Heathrow / EGLL / LHR, registration G-TTNF) landing on runway 05. And I couldn't help but notice there were service vehicles ("Verkehrsaufsicht" - "Traffic supervision") waiting at taxiway D1 short of the displaced portion of the runway. But why? They were not waiting for this Air France A318 (AF1710 from Paris Charles de Gaulle / LFPG / CDG - registration F-GUGO). And they weren't interested in this "hearty" Condor A321 (CFG1565 from Jerez de la Frontera / LEJR / XRY - D-AIAD) either. But what was it? It was the next aircraft that appeared on the horizon over Niendorf. And it was the one that a dozen planespotters were waiting for on this Easter saturday. Tadaaaaa... "Our" Airbus A380-842 from Emirates Airlines (A6-EUS). Flight UAE59, fresh from Dubai (OMDB / DXB) on its first afternoon rotation since the A388 started serving EDDH on October 29, 2018. "Funny" fact (not so much for me, to be honest): When this gentle giant of the skies approached runway 05, three minutes before touchdown, it flew right over the arena where Hamburger SV (who have "Emirates" as their main sponsor on their chest!) was playing one of his key home matches - and just at that moment it flew over the roof of the stadium, HSV's goalie failed to do his job and allowed the opposition to score the lead, as if he way busy looking at the A388... I wish I was joking - but that really happened. Right after the A380 passed, the two service vehicles entered the runway, like they always do after every landing and every takeoff of the A380 to check the runway for FOD before the next landing. So, effectively for this little, but to some Tower!3D players quite well-known little guy: The Vueling A320 (EC-MVN) coming from Barcelona (LEBL / BCN). And, of course, for general aviation aircraft like this Piper PA-46-500TP (N308ST). I don't know where it came from, though. It might have been Mönchengladbach (EDLN / MGL) where it seems to be based. Less exciting: Flight LH16, a A320neo (D-AIND) from Frankfurt (EDDF / FRA).

Yeah, T3D does grill the GPU, even when paused and/or escaped. So you better keep the fans clean at all times.

Forget the two WOW Air Neos - the airline has ceased operations. https://www.flightglobal.com/news/articles/wow-air-ceases-operations-and-cancels-all-flights-456970/