Loading...
  OR  Zero-K Name:    Password:   

Starlight Bugs

11 posts, 745 views
Post comment
Filter:    Player:  
sort

4 years ago
So I have found two bugs for starlight:

Starlight Can't Aim Units even with the full line of sight Video:
[Spoiler]

Starlight doesn't have the correct range indicated:
[Spoiler]
+3 / -0


4 years ago
I am not too concerned about the range indicator bug provided that the following hold:
  • Everything in Starlight range during structure placement can be damaged by the Starlight.
  • Everything outside Starlight range while the structure exists cannot be damaged by the Starlight.
As far as I know both those statements are true.
+0 / -0

4 years ago
the 2nd video basicly says that both statements are wrong tho
+1 / -0


4 years ago
I disagree. The video is good evidence for the second statement and has no bearing on the first.
+0 / -0
Ok...I am starting to be confused. Is there a GoogleTranslate for what you just said AUrankAdminGoogleFrog :D?

You must understand that I know you guys are working hard on your free time to fix these bugs, and it's ok to tell things straight. You don't need to be evasive with us in words. We can even help you with these bugs if somebody has the time and knowledge.

I will try to learn some LuaUI so in the future I will be of a bit of help for you guys. I don't know how much it will take for me to understand the full coding process for Zero-K but, I will try my best if I also got the time :).

Now regarding Starlight, people that don't usually play FFA and have no experience with the weapon have a hard time micromanaging it right now. I just saw some matches were silver star players couldn't aim well with it because of the bugs of course and also because "Fire at Will" state blocks your manual attacking location.
+1 / -0

4 years ago
Github commit link

I think the last buff to starlight makes the starlight now 'lie' about it's range. For whatever reason the range thing has just been broken, where the lazzer doesn't reach the end of range. So when placing the structure the indicated range lies about it's maxrange, saying it's shorter than it actually is to offset the bug. Test by having a starlight, then trying to build a starlight in the same place. In the least, you get to know for sure what's in range when constructing the thing.
+0 / -0

4 years ago
it can also shoot at the sky if it shoots above the glint
+0 / -0
My memory is fuzzy ,last time i played around with starlight was at least 1 year ago,so i might be confusing things.
From what i remember the error dint use to be so big,it was much smaller.

What i do remember is that i made starlight in range of singu but when i targeted it it dint want to move to the edge of the range it stayed some distance away,at the time i believed it was the terraform around the singu messing the targeting but now im not so sure anymore.
+0 / -0
A proper solution to Starlight (and other spherical range weapons) weapon UI would be to extend the engine function that draws the range circles.

Currently it compensates for ballistics by binary-searching how much range boost the weapon gets per angle of the circle. For spherical weapons, it could compensate for the effective loss of range when their aimpoint is high up.
+0 / -0


4 years ago
By the way, I fixed the first bug: https://github.com/ZeroK-RTS/Zero-K/commit/b109f4fe3a4932b4720db07adf08bf6935996ef7

Some good points have been made about fixing the range so the owner of the Starlight knows which attack commands will be followed. Either the engine needs to be extended a bit to draw spherical range rings properly or a lua range ring should be added. Defense ranges already needs to draw correct range rings in lua so adding a working ring for the owner of the Starlight is not extra work. Also, perhaps all turrets should have attack ground commands beyond their range be blocked to give better UI feedback.
+1 / -0
quote:
Defense ranges already needs to draw correct range rings in lua so adding a working ring for the owner of the Starlight is not extra work

If done the way engine does its ballistic calculations though, it's gonna be a lot of extra calculations. Engine gets away with them because it doesn't draw a lot of these all the time; but defense circles are shown all the time and for all known enemy turrets.
+0 / -0