DeltaVII

Unfortunately, to me it is a problem. I experienced trouble at KLGA operating runways 4 (for arrivals) and 13 (for departures) when I couldn't get taxiing aircraft on P to cross runway 4 and get to runway 13, because the landing of the EDVs and others now was so late that the next aircraft was already on the short final. This happened for long enough that I had airplanes queuing on B back to M and had to disable runway 4 for landings just to get those on P and B out (which led to NO aircraft approaching anymore after switching runway 4 back on as active runway). This also turns out as a problem for approaches "next door" at KJFK (18:00). Today, I had to instruct ICE615 in approach on 22L to go around as EDV3810 wouldn't get off the runway quick enough, and after that the same happened with IBE6253 behind EDV3622, because the separation behind the CRJs is not wide enough for following traffic to get the runway cleared from the EDV. I have no problem with stressful situations, but this is a general issue with the Endeavors (and other CRJs?) now, since they now exit at J, not at H, creeping down 22L.

DELETED: DON'T HIJACK AN ANNOUNCEMENT TOPIC.

And what exactly doesn't work?

I guess the reason is the job to calculate the taxiways is not aborted when you delete the plane. It just keeps going until it finds a solution - and dumps it after noticing that the plane has been deleted. It happens when you have long taxiways and many intersections, because the game not only takes the assigned taxiways, but it calculates taxiways inbetween, in case you didn't include some taxiways. For example: A plane came off 22R at KB and goes into F. You say something like "taxi to terminal via K B G F", going into G and then turn right into F for the gates. One possible way to now calculate would be K B G Y Z F with the plane crossing 22R twice (something similar happened to me, lately, with another instruction). I always have these problems getting incoming flights in 4R. Whenever a plane exits at FB there's never a way to get it home, not even an Endevour, let alone a FedEx. 22L is problematic only for cargo flights. In general, every flight taxiing a long way on A or B takes longer to calculate, like a Speedbird going from V to 13R via B MC P PF. (That, by the way, dear developers, would be another argument for progressive taxi in the next Tower version... "left on B, hold short of MC" has way fewer calculations to make... ;) )

Hummel, Hummel ...

For the taxiway part: When you try this again, could you check whether one of the next landing planes is assigned or a departing plane is occupying the same gate as the one that's not moving? There are similar problems described in the KLGA taxi thread (also with KSAN). It might be a related issue.

I say EDDH ! ;)

Could you then please talk about including progessive taxi in the new version? ;)

I just had the same problem at KSAN, so it's not a KLGA-taxiway-F-exclusive issue. At 10:17:50, SWA4014 was given gate "T1_10" after being ordered to exit the runway at B8. But it didn't move an inch, couldn't even calculate the - short - way to the gate. The reason was obviously that SWA2573 had just spawned before at the same gate "T1_10" and was given pushback clearance at 10:15:19. It was not until I deleted SWA2573 (!) that SWA4014 could start moving. The game log is attached. And while I'm at it (from the same session), I found another bug at KSAN concerning general aviation aircraft (I don't remember whether it's exclusive to GA). I had seen it before operating runway 9, but now I also have the game log (it's the same). When issued the LUAW command, the aircraft turns a clockwise 360 before lining up. This happened with N940QS at 10:33:46 at the B1 entry for runway 27, but it has happened before on the B10 entry for runway 9, too. Unfortunately, the game log doesn't show it. I only have a screenshot. 20180115-1218_KSAN_plane-stuck_game.log

I think I found the reason just now. I had EDV3325 (CR9) standing at F at 15:07 and not moving. The following DAL986 (320) did taxi to its assigned gate from the same spot. Then, EDV3476 and EDV 3718 (both CR9) at 15:25 and 15:37 respectively both taxied to their gates at Terminal C from F without a problem. Then, EDV3431 (CR9) at 15:49 was stuck at F being assigned for Terminal C, with the following NKS922 (320) taxiing correctly to its gate. Epiphany happened when a JIA5175 (CR2) was stuck at F at 16:16 being assigned for gate C8 at Terminal B (according to the Google Maps satellite footage of KLGA, according to the game log it's "B_C4"). After deleting it, the next aircraft was UAL303 (320), which exited at F and taxied to its gate - which happened to be the exact same gate C8 at Terminal B, too! So, the "road calculation error" seems to occur when two landing aircraft are given the exact same gate. So it could be a game error (seems like the program only did a check for free gates for aircraft already sitting at the gate and waiting for departure, instead also checking whether the gate will be occupied by an approaching or taxiing aircraft). Since I'm now allowed to attach files bigger than 20kB, here's the game log. At 15:03:27 ASQ5281 is given pushback clearance at gate D6 (takeoff clearance at 15:12:49), at 15:07:26 EDV3325 is given gate D6, at 15:17:21 DAL986 is given gate D6. At 15:37:43 EDV3480 is given pushback clearance at gate D1 (takeoff clearance at 15:49:33), at 15:49:20 EDV3431 is given gate D1, at 15:51:14 ASQ5463 is given gate D1. At 16:02:06 AAL358 is given pushback clearance at gate B_C4 (takeoff clearance at 16:11:57), at 16:16:56 JIA5175 is given gate B_C4, at 16:18:18 UAL303 is given gate B_C4. (AAL358 was given the departure handoff at 16:13:20, even before JIA5175 got assigned its gate, so this seems to be insignificant. The error may probably be able to show until the aircraft leaving the gate has left the DBRITE screen and the program releases the handle on the object - which is still there even after departure handoff, as everyone knows who has experienced double callsigns/flights spawning like the AVA85 at LAX...) 20180113-0123_KLGA_errors_game.log

Actually, I remember at least one topic from the Steam community wondering why after six hours of playing there were no more departures... This one: https://steamcommunity.com/app/588190/discussions/0/1488861734115962611/

Hi Ariel, I'd love to post the game log, but unfortunately I'm still not allowed to upload more than 20 kB of attachments - and the full game log alone is 1.5 MB. Some info on my system: - AMD A10-5800K (4x 3.8 GHz) - 8 GB RAM - AMD Radeon RX 560 (4 GB DDR5 VRAM) - Windows 10 Home 64-bit - Latest Radeon 17.12.2 driver - 22" LG monitor (1920x1080 pixels @ 60 Hz) Recently, I had another crash while reproducing the situation (same situation: KLAS, 10:00, stormy). It happened after the first plane - SKW5400 - asked for pushback. I didn't even get to talking. When it happened, the last game.log entries were: (.... list of Terminal/maxknot assignments) Terminal: GA8 maxknot: 12 Terminal: T57_in1 maxknot: 34 Terminal: T71A_in maxknot: 23 start speech! Record error state: False speech db lengths: 8286 / 136 / 699 / 31483 / 2564 speech airplanes: [here comes the list of callsigns; I skipped this part] 09:47:06 * SKW5400 => ADD HISTORY: SKW5400: Los Angeles Tower, SKY WEST 5400 requesting push and start. 09:47:06 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 24R * SWA3185 => STATE CHANGE from STATE_INCOMING to STATE_INCOMING 09:47:06 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 25L * SWA3185 => ***** no free terminal SPEAK: Start speak plugin (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) RunwayToggled: 24R Clear allowed runways Add allowed runway: 25L Add allowed runway: 24R RunwayToggled: 25L Clear allowed runways Add allowed runway: 25L Add allowed runway: 24R ...... aaaaaaaand that's it again. So, it's a different situation. I don't know whether there was the very first lightning of the scenery happening when it crashed, but it could very well be. I hope it still helps. (If you need other parts from the game.log, you just need to say which and where to find them and I'll gladly post them.)

Short update on the issue: Hasn't happened the one time I tried using stormy weather, but I wasn't lucky timing the CPA push from Terminal B at C10, also, so I'll keep trying that scenario.

I can confirm, this happened to me quite a while ago (sorry, no logs; I haven't played KLGA for a while... hmmm, I probably should...), also with an Endeavor flight. Might be an issue with EDV flights, specifically.

I just experienced a game crash at KLAX after giving a Cathay approval for push. Luckily, it was only the second plane handled. Looks like a graphics engine problem to me. I had random weather (which was set to storm, obviously, since the game crashed during lightning), active runways 24R and 25L for incoming traffic, the clock set to 10:00. The game version is SP3 with Real Colors SP4 and Real Traffic SP6v3. My graphics info: Direct3D: Version: Direct3D 11.0 [level 11.1] Renderer: Radeon RX 560 Series (ID=0x67ff) Vendor: ATI VRAM: 4041 MB From the game.log: 09:47:32 alt: 0 takeoff: False/False/-1 OWNER_GROUND r: 25R * SKW5400 => Add trash roads==0 COMMAND: CPA897 PUSHBACK APPROVED, EXPECT RUNWAY 25R 09:47:40 alt: 0 takeoff: False/False/-2 OWNER_GROUND t: T104_in * CPA897 => PARSE CMD: PUSHBACK APPROVED, EXPECT RUNWAY 25R 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND t: T104_in r: 25R * CPA897 => GROUND, roadcut: GROUND, TWO FIVE RIGHT PUSHBACK APPROVED. 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND t: T104_in r: 25R * CPA897 => SAY: GROUND, TWO FIVE RIGHT PUSHBACK APPROVED. CATHAY EIGHT NINER SEVEN 09:47:40 * CPA897 => ADD HISTORY: CPA897: GROUND, 25R PUSHBACK APPROVED. CPA897 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND t: T104_in r: 25R * CPA897 => STATE CHANGE from STATE_WAITING to STATE_TO_RUNWAY 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND r: 25R * CPA897 => Start calc route from: T104_in start idx: 22 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND r: 25R * CPA897 => Calc from: T104_in CPA897 => Route is: T104_in, C10, C, C1, B, (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) 09:47:40 alt: 0 takeoff: False/False/-1 OWNER_GROUND r: 25R * CPA897 => Add trash 09:47:46 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 24R * SWA3185 => STATE CHANGE from STATE_INCOMING to STATE_INCOMING 09:47:46 alt: 6693 takeoff: False/False/-2 OWNER_TOWER r: 24R * SWA3185 => ***** no free terminal GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 GfxDevice: creating device client; threaded=1 (The SWA3185 mentioned in the log was unknown to me, it hadn't appeared on DBRITE, yet.)

I found another issue with KPHX. (Might be an issue with calculating the taxi path.) I had FDX1262 (M11/H) ready for push, so I assigned it to expect runway 7L. It returned "Unable to takeoff from this runway. The runway is too short." So I assigned it to expect runway 8, and FDX1262 repeated the command. But nothing happened. It stood at it's parking spot closest to H forever without moving and effectively blocking another UPS857, that spawned a few minutes later. It seems like it took too long for the FDX to calculate the waypoints to runway 8, since this would have been H H4 G4 F F6 E6 T C C1 B1. I had to delete the FDX to get the UPS moving - which then, after pushback, took a wild ride through the nothingness parallel to H directing 250°, starting at the FDX1262 gate (!), until I told it to hold and repeated the order ("UPS857 RUNWAY 7L TAXI VIA H H3 G3 F F3"). (I'd provide the logs, but the forum won't let me, since I'm a newbie, as it seems, who can only attach 20-kB files (the image alone is 1,633 kB, plus 756 kB game.log, plus 523 kB output_log.txt. It was around 19:50.) Addition (2017/12/24 23:36 UTC): A minor issue is aircraft landing on runway 8 that are already successfully landed behind B6 always exit at B8; none of them ever exits at B7 (which sometimes leads to a go-around for an approaching aircraft, when the two are separated 5 miles only). Or does that have a specific reason?