Pilot Archive
Thread: Hit'em 1,000,000 time and nada????!!!!
hit ctrl-shift-g....this will bring up your network status. If your ping is exceptionally high, like over 1000 consistently, then you're probably lagging too much to actually register a hit on your target, even if it looks like you're getting glancing blows. The problem is the server thinksyour target is in one place, but your client is lagging enough behind that it shows a "ghost" ship that isnt in thesame place as where the server thinks it is. So naturally, when you hit where you think the ship is, in "reality" the ship is already a shiplength or more ahead and the server says you miss.
I run into this sometimes. You have to log out and reopen SWGusually, though sometimes its enough just landing and relaunching. If you have any other programs in the background using bandwidth (kazaa or something, IM programs are ok), close those before you relaunch.
Message Edited by droid327 on 08-10-2005 07:18 PM
Took my brother out for a spin in my ARC-170, we decided to go hunting in Kessel. He was manning the rear top turret, and we would use a standard gunship poaching tactic. I run the ARC parallel to the Gunship, underNEATH it with our ship on it's side. The turret gunner is looking off to the side, and shooting the gunship.
Tactics aside, there would be looong long segments where he would suddenly just 'stop shooting' .. then start shooting again. At one point I was running parallel to a Gunship like this and he stopped shooting for upwards of 30 to 45 seconds. I finally ASKED him why he wasn't shooting, he said he WAS shooting.. but the numbers on the ship weren't dropping at all. This happened SEVERAL more times, and on any Gunship that it happened with .. we never got XP Credit for the kill.
This happened a LOT last night on Corbantis in Kessel. Everything from Gunships to TIE Advanced to Corsair Raiders, you name it. This problem would pop up for one target, go away for one or two.. come back for one or two. Aggrivating as heck.
sememon wrote:when you hit the ship are you getting some horrible beeping type sound?if so then your possibly trying to hit a ship spawned by some one elses mission. the crap thing about this, is that we cant hurt them, but they sure as hell can hurt us.
Here's the way our problem worked:
We run up beneath a gunboat, I'm pilotting while my rear gunners start working on the gunship's shields and engine. The shields and armor get whittled down at good pace so we can kill the engine. At this point, we ARE actually doing damage to it... no 'beep' noise like it is a mission-spawned mob for someone else (and yeah, I do know what you refer to. Good point, but that's not this issue). The engine gets dropped to 0% , all of the sudden my rear gunners stop firing completely (visually to me only, it turns out). I would ask if they're firing , and get "Yeah we are but the numbers aren't dropping.. it even shows the shields flashing on it!".
At this point if I didn't spin around and start blasting this thing myself, it would eventually just "pop" on its own and we got zero xp for it.
When the problem starts happening, I stop seeing the gunners shoot.. and they stop draining capacitor energy. How ever to the gunners, they ARE shooting constantly.. and their Capacitor energy is steadily going down. They just are not changing the percentages on the target at all (i.e. not seeming to land any hits).
Now mind you, this is on a stationary target with a disabled reactor! It's not a matter of "incorrectly leading the target", it wasn't moving. It's not a matter of "maybe it was a mission spawn you can't damage" because WE TOOK OUT the Reactor.
This really does frustrate me to no end! It basically killed our night, we had to finally just call it quits.