??ShadowMap???Shader??????

db123

????Copy??GPU Gems I??11??

1. 
   
2. float3 offset_lookup(sampler2D map,
   
3.                      float4 loc,
   
4.                      float2 offset)
   
5. {
   
6. return tex2Dproj(map, float4(loc.xy + offset * texmapscale * loc.w,
   
7.                                loc.z, loc.w));
   
8. }
   
9. We can implement the 16-sample version in a fragment program as follows:
   
10. 
    
11. float sum = 0;
    
12. float x, y;
    
13. 
    
14. for (y = -1.5; y <= 1.5; y += 1.0)
    
15.   for (x = -1.5; x <= 1.5; x += 1.0)
    
16.     sum += offset_lookup(shadowmap, shadowCoord, float2(x, y));
    
17. 
    
18. shadowCoeff = sum / 16.0;
    
19. 
    

复制代码

??????DX?DEMO-ShadowMap:

1. 
   
2. // Pixel is in lit area. Find out if it's
   
3.         // in shadow using 2x2 percentage closest filtering
   
4. 
   
5.         //transform from RT space to texture space.
   
6.         float2 ShadowTexC = 0.5 * vPosLight.xy / vPosLight.w + float2( 0.5, 0.5 );
   
7.         ShadowTexC.y = 1.0f - ShadowTexC.y;
   
8. 
   
9.         // transform to texel space
   
10.         float2 texelpos = SMAP_SIZE * ShadowTexC;
    
11.         
    
12.         // Determine the lerp amounts           
    
13.         float2 lerps = frac( texelpos );
    
14. 
    
15.         //read in bilerp stamp, doing the shadow checks
    
16.         float sourcevals[4];
    
17.         sourcevals[0] = (tex2D( g_samShadow, ShadowTexC ) + SHADOW_EPSILON < vPosLight.z / vPosLight.w)? 0.0f: 1.0f;  
    
18.         sourcevals[1] = (tex2D( g_samShadow, ShadowTexC + float2(1.0/SMAP_SIZE, 0) ) + SHADOW_EPSILON < vPosLight.z / vPosLight.w)? 0.0f: 1.0f;  
    
19.         sourcevals[2] = (tex2D( g_samShadow, ShadowTexC + float2(0, 1.0/SMAP_SIZE) ) + SHADOW_EPSILON < vPosLight.z / vPosLight.w)? 0.0f: 1.0f;  
    
20.         sourcevals[3] = (tex2D( g_samShadow, ShadowTexC + float2(1.0/SMAP_SIZE, 1.0/SMAP_SIZE) ) + SHADOW_EPSILON < vPosLight.z / vPosLight.w)? 0.0f: 1.0f;  
    
21.         
    
22.         // lerp between the shadow values to calculate our light amount
    
23.         float LightAmount = lerp( lerp( sourcevals[0], sourcevals[1], lerps.x ),
    
24.                                   lerp( sourcevals[2], sourcevals[3], lerps.x ),
    
25.                                   lerps.y );
    
26.         // Light it
    
27.         Diffuse = ( saturate( dot( -vLight, normalize( vNormal ) ) ) * LightAmount * ( 1 - g_vLightAmbient ) + g_vLightAmbient )
    
28.                   * g_vMaterial;
    

复制代码

???????tex2D??tex2DProj??????????????????????????????????????????????????????????16???????????????????

???????GPU Gems??11????????

1. 
   
2. offset = (float)(frac(position.xy * 0.5) > 0.25);  // mod
   
3. offset.y += offset.x;  // y ^= x in floating point
   

复制代码

???????????????????
????

1. 
   
2. Figure 11-4 The Sampling Pattern Used for the Four-Sample Version of the Shader
   
3. 
   
4. We can implement the four-sample version as follows:
   
5. 
   
6. offset = (float)(frac(position.xy * 0.5) > 0.25);  // mod
   
7. offset.y += offset.x;  // y ^= x in floating point
   
8. 
   
9.    if (offset.y > 1.1)
   
10.   offset.y = 0;
    
11. shadowCoeff = (offset_lookup(shadowmap, sCoord, offset +
    
12.                              float2(-1.5, 0.5)) +
    
13.                offset_lookup(shadowmap, sCoord, offset +
    
14.                              float2(0.5, 0.5)) +
    
15.                offset_lookup(shadowmap, sCoord, offset +
    
16.                              float2(-1.5, -1.5)) +
    
17.                offset_lookup(shadowmap, sCoord, offset +
    
18.                              float2(0.5, -1.5)) ) * 0.25;
    

复制代码

?????
[em3] [em2]

oz01

??????????????????

db123

oz01: Re:??ShadowMap???Shader??????

??????????????????

???
????????????Texture Addressing Modes >>><<??

Texture Addressing Modes (Direct3D 9)
Your Direct3D application can assign texture coordinates to any vertex of any primitive. For details, see Texture Coordinates (Direct3D 9). Typically, the u- and v-texture coordinates that you assign to a vertex are in the range of 0.0 to 1.0 inclusive. However, by assigning texture coordinates outside that range, you can create certain special texturing effects.

You control what Direct3D does with texture coordinates that are outside the [0.0, 1.0] range by setting the texture addressing mode. For instance, you can have your application set the texture addressing mode so that a texture is tiled across a primitive.

Direct3D enables applications to perform texture wrapping. It is important to note that setting the texture addressing mode to D3DTADDRESS_WRAP is not the same as performing texture wrapping. Setting the texture addressing mode to D3DTADDRESS_WRAP results in multiple copies of the source texture being applied to the current primitive, and enabling texture wrapping changes how the system rasterizes textured polygons. For details, see Texture Wrapping (Direct3D 9).

Enabling texture wrapping effectively makes texture coordinates outside the [0.0, 1.0] range invalid, and the behavior for rasterizing such delinquent texture coordinates is undefined in this case. When texture wrapping is enabled, texture addressing modes are not used. Take care that your application does not specify texture coordinates lower than 0.0 or higher than 1.0 when texture wrapping is enabled.

Setting the Addressing Mode
You can set texture addressing modes for individual texture stages by calling the IDirect3DDevice9::SetSamplerState method. Specify the desired texture stage identifier in the Sampler parameter. Set the Type parameter to D3DSAMP_ADDRESSU, D3DSAMP_ADDRESSV, or D3DSAMP_ADDRESSW values to update the u-, v-, or w-addressing modes individually. The Value parameter determines which mode is being set. This can be any member of the D3DTEXTUREADDRESS enumerated type. To retrieve the current texture address mode for a texture stage, call IDirect3DDevice9::GetSamplerState, using the D3DSAMP_ADDRESSU, D3DSAMP_ADDRESSV, or D3DSAMP_ADDRESSW members of the D3DSAMPLERSTATETYPE enumeration to identify the address mode about which you want information.

Device Limitations
Although the system generally allows texture coordinates outside the range of 0.0 and 1.0, inclusive, hardware limitations often affect how far outside that range texture coordinates can be. A rendering device communicates this limit in the MaxTextureRepeat member of the D3DCAPS9 structure when you retrieve device capabilities. The value in this member describes the full range of texture coordinates allowed by the device. For instance, if this value is 128, then the input texture coordinates must be kept in the range -128.0 to +128.0. Passing vertices with texture coordinates outside this range is invalid. The same restriction applies to the texture coordinates generated as a result of automatic texture coordinate generation and texture coordinate transformations.

The interpretation of MaxTextureRepeat is also affected by the D3DPTEXTURECAPS_TEXREPEATNOTSCALEDBYSIZE capability bit. When this bit is set, the value in the MaxTextureRepeat member is used precisely as described. However, when D3DPTEXTURECAPS_TEXREPEATNOTSCALEDBYSIZE is not set, texture repeating limitations depend on the size of the texture indexed by the texture coordinates. In this case, MaxTextureRepeat must be scaled by the current texture size at the largest level of detail to compute the valid texture coordinate range. For example, given a texture dimension of 32 and MaxTextureRepeat of 512, the actual valid texture coordinate range is 512/32 = 16, so the texture coordinates for this device must be within the range of -16.0 to +16.0.

Additional information about the texture addressing modes is contained in the following topics.

Wrap Texture Address Mode (Direct3D 9)
Mirror Texture Address Mode (Direct3D 9)
Clamp Texture Address Mode (Direct3D 9)
Border Color Texture Address Mode (Direct3D 9)