Maybe a technical one but... WHY does orbital have to pathfind AT ALL?

it's driving me up the wall how I'm loosing important orbital engagements to orbital units thinking LONG and HARD about how they're going to navigate empty space. And when they finally make a decision make right angles instead of straight lines.

Can we not remove flowfield from orbital and simply implement a less costly perfectly spherical plane for them to navigate on rather then navigating the planets (which are cubes)?

formations can be slapped right back on and might even work better. considering there are no obstacles in space (apart from other units and then some) they would look and behave a lot better.

Or just any solution that involves them not getting stuck in space, not thinking for hours and not making right angles to get to a point.

Becuz REASONS.

If you would click on the EXACT opposite size of a planet as a move order for a single orbital unit, what do you think would happen?

The unit would go all paths simultaneously as long as I don't look and then suddenly snap to one of them when I do?

But what if you also removed pathing?

Remove the pathing, just say if x < xdes then x+=(whatever how fast they go)
and if y < ydes then y+=(whatever how fast they go)
if x > xdes then x-= "
if y > ydes then y-= "
xdes and ydes are just variables I made up that store where you sent them

Seems legit.

legit enough to get those things moving
this is in gml, not in c++, so it might or might not work
i dont know c++


yet

if you ever give a command to the exact other side of the planet without trying to just do this then you deserve a cookie because those odds are so stacked.

lol

amirightoramiright?

am I the only one finding orbital needs a fix?

No, i also feel that it is stupid when orbital units just stop for multiple seconds before doing anything.