Keith Smith

Members
  • Content count

    202
  • Joined

  • Last visited

Community Reputation

74 Excellent

About Keith Smith

  • Rank
    Advanced Member
  • Birthday 01/01/1974

Contact Methods

  • Website URL http://pilotedge.net

Profile Information

  • Gender Male
  • Location New Jersey
  1. Western US: new airports and standalone option

    As promised, Montana received its upgrades earlier this week, including BIL, GPI, HLN, and MSO This marks the end of the Western US v2 upgrades! There are now 42 towered airports within Western US and 43 within ZLA.
  2. Online event: Long Weekend in Vegas

    PilotEdge is resuming monthly events (we started in January with a SLC-based event). Each month will alternate between ZLA and Western US so that all subscribers will have a chance to take part. For this event, pick up clearance and depart within the first hour of the event, choose from one of two departure airports (LAX or SNA). Choose from one of two arrival airports (LAS or HND). Preferred routes are as follows: LAX-LAS jet RNAV: ORCKA2.MISEN KEPEC6 LAX-LAS jet non-RNAV: SEBBY2.DAG.CLARR3 LAX-LAS turboprop: SEBBY2.DAG.CRESO4 LAX-LAS piston: SLI8.SLI POM DAG.CRESO4 LAX-HND jet RNAV: SEBBY2.DAG.JOMIX1 LAX-HND jet non-RNAV: SEBBY2.DAG.CLARR3 LAX-HND turboprop: SEBBY2.DAG.CLARR3 LAX-HND piston: SLI8.SLI V21 PDZ V442 APLES V394 DAG V587 BLD SNA-LAS jet RNAV: FINZZ2.MISEN.KEPEC6 SNA-LAS jet non-RNAV: MUSEL8.DAG.CLARR3 SNA-LAS turboprop/piston: MUSEL8.SLI POM DAG.CRESO4 SNA-LAS piston: ANAHM9.SLI POM DAG.CRESO4 SNA-HND jet RNAV: MUSEL8.DAG.JOMIX1 SNA-HND jet non-RNAV: MUSEL8.DAG.CLARR3 SNA-HND turboprop: MUSEL8.DAG V587 BLD SNA-HND piston: ANAHM9.HEC V21 BLD
  3. Western US: new airports and standalone option

    January saw the addition of Fresno (FAT) and Redding (RDD) to northern California. On February 1st, we added Jackson Hole (JAC) and Casper (CPR) to Wymoning. Montana should be receiving its upgrades in March and then Western US V2 will be complete.
  4. Western US: new airports and standalone option

    3 more airports have been added to Western US: 1) Boeing Field (KBFI) 2) Olympia (KOLM) 3) Tri-Cities (KPSC)
  5. Western US: new airports and standalone option

    2 more airports have been added to Western US: 1) Boise, ID (KBOI) 2) Friedman Memorial, ID (KSUN) Friedman has a pretty neat NDB/DME-A approach with a long visual segment and a FAF inside of NDB.
  6. Not sure if this made it into the release notes, but for PilotEdge users, the TX selector for COM1/COM2 works correctly now.
  7. Hey there, we were chatting in DirkaDirkaGaming's twitch stream but I didn't have a way to reach out to you. I figured I'd try here. Could you drop me a PM? I'd like to let you know about the datarefs we use for the TX/RX datarefs we make available in case the Saab has TX/RX indicators for the com radios. Separately, I'd like to share with you which datarefs we use for com1/2 volume, the com1/2 TX selector, etc.
  8. Western US: new airports and standalone option

    3 more airports have been added to Western US, bringing us to 29 towered airports for that coverage area and counting: 1) Eugene, OR (KEUG) 2) Medford, OR (KMFR) 3) North Bend, OR (KOTH) The current coverage area can be viewed here: https://www.pilotedge.net/pages/operating-hours-and-service-area
  9. Western US: new airports and standalone option

    6 more airports have been added as we continue to build out towards the v2.0 road map. 1) Arizona: Flagstaff (KFLG), Prescott (KPRC) and Tucson (KTUS) 2) Colorado: Centennial (KAPA), Colorado Springs (KCOS) and Grand Junction (KGJT)
  10. When we first launched the Western US Expansion Area at the end of 2016, the idea was to provide a small number of core airports and a healthy number of rotating bonus fields for jet pilots to stretch their legs. The airspace didn't have enough towered airports to warrant a standalone subscription, so it was released as an optional add-on. Since the launch, our thinking has evolved and the purpose for Western US has changed from a relatively small collection of widely-spaced airports for airliners to a larger ecosystem of airports for a wide range of aircraft, including pistons. To that end, we've made some changes: 1) The bonus fields have all become full-time airports. No more rotation. 2) Amarillo, El Paso and Four Corners Regional have been added to the airport list. 3) We've announced a road map for the Western US coverage area containing just over 40 towered airports, including all of the Class Bravo airports, all of the Class Charlie airports and strategically-selected Class D airports within the Western US coverage area. 4) This is a big one...Western US is now available as a standalone subscription. It will eventually contain as many towered airports at the ZLA coverage area and is already well on the way with 20 towered airports. This change allows pilots to have "Western US only" access for the same cost as a traditional ZLA-only subscription. They'll even have ZLA overflight privileges at or above 14,000ft, allowing them to transition ZLA as the go from one Western US airport to another (eg, SFO-PHX)
  11. Pilotedge: a new online network, beta has started

    The Western US expansion is happening Dec 27.
  12. airspace expansion coming before end of 2016

    And here it is: http://pilotedge.net/pages/western-expansion
  13. A more formal announcement will be made when the launch date is finalized, but we will be adding full time support for: SEA, PDX, SLC, ASE, DEN, and PHX. Additionally, we'll provide part time coverage for: OAK, SJC, RNO, MRY, SMF, GEG, YKM, EGE, ABQ. "Part time" means that we'll cover ONE of those fields at a time for a period of two weeks before closing it and moving to the next one in the list. This provides fresh airports, additional traffic concentration (since the part time field is temporary) and interesting piston/turboprop routes since the primary full time fields are generally pretty far apart.
  14. PilotEdge v1.2.0 was just released with simultaneous dual comm support for windows/linux/mac. For any aircraft developers who want to ensure their aircraft are dual comm compatible... - TX is determined by sim/cockpit/switches/audio_panel_out (6 for COM1, 7 for COM2) - RX for COM1 is determined by sim/cockpit2/radios/actuators/audio_selection_com1 and sim/cockpit2/radios/actuators/com1_power - RX for COM2 is determined by sim/cockpit2/radios/actuators/audio_selection_com2 and sim/cockpit2/radios/actuators/com2_power It's possible to be receiving COM1 and COM2 simultaneously. However, only one radio can be set to transmission (via the audio_panel_out ref). There are xplane commands to set the transmit and receive radios in xplane already, feel free to call those commands from your audio panels, or set the datarefs directly. These are all stock datarefs already in xplane, they're not PE specific. This should simplify the audio panel greatly. The TX setting is completely independent of the RX setting now. Also, TCAS is now supported through the standard xplane datarefs. This requires you to set your 'other aircraft' to the max number of TCAS targets you want to display (plus 1 since your aircraft is included in the count). The next thing I'm hoping to add is volume support since I believe those datarefs now exist on a per radio basis.
  15. Wind Direction in X-Plane (True vs. Magnetic)

    That's the most fiery debate about winds I've ever seen. That aside, if it helps clear up the magnetic/true debate...METARs include true headings. Winds aloft are reported as true, too. However, when the tower reads out surface winds, they are read in magnetic. This is because they're not reading the winds from the METAR, they're reading from equipment in the tower which is showing the winds in magnetic degrees. Controllers on PilotEdge and VATSIM don't have such equipment. They DO read from the METAR and have to apply magnetic variation each time they issue the surface winds. So, if the METAR for LAX shows wind "26009KT", it would be read as "wind two fife zero at niner."