Jump to content
  • Advertisement
Sign in to follow this  
Balaam

2D in 3D Texture woe with C# (pictures! yay!)[Solved .. I think]

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

I'm aware of the texel thing and the article over on MSDN but I still can't seem to get everything to go right. I'm hoping some one here will be able to put me out of my misery. I'm using quads as 2D tiles - I can plot them no problem but when I move around the textures get screwed up. Here's what it looks like at the start: This is my debug tile, all the sides are different colours and the middle has a nice gradient, everything is okay. Now I moved up or down and a bit annnnddd... The pink line comes from the space surrounding my texture in the main texture file. Why grahhhh? Here's the code: Problem.zip(Visual Studio 2005) It's very light - I've written it especially just to try and sort out this problem. I would love someone to be able to tell me what changes I would need to make. I'm not in love with the current aspect ratio I'm willing to change :D

The likely culprits

The actually quad size which is currently like this:
     verts[TopRight].Position = new Vector3(0.25f - 0.003f, 0 - 0.003f, 1f);
     verts[BottomRight].Position = new Vector3(0.25f - 0.003f, -0.25f - 0.003f, 1f);
     verts[BottomLeft].Position = new Vector3(0 - 0.003f, -0.25f - 0.003f, 1f);
     verts[TopLeft].Position = new Vector3(0 -0.003f, 0-0.003f, 1f);
        
The 0.003f business is making my texels pixel specific or so I hope.

The camera setup

device.Transform.Projection = Matrix.OrthoLH(5.0f,
                5.0f, 0, 1.0f);
Or sometimes I have it like this
device.Transform.Projection = Matrix.OrthoLH(5f,
			3.75f, 0.0f, 1.0f);
Making my tiles nice and not squashed - either way I'm stuck with the same problem. Please help me and my hair. [Edited by - Balaam on December 13, 2005 2:03:53 AM]

Share this post


Link to post
Share on other sites
Advertisement
With help I've managed to remove the pink lines by clamping the texture.

I added this code on setting up the device.


device.SamplerState[0].AddressU = TextureAddress.Clamp;
device.SamplerState[0].AddressV = TextureAddress.Clamp;
device.SamplerState[0].AddressW = TextureAddress.Clamp;


But when moving the border lines of my tile still thicken to two pixels when they should be one and sometimes disappear entirely.



There should be one pixel red line at the bottom of these tiles.

Share this post


Link to post
Share on other sites
If you are trying to use projection coords its possible to get this kind of artifacts. To avoid getting this use TransFormed lit vertices so you can use real screen coords.

Luck!
Guimo

Share this post


Link to post
Share on other sites
I'd really rather avoid that approach unless there's really no other option.

In transformed coords all the vertices have screen locations - so as far as understand it I'd have to modify the vertices each frame to render the same tile at different places.

Share this post


Link to post
Share on other sites
Okay I think I've managed to fix this. So I'll write up what I did just in case anyone else finds themself in the same position.

My quads where quite small like 0.5 and I was moving the camera over them by a very small increment. I'm guessing the problem was rounding error. So to solve this I increased the camera movement step, increased the quad size to a few points squared and pushed up the resolution. This seemed to make all the bad things go away :D

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!