In this case, it disregard top menu setting!
It useful if you plan to run other app which working with the lights (Like Metro Exodus %).Ĭ) Application for switching. Then no other auto-switch app running, profile switched to "Default" one.ī) Disable monitoring - then you switch to this profile, all monitoring will be disabled. At "Profiles" page, you can see a list of profiles and can set 3 settings for each:Ī) Default profile - it's needed for auto-switch.Then you change color effects or event settings, it can apply for current (selected at top dropdown) profile only.All settings will be copied from current. It's named "Default" until you rename it. By default, one profile created, keep all of you current settings.How profiles works (now, i plan to change it a bit):.HCU/Software/Alienfxgui - here are all gui app settings, including mappings and profiles.HCU/Software/AlienFX_SDK - here are all device and light settings.I recommend you first make a backup of the settings. What version you use? It looks like a bug i fix in 9.10.Īnyway, thank you, i check with latest one.Ġ.
#Troll ff works how to#
I do have to check how to make an autoit tray app, but I know it is possible (AutoHotkey is/was made that way), and then the minimum delay becomes that of your app executing.Īgain, I'm not complaining, just trying to make a parallel version of the AWCC FX without the UWP baggage, but would it be faster and possible to have / compile a lighter version of the AlienFX-Cli with only the 'set-all' command (possibly with a "SetFX R G B BR" syntax)? Gives me some measure of breathing effect (choppy, but I can't use less than a second wait in batch like AutoIt does) instead of increase and turn off suddenly like AWCC does. So, even a batch driven set of commands like this:
0 kommentar(er)
