Future Of FFP Effects?

I have heard that shaders are the future and that ffp will me obsolete with
DirectX 10, does this mean not supported? Should I be thinking of shaders
insted of FFP if I want my game to be playable in five years?

While it's always a plus to learn shaders, I wouldn't worry about the FFP issue. I believe Microsoft said that both Directx9 and Directx10 will be available at the same time on there new OS(that way most of the old programs are still supported). Unless your using an Directx10 based engine, there shouldn't be any cause for concern.

BTW - Where did you hear that FFP will no longer be supported?

I heard it on the forum over at gamedev.net. Maybe theres no truth in it?
I have tried vs/ps before but they seem to lower the framerate compared to
a comparable effect with FFP. This might be because of my card however (Nvidia GeForce Fx 5600).

For me, FFP is a shader... it's written in a shader language, it just doesn't need ps/vs. And it wouldn't be wise anyway not to support FFP any longer o_O

umm..
FFP code has nothing to do with shaders. It's certainly not written in a "shader language". It's written in a simplified form of Direct 3D code.. If you are talking about the "FX" format, it's just a simple way to set things like texture stage states and other variables called types.

For instance, in your FX file when you want to set the srcblend mode you just use:
srcblend=one;

in D3D C++ code this same command would look something like this:
d3ddevice->SetRenderState( D3DRS_SRCBLEND, D3DBLEND_ONE);

So the same applies to all the FF code you may see in effects files. It's just a simple way of setting d3d variables, called types.

Direct 3D has no internal distinction between regular D3D code and so called fixed-function effects...this is maybe difficult to explain, but think of the FF style "effects" as merely configuring hardware texture blending attributes.. this mean the hardware has specific hardwired functions it performs on textures-- you can tell it which ones to use in what order, but you cant program them. I believe on newer cards the FFP is actually emulated in the shader units, so maybe they dont even have a FFP (not sure about this, but it will be this way soon for sure).

What Fixed Function code cannot do is modify anything on the purely vertex or pixel level once something has been sent into the rendering pipeline (except in certain specif cases like per pixel dot3 bump mapping..which is a fixed function that does affect pixels data...but it cant take vertex data and interpolate it to pixels).

Direct 3D gives a lot of useful funtions for setting blend modes, etc, that dont need the "programmability" of shaders...so of course there will always be fixed functions. D3D is an API, a set of functons that makes accessing hardware easy. There will always be a need for standard fast functions for specfic task, like creating a texture from a file, or blending a pixel over another pixel in a set way. The API is NOT the hardware.. so ultimately why should care how it does what it does?

Matt, so FFP is sort of a DX script that, lacking hardware support, is translated into a shader for use?

That would explain the big fps drop I see when I use vs/ps shaders! Perhaps my nvidia has ffp hardware support! But with the newer cards, there should be no noticable difference in the speed (they will both be slow)?

My concern is that a game development cycle that takes years, must be forward looking tecnologically. So perhaps I should use shaders instead of FFP, since you can do more and it will probably outlast FFP?

Quote:

---

Matt, so FFP is sort of a DX script that, lacking hardware support, is translated into a shader for use?

---

no, its more a kind of internal switches inside your gpu, while shaders let you create your own functions