drogoth232
Smash Lord
- Joined
- Nov 28, 2011
- Messages
- 1,072
Thanks to BlackJax for most (if not all) of this information.
When importing into the newest brawlbox, when you see the MDL0 of the character (what you replace for the new character), you should see some values on the top right window. Facepoint count and Node count are the important ones.
Node count for brawl characters are around 300, although I have seen 600 (that might have been a skin wrapped character, though). Node count is essentially how accurate your skinning is. The more accurate (all the weights have like 0.0000000001 difference), the higher the value. The less accurate, the lower the value. When importing and using Tristripper, it's weight precision. A value of 0.01 should be fine, although you can play around with it and check your results out to see if a higher value would be better (with a value of 0.01, that means that values that are 0.01 apart are considered the same).
Node count can inflate when using the Blend tool a lot while rigging. Keep that in mind.
Facepoint count is the more obvious one. It's a value of all the Faces, Verts, UV Points, and some convoluted stuff that equates to the final value. In a vacuum, a Facepoint count of 17,000 will be around when a model will lag with 4 on screen on Skyloft (iirc). It is important to remember that the Facepoint count only takes into account models that are on screen. So if the model has expressions and has visibility bones set up properly, they won't affect the lag until they show up (but if you did set visibility bones up properly, there won't be a problem at all). This can be seen with Wolf and how his Facepoint count is at 22k, but he doesn't lag (because visibility bones are set up properly).
NOTE: High polycount = High Facepoint count
Low Facepoint count != Low Polycount
Just because you shaved off 9000 faces, doesn't mean you'll see that much of a reduction of Facepoints. But the best way to reduce Facepoints is by reducing faces.
I have no idea what the formula for calculating it is, but this is what I've found out from asking people and a lot of testing.
Hope you find this information useful.
Useful stuff:
Uber Vert Count:
I just checked out uber vert count (a simple google search will do wonders), it's accurate on the cube, but not on other objects (calculated uvc was at 970 while in bbox it was around 2k without being able to optimize the facecount any further). I might have been wrong, so I'm going to put it here anyways.
The link to it is here: http://www.ericchadwick.com/examples/files/HaywoodTools-UberVertCount.mcr
What you'll have to do is copy the whole page, open max and go to maxscript (at the top), go to new script. Paste it in, and go to file->save as and call it whatever you want (I called it uber vert count because duh). After saving, go to run and find your script and open it up. Then go to customize -> customize ui (or something similar to that), there should be a giant table that you can scroll down in. Go all the way down to uber vert count, assign a hotkey to it (make sure to click assign), and then hit that hotkey anywhere in Max.
It'll open a window up, upon which you have to select a single object (this is important, it is a single object. Not multiple) and then click on "Do it". It'll calculate the amount (which can take a while depending on how complicated your object is) and then output a result within the same window. Tadaaaa!
Beautiful, Yet Friendly Pt 2:
I absolutely recommend "Beautiful, yet friendly", specifically part 2 which is here: http://www.ericchadwick.com/examples/provost/byf2.html
I didn't find this myself at all (although I did just google it now), blerb brought this to my attention a few days ago and it's pretty great to say the least. A good read (albeit a bit confusing for the early starter).
Read the other parts too, if you have the time to do so.
When importing into the newest brawlbox, when you see the MDL0 of the character (what you replace for the new character), you should see some values on the top right window. Facepoint count and Node count are the important ones.
Node count for brawl characters are around 300, although I have seen 600 (that might have been a skin wrapped character, though). Node count is essentially how accurate your skinning is. The more accurate (all the weights have like 0.0000000001 difference), the higher the value. The less accurate, the lower the value. When importing and using Tristripper, it's weight precision. A value of 0.01 should be fine, although you can play around with it and check your results out to see if a higher value would be better (with a value of 0.01, that means that values that are 0.01 apart are considered the same).
Node count can inflate when using the Blend tool a lot while rigging. Keep that in mind.
Facepoint count is the more obvious one. It's a value of all the Faces, Verts, UV Points, and some convoluted stuff that equates to the final value. In a vacuum, a Facepoint count of 17,000 will be around when a model will lag with 4 on screen on Skyloft (iirc). It is important to remember that the Facepoint count only takes into account models that are on screen. So if the model has expressions and has visibility bones set up properly, they won't affect the lag until they show up (but if you did set visibility bones up properly, there won't be a problem at all). This can be seen with Wolf and how his Facepoint count is at 22k, but he doesn't lag (because visibility bones are set up properly).
NOTE: High polycount = High Facepoint count
Low Facepoint count != Low Polycount
Just because you shaved off 9000 faces, doesn't mean you'll see that much of a reduction of Facepoints. But the best way to reduce Facepoints is by reducing faces.
I have no idea what the formula for calculating it is, but this is what I've found out from asking people and a lot of testing.
Hope you find this information useful.
Useful stuff:
Uber Vert Count:
I just checked out uber vert count (a simple google search will do wonders), it's accurate on the cube, but not on other objects (calculated uvc was at 970 while in bbox it was around 2k without being able to optimize the facecount any further). I might have been wrong, so I'm going to put it here anyways.
The link to it is here: http://www.ericchadwick.com/examples/files/HaywoodTools-UberVertCount.mcr
What you'll have to do is copy the whole page, open max and go to maxscript (at the top), go to new script. Paste it in, and go to file->save as and call it whatever you want (I called it uber vert count because duh). After saving, go to run and find your script and open it up. Then go to customize -> customize ui (or something similar to that), there should be a giant table that you can scroll down in. Go all the way down to uber vert count, assign a hotkey to it (make sure to click assign), and then hit that hotkey anywhere in Max.
It'll open a window up, upon which you have to select a single object (this is important, it is a single object. Not multiple) and then click on "Do it". It'll calculate the amount (which can take a while depending on how complicated your object is) and then output a result within the same window. Tadaaaa!
Beautiful, Yet Friendly Pt 2:
I absolutely recommend "Beautiful, yet friendly", specifically part 2 which is here: http://www.ericchadwick.com/examples/provost/byf2.html
I didn't find this myself at all (although I did just google it now), blerb brought this to my attention a few days ago and it's pretty great to say the least. A good read (albeit a bit confusing for the early starter).
Read the other parts too, if you have the time to do so.
Last edited: