Spring RTS Engine

While considering the problem of the BA Mercury/Screamer weapons failing to hit targets due to radar hover, it occurred to me that it would be pretty cool if weapon projectiles - especially for tracking weapons such as missiles - could have their own radar or even LOS. This would allow them to home in on their targets as they get closer to them.

Perhaps the optional ability to have the radar attuned to it's current target so as not to provide additional radar coverage?

Another possible use: stealth probes that could be launched from a distance and sent into enemy territory.

As far as I'm aware this is not currently possible but is it feasible or even practical to add such a capability?

Tuned into one target perhaps, but radar plotting in flight seems like a resource intense idea. I'm sure its possible. But just think how bad it would lag the game if you had everyone using them in a multiplayer game.

Why would it? Does sending loads of spy/radar units all over the map cause extreme lag?

I'd imagine it would only be used on special weapons with low fire rate anyway so it's not like you're going to get lots of them at the same time.

1. a radar vehicle/unit is much slower than a projectile (its los would have to be updated every gameframe instead of every 15th !)
2. you would double the objects with los this way in worst case (what increase the cputime again)
3. los is already one of the most cpu intensive calculations

OK, forget LOS. How about just radar? My primary objective here is to work out if this would help long-range missiles correctly home-in on their targets.

LOS and radar aren't any different in how they are calculated.

But if the weapon only receives radar of its target then that isn't going to kill the CPU is it?

edit:
if you want to improve targeting, why don't you increase the radar/los distance during aiming (in cob)?

Or use Lua to spawn an invisible scout near the target?

Why don't you just have it aim at the unit rather the radar dot, and screw giving it LOS entirely? Surely that would suffice?

Alternatively: LUA + kamiksae aircraft unit launcher cannon?

Guessmyname wrote:Why don't you just have it aim at the unit rather the radar dot, and screw giving it LOS entirely? Surely that would suffice?

You beat me to it. This occurred to me on my way home from work. Perhaps an "AccurateRadar=1" weapon tag?

Though the Kamikase launcher sounds good.

Or better yet a "don't shoot at radar blips" tag for precision weapons with slow reload.

But I want my long range SAM's to fire at radar blips; that's the point of them: kill the enemy planes before they get close.

But it's kinda silly to have inaccurate radars when your weapons that depend on them ignore the inaccuracy, no?

KDR_11k wrote:But it's kinda silly to have inaccurate radars when your weapons that depend on them ignore the inaccuracy, no?

Not really. If you have a missile that tracks its target, then it should be able to actually hit it, and not the radar blip it originally was aimed at. But it is silly for just about any other type of weapon.

jK wrote: 3. los is already one of the most cpu intensive calculations

Thats the problem one unit calculates Los or/and radar when it shouldn't cause another unit already covered what other unit (mostly radar) wanted, though it doesn't do any good(unless if two units surround and enemy unit and makes a more precise radar Blip)!
About radar ->

+ What does the middle circle highlight change?

The inner circle is LOS.
The slightly larger circle is Air los, ALOS, for seeing planes and, iirc, particle effects.
The outer, as you know, is radar.

The next version of spring will have more color distinctions and fanciness.