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

Test Results with TES4:Oblivion #32

Open
llde opened this issue Mar 8, 2018 · 0 comments
Open

Test Results with TES4:Oblivion #32

llde opened this issue Mar 8, 2018 · 0 comments
Labels
perf-data Performance reports

Comments

@llde
Copy link

llde commented Mar 8, 2018

The test are made on a laptop with AMD GPU, using mesa and amdgpu driver.
Wine staging 3.3.
Test maed using DRI_PRIME=1 to force discrete gpu
The test were made only with CSMT active.

FPS wise there isn't a sigificative improvement, between 20-40 FPS with or without PBA patchset.
Without PBA sometimes the game drop to 10 FPS (expecially when casting).
With the PBA patchset the game keep a better on operations that will result in a framerate drop without PBA. In some case the drop still happen but it is less noticeable.
With PBA there is no noticeable difference between mesa_glthread=false and mesa_glthread=true, instead there is a difference without PBA.
When I was testing PBA, I have an unexpected close (without crash) when I tried to load waterfront. I was with WINEDEBUG=-all, so I could not get a trace if it existed. I was unable for now to reproduce the issue with WINEDEBUG=warn+all.

In the last case I'm getting in the log:
0034:fixme:d3d_perf:wined3d_buffer_map Fences not used for persistent buffer maps on CS thread, using glFinish.

@acomminos acomminos added the perf-data Performance reports label Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf-data Performance reports
Projects
None yet
Development

No branches or pull requests

2 participants