"the visualisation plug-in executed illegal operation."

[dro]

Are you trying to use the multi-vis mode by any chance? As you might need to re-select the vis plug-ins to be used via the right-click menu on the main window vis area though doing that in general even if only using the single vis mode might be best (i.e. select none & then select what's needed). As so far I can't replicate the vis selection failing if done via that menu or via the vis prefs page & selecting in there.

[carls.haven]

i am using multi-vis, specifically staying on x86 for it. if i turn off multi-vis and the other two, then only the analyzer autostarts. with it and all three on, the other two starts but the analyzer does not. i tried it on a separate computer and the analyzer would not autostart either way. would providing a copy of my portable install be of help any?

[dro]

I'll have to recheck multi-vis handling & get back to you.

[dro]

The feature is broken when it comes to the menu handling & probably more now I've started having a look into this. So its not updating the config file & depending on how things are reacting it may or may not allow the actions to start the plug-in which likely aligns with what was reported. This isn't a feature I often use so I'm still trying to determine when I broke it but will look to get it working again for the next build.

[carls.haven]

ok thanks

[dro]

The main part of the issue is from when I added in running / stopped status text to the menu items & that broke some of the handling used to figure out what's being worked with. This is going to essentially require selecting the none option & then re-configuring the plug-in to use which isn't something I'm going to have the installer try to do as there could also be prior setups where it's still working ok since going over 2 vis plug-ins was also triggering some weird handling issues with everything else that had changed since this was first added.

There's also some message handling changes due to working with modern skins that inadvertently broke things with trying to batch turn the plug-ins off so that's now been modified to hopefully be better behaved even if the vis might cause a crash (as they can do) by at least clearing out the config settings before things are messed around with. Hopefully all of that will manifest as working ok when the build is up.