Jump to content

tkyler

IXEG
  • Content Count

    2,034
  • Joined

  • Last visited

  • Days Won

    226

tkyler last won the day on April 7

tkyler had the most liked content!

Community Reputation

2,394 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

18,132 profile views
  1. not for V1.9; however, V2.0 is in the works and well underway. https://forums.x-pilot.com/forums/topic/19322-update/
  2. 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
  3. 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
  4. 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
  5. ....for the crickets.
  6. 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
  7. 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
  8. 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
  9. I will yes. Quite a bit more progress on the cockpit. Finally some "downhill work" after messing about with the interior trim -tkyler
  10. 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
  11. perhaps VS mode wasn't activated? Were you trying it while sitting on the ground? Works on this end.
  12. 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
  13. 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
  14. another peek of the business end of things.
×
×
  • Create New...