Question about fullscreen 320x240

I am in 800x600 and I want fullscreen 320x240
the correct flags are SDL_SWSURFACE | SDL_FULLSCREEN
right?

Why is it I get a full screen display and what looks like a clipped 320x240
area. Do I need to use SDL_HWSURFACE?

This is kinda neat stuff here…

Dave

I am in 800x600 and I want fullscreen 320x240
the correct flags are SDL_SWSURFACE | SDL_FULLSCREEN
right?

Why is it I get a full screen display and what looks like a clipped 320x240
area. Do I need to use SDL_HWSURFACE?

You need to add a 320x240 video mode to your XF86Config file

See ya!
-Sam Lantinga (slouken at devolution.com)

Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec

How silly of me.
I am by no means a pro at doing this sort of thing. I read the howto but it
was (I am afraid) to technical for me.
I got a valid (nice and safe looking) 320x240 mode enabled. I just don’t know
why my mouse doesn’t work in it properly. I can’t move the full range
vertically (according to the position of the pointer on the screen) and things
below the pointer show up selected in that mode. I am currently not showing
the pointer via SDL_ShowCursor(0) in my little test program to avoid any
problems.

Any ideas on how to fix my pointer and or a pointer to a good easy reference to
getting the most from my card via XFree86. I realize that someone must have an
accelerated version for my RivaTNT but I’ll be damned if the performance has
ever been anything but slow in 3-D Mesa demos.

Any help whatsoever would be nice.
Thanks
Dave

I got a valid (nice and safe looking) 320x240 mode enabled. I just don’t know
why my mouse doesn’t work in it properly. I can’t move the full range
vertically (according to the position of the pointer on the screen) and things
below the pointer show up selected in that mode. I am currently not showing
the pointer via SDL_ShowCursor(0) in my little test program to avoid any
problems.

This is a bug in doublescan (I think) video modes under XFree86.

I’m not sure if it is fixed in newer versions of XFree86.

-Sam Lantinga				(slouken at devolution.com)

Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec

David Leimbach wrote:

I realize that someone must have an
accelerated version for my RivaTNT but I’ll be damned if the performance has
ever been anything but slow in 3-D Mesa demos.

go here for nvidia’s riva xserver. currently its xfree 3.3.5 with some
patches(vmwares DGA patch, some stuff for acceleration, etc…) and a glx module
for 3d acceleration, its easy to setup and rather stable. note: 3d acceleration is
currently only available in 16bpp.
http://www.nvidia.com/Products.nsf/htmlmedia/software_drivers.html

Jess

Thank you!!On Tue, 15 Feb 2000, Jess wrote:

David Leimbach wrote:

I realize that someone must have an
accelerated version for my RivaTNT but I’ll be damned if the performance has
ever been anything but slow in 3-D Mesa demos.

go here for nvidia’s riva xserver. currently its xfree 3.3.5 with some
patches(vmwares DGA patch, some stuff for acceleration, etc…) and a glx module
for 3d acceleration, its easy to setup and rather stable. note: 3d acceleration is
currently only available in 16bpp.
http://www.nvidia.com/Products.nsf/htmlmedia/software_drivers.html

Jess

Hi!On Tue, 15 Feb 2000, Jess wrote:

go here for nvidia’s riva xserver. currently its xfree 3.3.5 with some

I would recommend that you get the old (XFree86-3.3.3.1-based) version
from http://www.lokigames.com/support/gldrivers/ instead. The new one
breaks Quake 1…3 (and a few other programs I have) because it claims to
support features like paletted textures but crashes when they are used
(Quake 1 can be made to work by using the -no8bit option though). I didn’t
see any performance gains in the new driver either.

Bye,
Christian


/ Coding on PowerPC and proud of it
/ http://www.uni-mainz.de/~bauec002/