On 12 Apr 2013, at 11:47 PM, Michael Andersen wrote:
I found the root of the problem: there is something fishy with Nvidia's sync
to vblank implementation. If Vsync is turned off, everything works ok, if it
is turned on then all hell breaks loose. I just downloaded and installed
their
On 15 April 2013 11:56, Rutledge Shawn shawn.rutle...@digia.com wrote:
On 12 Apr 2013, at 11:47 PM, Michael Andersen wrote:
I found the root of the problem: there is something fishy with Nvidia's
sync to vblank implementation. If Vsync is turned off, everything works ok,
if it is turned on
On Monday 15 April 2013 12:08:34 Michael Andersen wrote:
On 15 April 2013 11:56, Rutledge Shawn shawn.rutle...@digia.com wrote:
On 12 Apr 2013, at 11:47 PM, Michael Andersen wrote:
I found the root of the problem: there is something fishy with Nvidia's
sync to vblank implementation. If
On Apr 11, 2013, at 8:43 PM, Alan Alpert 4163654...@gmail.com wrote:
On Thu, Apr 11, 2013 at 10:08 AM, Michael Andersen
mich...@steelcode.com wrote:
Forgot list in reply.
So no hope of it being fixed in 5.2 then... oh well. I'll go file a bug
report. Does this happen on windows too or is
Is vsync enabled in your driver? Sounds like it might not be. If not, then
Qt Quick 2.0 will render at 100% cpu rendering maybe many thousands of
frames per second, even though you only see 60 of them.
Unfortunately, VSync is enabled, that would have been a good explanation.
I am using the
I am using the Nvidia binary drivers (v304.51) so in order to double check
that applications actually *were* vsynced, I ran glxgears.
Also forgot to mention that glxgears was indeed vsynced:
$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the
On Friday 12 April 2013 09:26:16 Michael Andersen wrote:
Is vsync enabled in your driver? Sounds like it might not be. If not, then
Qt Quick 2.0 will render at 100% cpu rendering maybe many thousands of
frames per second, even though you only see 60 of them.
Unfortunately, VSync is
On Apr 12, 2013, at 9:26 AM, Michael Andersen mich...@steelcode.com
wrote:
Is vsync enabled in your driver? Sounds like it might not be. If not, then Qt
Quick 2.0 will render at 100% cpu rendering maybe many thousands of frames
per second, even though you only see 60 of them.
On 12 April 2013 09:55, Sletta Gunnar gunnar.sle...@digia.com wrote:
On Apr 12, 2013, at 9:26 AM, Michael Andersen mich...@steelcode.com
wrote:
Is vsync enabled in your driver? Sounds like it might not be. If not,
then Qt Quick 2.0 will render at 100% cpu rendering maybe many thousands of
No, I don't have a solution. I'm unsure though if it's that hard to fix, we
should probably profile it and see what's the culprit.
For me the problem was that both the application process and the X server
CPU consumption raised to about ~40% each, so it looked fine, but it didn't
/feel/ fine.
846cf1a13f80fe4590cc9ad4d9972d7a173accd6 to QtBase, which is going into
5.1, resize issues on gnome for instance.
I will grab the 5.1 alpha and see if the behaviour still exists.
Not that I _really_ expected things to be different, but the problem still
exists on 5.1.
As the app runs
I found the root of the problem: there is something fishy with Nvidia's
sync to vblank implementation. If Vsync is turned off, everything works ok,
if it is turned on then all hell breaks loose. I just downloaded and
installed their latest drivers (310.44) and the problem still exists there.
So,
Hi list,
I have a loading throbber in my application that is completely killing the
performance. If it is rotating then the application does not repaint while
it is being dragged and if more than two or three copies of the application
are running then it starts lagging Unity. I'm on Ubuntu 12.04
Hi,
I checked your code with QtQuick 1.1 (which is what I have as of now) and
it seems to be working perfectly fine. I ran 10 instance of application.
The logic seems correct in your code.
On Thu, Apr 11, 2013 at 11:31 AM, Michael Andersen mich...@steelcode.comwrote:
Hi list,
I have a
I just ran the code with QtQuick 1.1 as well, and it works fine with no
lag. So this must be a QtQuick2 problem...
Cheers
Michael
On 11 April 2013 18:40, preeteesh kakkar preeteesh.kak...@gmail.com wrote:
Hi,
I checked your code with QtQuick 1.1 (which is what I have as of now) and
it
I can confirm this. We have the same problem as well in KDE4 (that is Qt4),
so it's not a regression, but something that hasn't been fixed. (I once
even spent some time trying to figure out if it was fixable).
I guess you should report it here:
Forgot list in reply.
So no hope of it being fixed in 5.2 then... oh well. I'll go file a bug
report. Does this happen on windows too or is this a linux thing?
Does anyone have any ideas for a workaround? Other than don't rotate
stuff ?
Cheers
Michael
On Thu, Apr 11, 2013 at 10:08 AM, Michael Andersen
mich...@steelcode.com wrote:
Forgot list in reply.
So no hope of it being fixed in 5.2 then... oh well. I'll go file a bug
report. Does this happen on windows too or is this a linux thing?
It could also be a driver thing. When reporting the
18 matches
Mail list logo
