Keith Smith

  • Content count

  • Joined

  • Last visited

Community Reputation

73 Excellent

About Keith Smith

  • Rank
    Advanced Member
  • Birthday 01/01/1974

Contact Methods

  • Website URL

Profile Information

  • Gender Male
  • Location New Jersey
  1. 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)
  2. Pilotedge: a new online network, beta has started

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

    And here it is:
  4. 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.
  5. 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.
  6. 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."
  7. Helicopter tennis

  8. 52 minute version with all flows and check lists: A 12 minute version of the same thing, focusing mostly on the ATC exchanges: ATC was provided by PilotEdge. Shared cockpit by SmartCopilot. Aircraft is the FlyJSim 737-200. Captain was new to CRM as of the morning of the shoot (that would be me), FO has recent airline experience. FO actually has more work to do if the Captain in the pilot flying, so that's why we set it up this way. There aren't many videos showing formal CRM procedures in sims, so this one is a bit different.
  9. Linux plugin now available

    The current distribution now includes 32-bit and 64-bit Linux plugins. So...all 5 Linux users can now rejoice.
  10. Real IFR Training

    Oliver, Suggest checking out the IFR workshops (available for free) here: Additionally, there's a decent IFR training program (focusing on IFR procedures, not stick and rudder) here: And here's a comparison to VATSIM and other online networks: Simply put, if you logged in at 8am, 12pm, 3pm, 6pm, and 8pm PDT for the next 7 days in a row, PilotEdge will have ATC available during 100% of those flights. You simply do not know what you'll get if you fly on VATSIM, and it certainly won't be consistent. Sometimes you'll talk to approach...other times you'll only talk to center. Other times there will be nobody there. Additionally, if you were to fly from a Class D airport to another Class D airport, on PE you'll go from Ground to Tower, to approach, to tower, back to ground...5 freqs at least. On VATSIM you'll very likely only work with a single freq the entire time (because when they do have multiple controllers, those additional controllers are typically working individual positions at the popular airports, such as LAX_GND or LAX_TWR). So, even though we have a limited number of controllers online, the same is generally true for a given geographic area on VATSIM, too...but we cover all the frequencies, so the pilot workload is higher. Hope that helps!
  11. How to perform same functions in xplane 10 as in FSX?

    I have to make this quick, so it won't be detailed, but check the 'View' menu. Not every plane has a 2d cockpit, some only have 3d cockpit. You have 6 DOF to move around the 3d cockpit using the keyboard and/or mouse (right click and hold), or Q, E, R, F, comma, period, plus/minus and arrow keys. You can view all the key assignments from Settings->Joysticks & Equipment -> keys tab. There is only one map, don't click it, there's no reason to. You can zoom and pan with arrow keys or the minus/plus keys. Regarding a/p. you need to play with it and you'll get there (I know that isn't particularly helpful, but there isn't an autopilot I haven't been able to work out by simply spending some time and working it out). If I had more time I'd go into a lot more detail, this is the best I can do right now.
  12. X-Passenger for X-Plane 9/10

    Medical emergency or unruly passenger would be more realistic if you're trying to get them to deviate to nearest suitable field.
  13. Any glider pilots?

    I've flown a lot RC gliders (slope soaring, little bit of thermal, lots of dynamic soaring). Have flown full size 3-4 times. I really enjoy gliding in X-Plane. We do group flights on PilotEdge some times, it really is a blast. I've published the ASK-21 shared cockpit configuration file for Smart Co-Pilot as well so you can do shared cockpit flights, too.
  14. Shared Cockpit: handflown B732 from SAN-LAS on PilotEdge

    Here's one more, same route by during a busy event. Route: PEBLE4.SXC LAG DAG.CLARR2, visual 25L (we were denied the sidestep to 25R by the tower) This was flown entirely without autopilot for the duration to see what the change in workload would be. Lots of vectors and speed restrictions make for an interesting sequence. Some slightly bizarre conversation as well (10:20 is a good example): Flying an airliner with shared cockpit and ATC really does bring it to a whole new level of realism and workload. Not being trained in the realm of CRM, I've found it's taken a few flights to find my stride with this type of flying, but it's been a great experience. Overall the workload is absolutely lessened by having 2 pilots, as long as you're all on the same page.
  15. A number of us have been enjoying the recently-released FlyJSim 737-200, especially with shared cockpit. There is a fly-out on the PilotEdge network on Jul 9 from SAN to LAS with a quick turn to BUR, starting with a gathering at 7pm PDT at SAN, and then wheels up by 7:25pm PDT (or at least in the departure line by that point). The route is PEBLE4.SXC LAX DAG.CLARR2 (for the B732 or any other non-RNAV jet), or use the KEPEC3 arrival if you are RNAV-capable. Some of us will be doing shared cockpit flights and live streaming on twitch (myself and helipilot7), so feel free to follow along. Anyone is welcome to join in any plane you like, but this is primarily a turbojet group flight due to the distances involved. If you want to fly a piston into Vegas or HND/VGT, go for it, but I'd suggest starting a bit closer, maybe from Bullhead (IFP). If you haven't checked out PilotEdge, this is a good opportunity to utilize the free 2 week trial and experience what the network has to offer. Briefly, it's a subscription-based network that offers -guaranteed ATC 15x7 within the coverage area (40 towered airports), - intelligent support for shared cockpit via the SmartCoPilot plugin. The second person logs in with an @ at the end of the callsign, otherwise use the same callsign as the primary aircraft, the server takes care of the rest - advanced radio system using real world frequencies at all times (no controller list). You just tune SAN clearance delivery, then ground, tower, etc. For this flight, it'll be SAN clnc (125.90), SAN ground (123.90), SAN tower (118.30), Socal Dep (119.60), LAX Center (119.95), LAX Center (125.27), LAS approach (125.02), LAS Approach (135.00), LAS tower (119.90), LAS ground (121.10). You don't need these all in advance, but this gives you an idea of the workload that will be involved compared to other flights you have done in the past on networks that don't utilize r/w freqs. There is much more on offer, but for the purposes of this fly-out, that's the most important stuff. Here's a video of the SAN-LAS route being flown with shared cockpit on PilotEdge: