glCallList & FullScreen Sloooow

I’ve got a problem, I use 3 config (AMD XP 1800+ GF2MX, AMD DR 800 VOODOO3,INTEL CELL 433 VOODOO3) and I’ve got a crazy problem.
I’ve seen in the red book that it’s possible to use Display List.
So I was using this feature to do my font display.
Everything is ok on my XP+GF2MX but on VOODOO3 in the fullscreen mode, the system is very slow (so slow that it looks as frozen) (got 85 FPS in windowed mode, and less than 0.01 FPS in fullscreen on this VGA)
When I disable the display font line:

glCallLists(strlen(text), GL_UNSIGNED_BYTE, text);

everything is Ok (run fast and correctly).
I haven’t noticed this fact because I was dev’ with the GF2Mx but on Voodoo card it seem to be a problem.

I must have a problem with this glCallList ('cause I couldn’t believe it comes from my Voodoos 3).

Has anyone an idea of that problem?
Is it due to Voodoo?
Waooww I’ve got a voodoo that runs faster in windowed mode than fullscreen? lol … a miracle? (aouch 0.01 FPS great man , I’m the best

Thanks if anyone can get me out this crazy thing.

It could be that 3DFX never really bothered to make display lists run very fast in their GL implementation.

Aouch

I looked for the tutorial from www.gametutorial.com about fonts, and it do the same (also I’m in doubt of my cards)… but how it’s possible ? the drivers would fit with OpenGL 1.1 specs…
(Latest official Drivers,and last unofficial beta used).

Is there another gl command to do this trick on Voodoo3?

Maybe it won’t help you much, but i’ve got voodoo 3 too, and using display lists is sure way to slow it down 3 times.
Once I had the same problem like you do (I mean 0.1 FPS). Solution was not using the display lists .

Maybe the 3dfx drivers implement display lists in software. Could this cause a slow down?

-Tyler

How else could they implement display lists? The voodoo series of cards didn’t/doesn’t have hardware T&L, so everything bar the triangle rasterising was/is done in software.

Just out of intrest did the voodoo5 have display lists?

-Tyler

well, did the voodoo5 have T&L?
there’s your answer.

Originally posted by vshader:
well, did the voodoo5 have T&L?
there’s your answer.

That is definitely no excuse for letting display lists run slower than immediate mode or vertex arrays. This sounds like it’s entirely due to crappy drivers.

– Tom

So, is there a way to replace the display list code with vertex array code or something else working on voodoo?

What will become this part of code?:
glCallLists(strlen(text), GL_UNSIGNED_BYTE, text);

'cause would like to keep my font code, and using it on voodoo without problem.
Thanks

Just another Point: May be voodoo3 doesn’t support T&L and display list, but …why it works in windowed mode?
My problem appears only when using display list in fullscreen.
A drivers Bug?
Thanx

Solution: Get a GeForce4 Ti4x00 series card.

Seriously, the Voodoo cards are so out of date, and you could get my GF2 GTS 32meg AGP 4x with fastwrites support for like $45 incl shipping… there is no excuse not to have one

Yes sure I don’t want to keep a such old series (wich as more effect for 2D than can expect all NVidias ie: emulators on TV )
But my problem is: if I do applications for commercial use, I must prevent from bugs with some Video Card (I can’t imagine I told every costumer “Go Buy a GF4” …).
My regards on that problem is only to prevent this bug (or implementation failure) from other cards.
Voodoo’s, Matrox old series, FireGL , TNT2, etc… Savage,…all those… can be found on costumers’ PC’s.
I just wandering if it only occurs with voodoo and if it’s a problem coming from my app or from drivers.
Thanks for all

Here’s a thought: on my old 8 Mb Savage3D, OpenGL rendering would slow down to a crawl like you are describing when I would enlarge the window beyond a certain point. I seem to recall that it only happened in 32-bit color mode. I attributed this to the driver switching to software mode because it didn’t have enough onboard memory to support this window size. Maybe when you switch to fullscreen, it is switching to software mode. Taking out the code that draws the text might just be speeding it up enough to give a reasonable frame rate even though it is still in software mode. How much mem does your Voodoo 3 have?

You will note that a lot of commercial games don’t support Voodoo cards anymore.

People who bought Voodoos were mostly gamers who cared about cards. Those people have long since upgraded to something better.

Aaron: My card is 16Mb memory but it’s not the problem 'cause in fullscreen I set up resolution to 640x480 and in windowed mode I go up to 1024/768…

jwatte: yes I know that no commercial games support the voodoos “for special features” but a commercial application must run on every card without bug. (I don’t search for psecials feature …only want to have my scene rendered correctly [in software or hardware mode} at least 15Fps in 640x480.

I just want to avoid problem with other graphics cards. And to be mostly compatible.
Thanks Aaron for that point on Savage.

You surely don’t switch to 32bit color mode, do you?

Originally posted by zeckensack:
You surely don’t switch to 32bit color mode, do you?

From what I remember, Voodoo3 couldn’t do real 32-bit rendering.

Originally posted by josip:

From what I remember, Voodoo3 couldn’t do real 32-bit rendering.
Yes, that’s why I asked

Antorian,

Can you please check this and make sure you switch to a 16bit color mode when going fullscreen?

But your problem is a speed problem, right? As long as you can scale all your textures down to 256x256, you can run on Voodoo, albeit slowly. Running slowly is still correct. Ergo, no problem.