crbascott

What is the name of the installation program you are running?

LX is the IATA code for SWR. I already included it.

@nyergesdesign failed to include it in RC for KSFO. The following are liveries that need to be added to RC for KSFO to match up with the RT schedule: B773_lx B77L_ba A343_sk

Gary, recently I had an occasional loading issue with stormy weather. I have found turning off Reflections in the graphic settings has solved my issue.

Ariel, that is NOT the correct install location if you have Tower!3D Pro.

Wow, Joe, just thought I'd add some "food for thought". Leave it to you to be closed-minded and bash constructive discussion. Joe, I am a programmer myself. The schedule is data ... it is not code. It is a programmer's responsibility to logically ensure every situation is taken care of. I personally don't think that is possible given the variety of airports layouts and thousands of scenarios. You mention a lot of theory and even brought up having "no clue" - and then you say it can all be accomplished "with a simple modify of the current code". I'm sure Vic and Gabor would agree that this is laughable. I agree my idea is not custom schedule friendly, but that is irrelevant in my opinion. But then I don't have a YT channel that relies on my custom schedules. Besides, being a programmer, I have automated the current schedule making process - it only takes me a couple of hours and that's just to do some manual tweaking for playability. I would simply modify my existing code if FT decided to go down this route. I'm surprised as a real life programmer you haven't and wouldn't do the same. FYI - my idea is not unique to the aviation sim world ... "straight insanity" already exists. Again, due to my several years of programming experience, I'm just providing out-of-box coding alternatives. I don't care which route FT takes, as long as works. :)

Another option is less reliance on code and more reliance on the schedule. Below is a simple conceptual example of a schedule file. Orig,Dest,Flight,Time,Activity,Tail#,Gate/Location MUC,ATL,DAL131,14:52,A,N1234,A20 ATL,ATL,TUG100,15:52,T,N1234,HANGAR1 TPA,ATL,DAL1373,16:00,A,N5678,A20 ATL,ROC,DAL1584,16:58,D,N5678,A20 In this example, we no longer need a terminal file because the gate is assigned by the schedule. We would now need an inventory of tail numbers for each airline that would bring up the appropriate plane type and livery (this would also allow regional airlines to fly with different colors). In the example above, DAL131 is scheduled to arrive (activity A) at 14:52 at gate A20. N1234 is a 763. N1234 is scheduled to be towed (activity T) to Hanger1 at 15:52. DAL1371 is scheduled to arrive (activity A) at 16:00 at gate A20. N5678 is an M90. DAL1584 is schedule to depart (activity D) from A20 at 16:58. This could possibly eliminate the need for loading 8 hours of flights and determining restarter planes. Obviously more thought would need to be into this, but I think it is a viable alternative to adding more complex coding. Although, we'd still need progressive taxi for added realism and to be able to "park" a plane somewhere while it's gate is occupied. Craig PS - It would probably be nice to not have to specify the gate to incorporate randomness, but I added it to "reduce code" . :)

I'll relay the message to Chris. However, I am aware of the ICAO airport naming conventions ... just haven't seen any "hot" hints for those that begin with L ... yet! Craig

I'm pretty sure the European airport is going to start with an E, the Canadian airport with a C, and the Australian with a Y. That's as much as I'm going to guess. :)

Vic, The issue is on the installer side. When you download RT for Tracon you get Tracon_RT.zip. Inside the zip file are Tower2011rt-sp2.exe and Tracon2012rt-sp2.exe. Neither one of these installers installs a schedule file (schedule.txt). The screenshot below shows what gets installed in the databases folder. The installer needs to be fixed. Craig

Kev M, Using pure flight data it is basically impossible to tell the difference between cargo and commercial. So, without a ton of airline/airport specific knowledge this would be tough to implement. In lieu of made up ICAO/IATA codes (which I can tell is undesirable by both FT and ND), maybe adding a field to indicate commercial/cargo in the schedule could be implemented but again this would take a lot of work on the schedule making side. No matter what, it sounds like a wish list item for a future version. Craig

Kev M, I did something very similar for Tower!2011 because I wanted KDFW to operate more realistically. This worked fine for this confined situation and the fact that we had the ability to customize liveries & airports/gates. However, for Nyerges to implement this holistically would be somewhat unrealistic as to the hundred of airlines involved - including the massive number of livery updates needed. Also, for "real" traffic/color to have a bunch of "invented ICAO & IATA codes" kind of goes against the purpose of the products. Furthermore, without gate specific assignments we would still be lacking in the ultimate goal of realism. Craig

Real Traffic updated landing distances several releases ago, but there has been no update to KLAX that I'm aware of.

This thread may help you.

KMCO is not the next one out. Plus there have been mentions of European, Canadian, and Australian airports. All of this has been shared on the forum by FeelThere.

Hmmm, hints seem to indicate otherwise.

Do you have Real Traffic sp6v5? Looking at your log file - the terminal and schedule file you are using is not what was released by Nyerges Design. Also, you are issuing the following command RUNWAY 28R CLEARED TO LAND HOLD SHORT OF TAXIWAY T. This is not telling the plane what exit to take - it is telling them to hold short of this exit. I personally don't use that command because it really has no affect on the plane. If you want a plane to exit at T you need to issue a CLEARED TO LAND command followed by an EXIT AT TAXIWAY T command. KSFO's SP1 should not affect KLAX at all. Do you have Tower!3D Pro version 3.3c?

The loading stall at 63% is due to the full schedule more than likely. There are a couple of flights with missing commas: CLT, BOS, 321, AA, 1806, 20:15, 12:00 1, AA BOS, LGA, E90, AA, 2147, 12:00, 13:29, 1 AA

The SP is only for KSFO. What are your system specs? Do any of those airports load after a reboot?

Wayne, it was released yesterday. You know FeelThere, they like to do a quiet release and then announce it after a couple of days. The SP addressed most, if not all, of the SFO bug reports. Craig

This is a new problem so it really should be in a separate topic. Without a log it is pretty much impossible to tell what your issue is. FYI - I started the sim at 3:00 and got KAL214 as my starting flight. I started the sim at 2:00 and got AMX1665 as my starting flight and was able to send voice commands without any issues.

The current installer is Tower3DProSP33c_installer.exe, so you do not have the current version. Where did you purchase the sim from?

LOL - I'm sure we'll find something to talk about.

09:00 (41 arr, 40 dep) and 19:00 (45 arr, 36 dep) are the busiest hours using real traffic.

Geez Wayne - you just don't let up do you. I don't have a very powerful system and I did have issues with KSFO. But all the other airports mentioned above work fine for me in stormy weather. So, maybe there are other mitigating circumstances involved here - not sure I'm ready to call it widespread. But, of course, you're welcome to disagree. ;)