All Activity

Start flying.py View File Start flying.py is a simple program launcher that is somewhat more powerful than creating a batch file. If you launch other addons to run with your flight simulator this utility is for you. Set it up once and then you'll launch your Flight Simulator and addons with a single click. Submitter VirtualGAaviator Submitted 05/30/2023 Category Plugins and Utilities  

The percentage calculations are incorrect For example: "Expected climb distance = 21", "Actual climb distance = 19". The difference is not 90.48%, but 15.79%: (21-19)/21*100 = 15.789...%. Similarly for "Expected time = 7" and "Actual time = 7", the difference is 0%, not 100% : (7-7)/7*100 = 0% And so on. Or you give a different meaning to the "Diff" value...

Sure no problem! Now trying to see how I can gather and compile some data:

The Honeycomb has at least one other axis you could assign to Nose wheel steering, if I recall. If not, there’s probably a way to use the keyboard, assuming you don’t have rudder pedals.

Thank you. Disappointed the Honeycomb will not work on the NWS issue. It jst means I cannot fly the plane....and I love the plane.

That is very kind and not a bad idea as it might help someone in the future for sure!

Maybe I’ll make a video…

Thank you, Pils, that is what I had understood as well, but for some reason the name for that state is not taken and nothing much happens (in XP12 at least...) That is why I asked for more detailed instructions DANKE und alles Gute! Jürgen Edit a few minutes later: It worked now! Thank you both Graeme and Pils

That’s what he suggested; open the airframe manager, type in a name for the state, and press Save. Done!

Thank you Graeme, for this important hint. However I rather like to determine myself when to save a state rather then relying on the autosave feature so as to be able to start with that state in any future flight. Therefore my question is: Can I save a state BEFORE leaving the plane (and XP11/12 and how to do that? Thank you in advance already and take care. Cheers Juergen

This isn’t possible. Disable Zink, it’s highly experimental.

I understand the approach from the economic side, but I don't think you see what is my problem. I bought the MU-2 aircraft in November 2022. I think at this time MU-2 didn't support XP12 yet, that's one of the reasons I bought XP11. I was never able to use it properly because it didn't work well (for example i didn't fly the missing approach with VOR or cannot fly precise VOR2VOR navigation). I waited a few months for the bug fix and in May 2023 I get from the developer that I'm only 13%!? If I want to use it as intended, I would have to buy XP12, obviously I would also have to buy a new computer. This is ridiculous. I think it would be expected of a developer to at least fix the bugs for a live, non-archived simulator a few months after the released software. I emphasize that XP 11 is still available, not an abandoned version. Thank you if you change your mind and correct the mistakes and make a final release for the 13% (according to them I am not alone and not 8 buyers of all this wonderful aircraft). Thank you and best regards. Attila

N279MA Livery for MU2, Version 2.0 by TOGA Simulations View File This folder name is prefixed with an integer. It is not required, feel free to change the name; however, beginning with Version 2.2 of the MU2 (not out as of this posting), I (TOGA simulation) will be utilizing a system whereby you can name a livery folder with an integer prefix number, and in a text file, you will be able to associate a tail number with that folder prefix integer. In this way, the tail number in X-Plane an online networks will match the livery tail number. -tkyler Submitter tkyler Submitted 05/30/2023 Category General Aviation Livery For https://www.x-aviation.com/catalog/product_info.php/toga-simulations-marquise-p-226  

Attila, I'm sorry you found this impolite. It's not intended that way. It is matter of fact, and while that may be something you don't like, lying to you about the situation would be worse. We don't have any intentions of going back to spend resources on a dying platform like X-Plane 11. 13% is a small amount of customers to put resources into, and that number will continue to get smaller and smaller as people transition to XP 12. The update will always be available to you and free for X-Plane 12 whenever you decide to make that move.

noted and logged. not sure how that one got past me, but it did!.... Thx for reporting. -tk

man, that's pretty cool! I'll get to performance at some point and will revisit this for sure (with your permission) -tkyler

Hi All, Not fully ready yet but I've put together a W&B and performance calculations Google spreadsheet, based on the 4 blades AFM. W&B payload stations are listed as I configured them in Planemaker. Since we can only have 9 stations, it's missing some of them. Performance results so far look pretty ok. I'm cross checking them with ForeFlight performance profiles for the MU2 and I'm getting +/- 10 Lbs in terms of fuel. Happy to share if that could be handy when adjusting the flight model in future versions! Cheers!

Hello: I am currently needing help in 2 areas: Honeycomb Yoke: I am unable to figure out how to get my Honeycomb Yoke to steer the Challenger 650. I have flipped the NWS switch to on...still no response to the HY. Any solutions/suggestions. I have also downloaded a 2022 Yoke and Bravo Profile onto my Honeycomb system. Avionics, MFD, PFD,CDU are not lighting up. The screens remain off. What am I missing? I have attached pics of overhead showing all power, including APU functioning. Thank you, in advance, for your assistance. Tony Laughter tlaughter@gmail.com Log.txt

Proud new Moo owner here. First off, I am still in XP11. I was under the impression that the latest installer will detect this correctly and install 2.0.4, however the version file in the aircraft folder shows 2.1.0. FYI. The issue I am having is that the HSI CDIs (both sides) are not responding correctly to any of the RXP units when the CDI mode is set to GPS. Ground-based navigation is working as far as I have tested (briefly). I have tried all-GNS and all-GTN configurations. The deviation bar does not deflect (except during the initial test where it correctly shows half-left). During the test, the CDI course also sets itself to 150, but it does so regardless of my auto-slew preference on the RXP menu. After continuing past the test page, the course re-sets to an arbitrary value (024 or something, already forgot), and will be frozen. Rolling the course knob increments the digital readout but not the needle. Also, FYI, I didn’t touch any of the shipped GTN/GNS.ini settings at first, but I did check them while troubleshooting.

Hello Cameron, What you write is quite impolite. When I bought this product 2022 November, I didn't see it written as "end of support XP11" or "latest stable version of XP11". XP12 release at september 2022, XP11 still available on the x-plane.com. Please fix the bugs in the 2.0.4 version and please correct "20NM outbound VOR cannot activate NAV" function. Of course, your income doesn't leave me cold, but face it, ending your support for something a few months after its release is a pretty bad thing. Thank you and best regards. Attila

tagged for notification of reply

My understanding is that Coop is blocked by Laminar Research. - Laminar changed how avionics are rendered. - Laminar updated the default aircraft to use their new avionics. - We as developers are waiting on the SDK and tools to be expanded in many ways to allow us access to all XP12 can do. I've attached a Screenshot from the XP-Developer Slack chat where Ben Supnik explains some of the logic behind current choices. Further in the thread Ben S. explains that Laminar is looking to expand the "click" processing to better suit things like; real touch screens, VR, VR Gloves, and boring old mouse clicks. The obvious solution seems to be to provide patched versions of the default aircraft files that can hook the the mouse clicks but I don't think it's possible at this time with the way XP12 has changed. The thread that screenshot is from was quite long and several other developers(including Laminar for their own mobile titles) are wanting better functionality for these items so hopefully it's high on Laminars priority list.

Hi @Coop, can you provide a status on this report? I just ran into this today, and it is a blocker for me using my RealSimGear GNS530 for instrument rating practice. Hoping there's an update since the report has been here a while. I encountered the issue on the G5 v2.1.0 update. Thanks!