Jump to content

tkyler

IXEG
  • Content Count

    2,027
  • Joined

  • Last visited

  • Days Won

    222

tkyler last won the day on January 17

tkyler had the most liked content!

Community Reputation

2,372 Excellent

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

17,716 profile views
  1. 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
  2. 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
  3. I will yes. Quite a bit more progress on the cockpit. Finally some "downhill work" after messing about with the interior trim -tkyler
  4. 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
  5. perhaps VS mode wasn't activated? Were you trying it while sitting on the ground? Works on this end.
  6. 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
  7. 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
  8. another peek of the business end of things.
  9. 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
  10. 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
  11. 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
  12. working on it as we speak. Work on it IS in active rotation and its priority. -tkyler
  13. 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
  14. Thx Gents. Both these errors (legs page) and the #503 errors are fixed and in the next patch. -tkyler
  15. 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
×
×
  • Create New...