Gil Yoder

This is just what I needed. I'm pretty sure the brakes worked using Select Axis before, but some change created the weird behavior I described before, even in the actual use. The brakes would work up until they were fully deflected, and then disengage. This made it impossible to hold the plan still while reved up, unless the parking brake was used. Using the simulator variable mentioned in the post you linked was the perfect fix.

With your help I got the rudder issue fixed, but I've found another issue with the Thrustmaster. The breaking (both left and right) are behaving strangely. When I apply the breaks, the break peddles in the cockpit rotate as you expect until the peddle is fully deflected. At that point the peddles return to the non-braked position. IOW when the brakes are fully applied in the physical control, in the cockpit the breaks are fully disengaged. Do you have any idea why this happens?

Thanks for the reply. I checked with the game controller calibration app and it was behaving weirdly in that. Then I checked the usb cord, thinking I might try a different port, and I found a switch on the cord that seemed to have a setting for auto sims and flight sims. It had been switched to the auto sim side. When I changed that the usb controller calibration app starting working as you would expect. I think that will fix it in AAO and MSFS too, I have my fingers crossed.

I'm having an issue with my setup for my Thurstmaster rudder control. It has been a while since I've run MSFS. When I tried recently the rudder would not work, and when I looked at AAO, AA0 mad some changes to the config, but these changes don't work either. When I exercise the rudder peddles the "Move Joystick axis" changes to "Slider 0" and the value under the field goes from about 65000 (when the peddles are centered) to 0 (when the peddles are fully moved back on the right.) Moving the peddles from centered to fully back on the left does not change the value under the field at all, i.e., it remains at about 65000. This is reflected in the cockpit by the peddles animating from centered (when the value is 0) to full right when the value is around 65000. This image may help to visualize my problem. I hope someone can help me resolve this problem. Thanks!

Can I get some explanation (or documentation reference) for the various options under "Add Button Assignment" and how they impact the use of switches and buttons of Logitech Panels as midi devices? When I first open the "Add Button Assignment" dialog box and start flipping switches and buttons on my switch and multi-panel, I get something like "CHN: ? EVT: ????? CLICK" for each switch or button, for both on (or pressed) or off (unpressed) states. Then, if I select "Rocker" and do the same test, I get a different behavior. I might get a "CLICK" event for the first change of a button or switch, but all of the following changes will be a "LEFT" or "RIGHT" event. If I then reset "Rocker," some of the switches or buttons will continue to generate "LEFT" and "RIGHT" events, but at some point some of the switches will start generating only "CLICK" events again. It's difficult to predict what event a switch will generate under what condition, so I'm not sure how to ensure that a switch change will be recognized and acted upon in a deterministic way. There doesn't seem to be any explanation for these options in the MSFS document. I'd like to use the Logitech panels as midi devices because I want to be able to distinguish between a long click and a short click, especially on the multi-panel. Hopefully, someone can help me understand what's happening.

How long should it take for AAO to collect H: and B: variables from MSFS? When I read LVARS, it just takes a few seconds, but I started reading H: and B: a long time ago, five or more minutes now, and the "Collecting H: and B: variables, please wait" prompt still appears. I have to close AAO to make the prompt go away.

Thanks. That make sense. One of the graphics in the documentation had all three menu options enabled at the same time, so I thought that was the correct state. I should have known better.

I am trying to configure my Logitech panels. Right now I have a question about the Hardware menu in AAO. I'm confused a bit by the options. When "Saitek panels enabled" is checked, the two buttons below that, "Ignore sim electrical power," and "Saitek panel config" are greyed out. But when "Saitek panels enabled" is unchecked, the two options below it are available. So, my question is how to configure the panels. Do I disabled the panels, to configure them, and then enable the panels to use them? Or is the logic of the "Saitek panels enabled" backwards, i.e., is it enabled when its unchecked and disabled when it's checked? I probably could figure this out through experimenting, but if this is a bug, I wanted to report it.

That's a great idea. I will look into it. Thanks!

I have worked out some kinks to ACDB and posted an upgrade to flightsim.to. A video overview of the program is available here:

Never mind folks. I found several errors myself. I'll go back to the drawing board and try again. Thanks.

I am having a problem getting TTS checklists to work for me. I have created checklists for the K100 and placed them under D:\MyDocuments\LorbyAxisAndOhs Files\Scripts\K100 If I try to run the scripts by going to "Scripts/Run script files" and then select any of the script files from that dialog box, I can't get anything to run right. The control script produces no results that I can detect, and if I try to run any of the checklist scripts I hear "please confirm" a few times and then "checklist ended." I am guessing I have a syntax error or something else that I need is missing, but as far as I can tell I've followed the instructions given in the manual to the letter. Could someone please take a look at my scripts and let me know what I've missed? Thanks. https://1drv.ms/u/s!At8jZTR4z_zW5HkIU05PZSxmCIb6?e=YszRUj

I'd like to let everyone know that I have recently created a new utility called "Aircraft Checklist Database Builder" (ACDB). The program is designed to simplify the creation of checklist scripts for use by AAO. The program is free and is now available at flightsim.to here: Aircraft Checklist Database Builder I'd be happen to hear what you think about the program, if you use it. If you have any problems with it, let me know. I will try to provide fixes with little delay. Enjoy!

I gave this a try and came up with a little success, but I'm not sure how reliable it would be. I created the following bindings for the Asobo 787-10 just for the first throttle. This is for the normal forward thrust and works as expected. For the reverse thrust I configured a second lever in this way: When this lever is activated, the reverse thrust lever in the VC moves. It seems a little glitchy though. At one point in my testing, AAO seemed to disconnect from the sim, although it said it was connected, and the levers had no effect, When I reopened the event viewer though, it started working again. I'm not sure what that was about.

What aircraft are you trying to configure? I may be able to help if you are flying MSFS.

I have a little problem with the Assigned Axis pane in AAO. The tree view isn't displaying correctly. This can be illustrated best with pictures. The first shows names that I have given to the assignments, and the second shows the tree view along with the problems I'm noticing. Notices the Flight Controls and Throttle Quad groups in the above screen shot. Now look at the resulting tree view. Note in the second screen shot that "Flight Controls are not grouped together, and that "Throttle Quad" is completely missing from the tree. This is in version 2.26 b04 - MSFS.

Okay, I just found where the panels are to be configured. It just wasn't where I expected.

I had several that I guess shouldn't be active, but this raises another question. Shouldn't I see my Logitech switch panel and multi-panel somewhere?

Thanks for the info. I will try working with RPN scripts to see what I can do with that. It's a bit of a learning curve, but it sounds interesting. One question: I have not had much luck yet creating a setup even for one aircraft. twice now something happened and AAO crashed, and all the settings that I had configured disappeared. After the first instance I started saving changes as a template, but even that disappeared after the second crash. It seems that changes are not saved until the program closes. Is there a way to force a save to prevent the loss of changes other than closing the app?

I have just purchased Axis and Oh's to use with MSFS to configure my controls. I had been using another product, but I decided to change after experiencing poor support from the developer. Lorbi SI seems to have more respect for its customers, so I hope this is a good move. Right now I am trying to configure some of my flight yoke switches to handle camera views, but I haven't had any success. I think I could program virtual keys to do what I need, but I'd like to use events, if that's possible. In the Select Simulator Event dialog box I see two buttons, Test with 0 and Test with 1. I have tried to uses these buttons to see what specific events would do, but I never see any response in msfs when I do that. Do those buttons work? Also, I have tried several of the Camera events under VIEW / CAMERA EVENTS in that dialog box, and none of them seem to have any impact within msfs. Could someone help lead me to a better understanding of these things? Thanks!

Reluctantly I have disabled Amazon Polly in P2A. It's voices are amazing, but the implementation on the desktop is buggy. In P2A Polly would work for a while, but then it would start acting up. The worst was that it seemed to cause P2A to lock up during flights. If I paused a flight in MSFS by hitting ESC, P2A would free up and start working again, but as soon as I reentered the flight, P2A would freeze up again. Apparently something in Polly caused this behavior, because it didn't happen before I started using Polly, and as soon as I removed the Polly voices from P2A, it stopped happening. Even Polly Player would expose errors in the implementation of the system. For example, this is the error I would get trying to use several of the voices. I'm disappointed in this. Polly voices are among the best you can find now. Unfortunately, until Amazon fixes these issues, they are really unusable in P2A.

I'd like to report two pronunciation errors that I have heard several times in Pilot2ATC when a textual dialog is translated to speech. The first is the word "resume." In the context where the word is used in P2A the word should be pronounced "RE ZOOM." Instead it is pronounced "RE SOU MAY." This is a common error in TTS, so some kind of translation is needed to correct the speech. The second is the word "winds." Instead of rhyming with "BENDS," it is pronounced with a long i rhyming with "BINDS." The word "winds" is usually pronounced correctly during tts, but for some reason the text that's sent to the speech engine by P2A is "WHIND" instead of "WIND."

I am doing an IFR flight today, and I am experiencing a new issue for me. The first TTS statement from ATC for each new radio frequency is silent. I see the text in the window, and hear my copilot's replies, and then I hear any further communications from ATC until the radio frequency changes again. This might have to do with setting up Amazon Polly the other day, but the other day this didn't happen. Gil

Thanks for the clarification. I think I saw the Set Rwy button the other day, but it slipped my mind. (Not hard to do nowadays.)

While troubleshooting the taxiway issue, I noticed another little issue. The issue is with regard to forcing a specific runway for departure, if no SID is assigned. Steps to produce the issue: Start with a new flight plan. Click Add Wpt. Enter an ICAO for an airport with multiple runways, i.e., KHOU. And press enter. Click Info beside the map to see preferred runways. Click Add Wpt. Enter am ICAO for another airport, i.e., KFTW. Note the given runway under SID and be sure it is one of the preferred runways. (If not, you may need to take steps to set it as the runway.) Click SID. Select a non-preferred runway. Ensure Force Dep Rwy is selected. Click Load. Many times after following this sequence the preferred runway is still displayed below SID. Usually Clicking SID and then Load will resolve this, if the desired runway still shows in the dropdown Runway box. Because the workaround is fairly easy to do, I don't see this as a serious issue.