burns

Thank you. That fixed that problem.

Trying to start the Dodo 206 takes awhile. When I press the starter button, Linda 2.8.3 releases the button after about 30 seconds....I'm still pressing the button but Linda has released it. Result: Dodo can't be started. This didn't happen with 2.6.3. With 2.6.3 the button remained pressed as long as I held it.

I changed the HideMsgWindow call to have ("Setting OFF actions"). Window still doesn't disappear and the Linda console says: 211: attempt to call global "HideMsgWindow' (a nil value) I think the problem is the call is to HideMsgWindow and your function is called HideMessageWindow. I'll name them the same.

Is there a way to active this routine from a key press? Reason: using VAC (voice active commands), I already synchronize Linda by sending a key string to Autohotkey which moves the mouse to click on the sync button in Linda. Using the same Autohotkey routine, I'd also like to run the script after Linda in synchronized with FSX. So a key press or function call (outside of Linda) would be great.

The momentary toggles are an artifact of another application. A flight game that only read push buttons. I can't remember its name. I just redid the settings and converted the momentary setting to toggle. Everything is fine now (for buttons less than 33).

Moving the message functions to the top fixed that....except the message window doesn't close. The switches that are missed are either greater than 32 or on a controller that only temporarily shows them as on. IE, when the toggle is thrown the on condition shows for about 1 sec then goes off. This is by design. Hence, your software has no idea what the state of the switch would be. That said, except for the window not closing, everything seems to be working great.

Commenting out the ShowMessage, ShowMessageWindow and HideMessageWindow calls allowed it to work, somewhat. It missed a couple of switches. Could this be a timing issue??? Also, one of my controllers has 64 buttons. Can this routine handle it?

:smile:Thank you. Now to try it.... Didn't work. I have 5 controller boards that I use for switches and buttons. Should I have to edit anything to get the script to see them? Linda sees the boards. Is it sufficient to assign the script to the default aircraft in FSX to have it work with any aircraft or do I have to assign it for each aircraft I use? (dodo and some asa aircraft) The ShowMessageWindow("Scanning switches...") never shows. Linda Console says attempt to call global 'ShowMessageWindow' (a nil value)

Can you post it here? I don't have an account there.

FYI: Had to reinstall FSX after building a new system. When doing so, I installed the new FSUIPC 4.939. Now FSX works like FSX-SE with LINDA. IE, I have to tell it to sync to FSX prior to flying. It no longer does it by default.

No response?

Wish the solution was posted here as I have the same problem with my Razer Kraken 7.1 headset and VAC (dw's voice activated commands program). SAPI not working but speech setup works fine.

I think I explained it wrong.... I select the aircraft in Linda after starting FSX-SE and then the SYNC button appears. The button doesn't appear, even when FSX-SE is running with an aircraft selected, unless I also select an aircraft in LINDA. My inexperience here shows that this didn't happen with the CD version of FSX. Never had to use the sync button. With FSX-SE I use FSUIPC4.939. With FSX, I'm currently at FSUIPC4.934. In case that makes a difference.

I can manually select the aircraft, which I assume implies LINDA knows about it. Its just the sync button that isn't enabled. The directories look identical. 27 items in the linda/aircraft folder and linda-cfg/aircraft folder for both FSX and FSX-SE Once I select an aircraft in FSX-SE, FSX SYNC becomes selectable and LINDA does change when I change aircraft. But not until I select the first aircraft.

Okay, I found the button but its 'greyed out'...dim...not selectable when using FSX-SE. I can choose it when running regular CD version of FSX. Guess its a bug?