crbascott

Without the ability to zoom in effectively we can't use our eyes as much as we'd like, hence the need for both controllers to see the successful message - which is critical for crossing runway configurations.

You can use the sector editor and choose whatever waypoints/navaids you want to display. Details on how to use the editor are in the manual. Maybe sure to backup the original sector files just in case. In the above screenshot you are zoomed in rather tightly so that may be a factor also.

True, but the sim basically treats high speed exits and other exits the same. Planes exit at 19 knots and then always come to a complete stop prior to taxiing to the ramp. If I'm not mistaken, @Ripskin is sharing a commonly voiced opinion about Pro that planes exit too slow and that the stops either shouldn't occur or occur too soon when compared to reality. If you are interested in details on how the sim handles landings and exiting the runway, you are welcome to check out the following posts: https://forum.simflight.com/topic/85171-tower3d-pro-anatomy-of-a-ksfo-landing/ https://forum.simflight.com/topic/84430-tower3d-pro-anatomy-of-a-landing/

Can you provide a screenshot of what you are talking about? That may help users provide options for you - if there are any.

Dan, I would just recommend providing your own airlines file rather than instructing people to modify the real traffic file. I do this and so does Joe. When someone plays your schedule they use your files. When they go back and play the RT schedule or another custom schedule they can replace yours with the appropriate files. Straightforward and simple. Craig

As I said before it's all about gate availability and how the developers have chosen to load/handle eight hours of flights. The other error message would be more applicable to departures. So stupid, eh? Based on your years of development and aviation experience, the floor is open for solutions.

Below is a response to another post of yours that covers your question. I'd suggest patience. https://forum.simflight.com/topic/85405-kmco-is-out/?page=2&tab=comments#comment-516856

It's all about gate availability. You'll see messages in your log file like no free terminal and Airplane dropped, no declared terminal. I've explained how to get around this issue in a previous post. @Braf123456Please update your post immediately and delete the schedule file. This is from Real Traffic and should not be posted on the forum - it is not freeware!

I get this message too but have no issues.

As of this minute, I still get the original version when downloading from BMT Micro.

Assuming your installer is KJFK_for_Tower3D_4.2a.exe then you have the current version. I believe all the troublesome gates/pushbacks (i.e., get stuck or collisions that cause point reductions) were corrected with the last release. However, I still do see a crazy pushback every once in a while but they are basically harmless at this point.

Development has stopped on Tower!3D Pro. No, to directly answer your question. The best solution is to NOT use a full 24 hour schedule - use what I call schedule snippets. I explained this concept when I released my custom schedule for KJFK - https://forum.simflight.com/topic/84721-custom-schedule-for-kjfk-~-by-crbascott-~-bonus-files-included/

This partial log file only covers 9 seconds of your session. Nothing can be determined from this.

@C Bravo, the installers for airports released by FeelThere default to 3D instead of 3D Pro which can cause issues/headaches for Pro users. I'd recommend starting from scratch: Uninstall everything. Make sure the 3D and 3D Pro folders are removed. If worse comes to worse, just delete them and their contents. Reinstall the base sim - it should create and and install everything in the Tower!3D Pro folder. Install RT (Real Traffic) - there is only one RT DLC and the current version is sp6v7. The installer will ask you what version of Tower you have and will provide the correct default installation path. Install your airport add-ons. It is very import to make sure and change the install path to Tower!3D Pro. Install each of your RC (Real Color) add-ons. Again, the installer will ask you what version of Tower you have and will provide the correct installation path. After completing all this you should be up and running and you should only have a Tower!3D Pro folder. Good luck!

Kansas City is KMCI, I assume you are referring to KMCO which is Orlando. All the airplanes files should be updated, but if you see an airplane type in the KMCO or EDDM files that are not in the KLAX file you can add it. Now whether there is a livery available for the airline you want is another question.

You need to find your original confirmation emails. If you can't find them you'll need to contact BMT Micro at orders@bmtmicro.com or cservice@bmtmicro.com.

Verify your airplane types - all the valid values are in klax_airplanes.txt. I noticed a few values of 306 - which is invalid. I assume you want to use AB6.

@andredragtI believe you are referring to the following post: https://forum.simflight.com/topic/85171-tower3d-pro-anatomy-of-a-ksfo-landing My recommended strategy helps but I do agree with @cl30 that KSFO is still very difficult to run using the normal runway configuration.

You should definitely see an output_log.txt file in your Tower3d_Data folder. If not, you probably need to adjust your permissions on the Tower!3D Pro and subfolders for Full Control, Modify, and Write.

Firstly, caps off if you don't mind. Secondly, you need to pay close attention to the install path of the KJFK add-on. I believe it defaults to Tower 3D. You need to make sure you change this to Tower!3D Pro. Tower!3D Pro gives you TIST, KPHL, and KLAX with fake airlines. Real Traffic gives you real airline traffic with callsigns and airplanes. Real Color (or the variety pack as you reference it) gives you real life liveries for real airlines. Enjoy!

I would recommend playing a session using an airport with GA traffic at a time where you would expect to see GA departures/arrivals. After the session post your log file on the forum - in your case the file path and name should be A:\Program Files (x86)\Steam\steamapps\common\Tower 3D Pro\tower3d_Data\output_log.txt. The log file should tell us what is going on with your GA traffic.

Criticism is always easier than constructive solutions. How would you have the commands work in the next version of Tower?

It is explicitly stated in the manual there is no difference in the TAXI TO APRON, RAMP, TERMINAL commands. https://www.atcsuite.com/tower-promanual

I don't have that problem and I don't know what you did exactly, but it might be best to wait for a developer solution.

Undo what you did. Does the problem go away?