What will hit the processor the most!
by Greg Smith · in Artist Corner · 10/31/2002 (11:54 pm) · 2 replies
I got a list of things here that I was wondering what will kill the fps the most. In our game, art direction is really important but we are realizing it's at the cost of fps. So I got a laundry list of what we have so far and I was hoping any of ya'll seasoned game gurus can help us out figure where we have to make our sacrifices at.
Our player characters consist of
-Skinned Single Mesh at 3200+ Triangles
-Using a bones rig that consist of 53 bones (std. max bones) and 11 (4 point, 7 spline) controller object
-Texture Map at 512X512 res.
Right off the bat we know the character is poly heavy and are going to make efforts to bring the model down to 2500. Guesses among our group say it is the realtime enveloping. I am thinking the same, but I would hate to see us drop it for a multi-mesh solution.
please help me out here.
Greg
Our player characters consist of
-Skinned Single Mesh at 3200+ Triangles
-Using a bones rig that consist of 53 bones (std. max bones) and 11 (4 point, 7 spline) controller object
-Texture Map at 512X512 res.
Right off the bat we know the character is poly heavy and are going to make efforts to bring the model down to 2500. Guesses among our group say it is the realtime enveloping. I am thinking the same, but I would hate to see us drop it for a multi-mesh solution.
please help me out here.
Greg
About the author
#2
The polycount @ 3000 is a little high but as long as you are a bit more conservative on non-critical objects (tables, chairs, houses, trees, etc) it shouldn't be much of an issue.
Multiple bones... I don't think that this would be an issue at all. If someone else knows if it is I hope that they will respond.
The texture will probably affect your performance the most. You should probably not use more than one 512x512 texture per player object (though you should try to get the texture smaller if you can). For non-player objects the smaller you can get the texture and the more effective that you use the texture, the less it will impact on performance. Texture memory is still a very important issue that a lot of people overlook and it will affect your performance.
Logan
11/01/2002 (7:30 am)
Greg I don't think that you have anything there that is too bad on its own or in a fairly average environment or in average gameply. Below are my comments in regards to your points that you outlined previously:The polycount @ 3000 is a little high but as long as you are a bit more conservative on non-critical objects (tables, chairs, houses, trees, etc) it shouldn't be much of an issue.
Multiple bones... I don't think that this would be an issue at all. If someone else knows if it is I hope that they will respond.
The texture will probably affect your performance the most. You should probably not use more than one 512x512 texture per player object (though you should try to get the texture smaller if you can). For non-player objects the smaller you can get the texture and the more effective that you use the texture, the less it will impact on performance. Texture memory is still a very important issue that a lot of people overlook and it will affect your performance.
Logan
Torque Owner Mz