Capframex 1.9 Beta

[renanlofiego]

It is important to mention that I am here as a beta tester; I know there might be inconsistencies, and that is precisely why I am here—I want to contribute however I can. Please don't mind if I ask questions that seem silly or obvious. Thank you!

Hi, I’ve been testing the 1.9 beta and really love the new overlay. I even mentioned on X (Twitter) that it would be great to have a keyboard shortcut—or something similar—to change the overlay's position on the screen, since it sometimes gets in the way of the HUD depending on the game.

I’d like to share some feedback based on the tests I’ve run...

With the Black Myth: Wukong Benchmark Tool, I can't even launch the game; here is how my overlay is currently configured.

I also got the impression that the new overlay is costing a bit of FPS; I didn't notice this in Cyberpunk, but I did see it in *Red Dead Redemption 2.

I also noticed a desync with the game's FPS.

[renanlofiego]

I tested it in Cyberpunk, and I didn't notice much of a difference—neither in the end result nor in the FPS synchronization.

Using Rivatuner

Using Capframex Overlay

In the Shadow of the Tomb Raider free trial, I noticed that issue where the frame rate isn't synchronized.

[renanlofiego]

It seems that FPS synchronization for both games only returned to normal after I disabled PresentMon, closed CapFrameX, and restarted it.

Note: It was actually when I disabled it without closing CapFrameX that I first noticed this FPS issue.

I also noticed that I no longer see the framerate display.

[renanlofiego]

Another thing I noticed is the overlay refresh rate: in RivaTuner it's set to 500ms, whereas here it's 1000ms. Which one should I go with? Could this be the reason for the difference in FPS synchronization?

Rivatuner

Capframex

[DevTechProfile]

Great job, very much appreciated! I will go through all issues step by step over the next days. Having a beta tester who is willing to contribute is extremely helpful.

[DevTechProfile]

I need the following log files from you.

The native OSD log files are stored in %TEMP%:

• cfx_osd.log – general OSD renderer log
• cfxhook.log – DXGI hook diagnostics; requires CFX_HOOK_LOG=1
• cfx_vklayer.log – Vulkan diagnostics; requires CFX_VKLAYER_LOG=1
• cfx_present_stats.log – optional performance diagnostics

CapFrameX-side OSD messages are also written to %APPDATA%\CapFrameX\Logs\CapFrameX.log and the rotated
CapFrameX_*.log files.