you should be able to handle 10,000 no worries without optimization lots of picks and collision. I usualy try to keep within the 30,000 - 40,000 per frame.
Even with 40,000 polys, 8 ODE physics vehicles, sophisticated AI and quite a few brushes my current project will run at 40 - 80 FPS on a 1.2ghz athlon and 32mb geforce2 GTS.
Quite a lot of optimization was done in this instance, both coding and graphics side.
Most of the strain is on the CPU in this instance thanks to the old ODE and a ton of other stuff going on. Your CPU will also determine how many surfaces you can reasonably expect to have in your scene. with a pentium2 400mhz I try and stay between 20 - 50. More than 20 though, and you start to notice slowdown. 1ghz and up you can multiply the number considerably.
My game that currently runs at 40-80 FPS on the P2, on my newer Athlon64 3200+ with a geforce 3 64mb will run at up to 211 FPS.
My current partners athlonXP 2600+ with geforce 6800 hits 300 FPS.
Even with 40,000 polys, 8 ODE physics vehicles, sophisticated AI and quite a few brushes my current project will run at 40 - 80 FPS on a 1.2ghz athlon and 32mb geforce2 GTS.
Quite a lot of optimization was done in this instance, both coding and graphics side.
Most of the strain is on the CPU in this instance thanks to the old ODE and a ton of other stuff going on. Your CPU will also determine how many surfaces you can reasonably expect to have in your scene. with a pentium2 400mhz I try and stay between 20 - 50. More than 20 though, and you start to notice slowdown. 1ghz and up you can multiply the number considerably.
My game that currently runs at 40-80 FPS on the P2, on my newer Athlon64 3200+ with a geforce 3 64mb will run at up to 211 FPS.
My current partners athlonXP 2600+ with geforce 6800 hits 300 FPS.