Hmm, that does raise an interesting question, that I have no solution for.
At the end of the day it looks like the 'aperture.png' needs to be implemented in a way that can cope with final output display resolutions that can be different by 1 pixel (or the appropriate pixel size after magnification).
Most games I would probably run at a magnification of 3x or 4x so then 1 original game pixel is displayed as a 3x3 pixel or 4x4 pixel respectively.
Anyway, if using a magnification of 3x and also an aperture.png where 1 pixel is signified as a 3x3pixel, then that doesn't allow much room for detail or accuracy. When using a 2x magnification I don't think an aperture.png 1 pixel could be represented as a 2x2pixel;(the detail of rgb just can't be done).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sorry for rattling on there..
What resolutions are listed then? Just the initial resolution when first started?
Still it would be interesting to get a run down of the resolutions. It must be possible to get the list created, if someone that understands the code can have a quick look and point out which lines to remove to make the list only show resolution numbers only.
Sorting I imagine would be a little more difficult.
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|