crbascott

Tower!2011 didn't implement the PHNL water runways and I'm fairly confident this engine wouldn't be able to handle them either. On those same lines I'm curious if/how the second runway at EGKK will be handled by the engine/airport design since apparently it is primarily used for taxiing. I also wonder if the engine can handle realistic traffic volumes at EGKK or KMIA for that matter. I'd definitely love to see these airports, but preferably on the next version. 😉

Yep, enjoy the site. Where are the landing distances? But the landing distance being used by RT is less than what you quoted. So, is the issue the landing distance or the oft-mentioned runway taxiing speed issue? I know it's not as much fun, but in reality they really don't shoot gaps much at KPHX. Most departures are off 7L.

Not able to exit at B7 has nothing to do with the airport, but has everything to do with the landing distances of the planes as defined by Real Traffic. I don't know if any of these have been changed, but in prior analysis I found the following landing distances for the planes mentioned in Pete's #2. B738 - 4600 ft B717 - 4660 ft CRJ9 - 5235 ft. I personally don't see this as a "serious issue", but since you brought it up @pete_agreatguy what should the landing distances be? Is the distance for the CRJ9 too long or the B738 and B717 too short? Also, remember these same distances are used at all the airports including KSFO where we all think the planes exit unrealistically early.

Single vs. multiplayer mode makes no difference. It doesn't affect landing distances nor the way planes pushback. 🙄

Thanks - just trying to save myself some work. 🙂

Not including cargo areas was a definite theme of the original airports.

A simple ask ... Please use the format (or spreadsheet) provided in the first post for livery requests. Otherwise they will be ignored. Thanks!

Reminder: One week remaining to submit your livery requests for the RC for KJFK.

Yes, all the special characters (-,=,_,~,',*,+,<,.) in the callsigns should be removed as they are not used in the USA. Plus, the weird characters show up on the DBRITE, ADIRS, and STRIP. I can only assume you used them to try and keep from using duplicate callsigns. Regarding the PLANE NOT FOUND message. What Andre is pointing out is that the voice recognition would not work for this callsign. Actually, it has nothing to do with the dash in the callsign. The issue is using numbers in the phonetic callsign instead of words. This only appears to affect arrivals and not departures. Using the example above: KAXA,TIST,08:04,CN4,N-441TT,0,0,0,0,4 4 1 TANGO TANGO ---> does not work KAXA,TIST,08:04,CN4,N-441TT,0,0,0,0,FOUR FOUR ONE TANGO TANGO ---> this does work. So for consistency purposes, I'd recommend using words instead of numbers for all the phonetic callsigns.

Bug with Real Traffic. That definitely is the problem. RT needs updating.

To see your previous commands and responses you need to press the command history button (between the pause and camera buttons). It will expand the command panel and include a scroll-able box with recent commands.

FYI - keep in mind, this doesn't work with multiple monitors and putting the strip in a separate window.

As a custom schedule creator I've made snippets available for this very reason. However, I prefer to "keep it real" so "tampering" with the terminal file is not something I would entertain. Also, I don't think this would work at some of the bigger airports, especially KLAX. Unless you're talking 15 minute fragments. 🙂

Attached are the original airline/aircraft combos from my custom schedules that are not in RC for KJFK (23 not included at all and 14 found in other RC packs). If I found a livery in RC for KLAX I did not include it as I figured it's a must have. And, obviously, I excluded those already in @hexzed's list. RC_KJFK_Livery_Requests_crbascott.xlsx

Now that KJFK has been chosen by the community for the next RC pack to receive an update from Nyerges Design, we must put together a list of liveries that we would like to see added. Requests must be for "standard" liveries and not one-off special liveries. To be clear, these are only requests. Nyerges Design has the right to choose what will or will not be included in the update. To verify your livery doesn't already exist for KJFK, please use the Master List maintained by @Pedantic G found on the forum at https://forum.simflight.com/topic/85934-tower-3d-pro-real-colorsaircraft-master-list-by-airport/. To submit your request, please use the following format. Only one livery per post please. Airline (ICAO/IATA)1: Aircraft Type (ICAO)1: FlightNumber1: Link2: Other RC3: The above is fairly self explanatory and is being included in order to prove that a real flight for the livery pertains to the airport. 1Airline, aircraft, and flight number are required. Real Traffic files can be used to help supply the valid codes. Airline codes are included in kjfk_airlines.txt. Existing aircraft types can be found by looking at kjfk_airplanes.txt. Additionally, new/existing ICAO designators can be found several places on the web. 2It is recommended to provide a link to an actual flight using the livery from a valid source (ex: FlightAware, FlightRadar24, etc.) to help prove the legitimacy of your request. 3Other RC is not required but helpful to tell Nyerges Design that this livery already exists at one or more other airports, but is not included with KJFK. If you plan to submit more than five (5) livery requests, you are welcome to use the attached spreadsheet. The fields and requirements are the same. Please keep this topic clean and post legitimate requests only. There is no need to post a duplicate if someone has already posted a desired livery. If you have any questions, feel free to send a direct message to @crbascott. The deadline for request submissions is October 21, 2018 at 23:59:59 UTC. After the deadline, a consolidated list of validated requests will be provided to Nyerges Design. RC_KJFK_Livery_Requests.xlsx

OK, so to be clear planes not spawning due to "no free terminal" are sim engine/airport related and not due to the RT schedules.

Wayne, I find it interesting that you would point to poor RT schedules as a reason for planes not spawning. Could you elaborate? In most cases I've found gate availability to be the main cause. What are you seeing?

EDDM EDDS buglist I assume?

Yes, I’ll start a new thread soon. There will be specific detailed requirements to request new liveries.

It all depends on what other RC packs you have and what order they are loaded by the sim.

Is there not an installer? Sectors go in the sectors folder.

Envoy? LOL! In my best Jeff Foxworthy voice: "You might be a tower addict, if your typos are airline names". 🙂

This just might be the straw that breaks the camel's back. 🤬

Friendly reminder that the community vote for the next airport to receive new/updated liveries ends soon: Here's the link: https://forum.simflight.com/topic/86013-community-poll-next-airport-for-rc-update-voting-deadline-is-sep-30-2018/.

Although the current versions sheet doesn't reflect it, it appears RT (sp6v10) and RC for KLAX (sp2v4) have been updated. With RC for KLAX being updated over a week ago, is there a reason the RC Bundle (KLAX-KPHL-TIST) is being neglected? Very frustrating! 😞