No problem. You are free to use IntegerScaler in any way you wish as long as you hopefully clearly understand what and why you are doing.
But in case of a
public tip like this, I believe it’s important not to confuse many people reading this thread, as for how to properly use the app. Using resizing for scaling is typically a mistake.
Command-line options are unneeded for basic usage, and those options that prevent actual scaling from happening at all are even somewhat harmful for those who didn’t previously use IntegerScaler.
It’s still unclear what the actual internal game resolution (not default window size) is. Whatever that resolution is, window size before scaling must be equal to it, for integer-ratio scaling to work as intended — with no distortion. So e.g. if the game runs at 1280×720, the game window (its rendering area called client area) must be exactly 1280×720 as well.
If the game is a 3D game, and can be rendered at any resolution, but can’t be due to a limitation in windowed mode, for integer scaling to work just set `-resize` to the desired resolution at least twice lower than your native resolution, then use Alt+F11 in IntegerScaler for 2x upscaling. Of course, the game should adjust its internal resolution according to window size (not each game does this), otherwise distortion would occur.