What do you mean by flickering? Is only the single-pixel line flickering, or the whole screen?

How do you "refresh display every 100 ms using a single backbuffer"? Are you clearing the buffer before drawing to it again?

What happens if you take a screenshot with PrintScreen? Does it look correct or does it have any artifacts on it?

Are you forcing VSYNC off via your driver and/or application (using D3DPRESENT_INTERVAL_IMMEDIATE when creating your device)? Disabling VSYNC can introduce tearing which may well be what you're describing.

Alternatively, if you're hitting aliasing due to rasterization rules you might want to try enabling MSAA if your hardware supports it. Whilst this isn't necessarily a solution it might well allow you to isolate the cause of the problem - as the name suggests, MSAA should reduce/eliminate aliasing errors [smile]

Finally, have you tried running it against the reference rasterizer? When getting odd results its always a good idea to verify it isn't your hardware/drivers that are the problem...

hth
Jack

This is because the present is not synced to the vertical retrace. The only way to fix this for sure is to run in fullscreen mode, with a present interval that allows for vsync.

You can, perhaps, sit in a tight loop checking GetRasterStatus() (or whatever the device scanline return function is called), and calling Present() when it approaches 80% of max, but that's a weak hack at best, and will not work right on all hardware/display combinations.

Quote:Original post by tnarol
Yes, my application is windowed and I'm using D3DPRESENT_INTERVAL_IMMEDIATE. I tryed changing this to D3DPRESENT_INTERVAL_ONE but it doesn't change anything. What else can I do if I don't want to run fullscreen ?

The values set for your presentation parameters don't tend to have any guarantee. VSYNC in particular tends to get overridden by some drivers (e.g. mine have "always off", "always on" or "application preference" options). Could be worth checking the properties for your device - force it on or make sure that the application has the ability to decide.

hth
Jack

'Vertical Sync' is often abbreviated to VSYNC. Try changing that.

hth
Jack

Please, try to describe the effect you are experiencing. By flickering do you mean that the line does not move 'smoothly', that is, it seems to disappear and reappear on the next pixel, or that it seems to be 'broken' (one piece of the line moves to the next position while the rest stays behind).

If it is the first effect, make sure you are moving the line a single pixel at a time. If you move it, say, by a fraction of a pixel every frame, you will encounter this behavior since the line cannot be represented when it lies between two pixels.

Moving by a whole pixel (which means making your program resolution dependent) will eliminate this. Otherwise, setting a higher resolution, or enabling supersampling antialiasing will lessen the effect (unfortuantely your card does not support supersampling aa).

If it is the second effect, you can try matching the update frequency to a fraction of the monitor's vertical refresh frequency. If your monitor updates at 85 Hz, that is every 11.76 msec, updating the line every 100 msec will result in visual 'tearing', since the update will fall between two screen refreshes. Try altering your program to update every 117.6 msec (although it is difficult to time so precisely). Vsyncing will effectively have the same effect, but it is _not_ possible to vsync when your program runs in a window (at least I've never encountered a driver that could work this kind of magic).

Note that the second kind of flickering never appears on TFTs, since they refresh the whole picture at once.