Opened 7 months ago

Closed 5 months ago

Last modified 5 months ago

#12289 closed feature request (outdated)

SCI32: filtered background upscaling option in hi-res gfx mode

Reported by: HunterZ Owned by: sev-
Priority: normal Component: Engine: SCI
Version: Keywords:
Cc: HunterZ Game: King's Quest 6

Description

ScummVM version

2.2.0 (Sep 14 2020 23:43:32)

Bug details

Sierra games such as King's Quest 6 that have the "Enable high-resolution graphics" option in ScummVM use nearest-neighbor scaling to upscale the backgrounds from the original 320x200 to 640x4?? when this option is selected, as per the original engine's Windows 3.1 implementation.

Unfortunately this also has the nasty side-effect of reducing the effectiveness of ScummVM's scaler/filtering features.

Given that ScummVM already lets you do many things not supported by the original games' engines, it would be nice if there were an option to perform at least a bilinear upscale of the backgrounds instead of only nearest-neighbor.

Language

English

Version

GOG or CD-ROM releases, DOS or Windows 3.1 flavors

OS

Windows 10 Home x64 20H2 19042.804

Attach a save game if possible

N/A. Just start a new game and look at the background.

last version without the bug

N/A. This is an enhancement.

Attachments (2)

kq6lowres.jpg (284.4 KB ) - added by HunterZ 7 months ago.
kq6hires.jpg (350.7 KB ) - added by HunterZ 7 months ago.
King's Quest 6 in hi-res mode with bilinear post-scaling

Download all attachments as: .zip

Change History (4)

by HunterZ, 7 months ago

Attachment: kq6lowres.jpg added

by HunterZ, 7 months ago

Attachment: kq6hires.jpg added

King's Quest 6 in hi-res mode with bilinear post-scaling

comment:1 by sev-, 5 months ago

Owner: set to sev-
Resolution: outdated
Status: newclosed

We are working on enhancing our scalers framework, so eventually, it will be possible to use fancier scalers for better effect.

comment:2 by HunterZ, 5 months ago

Is there a ticket or discussion that tracks the scaler framework enhancement effort?

Are there explicit plans to address my specific concern, which I am concerned originates at the SCI engine level and not at the scaler framework level?

Note: See TracTickets for help on using tickets.