Capping a circle
polycounter lvl 14
Hi, I've been watching these forums a bit, decided to finally join 
I want to go into game design as a career, and this community seems fantastic!
So, for my first question (and I hope it's not one that'll make me look stupid), I'm wondering the best way to go about capping a circle on a low-poly model. I've read a few different ways people have said to go about it, but I'm not quite sure what the best would be, or if it even matters.
Now, I've done it two ways here that I've read about.
The first here, I've read that it helps with shading issues. When I used to use Blender this was the case, and this eliminated bad shadowing erros for the most part, but I'm not quite sure if 3DS Max has the same issues with shadows.
The second way I've read is better for Tri-Strips, but I've also heard tri-strips are no longer important, so I don't know what information I'm getting is correct :poly105:
So which one would be best to use? Or is there a better way?
Sorry again, if this was a stupid first post, I just couldn't find the answer by searching on here. Thanks very much for helping!
I want to go into game design as a career, and this community seems fantastic!So, for my first question (and I hope it's not one that'll make me look stupid), I'm wondering the best way to go about capping a circle on a low-poly model. I've read a few different ways people have said to go about it, but I'm not quite sure what the best would be, or if it even matters.
Now, I've done it two ways here that I've read about.
The first here, I've read that it helps with shading issues. When I used to use Blender this was the case, and this eliminated bad shadowing erros for the most part, but I'm not quite sure if 3DS Max has the same issues with shadows.
The second way I've read is better for Tri-Strips, but I've also heard tri-strips are no longer important, so I don't know what information I'm getting is correct :poly105:
So which one would be best to use? Or is there a better way?
Sorry again, if this was a stupid first post, I just couldn't find the answer by searching on here. Thanks very much for helping!
Replies
However the way I do it is to actually have a vertex in the middle of the circle and just connect up all the circle vertices to that center vertex (like a pizza in slices). It's only one triangle more than your 2nd solution, and it smooths much more regularly, which is good for normal-mapping. It also makes it easier to UV-map in more ways.
EDIT: Ya... I'm tired. I just remembered how to do it much easier. Sorry for the time wasting :P Thank you very much for the help though! Much appreciated, and now I don't need to wait for my posts to be checked by an admin.
In terms of putting the vert there, collapse is your friend. If I've already been using bevel or extrude to get it there, I'll do it that way. But if I am trying to cap a hole, I'll select the loop, scale it down holding shift, and then collapse. Holding shift while moving edges just extrudes those edges for you.
MoP, how do you get these to subdivide without getting the stretching and bumps like you see in subdivided cylinders?
Usually you delete every second edge to make quads out of them all. He was talking about leaving it all tris on a lowpoly (hence the talk of normals and UVs).
Supporting edges
I still get some tearing with turbosmooth... +1 for meshsmoothing ha
It may smooth better but it's less efficient for tri-stripping.
with how many polys we can push I'd rather a model light better than look worse but be slightly more efficient. With the # of triangles we can push being ridiculously high, I don't think there is much point in sacrificing visual fidelity for a near-zero performance gain.
To cap a cylinder with a vert for a fan, rather than extrude for 0.0 on the cap face, then collapsing, if you use the inset tool and collapse it doesn't require you to zero-out your extrude tool, which is useful for saving a whole click
edit: obviously this is for modern games, not DS/PSP/iPhone-spec work
Yeah, but in terms of normal-mapped in-game next-gen assets, tri-stripping is probably the least of your worries.
In fact I've never been told by anyone hell-bent on optimising rendering pipelines to worry about tri-stripping before (including graphics programmers, technical directors, art leads etc.).
And anyway, even if it did make a difference, I'd much rather have nicer smoothing there for more reliable normal-maps and better options for UV mapping other than a planar cap, than worry about the performance hit that not triangle-stripping a whole 10 triangles is going to cause...
Guys, just collapse to center and move on!
That's done with indexed arrays now. All the vertex data is dumped into an array, and the index list just tells the gpu which 3 make each triangle. The alternative is just dumping the info for every polygon into the array, duplicating data.