Augmentation process did not go as planned.

shoulders suck :[

use massive ODST shoulder pads to hide the rigging >.>

not my fault eh... I've been trying to make them look better :


good idea.

And I made the hands bending :

but what about the torso? the armpit area would still be messed up

Well,you gotta pick or the other.
Messed up shoulders or armpits?

Why does the biped not have shadows?

i had same question.

Sometimes if the bounding sphere is offset (middle is under bsp) it can cause shadows to not render. Otherwise I've had times where no matter what i do i could'nt get shadows to appear.

debug_objects 1 and look at the bounding sphere.

I never noticed it,for some reason.
Edited by Dumb AI on Jan 19, 2013 at 05:04 PM

I dunno.

gonna redo the gauntlets and still gotta get around to making a new helmet. if anyone wants the gauntlet mesh before I delete it forever, send a PM. shoulder armor is still WIP.

The helmet goes along with the armor pretty nicely.

Wow looks really good cannot wait until it is ingame.
Edited by ELVEVERX on Jan 19, 2013 at 10:24 PM

can we get an ETA for a complete biped?

gotta say, H4 armor looks pretty sweet

You can't even see the cubemap, why did you have to add that bit of stupid criticism?

Says the guy who has been arguing with him in 3 other threads xP

It's probably high-poly modelling without the use of Turbosmooth or Meshsmooth, I believe his way would be the best for low poly models in combination with OS.

what are you talking about? do you even know. its a lowpoly mesh...

Yeah something more like this though.

Lol
LMAO.
High poly model WITHOUT, turbosmooth?!
lol
lrn to concept hi-poleeeeeee plox

It would be too High-poly for stock CE, that is what I was trying to say. It is lowpoly ofcourse, but it would be still too high for CE.

Master noob, try using the handplates from the headhunters' spartans. From the motion comic in halo legends. Or use a variation of the halo 2 handplates

Like the hand plates on this
https://waypointprod.blob.core.windows.net/blogfilestore/legacycontent/halowaypointschedule/6.26.11/hh3_c_preview_508x212.jpg
Edited by DarkStarXIII on Jan 22, 2013 at 11:23 AM
Edited by DarkStarXIII on Jan 22, 2013 at 11:24 AM

Doesn't look it to me... he hasn't put a triangle count...

It looks fine. Halo can handle a lot more polies than people give it credit for.

Yeah it was just a speculation, I know that Halo can handle it. But can it optimize it correctly to minimize performance loss?

I think dat model up there looks pretty good. The visor bitmap thing could use work (From what I see) and the back looks a tad wonky. Might be the lighting. Does it have a tri count?

Could someone rig this with bones fit for FP animations? If you don't want to IK rig it that's fine, I can do that.

Mediafire link: http://www.mediafire.com/?zbcuc9461bn8ck4
Edited by Vergil on Jan 22, 2013 at 06:15 PM

Hey look! More rips and fag people taking credit for them!

Working on the flood MP biped, because no one can use/rip it :D

Altheros can!

The armor is oddly symmetrical...

made a (third try) pre-xbox halo spartan and now i'm texturin' it.

9761 tris for an ODST biped.

Yay or nay?

I can't get it much lower without making the biped seem mutilated.

Make LODs using the multi res modifier... 9.7k is a lot if you have multiple bipeds on screen...

Ultimately it depends on how many bipeds with that model you have loaded at once. You can almost always find ways to bring down the poly count from ~10,000. HOWEVER, the low poly bake would be the solution here and you'd have to utilize OpenSauce to allow that. Really it just comes down to how many bipeds of that model you have loaded at once. With modern PCs, it's been normally considered okay to have ~10,000 polies on a model. I will say though, the more you have loaded at once, the more the system will snap at you. Unless, of course, you're using Open Sauce.