Spring RTS Engine

Something I always hated just came up to my mind again:
In pretty much every situation where you select your factory and give a move order to a place you want your new units to go, those units when leaving the lab just move a little and then stop giving the "cannot reach" error. In order to fix this you have to do one move order in front of the lab and then the 2nd one to where you want your units to go...

Might be more of a bug than a feature request but I think it would be really cool to have this fixed...

This anoys me as well.

This is fail, and qualifies as a bug IMO.

Agreed, though it's much less of a problem if you get in the habit of adding a move command straight out of the factory first.

Peet wrote:Agreed, though it's much less of a problem if you get in the habit of adding a move command straight out of the factory first.

Hard to remember to do that evertime you give a move new move command tough...

widget / gadget?
(as a stopgap measure )

Maybe all factories should, despite the players orders, have a point a bit ahead of itself where units will move to before following player orders.

Peet wrote:Agreed, though it's much less of a problem if you get in the habit of adding a move command straight out of the factory first.

I try to, but sometimes forget. A widget/gadget would be nice, if an engine fix is too complicated.

trepan wrote:widget / gadget?
(as a stopgap measure )

That's what the bugfixer widget does, right?

I had forgotten about that widget.

KDR_11k wrote:

trepan wrote:widget / gadget?
(as a stopgap measure )

That's what the bugfixer widget does, right?

W4r 2 g3t?

KDR_11k wrote: That's what the bugfixer widget does, right?

Breaks guarding.

Peet wrote:Agreed, though it's much less of a problem if you get in the habit of adding a move command straight out of the factory first.

Which way is "out" if it's a 4-exit factory with a rotating buildplate?

I hate the posts that totaly disturb the point while offering bullshit instead!!stop redirecting attention to crap..u shouldnt make a special way point just so u can give the really nessasary way points..its rediculeous.

this really needs to be fixed...its a real hassle and is also not noob freindly.

A rotating build plate should have a fixed direction that it releases the unit at so that it avoids dropping the completed unit at dorky angles to begin with. How hard is it to predict the direction the unit needs to begin at in order to finish in the right direction? And how hard is it to enforce the unit only be finished once the pad is oriented the correct direction after delays such as running temporarily out of resources?

odds are madrat, that no one has gotten around to it yet.

MadRat wrote:A rotating build plate should have a fixed direction that it releases the unit at so that it avoids dropping the completed unit at dorky angles to begin with.

Well couldn't you fake this by adding some lines in the unit's Create() function which makes its base spin while let's say up to 99 build-% are left and after this value stops the spinning and resets the base to 0 rotation? That should work (I once had an accidental spinning of a sonar dish which started while the unit still was being built). For the lab you just let the platform spin but the piece that creates the unit just doesn't rotate with it so that principally the unit always faces towards the exit...

After having done that it just would be copy->paste work for all your units...

Surely the 'correct' solution in all cases is for the engine to fix the broken-pathfinding-on-leaving-factory bug? I accept a stopgap fix for a standard 1-exit lab might be worthwhile, but trying to hack a fix for more complicated labs seems the wrong way to go...

the problem with pathfinding is that there's noone who understands it well enough to fix any issues.

Actually the whole pathfinder system has quite an elegant design,
it's not hard to understand at all IMO. The reason that units have
trouble leaving factories is because when a unit finishes building,
the factory is open and thus partially non-blocking, which means
the pathfinder won't see most of it and go straight through given
the corners of a unit's footprint, while the ground collision checks
do and interfere (causing movement failures). I've played with this
a few times, but was never annoyed enough to really fix it.