[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 342881] fullscreen unredirection + multiscreen: Residue image of fullscreen apps on desk
From:       <empire () adslgr ! com>
Date:       2015-04-01 7:30:04
Message-ID: bug-342881-17878-HSEGghAov8 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=342881

--- Comment #21 from empire@adslgr.com ---
(In reply to Thomas Lübking from comment #20)
> Just to be very sure:
> DFP-0 is the 120Hz device you looked up eg. in "xrandr -q", not some string
> google cooked up?

I looked it up from nvidia xsettings GUI. DFP-0 is my 120hz monitor. 

xrandr -q lists the same monitor as DVI-I-1 because propriatery Nvidia drivers
have a peculiar dual naming of the outputs (e.g. DVI-I-1 and DFP-0) for some
reason that I will never ever understand but it does not really matter as I
tried both DFP-0 and DVI-I-1 and it still runs at 60FPS. 

> 
> How did you obtain the 60 FPS?

I have no way of measuring it, but it is clear as day that it is 60FPS and I
confirm it by disabling my other 60hz monitor and leaving only the 120hz
monitor enabled and then kwin runs at 120fps vsync'ed normally. Only when both
monitors are enabled then kwin runs with 60fps on both of them.

> try adding
> export __GL_SYNC_DISPLAY_DEVICE=DFP-0
> in /etc/profile to have it apply to everything

I already done that. Problem remains.

> Only one monitor can be vsync'd (but FPS could be restricted to 60 for both,
> yes - one synced and the other not)

I don't mind if one of them is not vsynced, I just want 60fps on the 60hz and
120fps on the 120hz. Or to be more precise on each connected and enabled
monitor, no matter how many of them, kwin should run on each one with as many
FPS as is their respective refresh rate.

> I cannot say whether the driver might restrict the synced framerate to the
> refreshrate of the slower screen when it detects a context to be on both
> outputs, but I cannot imagine why it should do that either.

Isn't there a way to find out programmatically how many fps kwin runs,
prefferably on each output/monitor?

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]