I am experiencing a lot of A&O app crashes with V2.80. No error message, just an app exit.

Mainly when editing/testing scripts and recently trying to add an axis mapped to vJoy. The scripts were simple MIDI commands for the XT Mini LEDs and layer changes.

I also tried to change an existing axis assignment from AXIS_ELEVATOR_SET to NONE and replace with a vJoy axis, but the AXIS_ELEVATOR_SET just kept coming back and I had to delete the axis completely and re-assign.

I am running the app as administrator.

Simply testing the following single line script will exit the app:

(>MIDI:3:PrgChng:1:1)

This is in OFFLINE mode. Will this make a difference considering its just talking to the XT Mini ?

Regards, Daz

Edited December 17, 20223 yr by Dazzlercee23

55 minutes ago, Dazzlercee23 said:

Simply testing the following single line script will exit the app:

(>MIDI:3:PrgChng:1:1)

This is in OFFLINE mode. Will this make a difference considering its just talking to the XT Mini ?

Not for me. I am testing it right now, nothing bad happens. Using the app in Offline Mode. My XTouch also has OUT ID 3. What exactly do I have to do to make the app exit?

The code is wrong btw. the Program Change only has one parameter (the channel), not two. And you must supply a value. "(>" means that whatever comes before it is passed along to the command or variable that comes after the ":"

0 (>MIDI:3:PrgChng:1) => Layer A
1 (>MIDI:3:PrgChng:1) => Layer B

 

Edited December 17, 20223 yr by Lorby_SI

55 minutes ago, Dazzlercee23 said:

I also tried to change an existing axis assignment from AXIS_ELEVATOR_SET to NONE and replace with a vJoy axis, but the AXIS_ELEVATOR_SET just kept coming back and I had to delete the axis completely and re-assign.

That's weird. I will look into it. But as long as deleting and reassigning works, at least there is a work-around.

But this doesn't qualify as a "crash" - am I missing something?

Edited December 17, 20223 yr by Lorby_SI

Yes, it is weird.

I corrected the code, thanks.

If I press TEST in the script editor on any script, the app just exits (OFFLINE mode only). I use a lights/layer reset script as a one shot global script at the beginning. Runs fine, but if I simply test it the app exits.

If I add an axis and then press ADD without assigning a function, the app just exits (I know you wouldn't normally do this, just for info. OFFLINE or ONLINE mode).

I installed the update over the existing installation. Is that OK?

Thanks, Daz

Edited December 17, 20223 yr by Dazzlercee23

I am also getting a 100% reproducible app exit if I update a global script.

For example in 'The Manage Global Automated Scripts' window; if I change a script from say 'beginning' to 'end', click add/update; as soon as I click CLOSE, the app exits.

Maybe I should try a clean install of 2.80.

Regards, Daz

20 minutes ago, Dazzlercee23 said:

If I press TEST in the script editor on any script, the app just exits (OFFLINE mode only). I use a lights/layer reset script as a one shot global script at the beginning. Runs fine, but if I simply test it the app exits.

Sorry, I can't reproduce that one. Has never happened to me, nor has it been reported before. Not sure what to tell you.

An app doesn't just "exit", Windows decides to close it. So there should be entries in the Windows Application Event log as to why. Please look for those and send an email with your proof of purchase to the support address. I may need log files from AAO too.

 

Edited December 17, 20223 yr by Lorby_SI

12 minutes ago, Dazzlercee23 said:

For example in 'The Manage Global Automated Scripts' window; if I change a script from say 'beginning' to 'end', click add/update; as soon as I click CLOSE, the app exits.

Sorry, also not happening here. The dialog is working just fine.

12 minutes ago, Dazzlercee23 said:

Maybe I should try a clean install of 2.80.

That does nothing for you. For a really "clean" install you would have to manually delete the entire database, losing all your scripts and configurations in the process.

Edited December 17, 20223 yr by Lorby_SI

Hi,

I did a clean install, restored database backup and my latest configdatabase.xml. Everything is now fine, something went astray somewhere.

Thanks for your help.