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.

Sign up for GitHub

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

Jump to bottom

S.T.A.L.K.E.R: Call of Pripyat performance regression #455

Closed
shoober420 opened this issue Nov 18, 2019 · 6 comments
Closed

S.T.A.L.K.E.R: Call of Pripyat performance regression #455

shoober420 opened this issue Nov 18, 2019 · 6 comments

Comments

@shoober420
Copy link

shoober420 commented Nov 18, 2019 •
edited
Loading

Software information

S.T.A.L.K.E.R: Call of Pripyat

System information

  • GPU: GTX 760
  • Driver: 440.31
  • Wine version: Proton 4.11-8
  • D9VK version: 0.30

S.T.A.L.K.E.R.: Call of Pripyat has encountered a serious performance regression. My FPS will be constantly what looks like literal 5 FPS.

ValveSoftware/Proton#3229
@misyltoad
Copy link
Owner

Logs/Apitrace?

@shoober420 shoober420 changed the title S.T.A.L.K.E.R: Call of Prypyat / System Shock: Enhanced Edition are at 5 FPS S.T.A.L.K.E.R: Call of Prypyat performance regression Nov 19, 2019
@shoober420
Copy link
Author

shoober420 commented Nov 19, 2019 •
edited
Loading

Here goes the logs. I'm on Proton, so installing apitrace would be weeeeeeird.

xrEngine_d3d9.log

xrEngine_d3d11.log

@shoober420 shoober420 mentioned this issue Nov 19, 2019
Closed
@shoober420 shoober420 changed the title S.T.A.L.K.E.R: Call of Prypyat performance regression S.T.A.L.K.E.R: Call of Pripyat performance regression Nov 19, 2019
@misyltoad
Copy link
Owner

If you can't trace it can you at least bisect?

@misyltoad
Copy link
Owner

https://git.froggi.es/joshua/d9vk/-/jobs

@misyltoad
Copy link
Owner

S.T.A.L.K.E.R.: Call of Pripyat has encountered a serious performance regression. My FPS will be constantly be what looks like literal 5 FPS.

Are you sure that's not because you're using debug logging?

@shoober420
Copy link
Author

shoober420 commented Nov 20, 2019 •
edited
Loading

@Joshua-Ashton
The performance was that way before I put the log command options in.

I have a feeling the new release will fix it...

misyltoad added a commit that referenced this issue Nov 26, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
ccc4e26 
See 89dfa2b

Closes #459 and #455
@shoober420 shoober420 mentioned this issue Nov 26, 2019
Open
misyltoad added a commit that referenced this issue Nov 27, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
48eefb9 
See 89dfa2b

Closes #459 and #455
misyltoad added a commit that referenced this issue Dec 6, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
d6cb7a0 
See 89dfa2b

Closes #459 and #455
misyltoad added a commit that referenced this issue Dec 13, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
cb5c655 
See 89dfa2b

Closes #459 and #455
misyltoad added a commit that referenced this issue Dec 16, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
74cfa2a 
See 89dfa2b

Closes #459 and #455
misyltoad added a commit that referenced this issue Dec 16, 2019
@misyltoad
[d3d9] Hook up platform-specific clock
640ed8a 
See 89dfa2b

Closes #459 and #455
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shoober420 @misyltoad