About KQVI

clone2727 · Post by **clone2727** » Sat Oct 02, 2010 3:50 am

md5 wrote:The Windows version of KQ6 is actually doubling all game graphics with a simple 2x scaler

200 x 2 = 440?

MusicallyInspired · Post by **MusicallyInspired** » Sat Oct 02, 2010 8:53 pm

That was confusing me as well...

bobdevis · Post by **bobdevis** » Sun Oct 03, 2010 6:49 am

4 bit float rounding error?

md5 · Post by **md5** » Sun Oct 03, 2010 7:25 pm

The actual resolution that is used by KQ6 hires is 640x440, yes. It's still a simple 2x scaler, even if it does aspect ratio correction as well

clone2727 · Post by **clone2727** » Sun Oct 03, 2010 8:00 pm

md5 wrote:The actual resolution that is used by KQ6 hires is 640x440, yes. It's still a simple 2x scaler, even if it does aspect ratio correction as well

No, the engine is performing the 200->440 scale on the fly at the same time as correction, therefore it's not a simple 2x scaler.

md5 · Post by **md5** » Sun Oct 03, 2010 8:52 pm

I beg to differ, it's simple in the sense that it doesn't do any post-processing, like SuperSai2x or Mame2x or HQ2x, which is why I said it's a simple 2x scaler in the first place

fingolfin · Post by **fingolfin** » Sun Oct 03, 2010 9:42 pm

But if it scales from 200 to 440 lines, it is not a 2x scaler at all. Neither a simple one, nor a complicated one.
Rather, it is a 2.2x scaler. And it obviously has to do something more complicated than using every line a fixed number of times; e.g. use ever line from the original data twice, but use every 5th line three times. Or something like that.

Also, I am not sure what you mean when with "post-processing" in SuperSai2x, AdvMame2x and HQ2x... ?

md5 · Post by **md5** » Sun Oct 03, 2010 10:46 pm

fingolfin: Yes, it's a 2.2x scaler, and it does what you said.

Well, I should have phrased this better: the 2x scaling doesn't do additional computations based on the neighbouring pixels like hq2x does (which I named postprocessing, as it's done after the initial scaling phase). It scales the resulting pixels by 2, and it does a slight aspect ratio change in the process, too

Scarlatti · Post by **Scarlatti** » Sun Oct 03, 2010 11:05 pm

md5 wrote:The 2x scaling doesn't do additional computations based on the neighbouring pixels like hq2x does (which I named postprocessing, as it's done after the initial scaling phase). It scales the resulting pixels by 2, and it does a slight aspect ratio change in the process, too

All of which, as I understand it, can't be performed by HQ2x and other filters because they multiply/polarize the pixels by a fixed number?

md5 · Post by **md5** » Mon Oct 04, 2010 12:11 am

Scarlatti wrote:
md5 wrote:The 2x scaling doesn't do additional computations based on the neighbouring pixels like hq2x does (which I named postprocessing, as it's done after the initial scaling phase). It scales the resulting pixels by 2, and it does a slight aspect ratio change in the process, too
All of which, as I understand it, can't be performed by HQ2x and other filters because they multiply/polarize the pixels by a fixed number?

The issue is that this upscaling is done per pixel, which means that adding more sophisticated scalers for these games is a pain. Some code rewrite will have to be done, plus there's still the issue where the scalers themselves might not be compiled to save space