MSFS

Constantly scanning the sky is an integral part of flying.  It’s for safety but also to take in the sites all around you. With that in mind, I want to show you how you can get awesome head tracking in your flight simulator with just a webcam and $3. You might wonder how this method compares to TrackIR. The short answer is that it’s not as precise as TrackIR, but still an excellent alternative that’s left me with almost no complaints.

For those who don’t know, TrackIR is the leading head tracking device on the market costing $149. TrackIR uses a camera and Infrared to track the movements of your head. It’s accomplished by mounting a camera in front of you and wearing the infrared light on your head. This allows you to look all around the cockpit and lean towards your instruments.

The method we’ll talk about today uses your web cam to track the movement of your face rather than infrared light. This is done with software called FaceTrackNoIR. This software tricks the simulator into thinking TrackIR is being used. The camera I’m using is the HD Pro Webcam C920, but any modern webcam will do. Your monitor should provide enough light, but if not, try to light your face as much as possible. This will increase the accuracy of the head tracking.

Once you open FaceTrackNoIR for the first time, you’ll need to configure your webcam. Click “Options” at the top left of the window and then proceed to “Webcam Utility.” From there, click “Devices” and your webcam should be recognized in the drop down menu.

Now that you’ve set up your webcam, you can go back to the main window. Here you will see various options that you can apply to the tracker. “Profile” allows you to save your settings and load them in at anytime. You might want to do this if you have different configurations for various sims. I use “faceAPI V3.2.6” for tracker source, “Accela Filter Mk2” for filter and “FreeTrack 2.1” for game protocol. I also set my smoothing to 30 samples and I invert the pitch axis. Lastly, you can adjust the curves for each axis.

When everything is set, you can click “Start” under GO!. You should now see a black and white video of your face with a yellow overlay tracking your head movement. This shows how your face is going to be tracked in the simulator. Always remember to click “Start” prior to opening the simulator. Otherwise it might not recolonize that you are using head tracking and you will have to restart the sim.

When it comes to compatibility, I’ve tested FaceTrackNoIR on Prepar3D v4.4, X-Plane 11, Aerofly FS2, DCS World 2.5, and IL-2. Each sim functions slightly different but they’re all very close in functionality. This is where you might want to start saving profiles for each sim. The head tracking works right away upon loading Aerofly FS 2, DCS World, and IL2. With Prepar3D and X-Plane 11, there is just a couple of extra steps to make the head tracking work.

For X-Plane 11, it helps to have the plugin X-Camera, which is free to download. But if you want your settings to save, you do need to purchase a license. Otherwise the free version works great for Track IR, as long as you’re okay with re-positioning the camera each time you open X-Plane. To turn the head tracking on, simply open the X-Camera control panel and check the “Enable Track IR” and “Retain Mouse Look Position” boxes. If the camera is not aligned correctly, you can use the arrow keys and mouse to center your view.

Prepar3D follows nearly the same process. The most efficient way to use head tracking in P3D is with camera software called ChasePlane. The head tracking should work automatically, but if not, click “Preferences” on the left and make sure “Enable Head Tracking (TrackIR)” is checked. Again, if the camera is not aligned correctly you can use the arrow keys and mouse to center the view.

From dog fighting over the Persian Gulf, or turning base onto final; FaceTrackNoIR has made a world of difference in my flight simulation experience. TrackIR can be a costly investment but if you already own a web cam you’re just a few dollars away from turning your head inside the virtual cockpit. Have fun out there everyone, see you in the skies!

Direct from the Microsoft Flight Simulator Global preview event in Seattle, join us we interview core members of the development teams at Asobo Studio and Microsoft. Over three episodes we will interview the teams behind the new flight simulator over the world & weather, aerodynamics & cockpits and finally community engagement.

In our final developer interview episode, we speak to Jorg Neumann, Head of Microsoft Flight Simulator, and Robert Jerauld, Director of Production all about the community engagement for Microsoft Flight Simulator (also known as FS2020 to the community).

Microsoft Flight Simulator was announced at E3 and we have been following the progress since.

Be sure to check out our 4K footage from the simulator, as well as, episode 1 which focused on the world and weather. If you missed it, episode 2 is here which is all about Aerodynamics and the cockpit.

Continue Finding Out More

Hands-On with Microsoft Flight Simulator

Technical Overview for Microsoft Flight Simulator

4K Media Library

Direct from the Microsoft Flight Simulator Global preview event in Seattle, join us we interview core members of the development teams at Asobo Studio and Microsoft.

Over three episodes we will interview the teams behind the new flight simulator over the world & weather, aerodynamics & cockpits and finally community engagement. In this episode, we speak to Sebastian Wloch and Martial Bossard all about the aerodynamics & cockpits in Microsoft Flight Simulator (also known as FS2020 to the community).

Microsoft Flight Simulator was announced at E3 and we have been following the progress since.

Stay tuned for our final episode (number 3) coming tomorrow. (Links below for you to bookmark). Be sure to check out our 4K footage from the simulator, as well as, episode 1 which focused on the world and weather.

Continue Finding Out More

Hands-On with Microsoft Flight Simulator

Technical Overview for Microsoft Flight Simulator

[Premier – live on October 2nd @ 16:00z] Microsoft Flight Simulator Developer Interview – Episode 3: Community Engagement

4K Media Library

Direct from the Microsoft Flight Simulator Global preview event in Seattle, we have over 30 minutes of brand new 4K footage. The new footage will take you all over the world including London, Paris, Berlin and beyond.

We have accompanied the footage with a brief bit of narration, but the primary purpose of this video is to give you the highest quality footage, complete with sound experience.

If you’re enjoying our coverage for the new Flight Simulat0r (also known as FS2020), be sure to check out our range of other content.

Be sure to subscribe to us on YouTube to stay updated with new content.

Continue Finding Out More

Hands-On with Microsoft Flight Simulator

Technical Overview for Microsoft Flight Simulator

[Premier – live on October 1st @ 16:00z] Microsoft Flight Simulator Developer Interview – Episode 2: Aerodynamics and Cockpit

[Premier – live on October 2nd @ 16:00z] Microsoft Flight Simulator Developer Interview – Episode 3: Community Engagement

4K Media Library

Direct from the Microsoft Flight Simulator Global preview event in Seattle, join us we interview core members of the development teams at Asobo Studio and Microsoft.

Over three episodes we will interview the teams behind the new flight simulator over the world & weather, aerodynamics & cockpits and finally community engagement. In this episode, we speak to David Dedeine and Lionel Fuentes all about the world & weather in Microsoft Flight Simulator (also known as FS2020 to the community).

Microsoft Flight Simulator was announced at E3 and we have been following the progress since.

Stay tuned for episodes 2 and 3 coming over the next couple of days. (Links below for you to bookmark).

Continue Finding Out More

Hands-On with Microsoft Flight Simulator

Technical Overview for Microsoft Flight Simulator

[Premier – live on October 1st @ 16:00z] Microsoft Flight Simulator Developer Interview – Episode 2: Aerodynamics and Cockpit

[Premier – live on October 2nd @ 16:00z] Microsoft Flight Simulator Developer Interview – Episode 3: Community Engagement

4K Media Library

Greetings everyone! I want to talk about a crucial part of IFR flight planning, that being Standard Instrument Departures (SIDs) and Standard Terminal Arrival Routes (STARs). SIDs, and STARs, are predetermined routes with speed and altitude restrictions that will guide you to and from the airport. Most airports have multiple published SIDs and STARs. Each one is setup to accommodate the direction you’re departing and arriving.

There are two different kinds of published charts. One being from the National Aeronautical Chart Office (NACO/FAA) and Jeppesen charts. They have subtle differences in layout but are based on the same idea and legend. If you would like to learn more about the differences between the two there is a great article on thinkaviation.net.

Typically air traffic control will instruct you to climb or descend via the SID/STAR. But there are situations where ATC will cancel certain procedures while flying a departure or approach. They might have you skip a few waypoints and send you direct or cancel speed or altitude restrictions. Don’t be caught off guard if this happens. 

One of my favorite free sources for charts is Airnav. This website covers the U.S. and its territories. From the home page click airport and then type in the airport code of your choosing. You’ll be taken to the airport page and from there you will find the SIDs, STARs, and approach plates toward the bottom the page. The next and most popular source you can use for charts is Navigraph. This website is a subscription based source that has both U.S. and international charts.

The last thing to cover before we talk about the charts themselves is how do you know which SID and STAR to use for your route? There are several sources to get routes. The most complete source being Simbrief. This is a free website that requires you to setup an account. Once your account is made you can easily plug in your departure and arrival. From there Simbrief will instantly build the route for you. It also provides several alternative routes if you wish to use one different from the main selection.

Another very easy to use source is Flightaware. This website is a live real world flight tracker. Here you simply type in the departure and arrival and you will be taken to a page listing all the airlines that run that particular route. After picking the airline you will go to a specific page for that flight. There it will show you the full route that the airline filed on that particular day. The only down side is that this only works for flights in the U.S. and flights traveling to and from the U.S.

Now that you know where to find SID and STAR charts, we’ll talk about understanding the charts themselves. Each SID and STAR have a unique name given to them. These names might abbreviate pop culture terms, sports teams, or points of interest in the area among other things. As you can see with the list of SIDS in Atlanta, two referencing the movie “The Lord of the Rings,” with GNDFL2 (Gandalf) and HOBTT2 (Hobit). You can also see another two that reference the movie Star Wars, with JJEDI2 and SITTH2 on the following page. The number you see next to the SID/STAR represents how many times the chart has been amended. The next time the SITTH2 departure is updated it will become SITTH3. After ten amendments the count goes back to one.

Let’s take a look at a SID out of San Diego International (KSAN). This SID is called the ZZOOO TWO, referencing the local San Diego Zoo. The transition we will use is MTBAL. The first thing to look at is the Departure Route Description located on the upper left. This description will clearly spell out the procedures that you need to follow. If an airport has multiple runways you will see different sets of instructions for each runway. Some SIDS are meant for just one side of the runway while other SIDS will include instructions for both ends of the runway.

For the ZZOOO Two we only have instructions for a runway 27 Departure. Upon takeoff we’ll climb with a heading of 275 at 500 ft per nautical mile, to reach 520 ft. Then crossing the JETTI waypoint at or below FL120 and not exceeding a speed of 230 knots. The line above the altitude lets you know this is a cross at or below point. If the line was under the altitude it would mean cross at or above. Two lines means you must cross at the published altitude.

The last thing to note about JETTI is the waypoint symbol with a circle around it, this is called a fly-over point. This means you must fly over this point before making the turn. Fly-over waypoints can be in place to avoid obstacles or to comply with noise abatement. The other waypoint symbols are called Fly-By points. These points are a little more lenient when making turns as you’re not held to flying precisely over them, hence the name fly-by.

After Crossing the ZZOOO waypoint we have our first transition option. A transition connects you to the rest of your flight plan. At this point flying the SID/STAR ends. If CENZA was our transition we would turn to a heading of 099 at 4000 when reaching the transition. The departure description gives one last instruction that If we’re a turbojet we won’t fly higher than FL230 while on the transition. If we’re a turboprop this altitude restriction is FL150. This altitude hold won’t be for long as you will eventually be cleared to your filed altitude.

If our transition is (IPL) Imperial or MTBAL instead of flying to CENZA we will proceed to JORRJ at or below 14000 heading 085 and from there flying a heading of 066 to GRIDR. At this point you’re connected with the other two transition options for the SID. Heading 072 will put you on the route for the IPL transition and heading 011 will put you on the MTBAL transition. Again during this phase you are expected to maintain FL150 all the way to the transition if you’re a turbo prop and FL230 if you’re a turbojet.

Now that we know the 3 different directions this route can take us, we’ll look at the notes on the middle left. The first note is telling us that our aircraft needs to be equip with radar. RNAV1 is saying your aircraft needs a navigation system that’s accurate within 1 nm 95% of the time. If it were to say RNAV2, the same applies except it’s 2 miles of being correct 95% of the time. The next note is requiring a DME/IRU capable aircraft or GPS system on board. Next you’re being informed that some aircraft may be vectored to the 3 waypoints after flying the downwind. This means ATC will tell you what heading to fly to reach the waypoints rather than following the SID. The next note is telling you to advice ATC if you cannot meet the altitude restriction of 14000ft at JORRJ. This ties into the next note that mentions parachute jumping is going on at all hours of the day at 13500 and below near JORRJ. Lastly you are being told that if your aircraft is not equipped with GPS and you’re using the MTBAL or IPL transition that the PGY DME must be operating.

The last piece of information to discuss is the upper right of the SID. Here you will find all the useful frequencies for the area. This includes ATIS, clearance delivery, ground, Lindbergh tower, and So-Cal departure. Note: if you’re flying online, some or all of these frequencies might be different from the real world frequencies.

After going over the SID lets take a looks at the STAR. The STAR we’re using is called LDORA Two. First thing to do is take a look at the route description in the lower left. For this arrival there are 3 transitions we can use to enter the STAR. These are Blue Mesa (HBU) BRAZO and OURAY. These 3 transition waypoints will lead you to FREZE. You’ll notice the Blue Mesa transition has a maximum altitude restriction (MAA) of FL260. This means you cannot fly above that altitude. From FREZE track a heading of 037 for PEEKK. Then it’s onto LDORA at FL130 and a speed restriction of 210. Remember this is a fly-over point because of the symbol that’s being used. From there fly a heading of 064 and ATC will vector you the rest of the way to the runway. If you lose communication with ATC you are to fly the ILS approach for runway 35L.

The route we’re flying requires the OURAY transition which has us track a 036 heading to FREZE. Once you reach OURAY you’ll notice an oval shape at the next waypoint KNOSA. You can see the same shape at HBU, FREZE, and PEEKK. These are points where you can enter a holding pattern if needed. This might be done to create separation between aircraft or if you’re too high on the descent. This holding pattern allows for the issue to be corrected before moving on.

We should cross FREZE at or above FL200, as indicated by the line below FL200. Continue the 037 heading to LARKS where we need to cross at or above 17000 or at or below FL190 and slowed to 250 knots. You will also notice a triangle symbol at this point. This is a non-compulsory reporting point. You are not required to report to ATC at this point unless told to. If the triangle was solid that is compulsory reporting point and you would be required to report. After LARKS it’s onto LDORA where we need to cross at an altitude of 13000 and 210 knots indicated by the line above and below the restriction. Remember LDORA is also a fly-over point. This means you must hit this waypoint. After LDORA you will be vectored to the active runway.

The last thing we’ll look at is the notes. The first 3 notes are similar to the SID. Radar is required. This is an RNAV1 approach and a DME/IRU or GPS is required to proceed. This STAR is also for turbojet aircraft only. Once you contact DENVER on TRACON you can expect your runway assignment. Expect PEEKK when Denver is landing south as there is another STAR named PEEKK3. Descend via mach speed until reaching the transition. At that time your descent should be 280 knots until ATC instructs you to lower your speed. If your aircraft is not equipped with GPS and you’re using the BRAZO transition the ALS, RSK, and PUB DMEs need to be operational. If using the Blue Mesa (HBU) transition without GPS the HBU DME must be operating.

After completing the STAR it’s onto the final phase of flight which is the approach plate. These plates are what guide you down to the runway. Because there is a lot to talk about with approach plates, it will be the subject of the next tutorial. Hopefully these examples have given you a good foundation to build on. Most modern jets will do most of the work for you through VNAV. But take what you’ve learned here, continue to study and grow!   

Microsoft has finally opened up its Insider Program for Flight Simulator 2020. We take an in-depth look into their August 15th media update, which included 5 new video clips and 2 brand new screenshots.

This is pre-alpha footage so always time for improvements from Microsoft.

Microsoft Flight Simulator 2020 was announced at E3 and we have been following the progress since.

Subscribe to our YouTube channel for more great content.

*This is a reupload with some edits based on feedback*

Thanks to Max and Ronnie from the FSElite team for additional details.

(The Written version of this video coming soon).