I've got a Cyro profile called MStd with button 14 set to use layering such that, while I hold that button, it will shift to another profile called MStdShift until I release that button, at which time it will return to the MStd profile. I am, of course, running both of these profiles in the Software app (i.e. not from Cyro on-board memory).
Every so often - say, several times an hour - I will notice that the Software is stuck on the layer profile, MStdShift. When this happens, I'm forced to switch out of whatever game I'm playing to manually select the base profile in the Azeron Software. It will then will be okay for a while, but will eventually end up stuck in the 2nd layer profile again. Obviously, this is not ideal, especially in multiplayer games where the game can't be paused while I'm toggled into the Azeron Software.
As I don't typically notice it right away - there are only a few buttons mapped differently in the MStdShift layer - it's hard to say exactly when and how this is happening, but my presumption is that the problem occurs when the Software fails to switch back to the base MStd profile (i.e. after I've activated the layer by holding the button, the Software doesn't switch back to the base layer when I release the button). But, since it takes a minute to notice the problem, I can't say for sure that something else isn't going on (e.g. is it somehow spontaneously switching to the 2nd layer when I'm not touching the layer button).
I'll note that I have no other buttons on either of these profiles set for layering or profile selection - all buttons are mapped to keyboard buttons, save for the one button mapped to profile switching. Thus, I don't think it's possible that this issue is happening due to me accidentally hitting some other button that is set to switch profiles or do layering.
I've exported logs and attached them. Note that I have a Cyborg active as well, though it's running profiles from onboard memory, of course (feature request: I would love to be able to run two instances of Azeron SW, one for Cyborg and one for Cyro).
ETA: I just took a look at the logs. They appear to be logging info level messages only, which seem to just be button presses. I can't see how that will be very useful in diagnosing this problem, so if there's a way to increase the log level, let me know - I can do that and then send logs again
Here is the setup of the base profile button in the MStd profile:
Here is the setup of the MStdShift button:
Every so often - say, several times an hour - I will notice that the Software is stuck on the layer profile, MStdShift. When this happens, I'm forced to switch out of whatever game I'm playing to manually select the base profile in the Azeron Software. It will then will be okay for a while, but will eventually end up stuck in the 2nd layer profile again. Obviously, this is not ideal, especially in multiplayer games where the game can't be paused while I'm toggled into the Azeron Software.
As I don't typically notice it right away - there are only a few buttons mapped differently in the MStdShift layer - it's hard to say exactly when and how this is happening, but my presumption is that the problem occurs when the Software fails to switch back to the base MStd profile (i.e. after I've activated the layer by holding the button, the Software doesn't switch back to the base layer when I release the button). But, since it takes a minute to notice the problem, I can't say for sure that something else isn't going on (e.g. is it somehow spontaneously switching to the 2nd layer when I'm not touching the layer button).
I'll note that I have no other buttons on either of these profiles set for layering or profile selection - all buttons are mapped to keyboard buttons, save for the one button mapped to profile switching. Thus, I don't think it's possible that this issue is happening due to me accidentally hitting some other button that is set to switch profiles or do layering.
I've exported logs and attached them. Note that I have a Cyborg active as well, though it's running profiles from onboard memory, of course (feature request: I would love to be able to run two instances of Azeron SW, one for Cyborg and one for Cyro).
ETA: I just took a look at the logs. They appear to be logging info level messages only, which seem to just be button presses. I can't see how that will be very useful in diagnosing this problem, so if there's a way to increase the log level, let me know - I can do that and then send logs again
Here is the setup of the base profile button in the MStd profile:
Here is the setup of the MStdShift button:
Attachments
Last edited: