I have multiple trigger(process created/ended, monitor profile changed) that do not trigger when the match condition "monitor profile" is active. It works without it.
I am not sure but additional to that and maybe a hint to why this does not work:
I believe in previous versions I was able to see in the context menu of DisplayFusion which monitor profile is currently active. I believe it was highlighted/slightly different color.
If I am hallucinating it would be a nice feature
If you open the DisplayFusion Monitor Configuration window, does it show the correctly detected profile in the upper left corner of that window when you want the trigger to fire?
No it was not there, I saved the profile again and it appears now. I tried to save and load the profiles several times and it did not work before.
I think I had some weird bug with the scale setting that was not set or saved correctly. I changed it to 125% a few days back but in the Windows 11 menu. I just now reverted that back in Windows to 100%. It works now for the profile to be detected after saving it regardless where I change the scale...so I guess this is solved.
thanks for the support.
