• Content count

  • Joined

  • Last visited

Community Reputation

1,564 Excellent

About tkyler

  • Rank
    Advanced Member
  • Birthday 09/23/1967

Contact Methods

  • Website URL

Profile Information

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

Recent Profile Visitors

11,156 profile views
  1. Problems with MU-2 v1.8 on xp11

    ....and...there's more in the works for the future, but don't bother to ask when. Alls I know is that the MU2 needs an upgrade and its time to bring it to top-tier immersion. -tkyler
  2. Problems with MU-2 v1.8 on xp11

    I will be testing on the latest yes.. -tkyler
  3. [Confirmed]VNAV descent

    Thank you for reporting. Changing the route during descents does indeed cause some issues...some of which are due to differences to the way Navigraph and Aerosoft encode some routes differently. We are working on 'normalizing' the data between the two, such that we have a common format to improve the VNAV performance when changing routes mid-flight. We appreciate your patience and sorry for the inconvenience. -tkyler
  4. Problems with MU-2 v1.8 on xp11

    99%....thats 99% of the manual complete....NOT the QA checks still to be done....but its a step closer. I expect to start the QA flights this weekend. -tkyler
  5. Problems with MU-2 v1.8 on xp11

    Maybe 95% now. The bulk of the manual, sans procedures is written, I'm just having to add and format all the procedures. The quality control that takes some time also. I still have to read through the entire thing once done and operate the aircraft in accordance to make sure I don't write anything that isn't in the aircraft and vice versa. Many procedures I left out of the previous version are added back into this one as the simulation has evolved, etc. -tkyler
  6. Problems with MU-2 v1.8 on xp11

    No chance on an updated plane without a manual describing the new feathers. I'm almost there. About 90% done, been working on it most of the week. -tkyler
  7. Holds have not been implemented yet. VNAV calculations can be problematic, especially when route modes are EXEC during descents, and we have resumed work on improving these calcs. LNAV is relatively solid statistically, but there are some combinations of procedures that can rear their ugly head. Supporting two datasets, Navigraph/Aerosoft has proven challenging due to the fact that Aerosfot uses "Runway Transition" data types and Navigraph does not...and I have found in many cases that problem routes are due to these difference. We are looking into our algorithms to see if we can hide the difference to the end user. It would have been immensely easier if we'd have just stuck with one dataset....oh well My current focus is on improving the FMS all around. -tkyler
  8. Hi John, I'd have to see the entire route you entered, including perf data to be able to "trace" the routing in code. What I would recommend is right after you EXEC a route, use the STEP function to step through the route and if you see these double lines, then pause the sim and save the file, IXEG_FMS_debug.txt, which will be in the IXEG folder. This file is generatred every time you hit EXEC, so you want to duplicate it when you see the error, less you hit the EXEC button again and lose the data that generated the anomaly. Then you can post that file here and I can examine the data and see whats what. Tom
  9. Problems with MU-2 v1.8 on xp11

    Sure. The manual update is "in progress" and I chip on the chapters a bit at a time. Being a relatively comprehensive rewrite, its a goodly amount of work. Can't say when I'll get it done, but I do work on it regularly. -tkyler
  10. Hello Gents, Sorry for the delay, college graduation, holidays, end of year stuffs. I'm back on the docs and as soon as its done, we'll release V1.9 update -tkyler
  11. Problems with MU-2 v1.8 on xp11

    tons of tweaks, and on V11.1 no less.....and its pretty much done. In fact, I was preparing the "whats new" document just this evening. While doing so, I realized that the POH is quite out of date in that the procedures in there don't include procedures for the realistic new features I just put in. Sooo....I'm working on reworking the POH and as soon as that's done, we'll kick out the update, v1.9 for XP11.1. Won't be in the next few days though...but not too far off. -tkyler For those's the list of updated stuff. Propellor start locks simulation. More accurate start sequence timing and EGTs Unfeather pumps (for putting props on locks and also for air-starts) More accurate fuel governor for idle and overspeed situations Accurate power lever range. Low thrust at Ground Idle, no more super thrust in the beta regime Proper beta range control of prop pitch via the power levers. Negative Torque Sensor / feather valve simulation. Cleaned up cockpit night lighting texture slightly to eliminate "blurred text" in several areas Fixed transponder ident function for Pilot Edge® network users. Was not working before. New volumetric propellors in side view. Small tweaks to the PBR textures for a bit shinier reflections. New preferences window for: setting default VFR codes for the GTX330. Joystick preferences for power lever usage. Split or "realistic" modes Updated procedures in the POH to reflect new features.
  12. I've got hardware working well with the Moo, both single paddle and dual paddle throttles. I am going to include a new preference, to operate the throttles either "realistically" or "split" In the realistic mode, your joystick throttle throw will match the MU2 power lever throw. That is if your joystick throttle paddle is all the way aft, then the power lever on the MU2 will be all the way aft (putting the props in beta mode). This is risky during flight, because during a descent, when you power back, joysticks generally do not have a detent to stop the lever motion...and so you can accidentally go into beta/reverse in this way. I am including a "detent tolerance" range preference though that will cause the throttles to snap into this detent when the joystick is in a certain range....and then light up the beta light on the panel (currently labeled "reverse") This allows users to know when they're at the limit of the prop governing range and have some joystick wiggle room without going into beta....and if you do pull the joystick throttle any further aft, then you know you'll be moving into the beta range ...and that could get nasty during descent. BUT, like in the real plane, when you land, you can just pull your joystick paddles further aft to go into reverse, and this feels a bit more natural. The other option will be "split", which is the way its been for some time. Cycling your joystick throttle paddle through its full range will either move the MU2 power lever between max throttle & Flight idle....or between Flight Idle & full reverse...and you use the "beta toggle" command (/ key) to swap between the two modes. In prop governing mode, this is quite natural as moving your joystick throttle forward will also move the MU2 power lever forward. But when you're in beta mode, moving the joystick throttle forward will cause the MU2 power lever to move backwards. This will ensure you don't accidentally go into beta. Its akin to "pulling the levers over the detent", in that it takes an explicit action (hitting the command key) to go into beta mode. Its natural once you get used to it, but at least now, you will be able to choose your preference. Only thing left before an update patch is for me to look at the EGT and Fuel Flow and have a few folks test. EGT appears way off in XP11 for some reason. -tkyler
  13. Hi all. with the "Black Friday" sale onging, I'm sure there will be new users who will notice the engine inconsistencies in the MU2 model, i.e feathered props and EGT, etc. XP 11 brought about several sweeping changes to the engine model and this current MU2 1.8 release was a "V11 compatibility" release, at the request of several folks who feel that some MU2 flying is better than no MU2 flying in V11. So even though V11 broke a few things, we have released it as the V1.8 update so folks could fly it again. While this is great for existing owners, for new owners it might come across as, "hey this is really broke" and unawares of how XPlane can break things during major version releases. Now the good news, is XP11 brought about some new functionality that will allow me to simulate the Garrett engine better and more accurately than ever before, and I am at present working through those changes and nearly done. So to those new owners, I say, hold on for a bit and we will be putting an update out in the near future that will get this MU2 engine working great. -tkyler
  14. well I got past the startup related issue and now am working on calibrating the NTS implementation (and NTS ground test) as well as "in flight air start" using the unfeather pump. Getting pretty close to that patch and much more accurate engine behavior. Definitely more than 10 plane-maker clicks I can tell you that Here's a good read I'm taking some sources from: I'll begin the visual rework for v2.0 in 2018. -tkyler
  15. Progress report on engine work/update patch. The engine model is now approaching very good accuracy over about 95% of Garrett behavior....including prop lock mechanism, both setting and releasing the locks...(and feathering if you forget) un-feathering pump functionality. No more "reverse" mode per se, only beta and prop governing modes as in reality. I'm considering removing the 'REVERSE' light...or at least relabeling it "BETA". Reverse thrust results with increasing beta angle. proper engine RPM control in both beta and prop modes. Condition levers at taxi will keep the RPMs around 72% range in both beta/prop modes...but will vary slightly as fuel controller response does its thing Proper lever you start engines with power lever between ground/flight idle as per real procedure, not at flight idle. Nominal thrust in the ground idle, beta more "super thrust" between ground idle and flight idle. overspeed governor. Fire-walling throttle with blades at flat pitch will limit RPM accordingly. NOTE that the Moo hasn't been tested in 11.1 yet. I've been warned by several inside folks that I should treat 11.1 integration cautiously, but until I get there I won't know. At the very least, this version will be the baseline and so still needs to be done for the current version. I've changed nearly all of the engine code. Patch date unknown. Still have to conduct flight tests with engine shutdown and air restarts....also looking to implement accurate NTS behavior during in-flight engine shutdowns...and unsure what I'll come across there. Update to the 1.x run will be free as usual. -tkyler