Memory Hit of Triple Buffering

[Simon F]

I actually enjoy tripple buffering and vsync on but hey i'm wierd so don't mind me

But that's the whole point. Triple buffering allows you to have vsync on and still render at full* efficiency.

The only downsides are the increased memory usage (negligible these days) and that the framerate may jump a little from time to time (but then you are just as likely to get that from other factors, e.g., texture uploads or extra translucency from explosions.)



Simon

*Assuming that the refresh rate is usually higher than the HW's rendering rate.

 

[jvd]

I know mr F . I use it often with ati's temporal aa . Works very nice.

 

[Simon F]

I use it often with ati's temporal aa

I presume you mean "alternating sampling pattern" AA.

 

[Quitch]

Thanks all, the common view seems to be that the memory hit isn't really worth worrying about and that's all I needed to know. Cheers

 

[jvd]

I use it often with ati's temporal aa

I presume you mean "alternating sampling pattern" AA.

No no . I use temporal smooth vision 2.1 hehehe it works very nice. Don't care if they all it hot dog vision. then end effect is positive

 

[MistaPi]

Is it possible to have a "force tripple buffering" option for D3D in the drivers or is this up to the game developers?

 

[Xmas]

Drivers could force just about anything, but I wouldn't expect such an option in any driver soon.

 

[Quitch]

Isn't that against the DirectX spec?

 

[Xmas]

You can force AA and AF, too, although DX gives the developer full control over it (just like with swap chains).

 

[Quitch]

Yeah, but I thought I read in a topic, something along the lines of "Why can I force Triple Buffering in OpenGL but not Direct3D in Catalyst" that it was because this was a violation of the spec.

Maybe I'm just making this up