Im doing some preformance checks and have hit a irritating problem. I do one draw call with 30000 vertex and about the same nr of triangles (a landscape). I get a nice FPS 100+ if I dont have the object on screen but get a drop to less then 40FPS if i loock right at it. This shuld indicate that the pixelshader is my application bottelneck but it can't be because if I use a pixel shader that use only one instruction to forward a color I get allmost the same FPS. Whats left now is the fixt rasterizer and z-testing things that I can't control so what to do? I get better but not good FPS if I turn z-testing off. What can I be doing wrong? If I use a different objet with just a lot of random triangles in a group that can overlap the problem gets even bigger because of the overdraw. I hope someone understand my problem and have some suggestions of something to try. Im using a 6800 card c++ directx9 tnx

This is one of the shaders I use when the problem occur:

vertexInOut VS1(vertexInOut IN)
{
vertexInOut OUT;
OUT.pos = mul( float4(IN.pos.xyz , 1.0) , matWVP);
OUT.color = IN.color;
return OUT;
}
float4 PS1( vertexInOut IN): COLOR
{
return IN.color;
}

as you can see they dont do mutch at all.
And with only one drawcall and little other overhead I expect to get a FPS over 100


What is IIRC?

And yes the speed goes up if the triangles are out of the viewing frustrum. I cant see how that could indicate a vertex shader bottleneck. The vertexes still have to be transformed for DX to know if thew are in the viewing frustrum or not and to do that it must run the whole VS am I right?

The device is created with:
res 1024x768
windowed
16bit z-buffer
one backbuffer
D3DSWAPEFFECT_COPY
no multisample
no v-sync
D3DFMT_A8R8G8B8
hardware vertex processing