After having upgraded from 1.0.1 to 1.0.8 I noticed that my app ran far
more slowly Fullscreen then it had before. Noticing that those video
memory protecting wern’t coming up and further noting that X’s vm
extension was being used, I looked at the code in src/video and read in
SDL_x11dga.c that DGA was only available for mouse handling and that DGA
video was being moved into a fullscreen only driver.
I need some of the fixes, particularly in audio in the latest releases,
but I can’t lose this functionality. Is there some way to restore or
enable this?
Nope, you just have to wait for the DGA 2.0 fullscreen driver to come out.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
After having upgraded from 1.0.1 to 1.0.8 I noticed that my app ran far
more slowly Fullscreen then it had before.
What video card do you have? Many cards actually speeded up with this
change.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
After having upgraded from 1.0.1 to 1.0.8 I noticed that my app ran far
more slowly Fullscreen then it had before. Noticing that those video
memory protecting wern’t coming up and further noting that X’s vm
extension was being used, I looked at the code in src/video and read in
SDL_x11dga.c that DGA was only available for mouse handling and that DGA
video was being moved into a fullscreen only driver.
I need some of the fixes, particularly in audio in the latest releases,
but I can’t lose this functionality. Is there some way to restore or
enable this?
Jeremy Peterson.
Sam Lantinga wrote:
What video card do you have? Many cards actually speeded up with this
change.
On my matrox g200 testsprite reports ~100 fps and ~250 fps with
testsprite -fullscreen using the 1.0.1 lib.
The same tests using a Voodoo 3 2000 report ~40 fps and ~72 fps.
With the 1.0.8 library the framerate remains constant at 100 fps and 40
fps respectively whether windowed or fullscreen.
The new library also breaks testsprite -fullscreen -hw -flip, as far as
I can tell. ( Those options used to reduce the fps considerably and
report that they used hardware surfaces. Now they report using software
surfaces. )