Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame Type always "Application" (AMD Fluid Motion Frames) #381

Open
DevTechProfile opened this issue Dec 19, 2024 · 7 comments
Open

Frame Type always "Application" (AMD Fluid Motion Frames) #381

DevTechProfile opened this issue Dec 19, 2024 · 7 comments
Assignees

Comments

@DevTechProfile
Copy link

I've integrated latest PM v2.3 into CapFrameX. Even when enabling AMD Fluid Motion Frames, Frame Type always being set to "Application".

Did I miss something? Do I need to pass more options/arguments to the console app?!

Cyberpunk2077.exe,21992,0x1B4CD825FE0,DXGI,0,512,0,Composed: Flip,Application,11290392.7197,5.7686,3.3141,2.4545,3.4651,5.6450,5.6450,0.0000,NA,NA,NA,NA

@markgalvan-intel
Copy link
Collaborator

Interesting. Did you specify "--track_frame_type" as an argument to the console application?

We just ran the released console application with CP2077 and AMD Fluid Motion Frames enabled and here is a snippet for the captured CSV:

Cyberpunk2077.exe,7440,0x23952EE0E10,DXGI,0,512,0,Composed: Flip,AMD AFMF,884162.7183,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,28.4829,8.3031,0.0000,0.0000,NA,NA
Cyberpunk2077.exe,7440,0x23952EE0E10,DXGI,0,512,0,Composed: Flip,Application,884162.7183,14.7700,3.8962,10.8738,5.4893,13.1780,13.1780,0.0000,36.7860,7.8551,-6.9301,884162.7183,NA,NA
Cyberpunk2077.exe,7440,0x23952EE0E10,DXGI,0,512,0,Composed: Flip,AMD AFMF,884177.4883,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,29.8711,7.8572,0.0000,0.0000,NA,NA

If the above doesn't help would it be possible to capture and ETL file for us to debug?

@markgalvan-intel markgalvan-intel self-assigned this Dec 20, 2024
@DevTechProfile
Copy link
Author

Interesting. Did you specify "--track_frame_type" as an argument to the console application?

Yes, I am passing "track_frame_type" in the argument list. What's interesting, it works with XeSS FG. I've tested it on another system. AMD Fluid Motion Frames still isn't tracked correctly by PresentMon 2.3.0. The Adrenalin driver reports twice the FPS.

@markgalvan-intel
Copy link
Collaborator

"The Adrenalin driver reports twice the FPS" - So the AMD driver FPS overlay is reporting double the FPS that PresentMon is reporting for Displayed FPS?

Can you please provide an ETL file for us to debug. If not, can you provide your system setup and application used for testing so we can reproduce.

@aretha-dev
Copy link

Nice to meet you.
I'm having the same thing happen to me.
I can't get the AFMF frame rate with Presentmon.
The frame type always shows as application.
I'm using the version installed with PresentMon-v2.3.0.msi.
My environment is a Ryzen 7 8700G CPU.
The GPU is an iGPU radeon780M.
The motherboard is a B650M-HDV/M.2.
The OS is Windows 11.
The games I played were ARMORED CORE VI and the demo version of Dynasty Warriors ORIGIN.
n both cases, PresentMon displayed the FPS before AFMF was applied.
The original AMD Adrenaline displayed the FPS increased by AFMF.

I don't know much about C or C++,
but is there anything I can help you with?

@markgalvan-intel
Copy link
Collaborator

Thank you for the system configuration information. We will test locally and debug what's happening.

@DevTechProfile
Copy link
Author

If not, can you provide your system setup and application used for testing so we can reproduce.

OS: Windows 11 24H2 Build 26100.2894
CPU: Ryzen 7 9800X3D
Motherboard: ASUS Rog Strix X670E-E Gaming WiFi
BIOS: 2604
GPU: RX 7900 XTX
Driver: 24.12.1
Game: Cyberpunk 2077 + latest patch

"The Adrenalin driver reports twice the FPS" - So the AMD driver FPS overlay is reporting double the FPS that PresentMon is reporting for Displayed FPS?

Yes, that's the case.

@markgalvan-intel
Copy link
Collaborator

Thanks for the update. We have reproduced the issue and are currently working with AMD to resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants