Leaderboard

This isnt' the kind of thing I'd normally throw out there....I don't like excuses, but there is some behind the scenes info on whats going on time wise. ...and I know how hard the team is working despite the circumstances. We had planned the release earlier, when everyone was avail to support, but my elderly mother had a AAA (Aortic aneurism) a short while ago and I had to bolt out of town for the emergency, and this delayed the release. I don't want sympathies or well wishes here or in PMs, please keep those to yourself.....that's not what this post is for. This delay pushed the release back a bit.....to this weekend where some of our team are out of town (one out of country) for events with their families they scheduled months ago...and unable to work efficiently as they'd like. They're trying the best they can..and we're trying to get back together as fast as possible so we can get on with the business of improving the IXEG. We'll be hitting this hard tomorrow as well. We are fully committed to getting everyone up and running. This post is simply to let folks know that "life happened" to us these past few weeks and we're not just ignoring folks or don't care, or have lowered our standards. With all that said, I'll be hammering away all week on the things I can control. The other team members will continue as well and we'll be running on all cylinders again very shortly. TomK

So....good example of why this port to XP12 is a pain. ..and this is just one of a lot. Went over this for a long while yesterday and just had trouble trying to code around it. Took it directly to Laminar and sure enough, the acceleration ramp between lightoff and idle is simply inaccurate. The acceleration curve shape between lightoff and idle is hard coded and not tweakable via PM. Below is the N2 ramp for the default 738 (which has the same problem). This is Laminar's own data of N2 vs. time (but my overlay comments). You can see the very rapid rise of N2 after lightoff...getting to within 80% of idle in a few seconds. So you may ask, "well why don't you custom code it"...and we do to some extent, but there is a limit. Some parameters, if we decide to override, means its all or nothing. So if we "override the engines" for example..then we have to write the entire engine model for all regimes and that is almost a product in and of itself. Besides, Laminar's model is mature and pretty good...no need to reinvent the wheel.....to me this is simply a "plane-maker design issue" oversight. A 'coefficient' should have been provided (and is what I'm lobbying for) to shape this curve...like a lot of curves in PM can be shaped. The good news is its official, we're filing a ticket to Austin. Also good news (but not perfect) is I've coded a workaround for the next patch to get us through.....because I'm sure it'll be some time before the next update to XP comes out with this fix. The limitation on my patch will be "don't mess with a running engine while the other one is starting". If you do, then the starting engine will exhibit this "rapid rise" behavior somewhat. ...but many folks may not notice it. and these kinds of sweeping modeling changes are all over the place, and have really wreaked havoc with the accuracy of our performance. BUT....we're working on that too now. TK

@AngelOfAttack I have identified and fixed the reason for the weird pitch during takeoff and landing. It will be fixed in the next version, so dont get too used to the effect ;-)

Hello. Any news about the fix ? i'm still getting no power for plane.

Please do so - it is what I have used to tune performance ;-) I agree on the ground effect thing - it does strike us seemingly more than the default 737-800, might be a geometry thing. If I make the nose more "heavy" on rotation you would be unable to pull it past 10 degrees until out of the ground effect - the landings one can get used to, but you need to be ready for the nose wanting to drop (more than on the real aircraft). I might take this up with Austin, but got him busy on the N2 acceleration during engine start for now ;-) Try taxiing again on a verifiably flat area - I find that even a bit of slope plays a huge role. The 737 starts rolling on my side at idle power up to 50 tons of weight, as it should. Cheers, Jan

Hello All, This will serve as an official announcement that we have released the version 2.0.1 update for the LES Douglas DC-3 v2. All customers who have purchased the LES Douglas DC-3 v2 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the LES Douglas DC-3 v2 from today forward, your purchased download will already be updated to version 2.0.1 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original LES Douglas DC-3 v2 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Both Variants: Fixed aircraft locked issues Fixed Cowl flaps from working without hydraulic pressure Differential power will be disabled when tail wheel is not on the ground and MAP above 35 Pilots are visible from outside, only when the aircraft is powered Cabin door manipulators are available when parking brake is set Improved American Airlines livery colors and resolution Improved Hellenic Aviation Authority livery resolution Added toe brake animation 'READ THE MANUAL' button now opens the online manual in your default browser Modern Variant: Fixed ADF1 ET timer - Does not reset when the unit turns off Fixed ADF2 timers - Not working properly Fixed Transponder ID button - Working when in STBY and TEST modes Fixed Transponder TEST mode - Three first knobs can change the code Fixed Transponder code - Resets to 1200 when unit is turned off Fixed Copilot's CI TO/FROM flag - Responding to pilot's CI Fixed some sounds not audible due to wrong coordinates (fire bell, overhead, etc) Fixed AP test tone Improved instruments night lighting As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!

Hi everyone! Thanks for everyone´s support and feedback for our initial launch of the IXEG 737 in XP12. This post will detail the bugs that were reported and confirmed by us. This post will be updated regularly and shall serve as a tool to check if something you observe has already been reported. Activation issues with the DRM that revolve around the "Level 2 check" failing - fixed Wiper switches not working - fixed for next patch Standby airspeed indicator drum not moving - fixed for next patch Bullseye windows on doors 3L and 3R too far outboard - fixed for next patch VRconfig.txt file missing - fixed for next patch Starter not strong enough at high density altitudes - fixed for next patch Engine start process going too fast - improved (total duration matches) but fix in LR´s court Wing illumination light not working - fixed for next patch Visual texture glitch on underside of left wing - fixed for next patch Taxi light a bit too dim MCP backlighting a bit too dim Window heat OFF logic reversed for right side windows - fixed for next patch No turnoff light for right side - fixed for next patch INVALID ENTRY message when trying to manually enter a V1 on TAKEOFF REF page - fixed for next patch Pitch up moment change during liftoff and landing too strong - fixed for next patch Idle fuel flow too low - fixed for next patch No CDU backlit keys - fixed for next patch. FMC / Gizmo crash when executing VNAV calc with only one waypoint in LEGS - fixed for next patch. ECAM gauge needles not lit up at night - fixed for next patch. Added four commands to command the fuel lever to idle/cutoff. For hardware binding to buttons/switches. Linked to default XP commands to connect/disconnect/toggle the GPU. Helpful for VR users. Cockpit door default to pen in the Turn-around mode Cockpit door occludes front galley lighting at night when closed. Fuel Crossfeed annunciator dimmer (less bright) when crossfeed valve open. Was too bright. - fixed for next patch.

Hello All, This will serve as an official announcement that we have released the version 1.51 update for the Take Command! IXEG 737 Classic Plus. All customers who have purchased the IXEG 737 Classic Plus up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the IXEG 737 Classic Plus from today forward, your purchased download will already be updated to version 1.5.1 for you. IXEG also has a new website documenting changes, so click here if you'd like to keep continually updated! What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original IXEG 737 Classic download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug fixes: Level-2 Validation failure Wiper Switch didn't work Standby airspeed indicator drum was not rotating Floating 3D polygons outboard of the rear doors VRconfig.txt file was missing Weak starter at high density altitudes Engine start too fast after lightoff. SLIGHT improvement implemented. Laminar acknowledged bug. Will revisit after. Wing lights were not working Visual texture glitch was underside of left wing Taxi light was too dim MCP backlighting was too dim Right side window heat annunciators were swapped Right Turnoff light was missing INVALID ENTRY msg appearing when trying to manually enter V1 on TAKEOFF REF page Pitch up moment change during liftoff and landing was too strong Idle fuel flow was too low - fixed for next patch CDU keys were not backlit FMC would cause Gizmo crash during VNAV calculation with only 1 waypoint in the route ECAM pie needles were not illuminated at night Improvements: Fuel Crossfeed annunciator annunciator is now more dim with xfeed valve open Additions: Four new commands to command the fuel levers 1 & 2 to idle/cutoff. Useful for single button/click action Cockpit door defaults to open in turn-around mode. Cockpit door occludes light from galley when shut. Linked to Default XP Commands (below) to connect/disconnect/toggle the GPU. Helpful in VR ixeg/733/left_fuel_lever_to_idle ixeg/733/left_fuel_lever_to_cutoff ixeg/733/right_fuel_lever_to_idle ixeg/733/right_fuel_lever_to_cutoff As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!

Captains, Firstly, we'd like to express our gratitude for your recent upgrade purchases. This week has been bustling with activity, as we’ve endeavored to respond to inquiries and meet the high demand for support. Level-2 Failure - Fixed! It quickly came to our attention that a number of our customers encountered a Level-2 failure, which restricted the aircraft's systems from functioning at all. We deeply regret any inconvenience this may have caused and assure you we've been working diligently to identify and rectify the problem. While we strive for perfection, it's an unfortunate reality that despite thorough internal testing, unforeseen issues can arise when a product reaches a wider audience. This particular setback wasn't evident during our beta testing but manifested for some once released. The good news is that we've isolated the cause and have promptly deployed a patch. To access it, please re-install the IXEG 737 Classic Plus from your order history. Didn't have Level-2 Failure? For those unaffected by this issue, there’s no immediate need to update. You can comfortably continue using the aircraft and await our next scheduled update for other enhancements. We truly appreciate the patience and understanding shown by many of you during this period. Thank you once again for your continued trust and support. Blue Skies, X-Aviation & IXEG

You were responded to in just over an hour of your original ticket submission. Check your spam. You've never replied since. Learn to be nice next time.

The ECAM "pie needle" illumination is missing, I've logged it and addressing it for the next patch. Can't explain the weird texture....XPlane 12 lighting still brings up surprised every now and then. -TK

As @Pils mentioned above, email/forum post from X-Aviation is the 'official' way. Soon though, we'll be putting up web based info, similar to the MU2...and the version listed at the top will be the most current version released. We won't change that version # until the actual release. Usually we synchronize updating the online info with the release itself, its part of our deploy checklist. So if you wake up one day, wondering if you've missed a release, you can check your version in X-Plane (use the 'Customize' button inside X-Plane to see the version)...and compare that against the version listed at the top of the (soon to be posted) docs. It will look like so when posted: So the current version listed inside X-Plane is now "1.5"....and that screenshot above shows what it will be when we make the next release and this info is put online. So just another way of checking versions. -Tom

Hey Morten, great to see you chime in! I will take this up with Austin in a little bit, right now we are on his case to fix the too rapid N2 rise after fuel is injected. You know him, it is better to feed him stuff one after the other ;-) All the best, Jan

Hi guy's, been a long time Regarding rotate feeling light, this is mostly an XP issue (at least in XP11 that i knew well). In short, the 737 has a supercritical airfoil (NASA term, or "aft loaded" airfoil as Boeing calls it). One of the differences between conventional and aft loaded airfoils is (as the name implies) that the aft loaded airfoils have the center of pressure further aft. Meaning also the center of lift is further aft than on a conventional airfoil. XP does not model this very well, and as far as I know has its center of lift at the 1/4 chord. So this means XP airliners have their center of lift too far in front which cause problems in the transition phase between ground and flight. Should be a fairly simple fix for Austin. There are some temporary "hacks" one can do, but it's a can of worms... Good to see the old girl in the XP12 skies - great work Jan and Tom

I did not do the original openGL...and I have never, not once, touched the code for the EFIS displays. Certainly I will investigate. We are seeing openGL funnies we haven't seen in the past. I believe Laminar have "tightened up" some of their requirements for us devs using openGL and this could have some influence. Now a little "insider info" for those here. For a while now, I've been setting myself up to work on XP full time and its' been a long road to get to this point, getting everything up date and redone for XP12.....BUT there's still a little bit further to go with regards to code infrastructure. I liken where we are now to a remodeling project in a crowded downtown.....so for example, you may work in some building that's getting remodeled and there is scaffolding all over the place, but the building continues to "operate". We want to make that operation as normal as possible of course, but while folks use the IXEG...we're changing lots of stuff under the hood to be more lean and "future proof". This whole "Level-2" activation issue folks are seeing is part of an interim technology..much like scaffoling...and won't be around forever. We are trying to make this rework as transparent to the end users as possible while we demolish / cut / retool / remodel code under the hood. A big part of this work will be the graphics code. With the 717 waiting in the wings....with six EFIS displays...EFIS graphics are a big deal now. SO...I'll just say that we're knocking heads with folks from Real Sim Gear and also Saso/Totoriko, to make sure we have modern tech/methods and we can move all these products well into the future. As far as this HSI thing....I'll be looking at it for sure. -TomK

I understand and respect your perspective. Pricing and upgrade strategies are always a challenging balance between covering development costs and keeping customers satisfied. We’ve based our decisions on years of data and experience in the market. There will always be a range of opinions, but we feel we’ve struck a reasonable balance. We believe in maintaining transparency and good intentions with our customer base, but our stance on this matter remains unchanged. Thank you for your feedback and for being a valued customer. We're more than confident the updates ahead will get much love, and for that we're excited to have you on the journey with us.

FYI @Pils....this release really is 'foundational' with an eye on moving forward. Indeed we've had to strip out a few things to make way for more remodeling. Part of our roadmap is to not only focus on the aircraft proper, but also develop more informational resources, i.e. a web-based documentation system to augment the written stuff, similar to the MU2....so there will be an 'IXEG website' where we can put out this kind of information, documentation and other value added content for users to access. NOW...will folks read the stuff we provide then? who knows but we're going to be putting it out there anyhow. TomK

This is a new feature to improve airflow in the cabin on flights where they serve beans or peas!

Hi Tom/Jan, I was doing some basic hardware integration with V1.5 (specifically using @VirtualCPT's excellent XMidiCtrl), and I noticed some results that may be considered bugs and/or misbehaviours, as follows: 1. Custom autopilot "toggle" commands leave 3D cockpit buttons depressed Current behaviour: After binding custom command, e.g. ixeg/733/autopilot/HDG_mode_toggle for heading select, to keyboard key, when the key is pressed (command phase “begin”) the 3D cockpit button for HDG SEL is depressed and the mode is activated, as shown by the lamps and on the FMA. When key is released (command phase "end"), 3D cockpit button stays depressed, see below: Expected behaviour: Using custom commands should have same effect as using mouse button on 3D cockpit manipulator, i.e. after releasing key, 3D cockpit button is returned to normal "out" position. Also, while key is held (command phase "continue"), 3D cockpit button stays depressed. 2. Using default autopilot "up"/"down" commands does not animate MCP controls and no sound is played Current behaviour: After binding default autopilot command, e.g. sim/autopilot/heading_up (or airspeed_up, etc.), to keyboard key, when the key is pressed the heading value in the "window" is changed, however the corresponding 3D cockpit knob on the MCP does not rotate, and no sound is played. Same applies to course knobs when using default "obs1" or "copilot_obs2" radio commands (there's no custom ones that I could find), and surprisingly the custom "HDG_bug" IXEG autopilot commands. (And possibly others?) Expected behaviour: Using default commands should have the same effect as using mouse on 3D cockpit manipulators, i.e. value changes in "window", knob rotates, sound plays. 3. Default vertical speed commands have no effect Current behaviour: After binding default autopilot commands for vertical speed, e.g. sim/autopilot/vertical_speed_up, to keyboard key, when key is pressed the vertical speed does not change, nor does the 3D cockpit wheel animate or play sounds. Expected behaviour: See #2 above. For context, the default autopilot commands are often the first thing people will try to bind, and are also part of default or hardcoded configurations for some hardware, e.g. Saitek panels. Additionally, they have the advantage (over the custom ones of many add-ons) of "auto-repeating" when "held". Any questions please let me know. Thanks!

and TBH....this UI with the cockpit is over 10 years old. There are a lot of things I want to redo for more "natural immersion"...so usability will get its turn soon. -TK

Thx @Pils I hope these didn't work in XP11 and then just "stopped working" in XP12 ??? We really haven't changed any of our manips / command structures. I will say that I think a really comprehensive "hardware compatiblity pass" for these kinds of things....similar to the MU2 hardware pass, is warranted. X-Plane has introduced tons of commands that weren't available when we coded this thing up...and we didn't tie into all of them at the time. Of course hardware wasn't as prolific and as full-featured as it is now.....so we do have some catching up to do here. As usual..this post is logged on my list. We're prepping a patch now for the obvious stuff from the last week...and I suspect we'll go a few more weeks seeing what else turns up, and once I feel we're stable...then I'll set about with the hardware pass. I'm also preparing 'MU2 like" online docs...and we have over 1200 custom datarefs....no telling how many commands. So it needs a good audit. -TK

I've not been getting reports about widespread stuttering, and at least on my end have made no mention of some form of a fix for it. I recall in the past some people had stuttering in the v11 version if their anti virus was kicking in. Creating an exception for the X-Plane 11 folder helped that. Either way, this topic is not about Gizmo, so let's keep it on track in here, please.

Four new commands: ixeg/733/engines/left_fuel_lever_to_idle" ixeg/733/engines/left_fuel_lever_to_cutoff" ixeg/733/engines/right_fuel_lever_to_idle" ixeg/733/engines/right_fuel_lever_to_cutoff" So for the next patch, coming up shortly....executing these commands will animate/move the levers between the extreme positions with a single command/click. We did not originally embrace the concept of animating the controls based on single clicks for various reason at the time. IN the MU2, this paradigm is ubiquitous and I suspect I'll end up auditing all the controls in the IXEG cockpit for which ones are suitable to animate to some position with a single click -TK

With regards to your observation of the exterior sounds...our sound engine makes no distinction between interior vs exterior with regards to the software...its simply a "sound" in all cases. All our sounds are effected only through: "play", "stop", "adjust volume", and "adjust pitch", nothing more. When you open the window from the inside view for example, we simply "ramp up the volume" of some sounds...they are already playing. Moving the camera around the interior has the same effect on other sounds...you get closer to the panel, the fan noise "ramps up" too...yet doesn't cause a crash. I think there's something more sinister going on; however, as Cameron mentioned......X-Plane and plugins is real chemistry. It only takes one unique combo to create a reaction and finding the catalyst can be a challenge. We are certainly dealing with that here in my opnion and getting Laminar to help find data points at this stage is a prudent step. Ceratainly we want to add this one to our knowledge base. -TK

Hello, it was the 124thatc plugin that was causing the "Level2-fail licence invalid" problem. After removing this plugin, the 737-300 works normally. Thanks to the Ixeg support team for their help.

I've just tested the fix, a short hop between Porto and Faro, with no issues to point out, besides the already reported bugs. I'm thankful to IXEG team for bringing my favorite 737 to XP12!

XP 12 IXEG 737 Classic until Cargo variant is made available.

@fortinworkaround....put two waypoints in the LEGS page at minimum before executing.....that should get you past the error.....then after you get airborne, you can put MIGLO into the first line and execute if that was your intended plan (one waypoint only). Looked like the crash happens when running a VNAV calc with only one waypoint in the legs page. Already fixed for next patch. TK

Did my first full flight, and here is what I have observed, I'm a NG/MAX instructor but never on classic so don't hold much credit then.... Taxi: Seems need a lot power to get moving, over 40% is quite high IMO but not sure if it's true on these old engines. T/O: I made a improved climb with BPS data, the runway is almost gone, 15% of margin seems about correct (maybe a little short, and I'm using ATM it should have more margin then). However the rotate feels very nose light and I almost feel I have a tail strike (if it's on -800) CLB: climb rate seems right, seeing the record about 10nm/2min longer than FPPM data, good enough. CRZ: Compare to realworld cruise table, the N1 and FF is almost spot on! DES: VNAV actually works mostly fine, and the descent rate matches FCTM data quite nicely. On final N1 and pitch all looking good. Flare: In contract to T/O, the nose is very heavy, kinda like most airliner port to XP12 or XP11 EFM without proper adjustment...(for example some A350 is almost unable to flare...) Landing roll: Factor out my short flare distance, the landing roll distance is almost the same as the number I got from realworld data with Autobrake1, very impressive! Over all, it feels believable and could flown by the book, The main problem seems with in XP12's new ground effect scope, feel both noes light on TO and nose heavy on landing (weird). and also maybe engine is a little bit under powered? I mean I'd love to have 22K engine then...but compare to 20K data it still feel a little bit short. I might push it harder to test it against the "Flight With Unreliable Airspeed/Turbulent Air Penetration" chart! Not many high-end add-ons can pass that!

..oh noooo ,thanks Jan and Jude ,my mistake ,i turned the upper knob of the HSI That's the problem when you don't fly a plane like that often enough

After few more flight I can say the rotation (both TO and LD) issue is the most annoying one, even the LVII bug I can get around, and all other bugs I can make a flight condition that get avoid, but only this one.... even with anticipation, the muscle memory on my home setting is hard to replace, explically when all other flight going smoothly so I almost forget these 2 kinks.

Thx for rerporting. I put it on my list this morning to check.

@Cameron Update doesn't work for me see my post please https://forums.x-pilot.com/forums/topic/27190-ixeg-no-power/?do=findComment&comment=195360

You are right, I can see it with the "front galley lights" being on! I think it is an artifact of X-Plane´s lighting engine resolution, lights that are further away will have less resolution when it comes to their lighting effects to save on rendering performance (kind of like the shadows do, too). I think the ultimate goal her is to emulate the cockpit door and rear wall being really opaque...so that there is no lighting from the cabin if the door is open (in the real airplane the galley lights go dim when the cockpit door is open).

Hi axmiha, I thought you were talking about the screen itself - but the keys should have backlighting that comes up with the center pedestal rheostat, which they don´t! So thank you for reporting that! That "phong" you see is not showing on my screen, but I have seen something like that before, I think it may depend on graphics card settings/driver/anti-aliasing?

the patch has been made and is being tested with select folks. Several testers have confirmed its fixed their issue thus far. It may still be a day or so as there are other precautions to be made.... and we don't want a 2nd occurrence to happen. Much better to take a day or two to make sure its good and get this one totally behind us. As to the unfortunate timing..see recommended post at top of this page if you haven't already. it explains the weekend thing. -TK

Got my discount code this morning and bought the Classic Plus right away. I just wanted to say "wow!". It's really looking good and I look forward to fly it later this week, when time permits. Great stuff! Now I can retire XP11

Same here, this is really frustrating... it never happened to me with any addon...

Thanks for the update. Some wear-in is expected with every release. No worries. Appreciate that you guys have been on here, keeping us updated. For me that is the most important. Bugs will sort themselves eventually. IXEG was my first payware back in 2017 and I'm grateful that it is being given a new lease on life in XP12

I can not WAIT to get there! Me and the wife used to live in a seaside town with lots of "snowbirds", folks who'd come down for the winter and drive horribly slow. I said then, " I can't wait till I can do that and enjoy it" TK

OK. I'll wait. "pensioners got lots of time" . Old saying in South Africa: "Pensioners are not necessarily bad drivers. They just got lots of time". At 74 started way back in the 1990's on flight sim. A 7" floppy disk back then.

Yes it will, though we will probably continue to provide the one avail now in parallel. So you'd have two ACF files...where the only difference will be the exterior objects. I expect we'll paint up the same liveries we do now, in high rez form, but of course new ones will have to be created for other liveries. This is probably annoying for "livery consumers" and great news for "livery painters" -Tom

The installer not that simple, it uninstalls the previous ver than installs the newer one, i assume that is to ensure a clean update.

A link for those who many not have seen it. http://togasim.com/ixeg_15_whatsnew/

https://forums.x-pilot.com/forums/topic/26656-mu-2210-pax-and-fuel-load-manager/

I moved the post to the Bug Reports forum. You can post here in the future.

X-plane 12 X-Plane 11 And this is the weird texture at night in the binder and pedestal. If any feedback is granted, I would say that the brightness of the analog pilots instrument is too intense, where you have to set it almost to minimum do handle the brightness. It could be related to HDR monitor and X-Plane HDR space, but yeah. I would describe like that. But on general. wow. That sent me back to my MCC training done in a 733 Level-D sim (motion was disabled to reduce costs).

Thanks for fixing !

X-Aviation have their own ways of doing things. The developers won’t be getting involved with SkunksCrafts to use theirs.

So to answer my own question. Well I did some more digging and it looks like that Navigraph is geared towards the flight simulator community and they use Jeppesen as their Navdata source. Now that is pretty durn cool-I am impressed. I used Jep for my Pilot Class way back in the early 80s. I am retired and will have to save up for the annual fee if I decide to go that route.