Time Vs Quality
polycounter lvl 18
Hi, this is my first post on the forums...
As we all know the in the game industry time is money...so where do we stop optimizing??? take the image below
...we can either leave the model with a T-Junction or be neat and clean like the one to the right...
Now do we need to do that? or just leave the T-Junction as it as, as its a minor thing(assuming no one will see it in-game). Also should the models(inorganic, like buildings) be snapped to the grids...
i prefer to make clean model which are snapped to the grid...but there are few people at my work place who argue that we should not be bothered about shuch trivial issues...
so what is your opinion?
As we all know the in the game industry time is money...so where do we stop optimizing??? take the image below
...we can either leave the model with a T-Junction or be neat and clean like the one to the right...
Now do we need to do that? or just leave the T-Junction as it as, as its a minor thing(assuming no one will see it in-game). Also should the models(inorganic, like buildings) be snapped to the grids...
i prefer to make clean model which are snapped to the grid...but there are few people at my work place who argue that we should not be bothered about shuch trivial issues...
so what is your opinion?
Replies
I don't know exactly what you mean by snapping to a grid. Being a slave to a grid isn't necessarily important, but making sure that buildings and props are touching the ground are.
Many times, you're not the only one who's ever going to touch a model. And if what you create isn't clean then it's going to cause problems for others down the road that have to work on what you created. Either that, or some QA tester to going to report a bug that you or someone else is going to have to fix. And it always takes more time to fix problems than to avoid them in the first place.
I always bother. To me, making clean models is not a trivial issue.
I don't know exactly what you mean by snapping to a grid. Being a slave to a grid isn't necessarily important, but making sure that buildings and props are touching the ground are.
Many times, you're not the only one who's ever going to touch a model. And if what you create isn't clean then it's going to cause problems for others down the road that have to work on what you created. Either that, or some QA tester to going to report a bug that you or someone else is going to have to fix. And it always takes more time to fix problems than to avoid them in the first place.
[/ QUOTE ]
What i mean by snap to grid is to have the model aligned in the orthographic viewports. The model on the left is properly aligned and all the vertices are snapped to the grid...while to model on the right is not
I insist on this as it is very frustrating for someone else to work on such models(like urs truely)...i understand that while doing organic modelling one need not and cannot use snapping, but in inorganic modelling why not use snapping as it makes the model nice and clean...
But it also depends on what kind of game you're making. I would most likely keep everything lined up to a certain point, and then move verts around to achieve a more natural look (not having everything perfectly lined up and squared out).
But, to get back to your original point, people that don't take the time to make sure models are clean and neat are just being lazy and inconsiderate, IMO. It really doesn't take that long to implement good modeling practices.
For the allignment thing use the flatten x/y/z tools which Meshtools provides (hmmm....somehow I think that comment is redundant on this site
[/ QUOTE ]
This is also built into Max 7 now.
I always bother. To me, making clean models is not a trivial issue.
I don't know exactly what you mean by snapping to a grid. Being a slave to a grid isn't necessarily important, but making sure that buildings and props are touching the ground are.
Many times, you're not the only one who's ever going to touch a model. And if what you create isn't clean then it's going to cause problems for others down the road that have to work on what you created. Either that, or some QA tester to going to report a bug that you or someone else is going to have to fix. And it always takes more time to fix problems than to avoid them in the first place.
[/ QUOTE ]
I agree 100%. Being a slave to a grid, often gives you a "gravity doesn't matter" look to models. Rooves don't sag alittle on old buildings. Car tires don't squat out a bit where they touch the ground (like real life radials do).
Clean models are good, but you don't need a grid to do so.