dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80868] Support screen scaling modes for external monitors
Date: Fri, 04 Jul 2014 06:48:47 +0000	[thread overview]
Message-ID: <bug-80868-502-3KTi4wgU8k@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80868-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2138 bytes --]

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

--- Comment #4 from Kamil Páral <kamil.paral@gmail.com> ---
(In reply to comment #2)
> A deeper question is, why run non-native modes to begin with?  Whether it's
> the GPU or the monitor, it's always going to end up scaled.  Why do you want
> to run 1920x1080 when you can run 1920x1200?

I see several reasons:

1) Games do not support all resolutions. All old games (think Diablo or
Starcraft) have a) fixed 4:3 ratio b) a fixed resolution around 800x600. Newer
games (think Warcraft 3) didn't have fixed resolutions, but still had fixed
aspect ratio. But even modern games sometimes do this - when Witcher 2 (AAA
game from 2012) came out, it supported only 16:9 resolutions, but none of 16:10
resolutions (they fixed in afterwards with a patch). Moreover, there is often a
resolution cap hardcoded in the game which is the maximum resolution the
developers tested the game with. So if you buy 1440p or 2160p display today,
you might be surprised how many games don't allow your native resolution to be
selected, for no apparent reason.

2) Performance reasons. If your system is not able to run modern games in your
native resolution even with low details, you simply need to use a lower one,
there is no other choice. Lowering your resolution is the number one approach
how to make the game faster. It is very common.

3) Some people might prefer to run in a lower resolution to make things
"bigger". This might not be too common and probably not apply to games, rather
desktop. But I personally know some older people with a bit worse eyesight, who
prefer blurry but bigger text and widgets, rather than small and sharp.


(In reply to comment #1)
> I'm not sure when I'll have time to implement this, but just about
> everything you need is already in place.  The attached patch should get you
> started and may even work...

Thanks a lot! I'm not able to finalize this patch, but I hope someone more
capable will (I can blog about it to get some attention).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3097 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-07-04  6:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 18:59 [Bug 80868] New: Support screen scaling modes for external monitors bugzilla-daemon
2014-07-03 19:04 ` [Bug 80868] " bugzilla-daemon
2014-07-03 19:10 ` bugzilla-daemon
2014-07-03 20:53 ` bugzilla-daemon
2014-07-04  6:48 ` bugzilla-daemon [this message]
2014-07-07 13:42 ` bugzilla-daemon
2014-07-07 22:11 ` bugzilla-daemon
2014-07-07 22:27 ` bugzilla-daemon
2014-07-07 23:34 ` bugzilla-daemon
2014-07-08  1:06 ` bugzilla-daemon
2014-07-09 17:46 ` bugzilla-daemon
2014-07-10 16:17 ` bugzilla-daemon
2014-07-10 16:21 ` bugzilla-daemon
2014-07-10 17:13 ` bugzilla-daemon
2014-07-11 13:46 ` bugzilla-daemon
2014-07-11 13:47 ` bugzilla-daemon
2015-01-26 16:12 ` bugzilla-daemon
2015-01-26 16:14 ` bugzilla-daemon
2016-01-06 13:49 ` bugzilla-daemon
2016-01-06 18:14 ` bugzilla-daemon
2016-01-06 19:28 ` bugzilla-daemon
2016-01-07 10:36 ` 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=bug-80868-502-3KTi4wgU8k@http.bugs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox