Spring RTS Engine

Of spring ever getting a system like this?

http://www.youtube.com/watch?v=jA2epda-RkM

You son of a...

Low to none.

it wouldn't be that hard to do, but it needs a dedicated developer, probably with some knowhow.

It looks cool.
I haven't played supcom enough to know how good it is,but It might have all sorts of restrictions..

the thing is, they are using fixed distance between units formations.
we do not have that in spring, and that allows for more variety (eg, it is not purely a bad thing). if you leave some space between units in formations, it is of course much easier to move two formations through each other, or move them through narrow passes (and it looking nice). it also requires units/models to be generally smaller though, compared to the map, to get the same gameplay.
is this right?

we dont need flow crap or whatever it is...
We just need to sort what we have a bit..
I mean why is it than when i have a line of units facing right and i stretch a move line at a location to the left of my units all my units will get criss crossed...

a\ / a
b \ b
c/ \ c

a form right will go to c from left and c from right will go to a from left...I mean WTF...

Gota wrote:we dont need flow crap or whatever it is...
We just need to sort what we have a bit..
I mean why is it than when i have a line of units facing right and i stretch a move line at a location to the left of my units all my units will get criss crossed...

a\ / a
b \ b
c/ \ c

a form right will go to c from left and c from right will go to a from left...I mean WTF...

This happens randomly. Also, I would imagine this is a problem with Custom Formations rather than with general pathfinding. I've expressed this before in the form of pretty diagrams but nothing got done about it.

It's the same If you remove custom formations.

i remember loosely that the problem was the sorting algorithm taking too much CPU time if you have a lot of units in the formation, therefore, an upper limit for the perfect sorting/arrangement of units is used. maybe you should also remember the why sometimes, when nothing is done about your requests.

hoijui wrote:i remember loosely that the problem was the sorting algorithm taking too much CPU time if you have a lot of units in the formation, therefore, an upper limit for the perfect sorting/arrangement of units is used. maybe you should also remember the why sometimes, when nothing is done about your requests.

2 units isnt a lot imo.

Spring pathing is borderline broken.

Can I set the weight the pathfinder gives to blocking units yet?

Gota wrote:It's the same If you remove custom formations.

I'm sure Custom Formations is relevant in some way though. It orders each unit a move command individually, so each unit has it's set move order to go to, each unit should have the most optimal path in terms of time it would take to get there, compared to any of the other units using that same path.

Why not just make a lot of dust and cheat on collission detection, while to friendly formations cross each other?

include this as a add. function for the MT-spring exe?

hoijui wrote:i remember loosely that the problem was the sorting algorithm taking too much CPU time if you have a lot of units in the formation, therefore, an upper limit for the perfect sorting/arrangement of units is used. maybe you should also remember the why sometimes, when nothing is done about your requests.

You dont need many units to get this result...
just a few..they will criss cross and cross each other's paths for no apparent reason,when they could just walk straight.
Take 5 units and test...
If 5 units are too much already than we definitely need some new system.

manolo_ wrote:include this as a add. function for the MT-spring exe?

This is a synced game. MT cannot work differently than ST.

I agree the pathfinder has some issues. We need a flow field expert :)

Also, watch the damn video if you haven't, BEFORE replying here. A few people didn't and it shows and is royally irritating.

what if you break a formation down into lines- like ants stupidly following the headleader- and if the headleader changes direction because of obstacles, all the tool has to calculate is that no leaders path crosses each other - would look mighty intelligent, and minimize calculation for every single unit.. - sort of snakes passing by each other..

also royally annoying forb were:

********
******
*********
********* ********

If your name is not on the list, consider yourself awarded.

PS: I also heard that SoupCom has >>ProblemsofItsOwn-thatarewaymoarImportanttosolve<<- can spring have >>ProblemsofItsOwn-thatarewaymoarImportanttosolve<< too?

We need to show Chris that Spring pwns supcom so we need to employ ├╝ber algorithms. Maybe hueg neural network. A pathfinding that sucks at first, but eventually outperforms the flowfield