CFX 1.7.x : Can't blacklist some applications
rphlrmblt opened this issue · 7 comments
With the CapFrameX 1.7.1 or even 1.7.2beta (latest build of 28th April), I can't add to blacklist some applications :
I've clicked a lot of time son the blue refresh button of Running Process without success.
It's Notepad3 from https://github.com/rizonesoft/Notepad3/releases
I've the same problem also for CoolerMaster+ and nPerf beta (closed beta).
Best regards.
I don't see the app in your running processes list so the blacklist works.
Our blacklist controls which apps are ignored by the capture service. It has nothing to do with the visibility of the overlay, that is entirely controlled by RTSS, not us.
If you don't want to see RTSS on a specific application, you have to create an RTSS profile for that application and in that profile set the "Application detection level" to "None"
If that app is running currently, you can quickly add it as an excluded app by holding Shift while clicking on the "Add" button
I can"t add the application because CapFrameX is not able to find it and allow me to add in blacklist. I'll try the RTSS tips !
I can"t add the application because CapFrameX is not able to find it and allow me to add in blacklist.
The only thing our blacklist does is preventing the apps from showing up in the list of processes to be captured.
If it's not showing up there to begin with, you obviously don't need to add it to the blacklist.
And again, that list has nothing to do with the overlay.
Ok, as the process isn't in this list : https://github.com/CXWorld/CapFrameX/blob/master/source/CapFrameX.Data/ProcessList/Processes.json it can't be changed in the CapFrameX interface if I understand well ?
I've used the RTSS trick and it works, nice to know it now.
Ok, as the process isn't in this list : https://github.com/CXWorld/CapFrameX/blob/master/source/CapFrameX.Data/ProcessList/Processes.json it can't be changed in the CapFrameX interface if I understand well ?
Even if it was on that list, it wouldn't change anything about the overlay because, as I already said, it doesn't have anything to do with the overlay.
The running processes list is for apps that are detected by the capture service as apps that can be captured.
You don't have to do anything if the app isn't even recognised as one that could be captured.
The capture service has it's own internal filters for what app is most likely a 3D app that could be captured and what isn't.
The ignore list exists, so that you can manually move unwanted apps that appear in the running processes list and preventing you from just starting a capture.
Thanks for the explanations what should be readable on a Wiki to avoid this kind of bug report. As I'll close the bug, these comments won't be directly visible.
Best regards.
What the running processes and ignore list does is explained in the manual here on GitHub.