I am currently using SDL to create a consumer product that goes on a variety of
hardware including a wall mounted PC based box running W2K. (In the future this
box may port to Linux - which was a major factor in picking SDL for the job)
I have hit problems getting the software onto this wall box. The software runs
in 800 * 600 * 32 bpp exclusive mode.
Basically I have two different screens that will be used: one’s an LCD and the
other is a TFT. On the LCD I get screen corruption that consists of flickery
banding effects and an extra strip of display appearing at the extreme right of
the screen. On the TFT screen the display appears solid but the driver throws
up an overlay message saying its running in failsafe mode and should be switched
to 1280 * 768. On a CRT it runs just fine.
I have retested the setup using a stripped down demo and see exactly the same
problems. I have cross tested by writing an equivalent exclusive mode java demo
and also by using the legacy version of the app written in native directX. Both
of these drive the screen solidly - there is obviously no underlying harware
problem with either the LCD or TFT setup.
Has anyone else seen similar problems? At the moment it looks like a long and
risky proposition to start debugging through the SDL dll to try and discover
what SDL is doing differently to the native directX code.
Tx in advance,
Tony
You can’t reset the resolution of pixel grid devices the way you can
with electron beam devices. My guess is that the other software you are
using is actually using the full physical size of the LCD and TFT
screen. It may look like it isn’t, but there is some scaling being
done somewhere.
Bob PendletonOn Tue, 2004-11-02 at 05:33, Tony Green wrote:
I am currently using SDL to create a consumer product that goes on a variety of
hardware including a wall mounted PC based box running W2K. (In the future this
box may port to Linux - which was a major factor in picking SDL for the job)
I have hit problems getting the software onto this wall box. The software runs
in 800 * 600 * 32 bpp exclusive mode.
Basically I have two different screens that will be used: one’s an LCD and the
other is a TFT. On the LCD I get screen corruption that consists of flickery
banding effects and an extra strip of display appearing at the extreme right of
the screen. On the TFT screen the display appears solid but the driver throws
up an overlay message saying its running in failsafe mode and should be switched
to 1280 * 768. On a CRT it runs just fine.
I have retested the setup using a stripped down demo and see exactly the same
problems. I have cross tested by writing an equivalent exclusive mode java demo
and also by using the legacy version of the app written in native directX. Both
of these drive the screen solidly - there is obviously no underlying harware
problem with either the LCD or TFT setup.
Has anyone else seen similar problems? At the moment it looks like a long and
risky proposition to start debugging through the SDL dll to try and discover
what SDL is doing differently to the native directX code.
Tx in advance,
Tony
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
–
±-------------------------------------+
Bob Pendleton <bob pendleton.com> writes:
You can’t reset the resolution of pixel grid devices the way you can
with electron beam devices. My guess is that the other software you are
using is actually using the full physical size of the LCD and TFT
screen. It may look like it isn’t, but there is some scaling being
done somewhere.
Indeed. On LCD screens the pixels are very much built into the hardware
itself, and running at a lower resolution than the device is built for
will at best run in a sort of emulated lower resolution using pixel
doubling, or smoothed scaling on newer screens. Otherwise you’ll get the
problems you describe. So best find out the native resolution for those
displays.