MJKERR

Excellent, that is great news What about graded stands based on aircraft type? For example at heathrow (not sure if this applies elsewhere) L,R, so two aircraft can use A single large aircraft then occupies the entire stand (central)

I would like to see an option to add a random aircraft from an airline fleet (type) Not sure how this could be applied For example some routes use A319 : B737 B777-200 : B777-300 : A380 B767-300 : B777-200 The flights rotate between them

The schedule file currently uses the two letter code Increasing this to three letters gives an optional letter

BA is normally BAW An additional letter is added I use E Europe Terminal 5 S Europe Terminal 3 W International Terminal 5 T International Terminal 3 I A380 Terminal 5 U A380 Terminal 3 I use a similar techinque for separating out Passenger and Cargo flights and their liveries, and again the stands they should use One example of this is a restriction on B747 cargo aircraft at Terminal 6 / Cargo

Not sure about this latest Holiday Sale I want to add two airports Real Color, but it is just four aircraft that I gain

I think I have had my first Go Around Delta B764 arrival on runway 27R Cleared to Land, as required However, when it visually appeared it was higher than normal It passed over the runway and continued on the same heading As a result I instructed the departure on the parallel runway to turn left 45 degrees, to avoid any chance of a penalty The Delta did not make any communication It never reappeared for arrival

I agree, this would probably be easier, and applied as required Some of this already exists, so just separates out the liveries Schedule format : GVA,LHR,320,BA,725,11:00,11:00,0,BA Origin, Destination, Aircraft, Airline livery, Flight number, Arrival time, Departure time, Unknown, Airline In my modified version of 2011 EGLL I can allocate this flight to any stand or range of stands, as the terminal file has all the stand numbers I can also apply any regional livery, if required as it is the fourth entry So this can become : GVA,LHR,320,BAE,725,11:00,11:00,0,BAE This is still a BA725 flight, but now uses British Airways Europe livery and will use a stand allocated BAE Another example LAX,LHR,388,BAU,269,11:00,11:00,0,BAU This is a BA269 flight, using British Airways A380 livery and will use a stand at Terminal 5B or 5C, suitable for a A380 Airline or livery : XXz The Airline codes stay the same, XX The second component, z, allows 35 combinations, A-Z plus 0-9

Have you been able to run the program in the past? When did you download and install? Have you tried a full uninstall and reinstall? What is the computer specification? RAM / VRAM / processor

Wow, what a difference My previous problem / issue with the FlyBe duplicate aircraft has also disappeared Such a shame we never noticed at the time I have now used 5.0 hours as the standard schedule (06:00, 10:00, 15:00 and 19:00 start times) It looks as if I might be able to remove the need to use remote stands as well!

Apologies, was referring to Ground controller at Heathrow I have been there twice, and there are training videos available on-line (if you watch the one on YouTube the ground controller does not even look out the window and watches the screens all the time) It is quite sad that about 60% of the view is to screens, but they are advised where possible to compare what they see to what is actually happening outside

My opinion is that the controller is an a static position, so there should only be the single panoramic view You can zoom in / out, as controller quite often use binoculars For many controllers they ironically spend slightly more time looking at the control screens and strips, rather than the overall view There are times when aircraft go out of physical view, so the use of the radar view is required

eeek, never noticed that! Limit for operators at EGLL is 2 hours, followed by a 30 minute break That was what I was using I did complete one shift from 07:00 to 10:00, that was about the limit of what is physically possible!

I have been looking into this a little more, as I would not mind adding a few VIP flights to my EGLL schedule I pretty much ignored it as in the last two years I only saw one such flight Equally, the VIP charter flights one of my employer uses does not use Heathrow! My friend at a local VIP passenger courier company has helped further VIP charter flights use stands 430 to 432 between 07:00 and 21:00, or stands 449 to 457 at any time Between 21:00 and 07:00 stands 449 to 457 are used instead Passengers arrive at Royal Suite, Terminal 4, the Dnata building or Signature Flights It is preferred that passengers are dropped off at Terminal 4 However, many prefer privacy so use the other buildings As a result they all of the above require a bus between the building and aircraft Arrivals become more complicated as all passengers (except those with prior approval) MUST pass through Terminal 4 This is where the bus is used twice, first from the stand to Terminal, then onward to the building to collect luggage I was wondering why my friend often showed photos from International Arrivals, yet other times photos from the buildings I can now work out if it someone leaving or arriving!

One step forward, two steps back... When testing any changes : I run the program hourly from 06:00 to 18:00 As soon as it has loaded I pause Open the game.log file and search for dropp (dropped) If there are none, I can move forward to the next hour If there are, then I need to work out why the flight or flights are affected Yesterday, whilst checking the four stands at Terminal 4 for A380, I noticed an additional aircraft at Terminal 4 (Kuwait Airways) that was not required This was similar to the problem I discovered a long time ago with FlyBe on Terminal 2 With so many aircraft it is often difficult to visually spot an incorrect aircraft I therefore decided to go back to basics, and edited the schedule file with just A380 aircraft I then discovered two further issues! The first was the program was creating an additional Emirates A380 at 14:00 and 15:00, again this aircraft is not required The second was the program was not creating the later required Quantas A380, it should be on the stand for use several hours later I had assumed the program was loading eight hours from the schedule So if I start at 06:00 the schedule between 06:00 to 14:00 would be loaded Equally, if I start at 15:00 the schedule between 15:00 and 23:00 would be loaded These are preferred start times After several tests it looks like only four hours is loaded This would also explain why several aircraft I would expect to handle never appeared later in the day As this was now effectively three issues, I decided to uninstall all four programs (Tower, EGLL add-on, real traffic and real colours) The issue with PlaneEd has been resolved I can now get the A380 exit runways correctly However, the issue with only fours hours from the schedule loading still exists This is really odd for such a small schedule file! Starting at 06:00 - Schedule file, edited for Terminal 3, stands 301, 303, 305 and 307 : DXB,LHR,388,EK,7,07:05,07:05,0,EK DXB,LHR,388,EK,1,12:25,12:25,0,EK LHR,DXB,388,EK,8,09:05,09:05,0,EK LHR,DXB,388,EK,2,14:20,14:20,0,EK PER,LHR,388,QF,9,05:05,05:05,0,QF LHR,PER,388,QF,10,12:10,12:10,0,QF SIN,LHR,388,QF,1,06:35,06:35,0,QF Resultant game log, edited : Create airplane: UAE7 type: 388 code: 388 category: 3 class: WIDE BODY JET Create airplane: UAE8 type: 388 code: 388 category: 3 class: WIDE BODY JET QFA9 - STATE: Incoming Create airplane: QFA9 type: 388 code: 388 category: 3 class: WIDE BODY JET QFA1 - STATE: Incoming Create airplane: QFA1 type: 388 code: 388 category: 3 class: WIDE BODY JET TT: 05:05 QFA9 388 TT: 06:35 QFA1 388 TT: 07:05 UAE7 388 TT: 09:05 UAE8 388

Tested with LAX, no difference, A380 (a338.apx file) still exit runway at the same location Default 6230 feet Updated 8000 feet Tower 2011, version 4.777.995

Here is what I am trying to do... I have reloaded the default a388.apx file The first aircraft to land is QFA9 A388 on Runway 09L However it is incorrectly exiting at A8 Increasing the landing length makes no difference

All the original (installation) files have date between 2010 and 2012 Most of the textures have a date in 2016 Any APX files I update have a date in 2020

I only have Heathrow, but it should work in any of three default Tower 2011 airports I have tested in Los Angeles Again, there is no difference but it is the same file in use between airports

380.apx 388.apx They have the same configuration I have created the A350 and B787 using copies of the B757 and B767 The technique works correctly, although in these two cases I have changed most of the variables However, for some reason it does not work for A388 I am wondering if the landing speed is the issue?

Apologies, should be 6230 not 6270, not that it makes much difference This file is dated 2011

I do not use the 380 in the schedule file, all are 388 C:\Program Files (x86)\FeelThere\Tower! 2011\Databases\airplanes.txt 380 -380-AIRBUS INDUSTRIE A380 -WIDE BODY JET 388 -388-AIRBUS INDUSTRIE A380-800 -WIDE BODY JET C:\Program Files (x86)\FeelThere\Tower! 2011\Airplanes\388.apx I do have a separate folder for backups as I make amendments, but they would not work in-game as the filenames would cause errors These are then renamed and copied to the Program Files folder E:\Users\User\Documents\EGLL\Tower! 2011\Database\airplanes-2020-10-18.txt

I have noted that A380 are departing Runway 09L at the wrong intersection A8 I have updated the landing length in the a388.apx file several times but it makes no difference The default is 6230 feet I have been increasing in 250 feet increments, up to 11000 feet Any ideas?

Due to demands on stands it can vary depending on availability See the chart for Terminal 4 Stands 449 to 457, between Terminal 4 and Terminal 6 (Cargo) This also forms part of the Royal Suite building Stands 430 to 432, to the east of Terminal 4 Stands 611 to 613 on the western Cargo Apron In almost all cases bus gate is required, and in some cases these are escorted If customs is required then it can mean two trips by bus!

This is great to watch at London Heathrow during the hours of darkness However, I do not think there is enough close-up detail in-game for there to be any benefit Although you may see it during the hours of darkness Ironically, I do not play this game during the hours of darkness

I am nearly ready to release my "heavily modified" EGLL Tower 2011 version, updated to real world Schedule from Summer 2019 It has taken me some time, not helped by the many Windows 10 updates that prevented use since I first purchased this in 2019! Just by luck I am on "sick leave" from work this week, so have been able to spend some time over the last few days conducting further testing before release An on-line manual will be included, as there are in-game limitations Equally, I hope this will help with the development of the Tower XX / 3D version Revisions : One - Latest airlines as at Summer 2019, sadly Fly Be Turbo Props had to be removed as they caused crashes on the active runways! Two - Correction to Intersection S3 with Runway 27L for departures, no longer any need to send departures to S1 / SB1 Three - Sadly some fictitious Terminal 2 stands (correct when the game was published in 2012) have had to be added, but they are in the graphics, and once you are used to them they are easy enough Four - A limitation in-game is aircraft that once arrived have then moved off-stand, then returned later I have resolved this by using remote stands, and this applies to as few aircraft as possible, on Terminal 2 and 5 Five - On the plus-side, full compliance with A380 aircraft An airport chart will be included, if you also want to send aircraft on the restricted taxiways (known as A380 Ground Movement) Six A - Addition of four missing remote stands for Terminal 5A Six B - Addition of missing Taxiway Y for use by the above remote stands from Terminal 5A (in tests this works correctly but looks strange) Manual Instructions Version ONE - Runway 27R arrivals / 27L departures 05:00, 06:00, or 07:00 These all now work perfectly Version TWO - Runway 27R arrivals / 27L departures 15:00 This is still be checked and refined Versions THREE - Runway 09L arrivals / 09R departures 05:00, 06:00, or 07:00 These all now work perfectly Version FOUR - Runway 09L arrivals / 09R departures 15:00 Testing will commence shortly