@alexander: as far as i know you have experience with direct3d programming. do you get such an effect to work with a simple direct3d application? ...maybe there is something wrong within a6?
@ventilator: Thanks for posting the cube map code.
Okay... what I have gathered this far is that there is a problem with some cards, maybe mainly GeForce, doing EMBM AND projected vertices at the same time.
Now what??? I have some ideas.... will have to work them out later tonight. 1). One option is to translate to vertex/pixelshader instructions. 2) Could also do a combo FFP and Vertexshader thing.
Here's the thing: If this demo did not run on your card. Run the DirectX SDK BumpWater.Exe sample and see what it tells you. It tells me that it's running in the fixed-function pipe on my card. If it tells you it's running with a vertexshader, then we have a direction to go. *Please report* what you find here. I want to translate things and ultimatley have adequate fallback techniques.
For those of us that like to tinker.... the BumpWater.Cpp is going to be our friend here.
i tried it on a radeon 8500. there it works... but that doesn't help me much!
@steempipe: if you use a projection texture you could try to render an inverted camera view to the bitmap you use for that. i think you would have a realistic reflection of the level then...
Correct, there should be (3) bodies of water. Are you seeing the one if you walk to the right? I am curious as to which effect file you are seeing.
@pocorev: Man, that is worse than just seeing black! Can't even begin to speculate on that one.
Looks like~ TextureTransformFlags[1] = count3 | projected; ~ is out of the question for most cards. Think I go out, cut the grass, and ponder this for awhile.
128MB Radeon 9800. BTW - Isn't there supposed to be 3 bodies of water? Thanks. 