CJSouthern

Thanks for that - much appreciated. Looks like the APR light is working just fine in the test - so the only remaining question is "why doesn't it work in the sim"? - As far as I can tell the DataRef is correctly specified (per the above example) - I can confirm that that variable does change when APR mode is delected ... just no light comes on. Odd.

Thanks. In the latest version of the configurator that doesn't seem possible; the only place one can type is in the search field -- and when they don't appear, there's nothing that can be subsequently clicked on to select it. I have got a work-around working though; I've located the relevant config file and edited it in Notepad. I just have 1 remaining issue now; I can't for the life of me get the approach light to come on. When I press the APR button both the APR and NAV lights should come on - but only the NAV one does; at this point I'm wondering if it's something as simple as a faulty LED. Here's the code in case anyone can spot something obvious: { "ByteIndex": 1, "BitIndex": 1, "ConditionLogic": "", "Conditions": [ { "Condition": "tbm900/lights/ap/nav", "ConditionValue": "1", "ConditionIsCustom": false } ] }, { "ByteIndex": 1, "BitIndex": 2, "ConditionLogic": "", "Conditions": [ { "Condition": "tbm900/lights/ap/apr", "ConditionValue": "1", "ConditionIsCustom": false } ] },

Thanks for that. The plot thickens; I can see from your excellent source that what I need is tbm900/lights/ap/nav ... usng the dataref tool I can see that this variable works great ... the only problem is that non of the tbm900 DataRefs appear in the list using the Honeycomb Configurator. Any ideas as to what I need to do to get them to appear?

Hi Folks, I recently purchased a Honeycomb Throttle Quadrant for use with the TBM 900. I've got most of it sorted, but I'm stuck on a couple of things; If I press the HDG, APR, or NAV buttons, the autopilot correctly changes to the requested mode (as verified by the annunciators on my monitor). However, only the HDG button lights up when pressed. The other two buttons work just fine, but they don't light up to say that they're active on the TQ. I'm very much a newbie with the Honeycomb configurator; but I can see the variable that HDG mode monitors, but I can't for the life of me find the equivalents for APR and NAV modes (mostly just NAV mode I want - I don't ever use APR mode). I've even gone as far as installing and running the DataRefTool - and I still can't see anything that's changing - and yet the annunciator on the monitor is presumably getting the info from somewhere. Can someone please give me a heads up here. Many thanks.

Thanks. I guess it is what it is; I'm just surprised that it's not possible (apparantly) to have maximum braking effort assigned to a momentary switch in such a way as it applies max braking when I push it and releases the brakes when I release it - without applying the parking brake control. It just seems all kinds of wrong.

That doesn't make any sense. IRL if I'm trying to stop an aircraft in a hurry I'll sure as heck be working the toe brakes hard - but I certainly won't be using the parking brake.

On my Honeycomb Alpha flight yoke when I assign Hold Brakes Regular to button 3 it works as expected - but if I assign Hold Brakes Maximum to button 3 then it sets the parking brake instead. Anyone else having this issue? Bug?

I must be losing my mind

Running TBM V1.1.13 on XP 11.55. Previously worked fine under XP 11.52r3. Hi all - I haven't flown for a few months. When I started XP it updated itself to v11.55. When airborn with the AP configured and engaged on a horizontal navigation mode it disconnects instantly whenever I tap the button to trim nose up or down. I've deliberately crashed the model and sporned a new airframe ... same result. Also getting an issue with the fuel pump; on v11.52r3 the pump wouldn't come on when set to auto. Now under v11.55 I also get a fuel pressure warning if I start in auto mode; to clear the message I need to go to manual mode then back to auto mode. Any thoughts anyone? The first issue is a bit of a show-stopper. I don't think it's anything I've forgotten.

Another option - perhaps just add the maintenance manager to the menu system much the same as we can use for getting to the additional info for ECS / gear / engine etc - and then have a checkbox that hides it all the time when the aircraft isn't moving? Can't say it bothers me, but would seem like something pretty easy to impliment.

What issues are you seeing with it?

Good to know that I wasn't the only one!

Thanks for all that you and your team do Cameron - I appreciate it.

If you ever win Lotto, check these out ... I'm still drooling ... https://slawdevice.com/en/

At the risk of starting a flame war, my 40 years of experience as an IT guy taught me that in terms of reliability & compatability, AMD's "walk" never seemed to quite match it's "talk". Personally, I run X-Plane on an Intel 10700K (not overclocked) on a Gigabyte Aorus MoBo with 64GB RAM - no plugins - and ... everything just works (with the exception of the occasional glitch). Take that as you see fit.

As an "aside", I suspect that P-Factor would make the aircraft a nightmare on takeoff for people like me who fly with a yoke but no pedals (thus have no rudder control). For what it's worth, I started my TBM simming with the 930 in MSFS 2020 and found it to be a worthless piece of cr^p (I since uninstalled the entire product) - so many many things that just don't work right (if at all). If you want a "pretty game" then I guess it's fine, but if you're wanting an accurate simulation then they're as different as chauk and cheese.

At the end of the day it's a simulator; so it should simulate. If you leave something a certain way in a real aircraft then guess how it'll be the next time someone returns to the aircraft? It's doing what it should do -- and it's one of the features I like.

[Deleted by user]

For what it's worth, over the past week or so I've flown the TBM from Nelson, New Zealand to Tahiti to Honolulu to Los Angeles to Montreal to Goose Bay to Greenland. Most of those legs are 2000 nautical miles plus - and took 10 hours plus. No issues.

You might like to check that you don't have the random failures feature of X-Plane turned on. Load the model and then click on Flight -> Edit Failures. Start by clicking the "Fix All Systems" button.

I've seen this issue too. For what it's worth, all you need to do is rotate the small knob one way (I think I roll the mouse wheel up) - and it takes you to the list of stored flight plans. So not quite 100%, but still quite usable (I use it all the time).

For what it's worth, I flew the beta last night and the rain effects looked great (RTX 3080 based system, no addons). Also for what it's worth, I have mixed experiences with NaviGraph; I've had some great support on a couple of issues but was very surprised to discover that their Navigraph Charts product doesn't include altimetry for enroute phases which is "kinda important" for IFR flight planning.

I'm no expert, but I would suspect that that would cause an issue. I can only see a limited number of practical options (the phrase "you're telling me what we need but I'm telling you what we have" from the Apollo 13 movie comes to mind). 1. Find a way to make what you have give the model what it needs 2. Use hardware that's compatible with the model 3. Fly a different model that's a better fit with your hardware Not seeing a "magic wand" option here unfortunately.

To be honest, my issues have mostly been "own goals" (with a few exceptions). One thing that some other kind folks helped me discover is what's under the Flight -> Edit Failures Menu; if you haven't already, you might like to see if random failures have been programmed and/or just hit "fix all systems". I'd be interested to hear if this is the source of any of your problems.

Per my post above (and elsewhere here) I had the same issue. It went away the INSTANT I updated using 11.41- format data. If I update using 11.50+ format data then the TBM shows data that's about 4 years out of date. Using the 11.41- format it shows the current AIRAC cycle.