About the unsupported error.. i dont know why it doesnt work on a geforce 3.. maybe it doesnt support environmental bumpmapping..
its a not a shader btw its a fixed function texture effect

See I told you I was clueless. Anyway, I wrote an action that assigns "mat_water". That is how you set it up correct? As far the environment mapping, I can get that to work using a different script.

TFactor is a DWORD value, not a texture. Maybe that's the problem.

maybe the geforce3 does only support 2 texture stages in the fixed function pipeline? that would explain it... jcl added the number of texture stages to this table -> http://conitecserver.com/wiki/index.php/ShaderSupportOverview it's strange though that 4 stages can be used with pixel shaders on a geforce3.

@matt: where do you set up bumpenvmat? isn't it needed? and why isn't it necessary to convert the bumpmap to a uv-offset map? could you post a screenshot or a demo of that effect?

Yes it could be the geforece 3 dosent have 3 stages.. in this case you will need a 2 stage fallback.. i would then forego the first stage and just use the last two.. that way you will still have the environment bump mapping.

I dont really know what the purpose of bumpenvmat is.. it seems to work ok without setting it up...when i do put it in it doesnt seem to work correctly..
maybe someone can figure it out?

Yeah you probably should convert the the bump map to a normal map.. i just forgot

For some reason when I use the code that Taros posted it works. Looks a bit funky but both the bump and the env mapping show up.

however this looks totally cool. using different textures is a loot of fun. thx for this

Could someone please make a screenshot?

@Ello:
how would the code have to be changed to convert it into a two-passes-technique?

JOEY.

GeForce 4MX only supports two stages, so would anybody who knows explain how to transform this code into a two-passes-effect? That would be very nice!

Or isn't there anyone who knows how to do it?

JOEY.