Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


tkyler last won the day on November 10

tkyler had the most liked content!

Community Reputation

1,736 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,843 profile views
  1. tkyler

    Throttle and Prop levers not movable

    That's good debug info. I'll ping the XA guys...haven't seen this one myself yet. Report back asap. -TomK
  2. tkyler

    Throttle and Prop levers not movable

    Thx Michael, Lets start with the GizmoLog.txt file, found in the root X-Plane folder. Fire up XP from scratch, doesn't matter if hardware is connected or not, load the MU2, verify the throttles/props not working, then shut down X-Plane and grab and post the GizmoLog.txt file here. -TomK
  3. tkyler

    Throttle and Prop levers not movable

    See this link: check out pages 2-4. OK..so if the props aren't spinning, the gizmo scripts are not running for some reason and we need to figure out why. That's generally 'back end' technology and I'll need to consult with both X-Aviation and the Gizmo developer for some thoughts on this and get back to you asap. Please be patient with us Michael...these guys I work with are indeed committed, but our spouses generally have some demands for our weekend time as we do have habits of working constantly. I'll put out some feelers just the same just now and we'll seek to get you answers asap. --tom kyler
  4. tkyler

    Throttle and Prop levers not movable

    Good thing there's a new and more advanced one coming then! So best way to confirm the gizmo scripts are running is if the props are turning (via external view). The prop animation is custom controlled by the scripts and would just be "locked in place" if gizmo isn't running. If it IS running and the levers don't work....then we'll need to look at the x-plane joystick mapping next just to be darn sure....and after that, we may be in for some debugging. Can't say we've dealt with this one much, if at all. Thanks for your patience and inputs. -tkyler
  5. tkyler

    Throttle and Prop levers not movable

    Quick question. you mentioned that the thrustmaster is unplugged....did you unplug it before starting X-Plane? Or unplug it after starting X-Plane. I'm guessing the former and that you've probably tried it a few times without the Thrustmaster joystick? First thing we'll need to determine is if the Gizmo / Lua scripts are running at all. If they are running and only the throttles and prop levers are acting up, that would definitely be odd. Some levers and buttons are 'default' and do not use custom coding and so would work when the throttles wouldn't. So lets start with this one question, I'll keep an eye on the forums here for quick responses and hopefully we can get you fixed up. -tkyler
  6. 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
  7. 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
  8. 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.
  9. Starting to put in the finer details. Moo work is getting accelerated, alongside the IXEG FMS.
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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