Dx11 a performance killer?

Don't know the in's and outs of it but the same was said of dx9 and dx10, the problem is that if something runs more efficiently but you make it do more, it will still run worse if you get what i mean.

Oh and FFS it is lose, you lose loads of fps, spell it as you say it. I don't care what first language you speak.

^^ But it DOES prove my earlier thoughts that Tesselation would hinder preformance when used. No matter how efficent you make the process, Tesselation = more work, and no specilized hardware can overcome that one fact.

Granted, in general use, this loss will be minimal, as I think larger implementations of tesselation (could potentially work on all surfaces, like AA) will be years down the line, when we have much more powerful hardware.

For the next year or so, DX11 + Tesselation will probably benchmark slightly (<5 FPS at MOST) slower then DX10 on average. That would be my best guess from what I've seen so far...

No, to render the same amount as we see now, TS is actually less costly, but thats again just like DX10. It offers more accurate things, where we cheated before, and TS is more like DX10.1, where we actually get more for the same thing, but, unlike DX10.1, it can also offer much better visuals and savings, depending on the game/dev

Tesselation doesn't hurt performance in and of itself, what hurts performance is that it creates vastly more triangles to render.

If you render 10,000 triangles, some of them tesselated, it takes the same amount of time (actually, it's faster) as it takes to render those same 10,000 triangles if all were built into the original model. Tesselation isn't what's hurting performance, it's that it's adding 5,000 more triangles to the mix.

But you see Jaydee, Tesselation doesn't do the same amount of work; it needs more Triangles to achieve the effect, so even though its faster on a per-triangle basis, its slower overall. So yes, technically, the process itself is faster, but the result will almost always be slower.