[Feature Request?] Add at least some sort of direction on on how to use exec for per-app profiles

[gardotd426]

Hey, so we spoke on reddit the other day, I was touting radeon-profile's greatness and you came to say thanks and we had a little back and forth. Anyhow, I had mentioned that seemingly the only functionality that radeon-profile lacked in relation to CoreCtrl was per-application profiles/fan curves or whatever, and you said that it actually did have that. Only, it's almost impossible to suss out how to actually use it, and there is zero documentation anywhere.

Also, there are only limited environment variables available, without any ability to add custom ones, for, say, mangohud, or aco.

But as far as actually using it at all, there's a name section, which obviously would be whatever you want to call it, and then a Binary section, for the program itself I imagine, and then "Binary parameters," which I have no idea what on earth those are, since they're not envvarsl, and then Log file, which is self-explanatory. Then, there's a list of provided envvars. But there's nowhere to select which fan curve or overclock profile, or even dpm performance level to use. So how could you even use this for anything?

I'm sorry if this should be self-explanatory, but to me it's definitely not, and I have no idea how to actually dictate which OC profile and fan profile or mode get used for the exec I create. If there's any way possible to add some guidance to the README, that would be excellent. Thanks, keep up the awesome work, and as I said before, if you need any Navi testing or debugging I have two different Navi GPUs and am more than happy to help.

[marazmista]

Hi. You are looking at wrong tab. From the description I suppose you are in Exec tab but for per-application profile there is an Events tab. There you hit add button, window will pop up, select binary as event trigger, change options and that's it. Also you have to check master checkbox Evable event tracking above the list with events to make stuff work.

Exec tab is simple launcher. You can select binary, add parameters and define environment variables that will be temporarily set. Example: binary: /usr/bin/wine binary parameters: /path/to/some_game.exe and in variables you can set GALLIUM_HUD= stuff or other than default WINE_PREFIX= for execution.

Also, there are only limited environment variables available, without any ability to add custom ones, for, say, mangohud, or aco.

Yes, list is limited and may be outdated because many new tools have been created but at the bottom there is Summary field that contain all items selected from Variables and Values lists. By default it is read-only but when you check Tune variables manually you can specify custom variables that are not on the list.

Here is file that contains items on lists and during compilation it is integrated into program: https://github.com/marazmista/radeon-profile/blob/master/radeon-profile/variables/envVars