All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28771] Vsync always on
Date: Sun, 15 Aug 2010 09:12:43 -0700 (PDT)	[thread overview]
Message-ID: <20100815161243.9F9221300DB@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28771-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=28771

--- Comment #21 from Hans Nieser <hnsr@xs4all.nl> 2010-08-15 09:12:43 PDT ---
(In reply to comment #20)
> (In reply to comment #18)
> > To use vblank_mode for dri2 in .drirc you need a seperate dri2 driver with
> > vblank_mode specified, driconf doesn't handle it right.
> > 
> 
> Great! Is there a bug open for driconf so this can be configured correctly?

I believe I've run into the same problem with my RV770 (running
mesa/libdrm/xf86-video-ati, tried both classic and gallium) from git master,
where initially in every OpenGL app my framerate seemed to be capped to my
screen's refresh (by default - even without a .drirc).

After making this change in my .drirc, the framerate is not capped anymore but
it will still be swapping buffers during a retrace, and so I still get
multiples of 60Hz (my screens refresh rate). This means in glxgears I get a
ridicilous framerate like 2400, but in actual games like ioquake3, I get a
framerate that jumps wildly from 30 to 60 to 120Hz, which I find really awkward
:/

Is there any way currently to just make it swap buffers without regard for my
screens vertical retrace? I realise that means I get a lot of tearing but I'd
rather have that than a frame rate jumping around like that.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-08-15 16:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 19:14 [Bug 28771] New: Vsync always on bugzilla-daemon
2010-06-28 16:31 ` [Bug 28771] " bugzilla-daemon
2010-06-28 20:18 ` bugzilla-daemon
2010-06-28 22:41 ` bugzilla-daemon
2010-07-15 18:55 ` bugzilla-daemon
2010-07-15 19:28 ` bugzilla-daemon
2010-07-15 20:18 ` bugzilla-daemon
2010-07-16 12:03 ` bugzilla-daemon
2010-07-16 13:30 ` bugzilla-daemon
2010-07-16 13:37 ` bugzilla-daemon
2010-07-18  5:36 ` bugzilla-daemon
2010-07-18  8:10 ` bugzilla-daemon
2010-07-18 10:35 ` bugzilla-daemon
2010-07-18 10:50 ` bugzilla-daemon
2010-07-18 12:09 ` bugzilla-daemon
2010-07-18 13:14 ` bugzilla-daemon
2010-07-18 13:22 ` bugzilla-daemon
2010-07-19 17:29 ` bugzilla-daemon
2010-07-28  6:00 ` bugzilla-daemon
2010-07-28 11:41 ` bugzilla-daemon
2010-07-28 13:44 ` bugzilla-daemon
2010-08-15 16:12 ` bugzilla-daemon [this message]
2010-08-16  9:45 ` bugzilla-daemon
2010-08-16  9:50 ` bugzilla-daemon
2010-08-18 20:22 ` bugzilla-daemon
2010-08-23  4:37 ` bugzilla-daemon
2010-09-26 21:19 ` bugzilla-daemon
2010-09-27  9:55 ` bugzilla-daemon
2010-10-19 12:45 ` [Bug 28771] Waiting for vline forced " bugzilla-daemon
2010-10-19 12:50 ` bugzilla-daemon
2010-10-22 13:17 ` bugzilla-daemon
2011-02-09 15:40 ` [Bug 28771] [RADEON:KMS::R300C:R300G] waiting " bugzilla-daemon
2011-02-21 21:44 ` bugzilla-daemon
2011-02-21 21:51 ` bugzilla-daemon
2011-02-22  0:03 ` bugzilla-daemon
2011-02-22  0:22 ` bugzilla-daemon
2011-10-20  8:57 ` bugzilla-daemon
2014-07-07 16:43 ` bugzilla-daemon
2018-06-12 19:09 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100815161243.9F9221300DB@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.