#### Archived

This topic is now archived and is closed to further replies.

# Original BumpMapping Method

This topic is 5372 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Well first of all Id say that this is not the best method in the world, nor the finest, but Its probably the fastest . You can see the effect here-> http://www.geocities.com/cippyboy_7/bump_test.jpg Its not the best texture in the world but there it goes. A few tech docs ->Uses only 1 pass with Multitexturing, actually its the same texture twice ->Its per-vertex although the texcoords show some nice blending(under the light it looks somewhat flat) ->Its totally software so it doesnt uses any extension besides that multitexturing, so it would work any card . I know it may not even be accurate but... I just wanted to make something original...

##### Share on other sites
Looks like the good old emboss bump mapping effect to me. How is that different ? My Vaudoo2 was able to do that.

Y.

##### Share on other sites
Well to tell the truth, what I have is a multitextured quad with the glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE,GL_BLEND);
and some light-texcoord calculations...

I noticed that the 2 textures act very interesting, 1 is something like a base color map and the other like an alpha map, and if I manually move it its only made of white and black giving the bump edges white/black colors. The blend is that nice because its texcoord based and if the light is in the middle(like in the pic) it looks flat underneath and strechted to the 4 texcoords .
I dont know if anyone ever came up with something like this but I did this on my own, no code inspiration whatsoever ...
I also know that the eye-candy BumpMapping is made using that dot3 extension, so on older cards/non-Nvidia cars might not work at all...

The struggle from my case is to find out how to modify the texcoords acording to the angle of the plane/triangle, because light x,y,z may not be the x,y of the texture so... I still need to work on that...

##### Share on other sites
The ARB_texture_env_dot3 extension is supported perfectly on every nVidia card of the Geforce 256 range and above.

Besides, if you''re wanting to support cards that are lower spec than that, then forget bumpmapping on those cards. Emboss looks terrible, and there really isn''t any point in doing it on a TNT/2.

You have to remember that you''re unique, just like everybody else.

##### Share on other sites
1)Well.. Nvidia is down... how about ATI and 3Dlabs ?
2)This stuff might be faster than anything because its just plain multitexturing .. is the normal dot3 bumpmapping as fast as this ?

My method must be worth while

##### Share on other sites
NVidia is down? I think not.

Dot3 is just as fast as another texture environment function.

I still don''t know why you''re messing with emboss. If you''re using anything above a Geforce 2, then just use Dot3, it''s FAR superior.

You have to remember that you''re unique, just like everybody else.

##### Share on other sites
I only meant that NVidia was out of my target list... so now I tryed aiming at ATI users and other no-one knows cards

Is this emboss texturing that Im doing ? I dont think so because it messes the texture color making it not so usable...
Anyways Ill drop it here and get that per-pixel-bump which is... fast ?

##### Share on other sites
Dot3 has been available on ATI and Matrox cards for ages. If you're targetting a T&L card, it likely has dot3.

[edited by - Ysaneya on December 1, 2003 7:44:22 AM]

1. 1
2. 2
frob
16
3. 3
4. 4
5. 5
Rutin
10

• 19
• 13
• 14
• 76
• 22
• ### Forum Statistics

• Total Topics
632138
• Total Posts
3004359

×