Have uninstalled/reinstalled after deleting the 3 specified folders in app/local and documents. Have reinstalled all Microsoft support redistributions. Clicking the app does not deliver a UI.  Support logs show nothing in error.  Same for 2020 and 2024 alike.  I’m stumped as I just purchased an xtouch mini with a goal of mapping the key presses to Control-1 thru Control-0.  I’m at a loss and any help is appreciated.

TIA,

-B

Edited June 22, 2025Jun 22 by btacon

11 hours ago, btacon said:

deleting the 3 specified folders in app/local and documents

Including AppData\Local\LWR ?

What does the Windows Event Log say? Normally, when Windows doesn't allow a program to run, it logs the reason for that in the Application Event Logs. And what about AntiVirus?

6 hours ago, Lorby_SI said:

Including AppData\Local\LWR ?

What does the Windows Event Log say? Normally, when Windows doesn't allow a program to run, it logs the reason for that in the Application Event Logs. And what about AntiVirus?

Morning Lorby. Yes, even local\LWR.  Good news is it’s resolved.  It seems that ALL of the shortcuts being produced were not allowing it to run as admin.  I went into the core folder where the Exe live and was able to start the UI with a run as admin command.  I then said, “create shortcut” and the software and/or the OS said “No!  Can’t create a shortcut here. Would you like create one on the desktop”?  I did, still not working, but when I set shortcut to RAA in properties, it all worked, both 2020 and 2024.  So immediate issue solved.  My only reflection is I’ve owned your software for a few years now.  Pretty sure it’s been installed, deinstalled, reinstalled and OPERATED more than a few times, but NEVER was this my experience in the past.  

No worries now and thanks again for the response. Now I need to learn how to use A&O to take key presses from my Mini X into Cntrl-0 thru Cntrl-9 key presses in sim to move back and forth between next and previous instrument because SU3 Beta has made the internal bindings inop most times and flaky and inconsistent when they do work.  Got any tutorials for that LoL!

-B

Edited June 23, 2025Jun 23 by btacon

21 minutes ago, btacon said:

move back and forth between next and previous instrument

You mean the camera views? I'm pretty sure that this can also be done with simulator variables and you don't have to rely on virtual key presses.

I'm not at my computer at the moment, but theoretically, the code would be like this, using an AAO RPN script:

2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) n (>A:CAMERA VIEW TYPE AND INDEX:1, Number)

"n" goes from 0 to the max number of instrument views (max - 1). When scripting this, you would only create one script, replace "n" with the script variable, and then control the desired camera index with the value parameter of the button event. You could also create toggle scripts that would move back and forth between the cameras, so you only need two buttons.

Edited June 23, 2025Jun 23 by Lorby_SI

Thanks. I will explore your solution.  A solution is needed because while the simulator(s), 2020 and 2024 both have a “Next Instrument/Previous Instrument” key bind which for the last 4.5 years I’ve bound to one of my hat switches, SU3 beta has broken those bindings and makes them behave as I described either working only partially or working once and then not working, only to work again on third or fourth try.  That is the problem I’m trying to resolve, a workaround for the beta.

I will explore your suggestion and thanks again.

-B

38 minutes ago, btacon said:

Thanks. I will explore your solution.  A solution is needed because while the simulator(s), 2020 and 2024 both have a “Next Instrument/Previous Instrument” key bind which for the last 4.5 years I’ve bound to one of my hat switches, SU3 beta has broken those bindings and makes them behave as I described either working only partially or working once and then not working, only to work again on third or fourth try.  That is the problem I’m trying to resolve, a workaround for the beta.

I will explore your suggestion and thanks again.

-B

I'm back home now. I will try and see if I can come up with proper "inc/dec camera" scripts. This will require using another AVar, one that knows how many sub-views there actually are.

Edited June 23, 2025Jun 23 by Lorby_SI

So, here are the scripts to cycle forward/backward through the instrument cameras (tested with the default 152)

- As script package to import into AAO

https://www.dropbox.com/scl/fi/0xvofxjljpy4y2smlxrew/Instrument_Camera_Inc_Dec_Scripts.xml?rlkey=0fzb5e8ayzsqe4601noemgcbw&dl=0

- As code:

Inc

2·(>A:CAMERA·STATE,·Enum)·2·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·
(A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Number)·++·s0·
l0·(A:CAMERA·VIEW·TYPE·AND·INDEX·MAX:2,·Number)·>=·if{·0·}·els{·l0·}
·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Number)

Dec

2·(>A:CAMERA·STATE,·Enum)·2·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·
(A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Number)·--·s0·
l0·0·<·if{·(A:CAMERA·VIEW·TYPE·AND·INDEX·MAX:2,·Number)·1·-·}·els{·l0·}
·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Number)

 

58 minutes ago, Lorby_SI said:

So, here are the scripts to cycle forward/backward through the instrument cameras (tested with the default 152)

Amazing and wonderful Lorby.  Will install and try them today.  I’m sure they are just what I’m looking for and since I don’t program for beans…a Blessing to boot!

TYVM

-B

I hope that they work for you.

With those variables and a control lvar, it should be possible to program any sequence of whatever cameras to cycle through. Like for example pilot view -> instruments 1 -> instruments 3 -> pilot again.

Edited June 23, 2025Jun 23 by Lorby_SI

On 6/23/2025 at 3:40 PM, btacon said:

Morning Lorby. Yes, even local\LWR.  Good news is it’s resolved.  It seems that ALL of the shortcuts being produced were not allowing it to run as admin.  I went into the core folder where the Exe live and was able to start the UI with a run as admin command.  I then said, “create shortcut” and the software and/or the OS said “No!  Can’t create a shortcut here. Would you like create one on the desktop”?  I did, still not working, but when I set shortcut to RAA in properties, it all worked, both 2020 and 2024.  So immediate issue solved.  My only reflection is I’ve owned your software for a few years now.  Pretty sure it’s been installed, deinstalled, reinstalled and OPERATED more than a few times, but NEVER was this my experience in the past.  

No worries now and thanks again for the response. Now I need to learn how to use A&O to take key presses from my Mini X into Cntrl-0 thru Cntrl-9 key presses in sim to move back and forth between next and previous instrument because SU3 Beta has made the internal bindings inop most times and flaky and inconsistent when they do work.  Got any tutorials for that LoL!

-B

Just posted this, might be useful to you.

 

5 minutes ago, Lorby_SI said:

Just posted this, might be useful to you.

 

Indeed and quite gracious.  Thank you friend.

-B