Jump to content

tkyler

IXEG
  • Content Count

    2,035
  • Joined

  • Last visited

  • Days Won

    231

Everything posted by tkyler

  1. as far as "what to look forward to", my response is "what are we still inspired to do"...and subsequently...will want to try to get to. The answer to that is a lot actually. Certainly the VNAV/FMC is highest on our plate. After that, the 3D cabin/doors wrap up, etc. After that, wing-flex.....after that, 400/500 variants, etc. Those of us who are a bit older knows how fast life moves and things can get in the way. For years, I've been working towards the goal of Xplane being the only thing I have to do to get by and I can honestly say that as of last month, that has finally happened.
  2. not for V1.9; however, V2.0 is in the works and well underway. https://forums.x-pilot.com/forums/topic/19322-update/
  3. OH...another possibility because it just happend to me. I forgot to de-active the parking brake. Indeed that keeps you from attaining takeoff speeds, even at full throttle. FWIW
  4. more 3D porn for the attentive. Nowadays, the 3D has to deliver excruciating detail, so its a big screenshot so nobody is getting faked out. Immersion is the name of the game! I'm getting close to wrapping up the cockpit geometry (texturing is another matter). After that I move to some details on the landing gear, then the wings...then FMOD sounds and the programming and texturing; however, with as much experience as I've had with this aircraft, I don't think the programming of the systems is the long straw. Its a relatively simple (but FAST!) aircraft and I have lots of legacy code from
  5. Our version models the "start locks" feature of these Garrett engines, which is the default setting when you load the MU2. When the start-locks are on, the aircraft will not provide any thrust when advancing the throttles....you will observe about 105% on the RPM gauges but no significant torque on the torque gauges with start locks engaged (the 106% RPM limit is the fuel governor keeping the engine from overspeeding with the prop pitch being 'flat', (i.e providing very resistance) The nominal procedure is to first move the power levers fully to the reverse position, which causes the p
  6. ....for the crickets.
  7. Quick update: We are deep into the VNAV rewrite. Not just poking around and tweaking....we're cutting out huge swaths of inefficient code....and I have to say, its going really well so far. I believe this will make the VNAV calculations an order of magnitude easier to perform.....and if there are any issues during testing, at least I don't believe it will be "whack-a-mole" where one bug creates another. We'll keep you posted. We are working on this regularly at this juncture. -tkyler
  8. we may have to move this one "up the chain" to Laminar. I know I haven't touched this particular object and even on my end the "triangles" just appeared at some point. That being said, it is probably something we can fix on our end...this is typical of Laminar tightening up their graphics code that exposes some weakness that wasn't exposed before... It is only on this one object on my end. We'll dig into it for sure. -TomK
  9. Holds / VNAV are in our current sights. What kind of progress we make remains to be seen, but we are actively focusing on it now. -tkyler
  10. I will yes. Quite a bit more progress on the cockpit. Finally some "downhill work" after messing about with the interior trim -tkyler
  11. I really couldn't say. Are you using "Dataref Tool" as your inspector? I will say I recall some "absentee datarefs" when I tried it, that I couldn't explain (and could plainly see with DRE)...which is why I went back to DRE for dataref work. I use DRE for dataref feedback and DRT for working with commands. DRE supports the pipe symbol for "OR", which makes it useful enough for me to isolate whatever datarefs I need. -TomK
  12. perhaps VS mode wasn't activated? Were you trying it while sitting on the ground? Works on this end.
  13. rgr, I was responding to your question about how to actuate VVI above. For the levers, we have the following datarefs to reflect throttle lever angle when in autothrottle: ixeg/733/engine/eng1_thro_angle / ixeg/733/engine/eng2_thro_angle ...FWIW, we also have for the reversers: ixeg/733/engine/eng1_rev_angle / ixeg/733/engine/eng2_rev_angle Regarding the default 737...as one who used to work for Laminar developing aircraft, they keep their customization to a minimum and develop their models to use the default datarefs. If some significant functionality wer
  14. VVI wheel dataref actuator is: ixeg/733/MCP/mcp_vs_target_act Regarding autothrottle servo, we don't currently have a dataref for that, but we should be able to add one. I'll have to get with Jan to go over the current functionality and see how we can weave it in. -TomK
  15. another peek of the business end of things.
  16. Actually I've been rethinking the 'complete rewrite'....but I should mention there there are two significant rewrites planned. 1). the VNAV algorithms and 2) the XP1100 Navdata integration. Originally, the idea was the XP1100 navdata is of a format that would make LNAV route building a bit less painful (being only one format instead of 2, i.e. Navigraph and Aerosoft)....and a reliable lateral route is required for a successful vnav calculation.....hence combining both heavy rewrite tasks into one activity; however, we've seen enough success with the recent LNAV route building....that we fe
  17. A bit more progress on the cockpit. The window trim proved to be really difficult to get lined up where everything looks "proportionate" with all the reference pictures / angles. But with those out of the way, things are moving a bit quicker again. The panel shown here is th legacy panel, not the new one...so that also will get a "detail" makeover. -tkyler
  18. Also, a clarification between depicting the published restrictions vs. honoring those in our VNAV calculations is warranted. Previously, we did not even show the restrictions correctly on the LEGS page....and that is a separate issue from a VNAV calculation where you have to assess those restrictions with other paramaters and ultimately calculate the altitude for a waypoint. As Jan says, the VNAV rewrite we're doing will address the issue. -tkyler
  19. working on it as we speak. Work on it IS in active rotation and its priority. -tkyler
  20. There is no power button on the copilot side Avitab. Since the avitab screen is shared between both, and 99%+ of users fly from the pilot side, we didn't want a copilot actuation of a power button to shut down the pilots side (in the case of a shared cockpit). Are you encountering the same issue with the power button on the pilot side Avitab? -tkyler
  21. Thx Gents. Both these errors (legs page) and the #503 errors are fixed and in the next patch. -tkyler
  22. The error message pertains to the LEGS page "drawing function", which means you were showing the LEGS page on CDU2.. Indeed I can recreate this error if I put CDU2 on the legs page and then repeat your procedure! Lucky you were on the LEGS page (sort of). Thx for finding and reporting. Its already fixed for the next patch. -TomK
  23. Thx Tim....we've seen one code break already and I'm already looking into that fix. I am quite driven to make this very reliable and accurate and user tests/inputs such as yours are. a great help. I'm committed to hunting these down as soon as they're found! -TomK
  24. Thank you gents. Its amazing to me that diversity of situations that you find that we just can't seem to locate ourselves. I will jump on this asap; however, we've had a death in our immediately family I'm dealing with the remainder of this week, but will return to debugging these straight away. With the rewrite out of the way, I do not expect this debugging to take long. Thanks so much for reporting. -TomK
×
×
  • Create New...