In Case you encountered a bug, please create an issue on Github
To discuss CapFrameX with other users, visit the following sites:
PCGH Extreme (german)
If you want to contact CapFrameX Developer Team, you can
Alternatively, contact us by mail to firstname.lastname@example.org
Questions and Troubleshooting
The overlay is showing me 0.0 FPS
Short answer: There is no running process detected or there are multiple processes detected and you haven't chosen one of them.
Explanation: Usually RTSS displays it's own FPS that are always showing, but in order to get an accurate format for our colors and limits to these FPS values we needed to transfer them from RTSS to CX and then put them on the overlay.
A side effect of this is, that we need to specify for which process we want these values so we bound them to the currently running process in our process list.
If a process isn't detected or you have multiple processes present in that list the FPS will show 0.0 because we don't know which process ID to provide to RTSS.
I'm pressing the capture hotkey but it's not working.
Make sure you got a process detected to be captured. Also make sure that it's only one because otherwise CX doesn't know which one you want to have captured.
If you enable the "Capture service status" on the overlay, it'll tell you if there are multiple processes detected or if there isn't any at all in which case it will just say "Scanning for process...".
Alternatively, as explained above, an FPS value of 0.0 will tell you the same thing in most cases.
My game doesn't get recognized
Process detection is mostly up to PresentMon, so we don't have full control over that. If you're having problems, you can still contact us and we'll see what we can do.
Sometimes, PresentMon fails to hook to the process right away, in that case you can try to scan for processes again by clicking the rescan button on top of the running processes list.
Also, older or customized Windows versions (1709 and older) can interfere with PresentMon so an up-to-date version of Windows 10 is always recommended.
Some sensors are suddenly missing on my overlay
Because we're still at a stage where we're adding new stuff regularly, with every new version there is a possibility for some unwanted behaviour when using a new version with already existing overlay config files.
We try to minimize this as best as we can but sometimes it's not possible. So if you're missing something in your list that was there before, try to reset the config with the button at the top of the list and alternatively delete the old config found in your documents folder.