I made this simple demo. It has one quad for floor and 2 quads for sky.(I can send you) It also has few cubes rolling around. Here''s the problem: when I get near the cubes FPS fall from 350 to 120 and if I get in the cubes FPS drops to 90-70. I have VooDoo3 3000 and 566 celeron. I implemented display lists, turned off lighting, blending(cubes are not transparent), texture mapping. I''ve got bare white polygons and FPS don''t change a bit, still 90-70. If cubes stand still is performance hit still visible. But in my demo most of the time cubes intersect(maybe that''s the cause). Only thing that helps is increasing minimum drawing distance, but then cubes and not drawn at all. Please help. I can send you code. Most of it is from NeHe''s Tutorials. konrad83@yahoo.com

Perhaps the performance hit is normal? 90-70 fps sounds like an OK value for your system.

when ure getting closer to the cubes youre filling a lot more pixels and the voodoo3 aint espically known for its high fillrate

http://members.xoom.com/myBollux

Yeah 70-90 if fine FOR Q3!!!! These are simple cubes. It shoulda be 300. And as I said I trned of texture mapping and still the same.

I agree with zedzeek, It sounds like a fill rate problem, especially since the numbers don''t change as you change the textures and lighting. Do you know how many layers of world you are seeing when you are close to a cube? The hardware has to draw, what the sky, the floor, and some number of cubes filling most of the screen.