Ok here’s my problem.
I’ve made an arch here and In order to do this I had to create a lot of edges.
I had to cut the object from top to bottom in order to keep everything in quads and still make the arch.
Am I modelling correctly in terms of creating for game design? Or should I be deleting those edges on the face and disregarding quads?
hey nogert
you have to many edges going up
you need to collapse all the ones that are not contributing to the shape
right after the arch you should collapse all those edges you should only have 1 edge out of all thosecollapsed arch ones and you should weld it to another vertice on the side
keep it up
Ah right, does it not matter than the arch edges will turn into tri’s rather than quads?
Thanks for the help.
no but you have to watch out for smoothing errors that can be caused by triangles
and longers triangles make longer smoothing errors
sometimes when you see a funky error from a tri try connecting it to the other side see if it helps
its a balance between poly budget,clean modeling,and outline shape
and if you dont se the back delete the poly there
Hello Robert,
What you are modeling there is a type of hard surface sculpt.
You won’t ever be smoothing it.
Any fine detail will be added in the normal map texture.
With that said, don’t worry about getting rid of the extra edge loops or keeping quads in this case. Just take all those edges from the arch straight to the corner.
I’ve done a quick mock up of your model in Maya to you show you what I mean.
Hope this helps. 
lookin better 
I would go ahead and take out those last two edge loops going up the center unless your going to use them for an extrude they are just wasted polys
There is no need to maintain quads for in-game meshes. The reason why you sometimes want to use quads is to allow for clean subdivision, either for SubD rendering or for sculpting. Games don’t use SubDs so that’s not an issue. If you’re planning on sculpting details in ZBrush or Mudbox, you’ll want to create two version of the mesh, one high-resolution with quads, and the other one lower resolution with triangles.
N-gons are still a problem. The reason why it doesn’t matter if you have tris or quads is that the game engine is going to split everything into triangles anyways. Triangulating n-gons is a bit more tricky than triangulating quads, so some software doesn’t know how to handle it. xNormal, for instance, will just flat out not allow n-gons. However, you can just triangulate any n-gons in your modeling package and you’re good to go.
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
