tool error

an emu · Post by **an emu** » Sat Mar 05, 2005 4:10 pm

no clue what that means...

SunnySharma · Post by **SunnySharma** » Sat Mar 05, 2005 9:09 pm

too high poly I guess

an emu · Post by **an emu** » Sat Mar 05, 2005 9:26 pm

ya it is reaaaaaaaaly high poly cause its a model downloaded from a site
i cant even say how high poly it is more than most maps
what should it be?

sureshot2 · Post by **sureshot2** » Sat Mar 05, 2005 9:28 pm

like 1200, to 2000

an emu · Post by **an emu** » Sat Mar 05, 2005 11:58 pm

is 1200-2000 even possible! the pelican is like 21,000 according to the gbx model

sureshot2 · Post by **sureshot2** » Sun Mar 06, 2005 10:04 am

well,do u want it to run like crap or no.

an emu · Post by **an emu** » Sun Mar 06, 2005 10:28 am

i want TONS of lag u know like u get on zanzibar with 16 ppl only worse....
(being sarcastic)
but ya i fixed this error, managed to get the polys down to 20,000 from 55,000 and now i just get this error in sapien that the collision model doesnt matcht the regular one

SunnySharma · Post by **SunnySharma** » Sun Mar 06, 2005 10:58 am

The collision model probably has a different frame(s) than your original. Create a new collision model for your object!

an emu · Post by **an emu** » Sun Mar 06, 2005 12:47 pm

i did. used the nodes from the banshee physics mass points and linked them to my collision model, then linked my collision model to the frame hull