Spring RTS Engine

I want to use the arms and gun for aiming up and down, but the ammo belt would move with them. Is it possible to have a face fixed in position in upspring so the belt would move but not the end, which should stay attached to the backpack?

Nope.

Indeed not.


We need bones, before i go on a rampage and destroy scriptor/servo/half the universe in animating rage.

Boo-fucking-hoo :'(

So I'll either have to restrict the arcs that the belt stays in the backpack but bobs up and down or abuse the body for aiming too... anyway thanks.

So I'm new here and I don't know the limitations of the spring engine. But could you make the hose 2 or 3 meshs' rather then one?

Skeram18 wrote:So I'm new here and I don't know the limitations of the spring engine. But could you make the hose 2 or 3 meshs' rather then one?

That wouldn't solve it, current animations require seperate pieces. I would suggest pivoting at the pelvis since that would remove this problem and look more natural as long as you limited the x arc.

I'll have the upper body as single object now anyway.

Any ideas on how to reduce polys on the model without sacrificing detail? Currently the infantry got twice the amount of polys than any vehicle I did and I've already removed over 500 tris...

Whats the poly count?

630 tris for the rocket guy and 888 tris for the minigun one. They had about 1200 to 1400 in the beginning...

how about simplifying the front of the MG belt/strap a little...and having fewer barrels on the mg itself?

rattle wrote:630 tris for the rocket guy and 888 tris for the minigun one. They had about 1200 to 1400 in the beginning...

Thats not too bad really, atleast I don't think it is.

unpossible wrote:how about simplifying the front of the MG belt/strap a little...and having fewer barrels on the mg itself?

The straps are about 80 tris each, could remove some I guess. The barrels are only 9 faces each (or 10 if faces I've hidden aren't ignored).

http://rattle.from-hell.net/dune/ the rest of the models. Only the MCV breaks the 1000 mark because of the 10 tires which I can't remove. A way to combat high polycount would be strict build limits to limit the amount of units in the game at any time later.

Hmm, sounds like me when I started modeling, I hardly even get the chance to brag about wiping out a lot of polies any more

Good luck, You shouldn't need too many polies, keep em under 1000 or so and you'll be fine..

Polies don't make the game lag you know. Did no one read Caydrs Proof about this? What Lags is the collisions. Although, More polies does make it harder to texture.

So I could make a unit with 10000 polies, and not lag the game?

*sigh*

Ehh, ignore that post on up there... Of course it would lag more... It would have to... And yeah, texturing would be a pain... *sigh* today is going to be very long...

Network lag != rendering lag. These are two completely unrelated things.

I'm not really an expert but for simplifying I can think is a few things I might concentrate on. First is using the texture to replace lack of polygons but making it have features that look 3D. You could also concentrate on bits that can't be seen very well. Then you can dissolve faces or remove vertices that aren't necessary. Also you could try removing things, then zooming out to a level that roughly represents the game level and see if it makes a discernable difference. You are usually allot closer in the 3D modeller than you are in game, at least in TA view.

I have no idea about whether or not it supports a fixed face but if you have it so that the distance from where the backpack goes into the arm (maybe multiple revolving parts) like a little bit sticking out that counder revolves and/or do a little maths with the belt's revolve and perhaps have the belt really two objects overlapping... etc.

those guys look awesome