I own a new CYRO and a very old CLASSIC Azeron (I still think I need to use Teensy for what I am doing?). I have a profile I want to use for my CYRO through software (not onboard). I have two profiles I will use through software (not onboard) with my CLASSIC Azeron controller. I am having a problem because when I click the checkmark on the CYRO software profile I want to use it also Automatically switches the CLASSIC's software profile to the profile I am using for the CYRO. How do I keep the CYRO profile independent from the CLASSIC's profile? If this is not possible I have no use for this CYRO at all. I have a massive amount of commands I use in the game I specifically bought the CYRO for (Total War Warhammer 3). I need it for nothing else and will not use it unless it can functionally be used at the same time I am using my CLASSIC controller. How do I get these two Azeron controller profiles to work independent from each other?
I cannot get my CYRO to work alongside my Classic Azeron
- Thread starter BluesDancer
- Start date
For the classic one switch to onboard profile to prevent it switching to software profile after exiting the software
The problem with using an Onboard profile on a Classic Azeron is I do not get the option for creating a button I can use for Layering. I must use a Software profile to get the 'Layering' option.
More in-depth detail on my problem with the two controllers and the Azeron software flaws:
Before reading all below my main guess to the big issue is that the profile saves for the Classic controller and the Cyro controller in the Azeron software has no way to separate one controllers profiles from the other controllers profiles. Also, my On-Board profiles on BOTH controllers cannot be programmed to switch if two are created within the software because 'Profile Switch' does not work and there is no 'Layering' option in the "On-Board' Options. 'Profile Switch' also does not work in the Software profiles for the Cyro (apparently the Classic controller software does not have a 'Profile Switch' option).
Problem 1) When I turn on the 'On-Board' profile on either the Classic or the Cyro the 'On-Board' of the other controller also switches on even if the other was set for 'Software' profiles. Both controllers will only stay 'On-Board' or 'Software'.
Problem 2) If I click on a profile ('On-Board' or 'Software') on the Cyro or the Classic controller it switches the profile set on the other controller to the same one used for the first controller. The Azeron software does not differentiate that profiles for the Classic are not profiles for the Cyro (and visa-versa). As I switch between profiles the other controller's profile switch to whatever was set on the other controller. This creates odd-looking profiles using the structure of the numbering system of the keys (example: what is set for key #1 on the Classic becomes the same command used for #1 key on the Cyro).
Problem 3) On the Cyro the "Profile Switch" option does not work. I can successfully check off the box named 'Apply to all OBM profiles' and then click on the 'Apply' button. I close the window then and re-open it and always see that the checkbox is not saved thus unchecked always.
Problem 4) This is similar to Problem 2 ... On the Cyro I notice there is no 'Layering' option within 'On-Board' so I use it in the 'Software' profiles only. This 'Layering' works fine in 'Software' profiles with the Cyro with one MAJOR problem. As I click on the key assigned for 'Layering' on the Cyro it also switches the profile on the Classic to whatever the profile the 'Layering' (on the Cyro) was set for but, now the Classic has this odd configuration of a profile on it I cannot use. and the Classic controller is pretty much useless then.
These are my problems. Here is the solution I tried yesterday. Sadly, this solution shortly reverted somehow back to the original problem and I am stuck with no answers to my problem again. Here is what I did:
I figured this is not a Cyro problem because it is new and has the latest software on it. I looked at the Classic and erased the software and installed some old versions of it. I first tried azeron-fw-28, then an old file I had called azeron-fw-60. This second file allowed me to run the Classic on an On-Board profile while the Cyro was on its 'Software' profile for a short while but, soon it reverted to the problems I have listed above. I then tried azeron-fw-classic-compact-89.hex which is included in the firmware folder for Azeron software. That one kept the problem without fixing anything.
Please Help!
Also, the Teensy program gets blocked by Smart App on Windows 11. I had to turn off Smart App to get Teensy to run.
Before reading all below my main guess to the big issue is that the profile saves for the Classic controller and the Cyro controller in the Azeron software has no way to separate one controllers profiles from the other controllers profiles. Also, my On-Board profiles on BOTH controllers cannot be programmed to switch if two are created within the software because 'Profile Switch' does not work and there is no 'Layering' option in the "On-Board' Options. 'Profile Switch' also does not work in the Software profiles for the Cyro (apparently the Classic controller software does not have a 'Profile Switch' option).
Problem 1) When I turn on the 'On-Board' profile on either the Classic or the Cyro the 'On-Board' of the other controller also switches on even if the other was set for 'Software' profiles. Both controllers will only stay 'On-Board' or 'Software'.
Problem 2) If I click on a profile ('On-Board' or 'Software') on the Cyro or the Classic controller it switches the profile set on the other controller to the same one used for the first controller. The Azeron software does not differentiate that profiles for the Classic are not profiles for the Cyro (and visa-versa). As I switch between profiles the other controller's profile switch to whatever was set on the other controller. This creates odd-looking profiles using the structure of the numbering system of the keys (example: what is set for key #1 on the Classic becomes the same command used for #1 key on the Cyro).
Problem 3) On the Cyro the "Profile Switch" option does not work. I can successfully check off the box named 'Apply to all OBM profiles' and then click on the 'Apply' button. I close the window then and re-open it and always see that the checkbox is not saved thus unchecked always.
Problem 4) This is similar to Problem 2 ... On the Cyro I notice there is no 'Layering' option within 'On-Board' so I use it in the 'Software' profiles only. This 'Layering' works fine in 'Software' profiles with the Cyro with one MAJOR problem. As I click on the key assigned for 'Layering' on the Cyro it also switches the profile on the Classic to whatever the profile the 'Layering' (on the Cyro) was set for but, now the Classic has this odd configuration of a profile on it I cannot use. and the Classic controller is pretty much useless then.
These are my problems. Here is the solution I tried yesterday. Sadly, this solution shortly reverted somehow back to the original problem and I am stuck with no answers to my problem again. Here is what I did:
I figured this is not a Cyro problem because it is new and has the latest software on it. I looked at the Classic and erased the software and installed some old versions of it. I first tried azeron-fw-28, then an old file I had called azeron-fw-60. This second file allowed me to run the Classic on an On-Board profile while the Cyro was on its 'Software' profile for a short while but, soon it reverted to the problems I have listed above. I then tried azeron-fw-classic-compact-89.hex which is included in the firmware folder for Azeron software. That one kept the problem without fixing anything.
Please Help!
Also, the Teensy program gets blocked by Smart App on Windows 11. I had to turn off Smart App to get Teensy to run.
Can you make a short video of the isuse ?
It should not switch on both devices, if the device you are switching from is set to obm profiles
It should not switch on both devices, if the device you are switching from is set to obm profiles