But that doesn't mean those developers (or heck, any old end-user) can't release panel configuration files where the G1000 is integrated into any given FS9 airplane, with the assumption that the customer has already bought the G1000 from you guys since that's the only way to get the G1000... right?Just like RXP.

Still looking at best options for consumers at this point in time.Hope this helps:-)

On behalf of those who might be interested in the G1000, I certainly hope you come to allow it :)I'm pretty much just a curious passer-by wondering what you dev-types will come up with next :D This is already looking vey impressive (not to forget the Avidyne systems).

>On behalf of those who might be interested in the G1000, I>certainly hope you come to allow it :)>>I'm pretty much just a curious passer-by wondering what you>dev-types will come up with next :D This is already looking>vey impressive (not to forget the Avidyne systems).Janne, thanks for the kind words regarding our Avidyne Entegra units ;-)As to the G1000, we hope to have some clarification for folks soon:-)

As a side note:Integration of this 'system' in to most any aircraft would be very very dificult, especially in VC mode. You would have to have a big dedicated 'blank' gauge 'slab' area to install it correctly.From working with Reality XP stuff quite a bit, I know how tough it is to get new gauges to work within the original panel designers 'holes' created for gauges (designed locations). Very few allow for the gauges to be placed 'randomly' around the panel.bmp file. This issue is compounded when you have a system like this that covers so much area.That is the reason (I imagine) that the only aircraft available is the default Cessna in 2D mode, as 2D panels *sometimes* have more latitude. But even then it can be tough for the default aircraft. I re-did a default DC-3 panel with Reality gauges/gns units, and the vc panel was very restrictive to where I could install various gauges.Of course, it is possible to dig into the model and various .bmp files of the original aircraft, but that typically is against the copyright of the original author.I would imagine, the best way to do this would be to integrate this system directly into a dedicated panel for this system, as Eaglsoft is interested in doing. Or, sell a version of an aircraft with a 'dumbed down' version of the G1000, then allow someone with a previously purchased system to be 'swapped'. F1 does this for their Barron Lite version of the aircraft, essentially allowing folks who already have RXP stuff to buy the 'lite' version and make an easy swap with the default gauges. Ron can correct me if I'm wrong.

Brian,You are correct re: integration of third party gauges from any vendor into the VC of any commercial or freeware package.You are also correct that "digging" into model and panel bmps for any purpose outside the definition of "private use" is prohibited by most commercial and freeware authors.Eaglesoft will of course provide fully integrated Aircraft/Avionics packages as scheduling permits.There are no plans to offer "dumbed down" or "lite" versions in order to entice customers to purchase yet another version of something they may already own.We hope to have more clarification soon:-)

I can report that the system does work well in its standard placement in the default 182 2d panel. Anyone trying to place these gauges into other aircraft will run into some problems though. First, it is programmed with speeds and engine parameters for the 182 only. Second, as already mentioned, any VC placement will only be possible in aircraft designed with a large gauge "area" and any aircraft with individually placed guages or with gauges showing through "holes" in the overlay bitmap will not work. Third, I have already attempted remaking bitmaps for placement into Flight1's Cessna 172 as this aircraft does have a VC with this possibility. While the placement and functionality of the PFD is fine, the MFD does not work as well with this more complex model. What you will find is that the MFD will flash its display as the refresh doesn't keep up with the redraw. I am quite sure this is something that will be addressed in future revisions and the final product that we will see in any Eaglesoft products should work quite smoothly. As also stated earlier, this product is really more tailored to the flight training environment which has traditionally used a fixed view as the focus is on avionics and procedure training vs the 3d immersion that hobby simmers gravitate toward.

Points well made Zane:-)

I have purchased this product (this past weekend) but have yet to put it to any real use, I just havent had the time :). At first blush it looks very good and very much like the real thing. I'm not endorsed in our club to use it yet, however.I don't know if this link will work for those who are not AOPA members:http://ipilot.com/shop/product.aspx?pid=18138This is an ASA product which us actually a desktop simulator designed to transition from the classic aircraft to the G1000. Looks really interesting. If the link above doesn't work then you should be able to go to the ASA site and find the product.Bruce.

http://www.my-buddy-icon.com/Icons/objects/red_3d_plane.gifAlex ChristoffN562ZBaltimore, MD

Ron,Now that your partners haave the code for the GarminG1000. Does this mean a GNS 530 or 430 is in the works? All you would have to do is,,remove some code here, clip a few code there...and voila you have 530 and a 430.:)But seriously, the 530 and 430 is a subset of the G1000. If its written in C++, is this something you guys are considering?;)Manny

>Ron,>>Now that your partners haave the code for the GarminG1000.>Does this mean a GNS 530 or 430 is in the works? >>All you would have to do is,,remove some code here, clip a few>code there...and voila you have 530 and a 430.>>:)>>But seriously, the 530 and 430 is a subset of the G1000. If>its written in C++, is this something you guys are>considering?>>;)>>MannyManny, first let us thank you for your kind words re: our Avidyne Entegra Units and our Cirrus series. Second, let's not get ahead of ourselves:-)Eaglesoft is heavily involved in all of its current and upcoming project workload as well as keeping an eye peeled for what will be required for FSX.For these reasons, we are reluctant to say much about future projects but we can say that we believe that everyone will be pleased as we move forward:-)

;)

:)

Just FYI, the next update (in the next week or so) will include the following new items:Projected Position Vector ahead of MFD GPS airplane.Overall brightness control option in PFD menuReference Airspeed Markers on airspeed tapeWind Direction Vector on MFDTraffic Reporting Improvements for high-traffic areas