On 05/08/2012 09:01 PM, ext Fredrik Höglund wrote:
> On Friday 04 May 2012, Samuel Rødal wrote:
>> On Linux, it's all up to the graphics driver in my experience. With the
>> binary Nvidia driver the only reliable way I've seen of enabling vsync
>> has been to do "export __GL_SYNC_TO_VBLANK=1" befor
On Friday 04 May 2012, Samuel Rødal wrote:
> On Linux, it's all up to the graphics driver in my experience. With the
> binary Nvidia driver the only reliable way I've seen of enabling vsync
> has been to do "export __GL_SYNC_TO_VBLANK=1" before launching an
> application. AMD's Catalyst control pan
On Monday 07 May 2012, Samuel Rødal wrote:
> On 05/04/2012 04:22 PM, ext Samuel Rødal wrote:
> > As for the open source drivers I don't know of any reliable way of
> > enabling vsync. There's the GLX_SGI_video_sync extension which is
> > supposed to give a uniform way to sync rendering regardless o
> > There is some risk involved though; an application with multiple windows
> > each being rendered to with OpenGL in a single thread will end up
> > achieving a max framerate of screen_refresh_rate /
> > number_of_animating_windows, due to swapBuffers blocking. Since it's not
> > a panacea, it mi
On Monday 07 May 2012 15:03:29 Samuel Rødal wrote:
> On 05/04/2012 04:22 PM, ext Samuel Rødal wrote:
> > As for the open source drivers I don't know of any reliable way
> > of enabling vsync. There's the GLX_SGI_video_sync extension
> > which is supposed to give a uniform way to sync rendering
> >
On 05/04/2012 04:22 PM, ext Samuel Rødal wrote:
> As for the open source drivers I don't know of any reliable way of
> enabling vsync. There's the GLX_SGI_video_sync extension which is
> supposed to give a uniform way to sync rendering regardless of graphics
> driver, but when I've tried it I've go
On Fri, May 4, 2012 at 9:16 AM, Samuel Rødal wrote:
> On 05/04/2012 05:55 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>>
>> On Fri, May 4, 2012 at 7:22 AM, Samuel Rødal wrote:
>>> On 05/04/2012 04:03 PM, ext Christoph Feck wrote:
On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
> Hello,
On 05/04/2012 05:55 PM, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Fri, May 4, 2012 at 7:22 AM, Samuel Rødal wrote:
>> On 05/04/2012 04:03 PM, ext Christoph Feck wrote:
>>> On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
Hello,
to be able to achieve smooth animations in QML 2,
Hi,
On Fri, May 4, 2012 at 7:22 AM, Samuel Rødal wrote:
> On 05/04/2012 04:03 PM, ext Christoph Feck wrote:
>> On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
>>> Hello,
>>>
>>> to be able to achieve smooth animations in QML 2, the animations
>>> should ideally use a fixed timestep, and not a
On 05/04/2012 04:03 PM, ext Christoph Feck wrote:
> On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
>> Hello,
>>
>> to be able to achieve smooth animations in QML 2, the animations
>> should ideally use a fixed timestep, and not a timer which might
>> have inaccuracies depending on the platform
On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
> Hello,
>
> to be able to achieve smooth animations in QML 2, the animations
> should ideally use a fixed timestep, and not a timer which might
> have inaccuracies depending on the platform and won't give fully
> smooth results.
Does OpenGL 2 ha
Hello,
to be able to achieve smooth animations in QML 2, the animations should
ideally use a fixed timestep, and not a timer which might have
inaccuracies depending on the platform and won't give fully smooth results.
In the context of this, and to avoid having values of 60 hard-coded (we
have a
12 matches
Mail list logo