5 replies to this topic

[rouncer]

I would have done this, its just my direct x 11 sdk didnt even install so I decided to move to java.

[geon]

Technically impressive, but visually... well, it does nothing.

I guess there are better situations in which it could be useful, but the only place on the model above where I can even notice it is on the chest plates, which could have been fixed just as well with only ~10 more polygons.

As it looks in the example, it's just a waste of electricity.

[v71]

Yeah, i am not impressed either,the model, even if hypertessellated didn't loose its 'low poly' feel i think you should work more on curves rather than single triangle tessellation which doesn't contributes anything to the visual impact once you turn off the wireframe.

[imerso]

The way I see it, automatic tesselation is actually quite handy.

The above example is just it, an example, but I agree it is a bad case shown. They could better show that in a building, or a terrain.

Nevertheless, supporting automatic tesselation in hardware, based on distance, is a neat feature, imho.

[rouncer]

Its cause its switching from "normal mapping" to "displacement mapping" and you cant tell much of a difference cause normalmaps fake all the normals anyway why doom3 was
fine...
I guess it just makes the model perfect, it makes more a definite impact if the low poly model is below say 1000 verts, then the displacement map really makes a difference.

Im still interested in displacement mapping, even tho heres a definite example why you dont even need it. :O

Remember theres more types of displacement mapping than just z-shoot-off-normal, you can actually go on all 3 axi too, and its a different way to make a realtime sculpting program.