Jump To Lightspeed Archive
Thread: Problem fighting A-wings. Bugged?
Page 1 of 1
Cumorah
Tue Jan 18, 2005 12:07 pm
#1
hi there.
Was up in space a few minutes ago and wondered why I did so bad versus those a-wings.
Thought the main reason was my mouse configuration so I changed that and jumped to area D-435 to have a look at the changes. Everything was okay when I fought B-wings but then I had to engage an A-wing.
I scored over 20 visual hits anyhow the a-wing's shield was at nearly 90%? Is the bug back where you could only hit ships from front and rear or is it only a problem I encounter?
Was up in space a few minutes ago and wondered why I did so bad versus those a-wings.
Thought the main reason was my mouse configuration so I changed that and jumped to area D-435 to have a look at the changes. Everything was okay when I fought B-wings but then I had to engage an A-wing.
I scored over 20 visual hits anyhow the a-wing's shield was at nearly 90%? Is the bug back where you could only hit ships from front and rear or is it only a problem I encounter?
SanRa_Ledav
Tue Jan 18, 2005 12:09 pm
#2
Cumorah,
Were the A-wings jumping around on screen? As in, their flight path resembled that of a housefly?
Were the A-wings jumping around on screen? As in, their flight path resembled that of a housefly?
Cumorah
Tue Jan 18, 2005 12:23 pm
#3
They tried to fly circles arround me so I followed them and hit their top... no damage. Was only to damage them when I directly hit their front and rear.
SanRa_Ledav
Tue Jan 18, 2005 12:27 pm
#4
Yeah, that's the top/bottom damage bug.
Seems quite often if you hit the top, or bottom of a ship, the blasts just bounce off the shields.
A-Wings are very tricky to get behind and stay behind.
Seems quite often if you hit the top, or bottom of a ship, the blasts just bounce off the shields.
A-Wings are very tricky to get behind and stay behind.
Cumorah
Tue Jan 18, 2005 12:38 pm
#5
That did not stand in the publish 12 notes....
A-wings can't be hit from top or bottom anymore
Cumorah
Wed Jan 19, 2005 1:58 am
#6
Seems like it was a false alarm. Nobody else had the same problems and after a restart everything was fine
Page 1 of 1