Spring RTS Engine

[Krogoth86] wrote:

Because of the great number of units it hard to realize what all are doing.

You're right concerning that "intrusion system" for which I once had proposed a description change. It does spawn sort of small flashy red circles where enemy units are moving. The sense behind this is that in contrast to radars you cannot jam this effect. The downside is that your turrets and units won't auto target those sensor reports.

Also, they won't detect air...and afaik buildings/non-moving ground-units neither. Their red-ring effect seriously needs some looking into though, the rings they make are ridiculously huge and cause serious eye-cancer (for testing, look what happens if a single cloaked sniper comes into range...).
For new description i'd propose "intrusion detector" or "seismic detector"...or "seismic intrusion detection system"...or whatever...

I thought the effect size was reduced some releases ago?!
Back then I voted for "camouflage detection" or something like that because its main purpose is just that - detect units that have stealth, cloaking or both...

Hmm i could be wrong, but i think i can remember seeing the large rings in 6.1 or 6.0 recently...gonna re-check in a game soon.

I saw the rings on 6.1. The ring for the parasite is big, the ring for the sniper is huge.

OMG AN EXTENSION DISCUSSION! INFORM THE MAJOR SO HE CAN CALL SLEKSA!!!

TOO LATE!

This version is crashing a lot. And a lot of luaui errors that when you luaui reload, it crashes the game.

CautionToTheWind wrote:And a lot of luaui errors that when you luaui reload, it crashes the game.

I already tracked that down a few days ago, it's fixed in SVN.

I usually always do /disable before /reload and I haven't ever seen LuaUI crash the game.

ZellSF wrote:I usually always do /disable before /reload and I haven't ever seen LuaUI crash the game.

In this case, it did:
viewtopic.php?f=11&t=13900

And it wouldn't crash if /disable was done before /reload ? I seem to recall there being a difference between those earlier.

I reload or disable many times (i disable for fps increase) and do not expirience crashes.

About BA in general: Shields seem fine - about 4 BB's will quite fast overpover it. They do block stuff now as far as i tested.
Kbots (esp lvl2) are still too weak imo, rarely see them in big games. Perhaps ppl need to rediscover them after recent buffs.

There are 2 changes needed that have big impact:
- fix mobile antis - those must work 100%
- reduce fighter sight distance (from 700 to 500-550) in order to reduce lag - see here viewtopic.php?f=11&t=13828&st=0&sk=t&sd=a Test em with new sight so they still work ok.

- perhaps increase corvetes DPS on max range in order to better fight hovers?

Otherwise this version is awsome.

ZellSF wrote:And it wouldn't crash if /disable was done before /reload ? I seem to recall there being a difference between those earlier.

No, wouldn't crash if you disable first. On my install, starting a BA6.1 game, selecting the comm and then doing "/luaui reload" would reproducibly crash Spring, every time. It's vital that you have a unit selected, else it won't crash.

eriatarka wrote: I already tracked that down a few days ago, it's fixed in SVN.

Spring SVN? Then lets hope for a quick release.

it does not crash for me like u said with these widgets:

ginekolog wrote:I reload or disable many times (i disable for fps increase) and do not expirience crashes.

About BA in general: Shields seem fine - about 4 BB's will quite fast overpover it. They do block stuff now as far as i tested.
Kbots (esp lvl2) are still too weak imo, rarely see them in big games. Perhaps ppl need to rediscover them after recent buffs.

There are 2 changes needed that have big impact:
- fix mobile antis - those must work 100%
- reduce fighter sight distance (from 700 to 500-550) in order to reduce lag - see here viewtopic.php?f=11&t=13828&st=0&sk=t&sd=a Test em with new sight so they still work ok.

- perhaps increase corvetes DPS on max range in order to better fight hovers?

Otherwise this version is awsome.

I think these are reasonable changes, so long as the fighter sight thing does not make them phail. If so, maybe they need some other enhancement to make them as good as before.

Isnt there a way to make fighters see only planes?and not the ground.
Than all youll need is to remove their ability to shoot land but its redundant anyways and you can spam fighters till u choke.

Need a link to this (BA6.1). UHF is down.

Any help?

Example of how fighters "should" operate.

L-1 + L-2 fighters "should" never attack ground units on their own, and always be free when any air threat comes into their patrol pattern/area.

L-1 + L-2 fighters while default "should not" seek out ground targets, but be allowed to fire on ground targets when manually forced to do so.

We have gunships and bombers for taking out ground targets, fighters main role is best suited to responding quickly to air threats, and should not being distracted by any ground targets.

MR.D wrote:Example of how fighters "should" operate.

L-1 + L-2 fighters "should" never attack ground units on their own, and always be free when any air threat comes into their patrol pattern/area.

L-1 + L-2 fighters while default "should not" seek out ground targets, but be allowed to fire on ground targets when manually forced to do so.

We have gunships and bombers for taking out ground targets, fighters main role is best suited to responding quickly to air threats, and should not being distracted by any ground targets.

Maybe it would somehow be possible to let them switch between this and current behavior with the on/off button?

ginekolog wrote:it does not crash for me like u said with these widgets:
[...snip...]

As far as I can see, you don't have the BA custom layout widget enabled, do you?