Latest Event Updates
FlightConnect, the application used by FlightMap and FlightGauge to talk to FSX and P3D, has been updated. This update includes support for FS9 flight plans. Third party flight plan software tends to output in the older format so FlightConnect can now utilize them. This version also better handles the situation where SimConnect is not properly installed for FSX. Users will get an error dialog on application startup letting them know that FlightConnect cannot talk to FSX.
For the new STEAM version of FSX:
I’ve had a few support cases from new users of the Steam version of FSX. The issue is with FlightConnect crashing on launch. It looks like sometimes the SimConnect library is not installed properly when the rest of FSX is installed thru Steam. This can be easily fixed by manually installing SimConnect from the installation directory of FSX. In my case it exists here:
For older FSX versions:
Today, Dovetail games announced the availability of a new Steam Powered version of Flight Simulator X. Vine Ripe Software is pleased to announce that FlightConnect, the application that FlightMap and FlightGauge rely on for simulator data, fully supports the Steam version of FSX right out of the box without any modification or patches.
More information on the Steam version of FSX can be found here (plus it’s on sale right now)
The FlightMap and FlightGauge trial versions on the Play Store have been updated to the latest release. I had not updated either for several revisions so this update includes all of the fixes and features from the last several major releases.
The latest release of FlightGauge for Android, a second screen cockpit instrument panel for Microsoft’s Flight Simulator X (FSX) and Lockheed Martin’s Prepar3D (P3D), has been release to the Play Store. This version improves support for low end tablets and includes many performance and stability updates.
It’s hard to believe that one year ago today I was launching FlightMap for Android on the Google Play Store. It seems like yesterday. What started as a personal GPS app to fill out my flight simulator cockpit has turned into quite a nice little utility. That first version didn’t do much and only worked on 10 inch tablets which was all I had at the time. It basically followed the airplane from the simulator and allowed you to create adhoc flight plans over google maps and map the next waypoint in the active flight plan in the simulator. Two main modes but for me, the gauges were the big accomplishment even though most people at the time didn’t care much for them. I wrote the app for me to begin with and it just happened that a few people liked it as well and for that I’m very grateful. Looking back it’s hard to believe that there have been 10 major releases of FlightMap in the last year. That’s pretty impressive for any software project :)
Over the next few months I was really able to perfect the flight plan management and display options as well as improve the overall look of the app. The basic design has not changed that much on the 10 inch tablets but it is more refined now with a lot more data on the screen. My beta testers at the time really know the struggle to get the display right. It took a lot of time but I think the outcome was worth it. My main goal has always been to keep the app simple and familiar to pilots and I think I have done that. That goal is the reason I have spent so much time making sure FlightConnect is as simple as it can possibly be and that FlightMap tries to be as smart as possible to require so little from the user to do what it does. Working with a primary simulator that has not been touched by the developer for almost 10 years certainly has made that challenging :) Around this time I was able to add Prepar3D to the supported simulators and I am hoping some of the bugs I’ve run into with FSX will eventually be fixed :).
About 4 months after the release of FlightMap I was able to release version 2.0. Google had just released the new Nexus 7 and I was fortunate enough to be able to purchase one and start work on supporting it. I didn’t realize at the time how challenging the design I had come up with for the app would be to support on various tablet sizes but I did ultimately figure out a way to do it. Now FlightMap supports all 7, 8, 9, and 10 inch tablets that I have run into. I’m working on fixing an issue with a 21 inch tablet now :) That first 7 inch version was a real challenge though. Trying to fit all of the features in without sacrificing functionality on the smaller screen took a lot of design work. It was ironic to me that the one feature most people said they didn’t want on the 10 inch tablets, the gauges, became the most requested feature on the 7 inch tablets when I didn’t include it in the first release. I was able to find a way to bring the gauges to the 7 inch tablets within a month or so but it was tricky.
I had a major surgery at the end of August which slowed things down a bit but I was able to continue work on FlightMap and even found time to release a new app called FlightGauge. The most recent release included a refresh of the graphics and new features for the major gauges as well as regional airport, ndb, and vor display. I’m really proud of where FlightMap has come and I’m looking forward to seeing where this goes in the future.
I am so thankful for all of the users of the software. I have learned so much about aviation from this project and I’m sure I have a ton yet to learn. Thank you for all of the support over the last year.