GraphicsDevice.Clear(Color.CornflowerBlue);

            // TODO: Add your drawing code here
            spriteBatch.Begin(SpriteBlendMode.AlphaBlend, SpriteSortMode.Immediate, SaveStateMode.None);
            spriteBatch.GraphicsDevice.SamplerStates[0].AddressU = TextureAddressMode.Wrap;
            spriteBatch.GraphicsDevice.SamplerStates[0].AddressV = TextureAddressMode.Wrap;

Quote:How does it look with TextureAddressMode.Mirror? Does it still clamp?

Quote:That aside, the art looks absolutely wonderful! Especially on the tv set.

Quote:Check the caps for your graphics card - http://msdn.microsoft.com/en-us/library/microsoft.xna.framework.graphics.graphicsdevicecapabilities.maxtexturerepeat.aspx is probably the most important one.

I think almost every card supports wrap mode.

Quote:It may also help to use the debug directx runtimes on the PC and see if you get any error messages.

Quote:What size are your textures? Are they non-power of 2? If so, does your card have the D3DPTEXTURECAPS_NONPOW2CONDITIONAL cap bit set? (This looks like exactly what happened when I tried a non-power of 2 texture on my ATI X300)

[5060] Direct3D9: (WARN) :Ignoring redundant SetRenderState - 24 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 5 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 6 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 7 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 8 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 9 [5060] 

Quote:Original post by Whogie
Ah, I see now. DebugView is quickly filling my log with stuff like:

[5060] Direct3D9: (WARN) :Ignoring redundant SetRenderState - 24 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 5 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 6 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 7 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 8 [5060] [5060] Direct3D9: (WARN) :Ignoring redundant SetSamplerState. Sampler: 0, State: 9 [5060] 

Calling it redundant is a little surprising...

Quote:Original post by Whogie
GraphicsDevice.GraphicsDeviceCapabilities.TextureCaps.SupportsNonPower2Conditional
is true.

Does this mean that I could potentially avoid resizing my textures as a workaround?

Quote:
D3DPTEXTURECAPS_NONPOW2CONDITIONAL
D3DPTEXTURECAPS_POW2 is also set, conditionally supports the use of 2D textures with dimensions that are not powers of two. A device that exposes this capability can use such a texture if all of the following requirements are met.

• The texture addressing mode for the texture stage is set to D3DTADDRESS_CLAMP.
  
• Texture wrapping for the texture stage is disabled (D3DRS_WRAP n set to 0).
  
• Mipmapping is not in use (use magnification filter only).
  
• Texture formats must not be D3DFMT_DXT1 through D3DFMT_DXT5.
  

If this flag is not set, and D3DPTEXTURECAPS_POW2 is also not set, then unconditional support is provided for 2D textures with dimensions that are not powers of two.

A texture that is not a power of two cannot be set at a stage that will be read based on a shader computation (such as the bem - ps and texm3x3 - ps instructions in pixel shaders versions 1_0 to 1_3). For example, these textures can be used to store bumps that will be fed into texture reads, but not the environment maps that are used in texbem - ps, texbeml - ps, and texm3x3spec - ps. This means that a texture with dimensions that are not powers of two cannot be addressed or sampled using texture coordinates computed within the shader. This type of operation is known as a dependent read and cannot be performed on these types of textures.