tkyler

IXEG
  • Content count

    1,790
  • Joined

  • Last visited

Community Reputation

1,513 Excellent

7 Followers

About tkyler

  • Rank
    Advanced Member
  • Birthday 09/23/1967

Contact Methods

  • Website URL http://www.x-scenery.com

Profile Information

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

Recent Profile Visitors

10,098 profile views
  1. IXEG FMC error transition EKLB

    Got this one fixed....this is a nav-data problem. I'll post an explanation later with diagrams as I find it a bit interesting to demonstrate some of the challenges here. The solution, is to edit the XML data file, particularly the transition in question. You will note in the latest data set (Navigraph 1706?), there are 5 waypoints in the transition, the last waypoint being "LB484". You need to delete from the XML file the waypoint BEFORE this waypoint, and change the Waypoint ID of LB484 to '4'. This will allow the procedure to load. More to follow. -tkyler
  2. IXEG FMC error transition EKLB

    Thanks for testing TomS. This looks to be an "ambiguous intersection" calculation....which I'll have to talk to Jan about how to handle gracefully. We labor under the assumption that the waypoint nav data sequence is "sane" and in some cases it is not....and in some instances, we cannot calculate an intersection (due to diverging paths). This is "hit and miss". LSZH, for example, has this problem with newer data where it did not with older data. Its like being in Texas and saying, "head due south till you get to New York City" The numbers just won't add up...but we'll come up with some message. -tkyler
  3. Flight Planning opens Console Bug

    Got this one fixed Paul. Thx for reporting. A discrepancy in the navigraph vs original aerosoft entries brought this one to light, but it was clearly an omission of a much needed line of code in a very specific "IF path". -tkyler
  4. Flight Planning opens Console Bug

    I noticed that just before I revised my post The version that is. I'll try to reproduce with the Navigraph set. Thx. Hope I can recreate, this is a very elusive bug when it rears its head. -tkyler
  5. Flight Planning opens Console Bug

    Hey Paul. What nav data set are you using? Aerosoft or Navigraph? -tkyler
  6. MU-2 Upgrade for X-11

    relatively so....I mean, I'm giving it to two guys to continue to test for me...and when they see no changes, we do the installer and send out the email. I'm happy with what I can see as of today. Given that I live in south Texas though, I have to deal with some hurricane Harvey related issues, so a few days leeway are expected, but other than that....relatively imminent. Hope thats not too vague. -tkyler
  7. MU-2 Upgrade for X-11

    Some of updates for V11 port...is a tiny bit more than just compatibility. I finally swapped out the throttle knobs for more proper looking plastic ones...also got reflective glass over the instruments and played with some of the reflections. On the systems side, just the annunciator core code has changed. Other than that, everything is about the same as V10....oh...except I fixed the braking and also the slip indicator there for Dion. -tkyler
  8. MU-2 Upgrade for X-11

    So I've been on vacation for last several weeks....went to Oshkosh and then a 2-week road trip with the wife to see the eclipse in Wyoming. The annunciator rework was a bit more involved than I originally though, but I think I have it under control and most of the "things that light up"...i.e. annunciators are working now. I have but a few more left to code up and test tomorrow and then I'm going to get it out to a few testers for V11 testing. The new annunciator code brings some subtle animation effects to the annunciator light "filaments", similar to the effects we did on the IXEG 737 where the bulbs fade in/out when they come on. Other than that, there won't be much to notice from the V10 version. The rewrite though, provides me a better framework so that as I get underway on the 2.0 version, I can custom code a lot more systems that were not simulated before. I think we're pretty close....few more days of testing though. -tkyler
  9. MU-2 Upgrade for X-11

    squeezed in a bit more work on the Version 11 compatibility...but I keep trying to sneaking in a few bits. The annun system really needed some love, so I dumped the prior code based and got the annunciator system rewritten so the annunciators lights are back. It won't feel much different from the consumer end, but the system is much more flexible for future dev work when I get onto the V2.0 version. Of course the brakes were re-done, etc. I'm currently working on wiring up on the annunciators to their systems. ...at least the systems that are relevant. Once the annun stuff is done, we'll test again and see where we are. -tkyler
  10. To IXEG - a roadmap?

    The road map is to get the V11 compatibility version out, which is imminent....then go back over the FMS ...VNAV, holds, etc. While that is ongoing, we are also working on new cabin 3D elements. That is the immediate path. After all that...and the plane is performing well and looking well, then I myself will be interested in some failures type of interaction -tkyler
  11. Unable to shut off VNAV v1.1

    indeed that is one we have never seen.....if its a quirk in our code, then I'm thinking maybe our code is self-aware and writing itself As Jan said, we're going to do a revamp here in the near future. -tkler
  12. Battery Bus sources

    Hi Jens, its a bit of a convoluted circuitry dependent upon multiple inputs...especially when messing about with failures. Standby power is normally sourced from "Transfer bus 1" via a relay that is energized from the DC bus 1. When the transfer bus 1 fails (or DC Bus 1), then this relay relaxes and connects the standby busses to 'Side 2'...specifically the battery bus. You should be able to fail the transfer bus 1 (or DC Bus 1) and the battery bus and have the standby system go down....BUT that won't happen because I just discovered a bug in my code while testing this. It does not affect your scenario however. ...and I have fixed the bug! -tkyler
  13. First official XP11 screenshot

    The above question illustrates the challenge for XA in developing a robust installer. The installers used have to be programmed to handle a wide variety of cases and some unknown number and type of files that may or may not be changed by the IXEG team in the future. This requires some time of fore-thought to determine what will be required by users and ensure those cases get coded into the installer. Bandwidth on this level is quite expensive so just downloading everything every time is not a valid option...so crafting a "smart installer" is where the time is going currently. The payoff will be a robust and quick installer for future updates. This whole transition to V11 has caused a bit of a "traffic jam" in our infrastructure and that's all this is....best to proceed through it cautiously lest we end up missing something obvious. Once past it, we expect a clearer road for updating. -tkyler
  14. MU-2 Upgrade for X-11

    Hey Dion....I removed the "lens" for the turn coordinator so you can see the ball, though the guiding lines are not there anymore. The lighting model has changed significantly enough that I can't fix it with the current paradigm of the Mu2, which is rooted in V8 tech...BUT you can at least see the ball now. Of course the pure V11 2.0 will rectify all that business. V11 is fancy enough that there will be some visual compromises is getting this one "compatible"...some parts that are shiny that shouldn't be...mostly exterior stuff. But I figure better to be able to operate it in V11 in the mean time. -tkyler
  15. MU-2 Upgrade for X-11

    I did manage to get quite a bit of time today working on the Moo in V11. I think I got everything under control and threw in a few texture effects. The nacelles are now 'true mirrors" as opposed to baked on...and the yoke is a bit shinier. I'm going to let a few people test it out to see if things work OK. I did make an adjustment to the brake code also...hopefully it'll be a bit more consistent. when the testers give me the all clear, we'll get it out for V11 compatibility. -tkyler