Reply 1620 of 3949, by Dege
Is the DirectX tab list influencing the Glide tab one? 😐
No. I mean that internal scaling is a global feature, affects both Glide and DX.
So, for Glide, you couldn't choose a scale-to-resolution because the resolution selector on Glide tab is working and has other meaning.
(and I'm planning to tie up DX resolution selector some day)
Would it not be possible to read the current or native resolution from the registry?
Hmm, I don't know it yet. But Windows itself somehow knows what the native res is, as it has a 'recommended' resolution on its slider in the display settings.
Though ideally there'd be a choice between scaling options..
Ok, but normally, scaling is not performed by dgVoodoo.
In 'Centered' case there is no scaling at all.
In 'Stretched' case the scaling is done by the driver or the display output itself, cannot control that (but seems to be bilinear in all practical case).
In 'Stretched with AR' case, dgVoodoo emulates that bilinear filtering. But, this mode is not even recommended, if the driver supports ovverriding the scaling mode for applications, it's highly recommended to use that method instead of this.
I tried Diablo1 and found that it suffers from the same problem as O2Jam. The game places invisible windows over the main game window so watchdog thread of DXGI pushes it back to windowed mode at once all the time the game tries to switch into fullscreen.
It can only be played in windowed mode if option 'Disable Alt-Enter...' is disabled. 🙁