Freesync support

[DestroyFX]

Hi, I just configured freesync on my side with latest mesa git and kernel 4.12 with DC patch.

On OpenGL (wine) with freesync enabled : It work perfectly
On Nine (wine) with freesync enabled : It's like without any kind of vsync, 150fps+
On Nine (wine) with freesync disabled : The vsync go down to 30fps instead of 60fps (It does that since forever, it's not related to freesync/DC patchs)

[axeldavy]

I don't know how freesync is handled in the graphic stack, and I don't know how much we can make it work with the dx9 swapbuffer model.
You can make gallium nine behave more like opengl with:
tearfree_discard=true as env var (or drirc config)
If it doesn't behave well, thread_submit=true can help too.

If freesync is implemented such that the opengl swapbuffer way works as is without modifications, these could help.

[DestroyFX]

@axeldavy I tested with both and each envvar and thread_submit=true seam to fix the problem.

[sarnex]

Somewhat unrelated but does freesync actually work with mesa and DC? I thought it was hooked up in the kernel but not in userspace yet. Maybe it's implemented so you don't need to touch userspace

…

On Tue, Aug 15, 2017 at 1:39 PM, Mathieu Bélanger ***@***.***> wrote: @axeldavy <https://github.com/axeldavy> I tested with both and each envvar and thread_submit=true seam to fix the problem. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#286 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGvNDKe6-a2X5Jp_q4M6jHYVoSHKPCuLks5sYdfngaJpZM4O3s-Y> .

[DestroyFX]

@sarnex
I used the last 4.12 with last DC in it I got there : https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.12

The rest of my gfx stack (libdrm, mesa, llvm, ddx) is 100% blñeeding edge, so it might need some other bit in the userspace that require like this week mesa or something, I don't know.

And it seam to work fine, it stay at 60fps then if it can't render that fast, it go down for example to 55fps, not 30. So I assume it's is working fine.

xrandr --prop
blabla
supported: off, on, auto
freesync_capable: 1
range: (0, 1)
freesync: 1
range: (0, 1)
underscan vborder: 0
blabla

[sarnex]

Have you checked using your monitor on screen menu that the actual refresh rate is changing?

…

On Tue, Aug 15, 2017 at 2:16 PM, Mathieu Bélanger ***@***.***> wrote: @sarnex <https://github.com/sarnex> I used the last 4.12 with last DC in it I got there : https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.12 The rest of my gfx stack (libdrm, mesa, llvm, ddx) is 100% blñeeding edge, so it might need some other bit in the userspace that require like this week mesa or something, I don't know. And it seam to work fine, it stay at 60fps then if it can't render that fast, it go down for example to 55fps, not 30. So I assume it's is working find. xrandr --prop *blabla* supported: off, on, auto freesync_capable: 1 range: (0, 1) freesync: 1 range: (0, 1) underscan vborder: 0 *blabla* — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#286 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGvNDLc72gTu9RW0A8x0KK98QFDQmgmmks5sYeCWgaJpZM4O3s-Y> .

[mirh]

Is there any improvement/difference now that DC is up and official?

[axeldavy]

My understanding is it should be working without changes

[axeldavy]

Moved here:
iXit/wine-nine-standalone#14