Sign in to follow this  

2d textured quads leaving trails

This topic is 4277 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

in my program i have a vb full of textured polygons that represent my map and i have another vb used for characters that holds a textured quad. when everything is still all is well, but when you move the screen around, everything leaves a little ghost on the tile behind it. for example: with all objects moving to the right, a red square leaves a dark red "ghost"(a couple pixels wide) behind it on the green square to its left until you stop moving, then it goes away. i have messed around alot with the presentation paramters, and no matter which i choose i get the same result. very stumped and can't even seem to find any other messages on the forum with the same problem so i thought i'd ask myself thanks for the help, let me know if you need more info daglamier

Share this post


Link to post
Share on other sites
Do you clear the backbuffer before rendering every frame?
Haven't you forgot the D3DCLEAR_TARGET Flag?

a sreenshot could help...

[Edited by - Kambiz on April 1, 2006 4:46:59 PM]

Share this post


Link to post
Share on other sites
What is the D3DPRESENT_PARAMETERS::PresentationInterval you are using? Do you have the same problem when using D3DPRESENT_INTERVAL_ONE?
How many backbuffers do you have?

Share this post


Link to post
Share on other sites
currently using 2 backbuffers with:
d3dpp.BackBufferCount = 2;
d3dpp.Windowed = TRUE;
d3dpp.SwapEffect = D3DSWAPEFFECT_FLIP;
d3dpp.PresentationInterval = D3DPRESENT_INTERVAL_ONE;

have also tried D3DPRESENT_INTERVAL_IMMEDIATE and get the same problem.

daglamier

Share this post


Link to post
Share on other sites
hmm, this does sound like a tearing issue to me... especially if it doesn't show up when you do a screenshot.

What have you got your drivers set up for? Make sure that VSYNC is set to "application preference" or "always on" - drivers are notorious for ignoring the values that us programmers request when creating devices.

Also, some drivers (and I think also in some SLI configs) you can set up extended render-ahead buffers that introduce latency into the final image. That combined with high frame rates and/or refresh rates can introduce odd ghosting/tearing/blurring effects..

hth
Jack

Share this post


Link to post
Share on other sites
Just tried my code on a second computer and it doesn't seem to have the problem at all. So it appears to be hardware based(probably vid drivers). Though I have heard some problems with lcd monitors, maybe there is something there i should fix...

The comp it works on has a crt and the one it doesn't has an lcd. Will drivers likely fix it or will there be something with the lcd monitor?

daglamier

Share this post


Link to post
Share on other sites
To me it sounds like a trait common to LCD monitors. They're generally slower than CRT and do leave 'trails'. It's been the reason why I haven't purchased an LCD monitor previously for games and such.

Share this post


Link to post
Share on other sites

This topic is 4277 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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this