summaryrefslogtreecommitdiffstatshomepage
path: root/docs/newvideo.txt
diff options
context:
space:
mode:
author Robbbert <pac0446@bigpond.net.au>2015-07-18 11:42:30 +1000
committer Robbbert <pac0446@bigpond.net.au>2015-07-18 11:42:30 +1000
commit7822e262feb3e1a73b19fa26366f72ac9f8c3c24 (patch)
tree4f5a01bb3a5034d289858a8521d3c73e505c303d /docs/newvideo.txt
parent3aa7f65e7c7467c9920999d80b525ca0daeb798f (diff)
Small doc update.
Diffstat (limited to 'docs/newvideo.txt')
-rw-r--r--docs/newvideo.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/newvideo.txt b/docs/newvideo.txt
index 8eef40441b5..10c752bf2b0 100644
--- a/docs/newvideo.txt
+++ b/docs/newvideo.txt
@@ -105,7 +105,7 @@ disable hardware stretching, otherwise you won't get that "perfect"
So, I recommend starting with these initial options and then tweaking
from there. One additional option you might want to try in
combination with the above is the -prescale option. -prescale takes
-an integer parameter from 1 to 8, and specifies a magnification
+an integer parameter from 1 to 3, and specifies a magnification
amount by which the screen pixels are expanded before they are drawn
to the screen. Why is this useful? And how much of a performance
impact does it have? Well, that depends on the mode you are running
@@ -117,7 +117,7 @@ them to the screen. Depending on the video card, this is usually a
small performance hit, but not too significant. The benefit is that
each prescale factor reduces the blurriness of the pixels.
-prescale 1 is the default, which does no scaling. -prescale 2 will
-double each pixel, -prescale 3 will triple each pixel, etc. For my
+double each pixel, and -prescale 3 will triple each pixel. For my
money, -prescale 2 is sufficient, but people with super high
resolution displays claim that larger -prescale factors work even
better.