DeltaVII

I guess he experienced what I found (but somehow always missed for documentation): A plane missing its path on pushback and subsequently either 1) spinning around backwards trying to catch it after not being separated from the tug despite calling ready for taxi (that's a bug I found on several airports such as JFK - at the MA ramp with the two Terminal-1-side gates closest to the building -, LEBL - at the GA-side EN ramp, or at EDDM's Terminal 2 alongside W2, mostly with the Dash-8s from Luxair or Croatia), or 2) just going offroad, parallel to W2 and across the runway into nowhere (unless it hits another aircraft in the process, I guess), which is what happened once or twice in my gameplay.

Holding points at LEBL in general just seem to be suggestions... 😉

Can you add the output_log.txt from that session? The forum rule is: "No log - no bug". At no. 1: The sim can't be instructed to use a taxiway twice, which you implicitly did. If you wanted to have the aircraft departing from H, you would have to say "EZY8575, runway 08R AT H via K Q ZZ". Other than that, the only way to use H from ZZ for a full-length departure is to go back to J. But I guess taxiway H is one-way only, so to return to J the sim had to utilize G. At no. 2: We'd need a log to analyze what happened. At no. 3: 5 miles in Tower is not enough, since the line-up process already takes up 42 seconds (26L) or a little more (08R). I've done some calculations. The basic final for a LUAW and departure is a 7-mile final. If you've got three (the first landing A/C, the departing A/C, the next landing A/C) medium jets like the A320, A319, B737, E90 involved. For every Heavy or A321 involved add another mile - if the first landing plane is a 777, the next departure is a 777, and the next landing plane is a 747, you add 3 miles for a 10-mile final on the 747. For every Super involved - by which I mean the A380 - add two miles. So with the 380 instead of the 747 in my last example, you'll need an 11-mile final for the A380 to shoot the gap.

Here are my contributions, based on FlightRadar. NEO_RC Requests.xlsx

Hey, Joe, just a small one: Flight "EWE5921" (09:52, LEBL - LOWW, callsign "EUROPE WINGS 5921") is actually a normal Eurowings flight EWG5921 (callsign "EUROWINGS 5921").

I found another one. I don't know whether it's one for @nyergesdesign or @FeelThere, but I got a ghost plane... I was using @ATControl -- Joe's custom schedule when GES251 landed on 25R exiting at D5. I gave instructions to taxi to the GA apron via T, EN, S. But the aircraft remained just sitting there. However the tag was completely gone. The next aircraft, EXS231, exited at D5 - and drove right over the ghost of GES251. So did every other plane exiting on D5. There was no penalty, however, but... The log says there was a NullReferenceException, so somehow the aircraft got lost. (You can find it in the log between line 66,238 and 66,248.) And later (line 72,481 ff. - unfortunately without a picture of it) LXA251 took off from 25L, but never actually took off - it just ran over the runway threshold and went offroad. It also denied contacting departure. Must have been the SUV version of a DF9... 20190307_LEBL_ghost-plane_game.zip

You can verify what @ac455 says, if you start Tower 3D from the installation directory using the "tower3d.bat" file. After you're done there will be a "game.log" file in that directory. Open it with WordPad or a similar text editor and you will find a lot of messages stating "***** no free terminal". Those are flights on hold at a waypoint outside the aerodrome's area, if you will. Tower 3D, as it is constructed, always needs an endpoint for arrivals. You can try it out when all gates for a ramp are occupied - there will be one call for push and start and a corresponding arrival calling in shortly after. Just let the departure sit at its gate without issuing a push instruction while the arrival lands. Then try to give taxi instructions to the gate. The PIC (or his/her FO) will respond "Negative, gate is not available" and stay sitting at the runway exit. As soon as you issue the pushback instruction to the delayed flight, you can give successful taxi instructions to the arrival. As long as there's no pushback available to open up a gate, arrivals to that occupied terminal are delayed. (The solution for this is on the wishlist for the next major version of Tower, which is "progressive taxi". This means you can send the aircraft on any way to any holding point on the airfield, until the gate opens. That holding point could even be an intersection on an inactive runway, as far as our wishes go. This is what happens in real life. One aerodrome where this is a very common occurrance is Kennedy. You may have already noticed, if you know the "Kennedy Steve" videos on Youtube.)

Reminds me of when I bought Tracon, started testing my HAM sector with the default flight plan and had a flight coming in operated by an airline I used to work for (and that folded a few years later).

I'm afraid there's going to be version 3.1 soon... (same with EDDS) https://www.dw.com/en/berlins-germania-airline-files-for-bankruptcy-halts-flights/a-47359882 Looks like they're folding.

I played KLGA tonight with departures from runway 31 - they all were holding before the runway under several scenarios.

You're obviously right. Disregard my comment, @707FAN.

Does it accept an intersection takeoff from E1 or D1? I think the taxi route is too long (longer than 6 taxiways, which is the maximum T3D can handle).

My go-to airports are definitely JFK, BOS, LGA - in that order. JFK because of it's old-school layout and the madness getting the aircraft in order while having the space and taxiways necessary to do so. BOS because of the crossing runways. When I get into a flow, everything just flows. LGA because of the timing and the effort it takes to not jam the airfield. (My least favorite airports are the boring STR and STT, as well as MEM and MCO.)

Do you mean actual procedures or an airport diagram? This might help with the latter.

I had a similar problem. What kind of computer is it? Mine is a PC, and my solution was: open the case, lay it on the side, take a clean brush, carefully wipe away fluff from the fans and heat sinks, then even more carefully use a vacuum cleaner on low suction to clean up. It simply overheated and subsequently went out.

In the command panel. Do you see the green mark on the active runway? Click on the runway you want to enable as arrival runway (the button is now green), then click on the active arrival runway you want to deselect, if necessary (if it's the same runway in opposite direction, it's switched automatically).

I have an awful, but probably helpful idea. I researched your laptop. It's from 2015, so I assume you've never re-installed the OS. MS had several issues with Windows Update that could f**k up your system in a way you normally wouldn't notice. My idea is: 1. Get an external hard drive that's twice the size of your system drive, make an image of your system device onto the external drive using the Clonezilla Live on DVD or USB stick. 2. Find a tool to read the Windows licence key (Windows OEM Product Key Tool by NeoSmart, for example) and write it down. 3. Download all drivers on the MSI website (except the Nvidia graphics driver, take this from the Nvidia website) and put it on the external drive. 4. Also backup all your data (don't forget your user profile's AppData folder with it's subdirectories "local", "local low", "roaming", where your emails may be stored in unless you have a newer Outlook version running) to the external drive so you can copy your personal files back into their respective folders. 5. Get an empty USB stick, download Microsoft's Media Creation tool and configure it as an installation medium for Windows 10 Home 64-bit. 6. When you're sure you didn't forget to backup anything in the process and that every step was successful, boot from the USB stick, delete all partitions, then reinstall Windows. 7. When you're done reinstalling Windows, install the drivers first (chipset, graphics, wi-fi, network, touchpad, card reader, printers). 8. Run Windows Update to get the latest security updates. 9. Then install and configure your software, copy your backup data back into their respective folders. 10. Try running Tower and Tracon again. If anything in this process fails and you need to go back to where you are now, you can still do so by running Clonezilla and restoring the "dirty" system from the image to the system drive. It's a lot of work, but sometimes that can fix "funny" problems. (I get paid for doing that professionally for my customers - except for #10...)

I hope so. I had the same thought as @battlehawk77 ...

@nyergesdesign Hey, Gabor, I've got another thing I'd like to add to the bug list for EDDM. I just saw it while playing for one and a half hour. There's an issue with the routes from the gates to the runway. (Note: I play with my own schedule, but that should not be a factor) I issued pushback for DLH1800 from the dysfunctional middle gate on the terminal side at O3. However, the route that was calculated led from the gate next door (and not from where the plane actually stood) to the runway. This could also be seen happening at some other gates at W2, for example the gate second closest to N (in this case: LGL9732 kept circling looking for a point to dock onto the route, as it seems). This also in an earlier session sent a Croatia DH4 backwards across runway 8R/26L from a stand at W2 around D3 while "pushing back", which unfortunately I didn't catch with screenshot and game log. Screenshots and game log attached. BugReport_EDDM_DLH1800-departure-botched-gate-routes.zip

Thank you, but unfortunately you missed one detail: when landing on runway 7 the touchdown is still at the same spot, so now it is within the displaced portion of the runway before the threshold (which is not allowed).

Time for an update to my favorability list... 1) Still JFK. There's enough space to get planes in order when the sheer volume of departures messes up my field. But I have no problems working through a 1-hour backlog. I'm currently working on a real schedule from today that even includes Kape Air, Eurowings, Norwegian Air UK (callsign "Rednose"), XL Airways, although the planes stay blank. But working on my tool to create it takes up too much time, unfortunately... 2) Still BOS. 3) LGA. Once I figured out how to close the gaps it's not as dramatic as it was in March. But still a challenge. 4) LAS. More interesting after the update. 5) PHX. Challenging, but playable now. Even when I up the ante by using a 2-runway config. 6) PHL. Improving my strategy helped. 7) MEM. Yeah, the boring part is it being departure-only at some times and arrival-only at other times. But the interesting part is getting into or out of the "parking lot". 8) LAX. Rather boring when I take traffic from the southern gates to 25R and from the northern gates to 24L, and too complicated when I use the runways according to the SIDs. 9) SFO. I try to manage arrivals on the 28s and departures mainly from the 1s. I fail too often and jam up A and B. Not even works when I pile arrivals up on B short of B4 to make a turn onto A... The aircraft creeping across the 1s is a turn-off. 10) SAN. Still challenging the same way as in March. 11) MCO. Too many polygons to play without stuttering on my machine. 12) ATL. I'd need six eyes and three brains for the full volume. 13) MUC. My own schedule did the trick, but it's time to update it. And the tug issue really bothers me. 14) STT. Boring. 15) STR. Too many flaws, too boring.

To get the real callsigns, you need the Real Traffic package. To get the real liveries for EDDS you need the EDDS Real Color pack (under the condition you have Real Traffic installed). And to get the real liveries for TIST, KLAX, KPHL you need the combined TIST/KLAX/KPHL Real Color pack (under the condition you have Real Traffic installed).

Thanks for your feedback, Vic. However, there's some things I'd like to add. I know that EDDM is not your product - but by distributing it on your website, it looks like FeelThere's approval. With all it's flaws. That is different from your work for FSX where at all times there's transparency of you not being affiliated with MS at any level and no one would expect a third-party developer to be. And there's another catch to it: Customers expect a much closer cooperation of developer and designer when both are small companies. For the eye of Average Joe, both FT and ND are not distinguishable. No matter what, every product management that to the average buyer seems poorly handled will inevitably bite FeelThere in the behind. And the thing is: We pretty much enjoy Tower3D (which is why we wait for Tower3D II). Most of us can even live with the problems that come with the logical design - like fixed landing distances, no use for high speed exits and such. But that is exactly why obvious bugs (like the EDDM tugs, the spinning Deltas on the M and MA ramps at Kennedy or missing holding points at KMCO) that are kept unhandled are such a pain in the ass! It's like buying a Learjet with a malfunctioning cabin pressurization system and randomly twisted rudder axes: you can use it, you might enjoy flying it, but there are limits that don't need to be there and should be easily fixable, and new features (like the autopilot performing a barrel roll) aren't necessary as long as the product itself is not fixed. And I mean "fixed" in a you-buy-a-learjet-you-expect-a-learjet way, and not in a you-buy-a-learjet-you-expect-an-A380 way. But please see it from our perspective, too. We come home, eat, and then want relax by enjoying an hour (or two) doing what we like: play a game directing planes. We're in the flow. And - boom - there's a plane just behind the holding line not finding a way to the gate, because that gate is inop due to a missing tug. Another plane won't push back because of the same issue. Then a Croatian DH1 goes on a cross-country tour on pushback and gets pulled across the runway into nirvana. Or a plane being issued the way to a runway starts spinning in circles through the terminal structures crashing into other planes (causing a penalty when another plane happens to spawn at that exact moment). Or planes being stuck on the runway and piling up for an hour, because others landing on crossing runways creep to their exits closing the window for safe departures. Or planes taking a wild exit instead of the one they were assigned to and producing a deadlock. Or planes stopping at the last taxiway before the runway and not stopping at the holding line crashing into the already lined-up plane. Or planes spinning in circles on the threshold unable to take off while another is on a 6-mile final approach to crashing into it. Those moments are unnerving and take away the fun experience.

What Pete means is using the 28s for landings and the 1s for departures, like in reality. And what's wrong with EDDM? A severe lot: @pete_agreatguy Those are definitely airport-related bugs. (I yet have to file another bug report for EDDS, besides the obvious flaws like the missing displaced threshold, the false colors on apron markings, and the plane-ly wrong runway markings that seem to be copied from KMCO).