Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by daemotron

  1. If you mean whether it will release this weekend, I don't think so. Tom posted a quick update last week, where the time frame sounded more like end of May - cf. this post:
  2. After almost a year of silence, the author has published another blog post, giving more details about the status and progress of the project: https://x-plane.hu/L-410/blog/2022/03/07/devil-in-the-details/
  3. As I see it, it's probably not worth letting visual surface effects (icing, precipitation on aircraft surface) get into the way towards release at this stage. XP 12 will bring a lot of changes there, so there's something to look forward to (new APIs to fiddle with, yay! - at least for the windscreen). I'm all good with beautiful steam gauges to start with - though I secretly hope the new lighting engine will help giving analog cockpit instrument this distinctive look of heaviness (I don't find a better word for it) which seems hard to create in XP 11.
  4. Just beautiful! Oh, and did I spot a flat-pitched propeller with engines off? Does it mean you found a way to somehow sneak in the blade latches?
  5. Absolutely fantastic, I love the way you animated those instruments!
  6. I received several reports from FSEconomy users, complaining about flight cancellations due to airborne refueling. Maybe @skiselkov could shed some light on how the fuel-related data refs are used. When starting a flight, the FSEconomy client attempts to set the fuel ordered in FSEconomy by writing the fuel weight split out among the tanks to sim/flightmodel/weight/m_fuel. Thereafter, the FSEconomy client monitors sim/flightmodel/weight/m_fuel_total, expecting it to be equal to or less than what it was during the last check. If it's found to be more than it was on the last check, it will cancel the flight with the "detected airborne refueling" message. So would be great to know if there are situations where sim/flightmodel/weight/m_fuel_total can increase in flight with the Challenger.
  7. Wow, what a beautiful cockpit! And did I spot there a GPS-free version for old school radio navigation?
  8. That's great, I highly appreciate this! Thank you very much!
  9. That'll be an excellent bird, looking very much forward to flying it! Speaking of modern glass, the GTN 750 would be a great companion for the G500. Any plans to (optionally) integrate it into the 3D cockpit?
  10. This is blatant piracy.
  11. Excellent news! This is bound to become a superb aircraft. Thanks for keeping us Moo fans up to date
  12. Tom, that's coming along great!
  13. What an excellent little bird! I just love it; it's great to fly. Any chance we might get a paint kit or at least a white livery for custom paint work?
  14. 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").
  15. Wow, what a pace Love how you're taking any effort to deliver the perfectTM product to us.
  16. 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
  17. 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
  18. I think I know what I'll be doing next week-end
  19. 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...
  20. 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
  21. Great! Also interesting how a dark colour makes the nose section appear to be less "brawny" than in white.
  22. 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).
  23. Wow, great to see how you're constantly pushing X-Plane beyond the current generation...
  24. No, only cargo doors will open. Pax doors will come in a future version...
  • Create New...