drkPvr render plugin - 1280x800 limitation lowers image quality

[GoogleCodeExporter]

What steps will reproduce the problem?

1: Set Options->PowerVR->Resolution to 'HD or window (up to 1280x800)'
2: Set nullDC Settings->Fullscreen on
3: Set desktop resolution to greater than 1280x800 (I use 1920x1080)
4: Start a game

What is the expected output? What do you see instead?

The expected output is: In 1.0.3, nullDC would render 3D natively at the 
chosen resolution.

But instead I see: Native render resolution is restricted to ~1280x800, 
then upscaled to desktop resolution - image quality is significantly worse.

What version of the product are you using? What build? What plugins?

I use version: 104_r11

I use the precompiled binary available on code.google.com

I use the following plugins:

PowerVR Plugin: nullDC PowerVR Direct3D HAL (May 9 2010)
GDRom Plugin: Image Reader plugin (May 9 2010)
AICA Plugin: nullDC AICA (May 9 2010)
ARM7 Plugin: VBA ARM Sound Cpu Core (May 9 2010)
Maple Plugin(s): nullDC Controller [WinHook] (May 9 2010)
Ext.Device Plugin: nullExtDev (May 9 2010)

On what kind of system?

My system specifications are as follows:

Operating System: Windows 7 x64
CPU: E8500 3.16Ghz
Video Card: Nvidia 9800GTX
Sound Card: Realtek HD (onboard)
Additional related hardware and/or software: None

Please provide any additional information below:

I realise the 1280x800 limit has been deliberately coded, but 1.0.3 looks 
much better.

Original issue reported on code.google.com by matbur...@gmail.com on 11 May 2010 at 12:35

[GoogleCodeExporter]

I noticed that right away also. Having it set to just "Window" does improve 
quality 
over the "HD or window" option and I believe achieves what you're looking for. 

So with that being the cases, is this really an issue? I mean we have 5 options 
which allow users to pick the qaulity they want from poor all the way up to 
your 
desktop resolution. Personally I think it could be simplier or relabeled but 
that 
it's not that big of a deal. I was fine with how it used to be also (1.0.3 and 
before). I don't know... could use some changes I guess. 

Original comment by wespipe...@gmail.com on 11 May 2010 at 3:08

[GoogleCodeExporter]

do you have any proof to suggest that it is rendering at a lower res and 
scaling up?

Original comment by danialho...@gmail.com on 11 May 2010 at 4:44

[GoogleCodeExporter]

Window resolution is the maximum supported by the monitor on each system 
(maximum).

The 1280x800 one limits internal resolution to that one (in case a higher one 
has
impact on performance).

The 640x480 is the same but also acts as a reference resolution (some stuff 
break on
greater resolutions).

Half resolution is half what the system monitor supports.

It's up to you to choose the right one.

Original comment by Mr.PsyMan on 11 May 2010 at 8:48

[GoogleCodeExporter]

Thanks, the 'Window' option does indeed render at desktop res. I'd not paid it 
much 
attention because well, it says 'Window' and I want 'Fullscreen', and also 'HD 
or 
Window' sounds like a better option than 'Window' :)

I think this is still an issue, but just a low priority one where the menu 
options 
need renaming for more clarity. Cheers.

Original comment by matbur...@gmail.com on 11 May 2010 at 9:19

[GoogleCodeExporter]

HD or window mean whichever is smallest (so its native up to 1280x800 and then 
upscales). Got a better name to suggest ?

In fullscreen mode the entire screen is covered by the application window, 
everyone 
should know that ;)

Original comment by drkIIRaziel on 11 May 2010 at 9:45

[GoogleCodeExporter]

Looks like I have to use my proficient English skills again :p

Original comment by Mr.PsyMan on 11 May 2010 at 9:52

• Changed state: Started
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Changed names. For some reason I don't like them... But they make sense.

Original comment by Mr.PsyMan on 11 May 2010 at 10:16

• Changed state: Fixed

[GoogleCodeExporter]

Thanks for the reluctant change :)

My suggestion would be the following menu structure and options:

PowerVR -> Resolution -> Fullscreen -> 1920x1080@60hz
                                       1280x720@60hz
                                       1024x768@60hz
                                       640x480@60hz (Native)
                      -> Windowed   -> 1280x960 (Double)
                                       640x480 (Native)
                                       320x240 (Half)

Obviously the list of fullscreen resolutions would be larger, as in 1.0.3. 
These 
would be proper fullscreen vsync-enabled resolutions too rather than an 
expanded 
window (see issue 25). With this structure there's a clear distinction between 
Windowed and Fullscreen modes, unlike currently where 'Windowed' and 
'Fullscreen' 
can be selected simultaneously.

Original comment by matbur...@gmail.com on 11 May 2010 at 12:33

[GoogleCodeExporter]

I don't think there is a reason to include bunches of different resolutions. 
Maximum
is as far as it gets, for everyone. The rest modes are a workaround for systems 
that
can't keep up or for software limitations.

Adding all supported modes will make the list too big for no reason.

Original comment by Mr.PsyMan on 11 May 2010 at 12:52

[GoogleCodeExporter]

As long as the 'Maximum' mode is a proper vsynced fullscreen mode, I'm happy. 
The 
current expanded window implementation with screen tearing isn't good.

Original comment by matbur...@gmail.com on 11 May 2010 at 1:02

[GoogleCodeExporter]

It's not the implementation. It's the graphics driver not supporting V-Sync 
properly.

Original comment by Mr.PsyMan on 11 May 2010 at 2:20

[GoogleCodeExporter]

That's a shame, as vsync works fine in the old method used in 1.0.3.

This is more issue 25 chat anyway :)

Original comment by matbur...@gmail.com on 11 May 2010 at 2:51

[GoogleCodeExporter]

Original comment by Mr.PsyMan on 11 May 2010 at 3:05

• Changed state: Verified