Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


tkyler last won the day on October 9

tkyler had the most liked content!

Community Reputation

1,727 Excellent

About tkyler

  • Rank
    Advanced Member
  • Birthday 09/23/1967

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    San Antonio, TX USA
  • Interests
    Aviation, sailing, woodworking, family, engineering, philosophy, psychology, travel

Recent Profile Visitors

13,267 profile views
  1. tkyler

    IXEG 733 Development Status

    So its been a while, time for another update. There was a pause after the rush of FMS work mentioned above. During this pause, I have finished up my NASA obligations...and demobilized from Houston back to San Antonio, where I live, and some much needed stability to my schedule. Last week, I dug back into the FMS code and started coding up the route editing features using the new XP1100 dataset. This is the backbone of the FMS future with regards to performance.....for VNAV calculations, performance progress and also holds. Its one of those things that I wanted to be real sure I was ready to dig into before doing so. This route editing coding will go on for a bit......'route editing' involves building the route data that the FMS will use during lnav and vnav tracking and so is critical to be flexible and correct. It is my belief that if carefully done now, the FMS will be functional and stable for many years to come, which is the most important thing. -TomK
  2. unknown just yet Tim....the first conversation happend after a tweak to the turboprop model in general, but Laminar has since introduced a completely new "Fixed Turbine Garrett" engine model and I plan to base the 2.0 simulation on this new code for the update....but have yet to explore it fully during this 3D work phase. It is my thought that work on the engine simulation for the 2.0 release could probably be back-ported to 1.9 with relatively little effort....but I'm thinking most folks would be crazy not to update to the new model when it comes out, it'll be that much better. That being said, it may still happen. I might find its less work on my end to use Laminar's model now. We'll see. -tkyler
  3. seems the cabin doors always take the longest....making it work inside and out and also animate without colliding with other geometry is always a pain....BUT its a improvement from the original.
  4. Starting to put in the finer details. Moo work is getting accelerated, alongside the IXEG FMS.
  5. create a folder called "coroutes" inside the IXEG folder. Page 12 of the "interface guide" in the documents folder describes more detail on using the coroutes feature -tkyler
  6. tkyler

    IXEG 733 Development Status

    Hello again. I'd like to give another update. During our investigation into updating our NavData to the XP1100 format, it became apparent that this must be the way to go for long-term future compatibility and more reliable route calculations, including holds, but would require a significant rewrite of the FMS base architecture to do so. So over the last 4 weeks, we have done exactly that. We now have the beginnings of a 2nd FMS running in parallel with... but independently of.... our original FMS. We are running 'newFMS' on CDU1 and 'oldFMS' on CDU2. We will NOT be simulating dual FMCs though. This old/new arrangement only exists so we can compare the new with the old while developing the new. It is much like building a new bridge alongside an old bridge...and when the new one is ready, we will remove the old. Much of the challenges we have faced with regards to drawing routes / vnav have been related to the limited nature of the navData format we have used since we began the project. Moving to a format which have been designed expressly for "navigation processing" will go a long way towards easing our algorithm development. The image below shows the two CDUs, both on the "IDENT" page, but clearly displaying differing data as they use differing algorithms/databases....and for those curious, the pilot CDU displays 'odd' formatting simply because we were testing our new display drawing code. We are very excited moving to this new XP1100 format. We have, in 4 weeks, accomplished what took us over 24 months to accomplish originally. Of course we have the benefit of experience, but the elegance and efficiency of the new navData format and architecture allow us to focus on the FMS functionality by orders of magnitude more than before. With the new infrastructure complete, we will begin working on the route editing. The current navData set only supports about 8 different waypoint types. Arcs are not supported, as is common in today's RNAV procedures, but the new format contains all path/terminator types typical in today's procedures. As usual, we thank you for any patience you have managed to muster as we work to improve the IXEG 733. P.S. Jan and myself will be at Flight Sim Expo in Orlando, FL/USA in a few weeks if anyone wants to talk shop. -Tom Kyler
  7. Hi Mirlo, I"m doing a bit of "multi-threading" at the moment, bouncing around between the Moo, the IXEG and NASA work. That being said, I need some access to an MU2 to move forward with some more 3D and a owner about 1.5 hrs away have invited me to come see his, but I've been a bit busy preparing for SpX16 launch, which is in 2 weeks. Things get VERY hectic in the 6-8 weeks preceding a launch. BUT.....the good part.....I have NO more space missions on the calendar for 2019....and will be making arrnagments to meet this MU2 owner asap and get what I need and will then continue on with this guy. It hasn't all been on pause though, duing my coding efforts for the IXEG, I have written a great deal of code that will also go in to the MU2, to bring it to a point of "serious systems simulation" like the IXEG. I have been working on that nearly every day in the evenings....so we're moving right along and I am definitely ready for this SpaceX mission to end so I can really dig into this thing. TomK
  8. Hello All. This post will be locked as its only intended for public statement. While many people are aware of the IXEG Development status, many others will not and so this post is intended to provide clarifying information. For a while now, IXEG development has sat relatively idle. The reasons for this are multiple and have been stated in other forums; however, two significant factors contributing to that idleness have since wained and IXEG are looking at how to best move forward with IXEG updates again. There are two areas we are looking at for updates, 3D cabin/doors/animations and the FMS. Regarding the FMS, IXEG are looking at transitioning to the XP1100 Navdata format, which is derived from the ARINC 424 standard. Moving to this dataset format would yield increased accuracy in the representation of procedures and more practical data with which to improve LNAV / VNAV / performance caclulations. If it turns out that porting our code to the new XP1100 format is too cumbersome in the short term, then we will seek to patch what we have now and transition at a later time. The important thing is that IXEG are moving again to improve the FMS. Regarding the 3D, this will be a bit more of a undertaking. The development tools IXEG used for 3D development are nearly fully deprecated and there has been a major transition to newer tools and methods. This necessitates IXEG reconfigure our source material to the new formats and we have a LOT of 3D material to translate. This means that the 3D updates will be longer in coming than the FMS updates. Once the 3D is ported to the new tools though, any updates we implement thereafter would come much quicker, simliar to what was done shortly after our release for those that recall. We apologize for the idle time and appreciate all our customers and any patience you've exercised. We are sincerely committed to making the most immersive and accurate simulation of this aircraft as we can and will continue to push towards that goal, no matter where its end may be. -Tom Kyler
  9. tkyler

    HOLD for the Classic

    That's pretty cool. For the record, I am finally back to working in the FMS, including adding the holds. I'm in the process of porting over to the ARINC 424 / XP1100 nav-data format, which should make things go much smoother for holds...accurate routes / entry....just about everything route related. But thanks for this script...it will be a bit before the holds features get distributed! -tkyler
  10. tkyler

    CDU FMC Error

    I feel ya.....you just hit on one of my biggest pet-peeves. That's why my posts tend to be a bit lengthy....a readers mind forms all sorts of questions as it peruses sentences and a lot of folks who write instructions don't address those derived internal questions, leaving more questions to the end user and the lost time to "experiment and test" to get those answers and the ensuing frustration. That was the impetus behind my statement above that communication is a finicky thing....and good comms quite rare IMO. Regarding all the other little things that you are trying to learn with frustration....all I can say is that I know how you feel. While some areas of learning go easy, still many many do not and for myself at least, I have to chalk this stuff up to the pains of 'learning process'. So...regarding the scenery, did you ever get it going? If not, then post the X-Plane log file (should be in the root X-Plane folder) and there are several experienced folks here who might be able to help out. -TomK
  11. tkyler

    CDU FMC Error

    Hi Michael, Well I have a confession. I am more like you than you know. I too got interested in "airliner" type flying a while back and even though I'm programming it, I haven't fully mastered it, I still have a lot to learn. What I have learned though during my research of FMC / CDU operation, is: 1) you'd be surprised how many people aren't exactly sure how things work when recalling it from memory and 2) there are indeed small deltas to how the FMC operates between software version and some folks never quite get to see the alternative operation and so get quite dogmatic on how its supposed to work, when in reality, there are variations. I have two very comprehensive FMC manuals and they simply do not give the 'minimum criteria' for the EXEC lit to be lit....at least not that I have been able to find. All examples given in these references have you to press the EXEC key while some waypoints are loaded. So...that being said, I think you have indeed found a bug in the tutorial document. I can only guess that we might have taken a screenshot of the PERF INIT page while some waypoints were loaded and we just didn't catch it. Philosophically, I see no reason the EXEC light couldn't light up after entering some PERF INIT data without a route (at least 1 waypoint), after all, its just a way to tell the FMC "do some calculations now"....and with only PERF INIT data entered, any calculations without the route would be minimal....there are a few, but nothing that alters the flight path of the aircraft. One of my (quite official) FMC texts uses the phraseology, It could be argued that PERF DATA without a waypoint cannot be a flight, and therefore is not a flight plan....nor is PERF DATA only a guideance mode or part of the navigation database. I think this was the logic I used when programming it originally. If you have at least one waypoint (from the navigation database), then you have a minimal flight and that's when you get the EXEC light (after ACTIVATION). More confusing to me still is the term ACTIVATE. For example, below is some text from my rather official FMC manual I have. The above says that entries have been activated by pressing the lighted EXEC key; however, we all know that before hitting EXEC for the first time, there are the words ACTIVATE on LSK 6R...which must be pressed before EXEC. So.... if, according the manufacturers own manual, 'activated' results from pressing the lighted EXEC key, what the heck are we activating when we press ACTIVATE? I tell ya, communication is a finicky thing! Anyhow, thanks for catching that, we'll make the appropriate updates and I hope you don't get too discouraged. Learning an airliner and the ins and outs is daunting and I myself have a long way to go, usually I only undestand one thing at a time and right now, its holds! Thx again, TomK
  12. tkyler

    CDU FMC Error

    Hi Michael, thanks for purchasing. I did the programming for the FMC and will try and answer your questions. Mike Ray's book was a effort separate from the IXEG development, so I can only surmise here as I have not gone through it myself fully. Mike's book contains some good info that specifically relates to the particulars of X-Plane and our simulation and so the "IXEG" part of that title has some validity; but in doing so, also gives the impression that it should coincide with our simulation behavior 100%, so I understand your perspective. Could you please provide the title of the tutorials, any version numbers if applicable... and the page numbers that you are following and I will take a look and see. I can say that the minimum requirements to get the EXEC light to light up in our sim is the presence of at least one waypoint....and then hitting the ACTIVATE button from the LEGS or RTE page. Once the ACTIVATE button has been pressed and the EXEC button pressed, then the route with be 'EXECUTED' (and the route on the EFIS will be shown in magenta). Any change to the route or weights after that point will cause the EXEC light to illuminate. In reality, there are many versions of software that the FMC uses and it may be that one version will illuminate the EXEC light once weight data is entered while another does not....I couldn't say without looking at the software version history of the real FMC, which I don't have handy. IXEG doesn't claim to implement any specific version. The FMC does have some unimplemented features (holds for example) and shortcomings with regards to the VNAV calculations, moreso when edits are made while in-the-air, but is robust in quite a few areas. We support two data sets, Navigraph and Aerosoft, and some aspects of the Navigraph data encodings are slightly different and have caused me difficulties in trying to support them both, particularly with STARs and SIDS that have runway transitions. If you have runways entered before entering SID/STARs ,then the behavior tends to be a bit more stable. Now I have been in contact with Navigraph as recently as this past weekend and they are working to alter the data so that it contains more resolution with regards to runway transitions. I believe this will allow me to stabilize the routes and editing appreciably. The plan is to implement the the new XP11 ARINC 424 formats for FMC data, which will give the most accurate routing IMO. I have begun writing code to work with this data, but it is not a fast process and I certainly can't give an estimate as to when it would be deployed. Unfortunately, I have been side-tracked for the past 3 years in a rather busy endeavor, but am happy to report that I am working on it again and very much looking into enhancing the IXEG FMC. -Tom Kyler
  13. 5-blade props will be a preference. -Tom
  14. the occasional proof that I haven't abandoned X-Plane or the Moo.
  15. a little more modern, worthy of XP11 features