Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/25/2022 in all areas

  1. This will serve as an official announcement that we have released the TOGA Simulations MU-2 Marquise version 2.0.1 update. All customers who have purchased the MU-2 Marquise v2 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the MU-2 Marquise v2 from today forward, your purchased download will already be updated to version 2.0.1 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original MU-2 Marquise v2 download and re-download the file. It will download as the latest version! See all the v2.0.1 changes by clicking here! As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    2 points
  2. Here is my Simbrief profile for the Moo. The profile is based from the Kingair BE20. The weights are accurate. Nevertheless, the fuel calculation is necessarily approximate, because you cannot create a profile from scratch in Siembrief. The fuel consumption should be less than 250 pounds per engine and per hour, so around 450-500 pounds per hour. Of course without reserve, alternate and winds calculations. I will check this on my next flights and maybe update the profile using the P000 option. Payload : 9 passengers, 85kg each (187 pounds), 55 pounds for the luggage. The equipments of the aircraft are very basic. I use the model with GPS. I did not fill the PBN field (the Kingair BE20 has not). https://www.simbrief.com/system/dispatch.php?sharefleet=30045_1658249223478 All suggestions welcome in this topic
    1 point
  3. FWIW, I've seen some issues with the nosewheel steering when changing hardware config settings and not restarting x-plane, especially with regards to the toe brakes. In other words, I'd assign axes to toe brakes..test..then change back to another axis..and the nosewheel would not steer anymore, even though the "override_nose_steering" dataref was zero (which means X-Plane is supposed to control the nosewheel with yoke)...and restarting the sim fixed the issue. Assuming folks don't normally change their axes after initial setting/saving of the profile, I didn't bother to figure out why this anomaly happened and chalked it up to some internal X-Plane weirdness with conflicting assignments "pedals vs. no pedals" in the same sim session. The only common denominator I found was there was some axis set to be a "toe brake" at some point in my testing. Just a potential data point.
    1 point
  4. Because there was a configuration designed for it to work with throttles 1,2 and 3. BUT other, highly desired preferences were not accomodated for a lot of users. In 2.01, I have accomodated this other functionality and in doing so, had to change the way the hardware is setup. HOWEVER.....with the new hardware assignments, The paradigms used in 2.0.0 can still be applied in 2.01 so the levers operate exactly the same as they did in 2.0.0 -TomK
    1 point
  5. Unfortunately, with this update there was a bug related to "props are on the locks". Well, right after starting the engines, propellers should remain in the configuration: Prop Locks - ie EGT Torque should be "0". Only returning the Throttle Lever to the REVERSE range releases the lock. This is how it worked in version 2.0.0. I was afraid of this behavior yesterday, which I wrote about here: https://forums.x-pilot.com/forums/topic/24800-tbm-like-throttle/#comment-182459 So now it is worse than it was ;-)
    1 point
  6. We probably don't exhibit this exact quirk/bug. I've got the system coded so it smoothly transitions to geometric vertical guidance only when the approach is an SBAS approach and is being flown in SBAS mode vertical guidance (selected using the mode switch on the ARR DATA page). If geometric vertical guidance is enabled, then from 5NM inbound to the FAF, I start blending the baro-VNAV with geometric guidance, until at the FAF it becomes purely geometric. As usual, Collins doesn't detail the exact bugs of their code in their user manuals, and so in absence of information to the contrary, I made it do the "smart" thing. Perhaps I should "fix" this and make it do the dumb thing? I'll give the docs you linked a read and think about it.
    1 point
  7. I did flight again after re-staring XP and suddenly worked again ... I will pay attention to the GNS mode just in case. Thank you
    1 point
  8. Request livery from Africa Airlines Congo..
    1 point
  9. Just a developer commentary to any who may also read this. CaptCrash did discuss these with me and I am happy he is looking at the performance and I am also keen to improve the performance numbers; however, the relative work (relative to everything else required to be done to get 95% of the customers happy) ... to get the last 15% of performance accuracy is such that I have always found it best to do those final refinement tweaks last, after everything else is working. This is generally because the final performance tweaks can be made quite quickly....with all due respect to the FLIGHT TESTING...which is not very quick though. As soon as the obvious issues slow down, I'll will take a deep breath and start on the fun stuff, which includes performance. Call it.."round 2" of V2 work! -TK
    1 point
  10. For the early-birds https://forums.x-pilot.com/forums/topic/24825-toga-simulations-mu2-version-20-paint-kit-rc1/
    1 point
  11. Man, this is sad. But ... yes, understandable. SR22 is the only thing which did not work on Linux for me and why I continue to have Windows on my PC.
    1 point
  12. As an option, the ability to easily determine whether the switch is being pushed on or off (in or out) Possibly a momentary short green or red glow. (Not realistic but in the RW, ‘in vs out’ visible and tactile i.e. not an issue. Optional if not desired)
    1 point
  13. I don’t know if we can say when but it is on the plan.
    1 point
×
×
  • Create New...