Jump to content

daemotron

Members
  • Content count

    174
  • Joined

  • Last visited

  • Days Won

    3

daemotron last won the day on October 13 2018

daemotron had the most liked content!

Community Reputation

85 Excellent

About daemotron

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    EDHI

Recent Profile Visitors

2,063 profile views
  1. daemotron

    Bug Report

    I just checked it, and indeed the GPS can override the NAV1 signal (at least for the Narco NAV there's a difference when toggling between VLOC and GPS). However, the new autopilot code requires that you move both Autopilot switches on the glare shield - they need to be set to FRONT and NAV1, and I noticed by default they were in BACK and NAV2 position. Plus you need to dial in a plausible front course, and bring the aircraft into an angle where it can intercept (<45° iirc). And of course your gyro must be adjusted...
  2. daemotron

    Cessna 310L v1.0.9 Update Released!

    Hm, it's Sunday, so be patient and wait until Monday. I'm sure Cameron will tackle it as soon as he can, so let's not begrudge him the weekend.
  3. daemotron

    Fox Island North elevation issue

    It's actually a (minor*) bug - 6Y3 was exported with an elevation of 0 (ft AMSL), whereas 3MI2 was exported with correct elevation (616 ft AMSL). When Runways follow terrain is active, the airport elevation is ignored by X-Plane, and the airport is rendered on top of the underlying mesh. If the option is disabled, or the airport definition specifies "always flatten", X-Plane ignores the mesh and creates a plateau using the specified airport elevation and the airport boundary - in this case, at 0 ft. Hence the funny "Moses" effect. *Doesn't make sense to use the scenery for 6Y3 without runways follow terrain - the runway is significantly sloped, and the terrain mesh shipped with the scenery doesn't cause any problems (steps, holes, ... whatever you may encounter out there in the "wild").
  4. daemotron

    TBM 900 v1.0.6 Update Released!

    Wow, what a pace Love how you're taking any effort to deliver the perfectTM product to us.
  5. daemotron

    [Solved] Gizmo Error when trying to activate

    Arg, you're probably right - it's too early in the morning, and I was too greedy and eager getting the TBM into the air. Will boot brain now and refuel with coffee. Then starting over
  6. Hi, this happens after entering my credentials in the XA activation window when trying to activate the TBM: Cycle Dump.txt debug.log GizmoLog.txt Log.txt
  7. daemotron

    TBM-900 Release Date Announcement & Previews!

    I think I know what I'll be doing next week-end
  8. Hi, this is just for information, nothing dramatic: After upgrading Bitdefender from 2018 to 2019, I found it blocks the X-Aviation installers from authenticating to x-aviation.com. Apparently the installers use HTTP (not HTTPS) to submit the user credentials entered in the installer, which is detected by the new Bitdefender version. Consequently, the installer freezes (you can still cancel the process). To work around, go to the Bitdefender notification page and look for the message related to this event. Below the message you'll find a button to add an exception for x-aviation.com. After that, you'll have to terminate the running installer process and start it again - and it will work flawlessly. That's how the message in Bitdefender looks like (the one marked in red):
  9. daemotron

    Condition Levers

    Hi, not sure we're talking about exactly the same thing here, but might be the mixture issue sneaked somehow back into version 1.5 - or maybe the fix can hit problems in specific circumstances; I can't tell. Here's what I experience: The Saab apparently needs mixture set to something substantial (in the vicinity of 1.0 or slightly below) for establishing a fuel flow. Today I was repeatedly not able to start the engines (which I could do all the previous days without problem...), and I was running out of ideas when I finally enabled the display for some data refs, mixture being one of them. I have one axis assigned to mixture, and when dealing with the Saab, I always had my hardware in the cutoff position. So far this never did any harm to the Saab, as apparently the plugin code at some place overrides mixture values and sets them to 1.0. With the data display activated, I could see the mixture value oscillating between 1.0 and some very low values, around 0.1 - apparently, my hardware controller got a bit noisy and thus interfered with what the Saab's code tried to do during engine start. The result is quite interesting - when starting the engine, ITT kicks in and rises up to 530° - but as soon as the starter cuts off, the temperature gradually decreases, and the engine rpm spools down slowly. For me the simple and easy fix is to keep my hardware mixture controller set to full (rich) - apparently there's less noise that end of the controller, and even if so, cutting off the engines using the condition levers works like a charm even with mixture set to 1.0. I don't know if it's possible to completely ignore mixture for establishing fuel flow (it's a turboprop after all where mixture controls don't exist - I'm aware some models use the mixture axis as condition lever, particularly when they have separate prop controls), but of course I have no clue whether X-Plane permits this or if mixture generally controls fuel flow, whatever engine type the aircraft is equipped with... would be convenient though to eliminate the mixture axis as a potential source of problems for the Saab to operate correctly...
  10. For quite a while, I used SMP and RWC in conjunction with NOAA and XP default weather. What I didn't like about those two (free) options is the abrupt change of winds, which can blow a lighter aircraft easily off course... (and even a heavy when the change occurs in a critical phase of the flight, e. g. on final...) Thus, I'm looking for a solution working well with SMP and RWC, overcoming XP's default weather limitations (winds aloft, update frequency...) and offering a smooth atmosphere transition when new weather data is loaded (XE does this, but has other issues why I'd rather continue using the Maxx stack). As far as I'm aware, FSGRW could be a solution, but the description is quite incomplete and I don't know how well it really works with XP. Before investing another 40 bucks, I'd rather have a positive confirmation from some of you folks if you're using it and are happy with it. FSrealWX Pro is currently not available, and here as well no idea how well it does its job. Maybe someone who gathered already some experience could comment? Thanks in advance for your most welcome inputs, Jesco
  11. daemotron

    Socata TBM-900 New Exterior Previews!

    Great! Also interesting how a dark colour makes the nose section appear to be less "brawny" than in white.
  12. daemotron

    Not setting correct textures.

    Yep, that's a general problem - seasons behave quite differently on the European and the North American continent (not just England) - due to the Gulf Stream and the different orientation of mountain chains, winter comes further down south in North America, and summer also reaches further up north. Just a thought on a future refinement of TerraMaxx - if season limits could be defined using latitudes and longitudes (i. e. tiles or areas), it would be possible to better define plausible seasons for various regions of the world (also thinking of Japan, New Zealand and similar areas with specific climatic circumstances).
  13. daemotron

    Problems with MU-2 v1.8 on xp11

    Major Tom?
  14. daemotron

    Socata TBM-900 New Exterior Previews!

    Wow, great to see how you're constantly pushing X-Plane beyond the current generation...
  15. daemotron

    need help

    No, only cargo doors will open. Pax doors will come in a future version...
×