Build engine games need VBE2.0 for higher resolutions as well

keropi wrote:

Build engine games need VBE2.0 for higher resolutions as well

Are you sure? I can play Duke3D up to 1024x768 with a VBE1.2 card and no TSR. I will say, some cards get a performance boost when running Duke3D SVGA with UniVBE/S3VBE20.

well it does say so in the setup at the screen section: " VESA modes (SVGA/VESA 2.0)"

keropi wrote:

well it does say so in the setup at the screen section: " VESA modes (SVGA/VESA 2.0)"

Duke3D uses the Build Engine which supports a MASSIVE array of video modes, far more than the Duke3D Setup program alludes to. Whether it can handle VESA 1.2 or not I don't remember at the moment.

But, one relevant point is that VESA 2.0 supports a multitude of resolutions, whereas 1.2 pretty much only supports 640x480, 800x600, 1024x768 and 1280x1024. So any game trying to run VESA SVGA using a resolution other than those four will absolutely require VESA 2.0 to do so.

X-MEN Children of the Atom?

Gemini000 wrote:

keropi wrote:

well it does say so in the setup at the screen section: " VESA modes (SVGA/VESA 2.0)"

Duke3D uses the Build Engine which supports a MASSIVE array of video modes, far more than the Duke3D Setup program alludes to. Whether it can handle VESA 1.2 or not I don't remember at the moment.

Believe me, it can. All of my VBE1.2 cards work at 640x480, 800x600 and 1024x768 without running UniVBE, Sci Tech Display Doctor, or S3VBE20. 😀

I was messing with the SVGA modes in Duke3D last night on my Matrox Millennium - 640x480 works fine, but the lower res options 300x200, etc) fail, complaining that they want VBE 2.0.

Blood however works fine for all resolutions, same card, no UniVBE, etc loaded.

badmojo wrote:

Blood however works fine for all resolutions, same card, no UniVBE, etc loaded.

There could be a number of reasons for that, but rest assured, VESA 1.2 does not support any resolutions outside the ones I mentioned above, so something else must be going on for other resolutions to be working in SVGA mode, such as Blood having its own internal VESA 2.0 driver, defaulting out of SVGA to VGA to try an honour specific resolutions, or detecting your video card and utilizing SVGA support specific to your video card.

I suppose it's also possible that the Matrox Millennium may have VESA 2.0 support but that the method Duke 3D uses to detect it may not work with that specific card.

Again, TONS of possibilities here. :B

The Millennium does have VBE2.0 baked in.