Coop1019

Glad to hear that fixed it. Attached is an image of where the clickspots are for the High Boost Pump switches. The cover needs to be unlatched by clicking below where the switch is. Let me know if this works:

Thank you for the log. I can see from this that the rudder pedals are being loaded in by X-Plane, but I can't see much more than that. Since our aircraft doesn't touch the toe breaks (we only trigger the X-Plane failure after real hard landings, but that is instantly visible in the X-Plane default failure page) I think it may be a joystick calibration/config issue. Can you try backing up, then removing these files inside X-Plane 11/Output/preferences: X-Plane Calibration.prf X-Plane Joystick Settings.prf X-Plane Keys.prf And removing the M20R_prefs.txt files from inside the X-Plane 11/Aircraft/AFM/M20 *version you prefer*/ folder. Let me know how this works!

Glad you found the menu. Interesting that the breaks aren’t working, I currently can’t reproduce this issue on my end, it could be something with 11.32.

The plane should certainly have breaks, can you check the AFM Maintenance menu and see if they are failed?

Found the issue. The "AFM" folder is required to be directly inside the X-Plane 11/Aircraft folder and not inside any sub-folders. If you move the "AFM" folder back a layer, the plane should work. Let me know if this fixes the issue

The current version on the store is 3.0.3, the version.txt is just mislabeled. I responded to your other post in Bug Reports where we can debug.

Can you upload your log.txt file so I can take a look?

Fixed in Public Beta 4.0.0 PB1. If you are interested in testing out the public beta, see here for instructions:

Edit for Access, see here: https://afms.im/Oc3vQf Hi Everyone. We have started Public Beta testing of V4.0 of the M20! If you own the M20 and want to be part of the testing group, join our discord here: https://discord.gg/Vkv2Eew And PM me (Coop #1019) your order number. I will then add you to the testing group.

We have decided to depreciate our auto-updater. It was causing more issues than fixing, so we have decided to stick with patch files until we reach a better solution. Thank you, everyone, who helped test out our installer. We hope to have a better solution in the future.

I am able to replicate the issue on my end. This will be resolved in the M20 11.30 full update coming in January.

Investigating now.

Weird, can you upload the log.txt from the X-Plane 11 directory?

I don't have a full list yet, but of course, Librain will be integrated

Perfect

Hotfix B has just been uploaded, this only affects Mac users if they were experiencing the same issue. The new version is being uploaded to the stores as we speak.

We have a fix for this: you can download it here https://forum.thresholdx.net/topic/503-m20-collection-303-hotfix/ This should work for you :) I am uploading the fix to the stores now.

Disclaimer: This has not gone through a full testing process as we are making the update available ASAP. It looks like the latest Navdata is causing a (seemingly random) crash on some systems. Here is a small fix that should resolve the issue. The patch file is attached. Note: This update contains nothing new beyond 3.0.2 except for this bug fix. The next major update is coming soon. Update: Added Mac Fixes. This update is also being distributed to the stores in the main download package. https://afmsimulation.s3-accelerate.amazonaws.com/m20/M20 3.0.3 HotfixB.zip

No worries. Let me know if you run into any other issues.

Interesting, I think that this would only happen if the PFD is turned off in X-Plane’s view. Do you have any hardware switches or plugins that command the avionics switch on or off? Can you also upload your log.txt from when this happens? Thanks!

Thank you for the idea. Though it would be nice to do this, there would then be compatibility issues with icons and liveries between the Ovation 2 and 3. (Though this is minor, reducing the file size of our download is something we aim for). This should work for your use case (though make a backup or be prepared to redownload the M20 goes haywire): if you rename the "M20R.acf" "M20R_cockpit.obj" and "M20R_vrconfig.txt" changing only the "M20R" portion (keeping file extensions and everything after (and including) the underscores, it should work. Let me know if you have luck with this!

Interesting, it looks like they were omitted from our manual on that page. I am marking that to get fixed in the next manual revision. To use, for now, the real manual should be accurate - the engine is tuned to match reality.

Our next update of the M20 will come after 11.30 is released (and stable) - it will have these new features. ?

Possibly, I can't make any promises here, but I will look into it ?

Hi Scott! There is quite a bit going on behind the scenes our current timeframe is getting the Pocket Rocket airplane out (torquesim.com) hopefully by early December. After that, all the new systems that I wrote for that (that are applicable) will make their way over to the M20 along with new sounds, avitab support, and some bug fixes. Expect that most likely mid-December. It should be an exciting rest of 2018 ?