DeltaVII
-
Posts
353 -
Joined
-
Last visited
-
Days Won
16
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by DeltaVII
-
-
Yesterday I had this problem at KSFO, too. Nothing had changed on my system (not even a Windows update, that was the first thing I checked), I'm using an account with administrative rights.
But after a reboot, everything worked fine.
It seems to not only impact the pilot's voices, but also speech recognition. Unfortunately, I forgot so save the log. I tried to address AMX1665, but the speech engine always understood AMX665, not matter how hard I tried to emphasize the 1. At least, I have a screenshot.
Note: I set the game to start at 03:00; according to schedule, AMX1665 is due 01:51, not 18:05. I don't know whether that has something to do with the issue or not.
-
Concerning the runway overruns, here's what happened to UAE204 (388/H) and SAA204 (346/H) on 4L:
I'm trying to reproduce the taxiway circling using another configuration.
Unsuccessfully.
-
9 hours ago, crbascott said:
J A KE B - that is an interesting taxi route. Is that used in real life - did you pick that up listening to ATC?
Not really. The J/B intersection is a pretty hard right turn, at least in Tower3D, since the aircraft moves pretty far into it, so to not let it take forever I just use the double-back maneuvre that's quite common at Kennedy to get them moving out of the way and not cause problems with other ground traffic (at least it was until August 31, 2017, if you know what I mean; tbh, that guy is responsible for me being interested in ground control and buying the game).
(Btw.: Also on my wish list for the next Tower version is requesting the ramp entry/gate from the crew.)
8 hours ago, FeelThere Ariel said:@DeltaVII, has this been happening repeatedly with the intersections? Could you verify if it happens with all A/C?
Thank you,
Ariel
For the B/F intersection I've seen it for the first time. At the B/YA intersection this has happened before with other aircraft types and airlines like Endeavor CR7 (when operating 22R@C via B D C).
-
I just played a session at JFK with KJFK SP2 and Tower!3D Pro 3.3c. There were four findings.
1) While taxiing J A KE B F with holding short of KE and F, a JBU154 began circling on the intersection of B and F after "Continue taxi" instruction at F.
2) While taxiing J A KE B D A with holding short of KE and D, a JBU162 also began circling on the intersection of B and YA after "Continue taxi" instruction at KE (the next taxiway to hold short of would have been D).
3) I had a runway overrun operating 4L for departures. I didn't catch it with a screenshot, but I believe it was BAW178 that started rotating just after crossing the 22R threshold and ran into the displaced threshold area of 22R on a full-length 4L takeoff. Normally, this shouldn't happen. As far as I know aircraft in the opposite direction are only allowed to use it for the rollout after landing, but not for takeoff, just like they are only allowed to use the displaced threshold in the direction of the arrows for takeoffs, but not for landing. (Correct me, if I'm wrong.)
-
22 hours ago, nrholland said:
Here's a copy of my desktop. There is no t3d.bat file on it. Did I not do it right?
No, you didn't do it right.
1) Put the t3d.bat that I created into your C:\Program Files (x86)\FeelThere\Tower!3D Pro folder. (NOT into tower3d_data !)
2) Now double-click on the t3d.bat.
3) Play Tower!3D and try to reproduce the error.
4) After the error occurred, close the game.
5) You'll now find the game.log file on your desktop and upload it here.
-
I know. It's just not that important.
-
By the way: I had another spin just now. This time it was WOW162 (330/H) departing from KSFO's 28R with clear weather at 12:39 p.m.. Unfortunately, the log doesn't tell anything.
(I hadn't updated to the latest 33c, though. Just for info.)
-
@nrholland If using the tower3d.bat doesn't provide a game.log file, you could try this:
Download the file attached to my post into your Tower!3D installation folder and execute it.
(The only line in it - you can check it before execution - is that the log is now generated on your desktop.)It starts Tower!3D, so you can try to replicate the errors and submit the game.log from your desktop to this thread.
-
The backtaxi thing happened to me, too. I just forgot to file a bug report.
@Peabody: For now, I suggest using the "at" instruction. "SOUTHWEST 2025 RUNWAY 19R AT M VIA C W G_3 G2 D M"
-
FoxtrotOne works for me, too.
-
Have you tried turning it of- uh, sorry, reflexes... :D
Have you tried putting it in a zip file?
-
Have you two already tried "FoxOne"?
-
On 10.3.2018 at 12:11 AM, mechajames said:Taxiways A and B don't highlight correctly and as a result aircraft ignore hold short commands for these taxiways. they do however taxi along correctly.
I can confirm, while for me that only causes major trouble when I give the initial taxi instructions to an aircraft leaving the ramp and remit it to hold short of A to give way for another aircraft. But yes, that is now a problem.
-
Actually, their blast pads do intersect. When you direct traffic via B M to the runway 9 threshold they stop at intersection J, which is the holding line for 22R as well as 9. You can see it on the diagram.
https://de.flightaware.com/resources/airport/KBOS/APD/AIRPORT+DIAGRAM
-
On 6.3.2018 at 7:23 PM, jonas243 said:
And when you want me to put them in an order regarding how much fun these airports are, it would be like this: 1.KBOS 2.KLGA 3.KJFK 4.KSAN 5. KLAS 6.KATL (at least with playing it alone)
I don't have much to add to your summary.
KLGA is indeed challenging. I took a 19:00 session yesterday with a 22 approach and 13 departure using @ATControl -- Joe's custom schedule. Problem: There were so many flights incoming on 22 that I barely managed to get flights cleared for takeoff. At the worst moment, they were lining up on P and B back behind M, about 30 planes waiting just for takeoff with an almost 1 hour delay. I should have delayed arrivals by letting them turn to 040 at the 15-mile mark and transferring them to departure just to get little breaks for takeoffs, but I just didn't think of this. (Well, at least at this point KLGA was very realistic... krch-krch)
In KATL what bothers me the most is lagging. There's just so much traffic and the vast scenery that I feel 30 minutes are like 5 hours elsewhere. That's why I don't play it much.
KPHX bothers me for the bugs like planes being pushed into the dirt, getting off of runway 26 at B7 and rolling over B so far that they almost stand on C while turning through the dirt, cargo planes rolling parallel to H through the nothingness and so on. Other than that, it's fun, as long as I use one runway for departures (25R) and one for landings (26), even when the Americans go to 25R via R and the others lining up on E. That configuration is quite simple and relaxed.
The most fun for me are KJFK and KBOS. For the same reasons as you said: lots of different configurations. I especially love JFK for it. One of my favorite configs is landings on 13L, departures from and selected landings on 13R, departures on 22R at the threshold at F. Another one is using 22L for arrivals, 22R at C for departures, 31L shortened at K for smaller aircraft departures (that are issued a left turn to 223 for the Breezy Point climb immediately after takeoff).
But I also love KBOS. My favorite config there is arrivals on 22L, selected arrivals on 22R, departures on 9, 15R (bigger jets), and 14 (for the Cape Air). But I also like a late schedule that includes a challenging runway change to night operations, like switching from 4L+4R departures/arrivals to 33L arrivals, 15R takeoffs, 9 takeoffs. Unfortunately, KBOS is not favorable for shortened operations, but the variety of simultaneous takeoffs and landings on the several runways makes up for that.KSAN is probably the most challenging to me. The airport layout is... phew. One mistake, and you really f-- mess it up.
Added 03/16/2018: ... that is until KSFO came out. I really start to hate it. So little space, so many planes to handle around the terminals. What bothers me most there is area around intersections A/F, A/J, A/E. Around that area I've had no session so far where I could avoid wingtip deadlocks. Even with 80% density my taxiways A and B are jammed, blocking outgoing traffic, and what drives me crazy is certain VRDs and SKWs exiting at L when landing on 28L effectively locking the 1L/1R crossing for outgoing aircraft. Oh, and of course incoming traffic on the 28s is so dense that I can't get planes out on the 1s. If I didn't collapse before I totally jammed the complete airport, I'd say it's worse than KLGA...
So, my order of favorite add-on airports is: 1) KJFK, 2) KBOS, 3) KLAS, 4) KPHX, 5) KLGA, 6) KSAN, 7) KATL, 8) KSFO.
-
20 hours ago, crbascott said:
It appears what I call the San Diego spin is different from yours. Mine occurs after take-off - rather hilarious honestly. Whatever you have experienced, I have yet to.
My San Diego spin happens during lining up for the runway at either point 9@B10 or 27@B1.
But I have also experienced a spin after take-off once. It's just that it happened at KLGA when taking off from runway 31@Z, but I couldn't reproduce it by now nor do I remember the flight or configuration.
-
8 hours ago, crbascott said:
I have seen the San Diego spin but it doesn't do anything to cause issues.
Except having to issue a go-around for the next incoming aircraft on short final when the spinning delays the line-up on the runway and closes the timeframe for take-off.
-
Looks like it didn't like the E2 part? If you play that exact time again, can you let it taxi to terminal via C M E? Does that work?
-
Oh, thank god! I wasn't ready for this, anyway. I'm still struggling with the default schedule... ;-)
-
On 10.2.2018 at 5:55 PM, crbascott said:
If you have a zip utility, you can zip the log file and it will create a much smaller file. I recreated your session and my log file was over 5 MB. My zip file was only 74 KB.
I know. But I don't like to distribute zip files, just as much as I don't like opening zip files from sources I don't know. They have been abused for malware way too often, and I don't want to encourage people to open zip files from a source they don't know (which is me)...
-
Relating to my post from December 23, the improved wayfinding in 3.1d did the trick getting the MD-11 to runway 8 (despite only accepting the "runway 8" instruction without taxi instructions, which leads to it taking the route "sc6, south_cargo, H, H7, G7, F, F13, E13, R, B, B2" - this means it enters the runway at B2 turning left to the beginning of the runway and making a 180 - or "runway 8 via C C1 B1" leading to the route "south_cargo, H, H7, G7, F, F13, E13, R, C, C1, B1", going all around the airfield).
There are three other issues, however:
1) AAL1061 (05:27:00) requested push and start at T_e9 and said it was ready to taxi without actually being pushed and still sitting at the gate.
2) FDX1403 (06:07:33) landed on runway 7L exiting at F9 and then didn't move an inch (with a lot of ArgumentOutOfRangeExceptions with seemingly the following aircraft in the log at 06:14:31 that span until I deleted the plane). However, from the beginning it had no-free-terminal messages in the log, if that's important. The same happened later with FDX1748 after it exited runway 7L at F8 at 07:14:22.
3) FDX428 (06:16:00) spawned at sc2, was instructed to taxi to runway 7L via H H3 G3 F F3 and then just went parallel to taxiway H in the wild starting at the first gate of that cargo area. When it went into the gravel behind the end of H, I stopped it, issued another taxi instruction at 06:20:32 via H H3 G3 F F3 and it calculated the route 25L, H1, H, H3, G3, F, F3.
I want to point out that I am in no way responsible for what the route looks like !
(Again, I had to shorten the log for size restriction, including repetitive Exception messages, since the already shortened log file with all messages inside would have been 9.5 MB. But if you need it, I still have the full log file and I could email it to you, if you provide me an address.)
-
On 5.2.2018 at 11:11 PM, Michi10 said:
2 If I want to drive an airplane from the runway direction terminal, for example, LAN XXXX Taxi to Terminal via A. It drives as I indicated, but on Terminal 8 it drives over R and S, why is that?
The same happened to me today at JFK. Interestingly, after letting ABX552 stop short of NC and instructing it to taxi to the ramp via A T, it did. Other problems were AAL flights finding the path from the E exit of runway 13L to terminal 8 via S or T (like AAL20 or AAL1280 in the log). I sometimes needed to just say "taxi to ramp", and they almost immediately found the path, while saying "taxi to ramp via B T" before - producing the same path! - did not work or didn't happen within the same time. All that while sending planes to their destination gate at NC/TA worked perfectly. Going through the log I noticed "taxi to ramp" produced a calculated route with multiple mentions of B like "E, B, B, B, T, T8_apron, T8_38" (AAL20) or "D, B, B, B, T, T8_apron, T8_40" (AAL1280). ABX552 produced a similar route from A at NC when instructed to "taxi to ramp via A T": "A, A, A, T, T8_apron, T8_32".
(Don't be surprised about the gaps in the game.log - I had to shorten it, because it was an 8-hour session, and the game.log was 14M, but I made sure to provide all lines including the flight numbers mentioned...)
-
16 hours ago, Avwriter said:
I don't know about your specific situation, but in the game, nav lights are generally on if an aircraft is preparing for an imminent departure. Thus, if an arriving plane is doing a quick turn-around, it may never shut off its lights, whereas one that is expected to sit at the gate for a longer period will shut them off.
Andrew
Even those who don't restart withing three hours of gameplay keep their lights on.
-
Sorry for "hijacking" the announcement topic.
One thing that happens since the latest update is that after reaching the terminals and shutting down, landed aircraft keep their nav lights on, which leads to the apron looking like a christmas tree after some time. Is that a wanted effect?
Domestic & Intl flights by same airline
in ATC Simulators
Posted
[OT] One more entry on my wishlist for Tower!3D 20XX... ;-) [/OT]