Pilot Archive
Thread: Serious Problem: Target Hit Registered Visually But Deals No Damage Please voice your support!
Page 8 of 8
MCarnage
Mon Nov 08, 2004 7:55 pm
#93
I had the same problem the first couple of times I played JTL.The 3 TIE Fighters you're supposed to kill on the first rebel mission would just fly around like drunken bees, especially when I got close, and any hits I could see and hear wouldn't cause the ship any damage. I had to restart that mission about a dozen times because I couldn't shoot them down fast enough,and I'd fail the mission. Strangely enough, I went and bought a new Joystick (Logitech Wingman Force 3D), installed the new drivers for it, and now the game works perfectly, and has been ever since (Now the TIE fighters are dropping like flies :smileyvery-happy
. I don't know if or how the joystick could cause these problems, but that's the only thing I changed. In both cases, my FPS/ping registered 30/~60, and my computer is an Athlon 2600+, 1.5 GB Ram, GeForce 6800 Ultra, so I've got a fast connection and my system meets or exceeds all the requirements for the game.In any case, this is just another variable to test.
. I don't know if or how the joystick could cause these problems, but that's the only thing I changed. In both cases, my FPS/ping registered 30/~60, and my computer is an Athlon 2600+, 1.5 GB Ram, GeForce 6800 Ultra, so I've got a fast connection and my system meets or exceeds all the requirements for the game.In any case, this is just another variable to test. Mith
Malliss
Wed Nov 10, 2004 9:40 am
#95
I have the same problem. Imade a new character and tried the very first imp pilot mission. After flying around hitting the ships for my mission (I know I hit them, I saw the shield bubble) for about 15 minutes doing no damage, I had to give up. I have an athlon 2500+, 1 gig RAM, and a Radeon 9600. I sent a ticket in, saying I have multiple characters in different factions that all have the same problem. Response - certain privateer factions can't hit imp targets. Huh? Was my ticket even read? Oh well, this NEEDS to be solved.
NoHandleWanted
Wed Nov 10, 2004 9:46 am
#96
I had the "hit but not hit" problem when gunning for a friend. Upgraded my ram from 512 Meg to 1.5 gig, and it fixed the problem.
I guess me client scored it a hit, but the target had actually moved on the server before my client was aware of it. Basically, I was
shooting after-images, lol. That stunk. 
Just noting a case where it was fixed, is all.
zweebo
Wed Nov 10, 2004 11:43 am
#97
Having read all the posts in this thread, the original problem (there are indeed others) sounds exactly like a problem with packetloss or possibly something to do with high upstream latency. If the ship warps and everything once-again syncs, the problem goes away.
Something to try: if something is using your upstream bandwidth in the background, close it. Verify that your bandwidth wasn't taken over by spyware. I developed a simple bandwidth monitor that may help you see what's going on: http://www.zweebo.com/techware
I know with my cablemodem, if my upstream bandwidth is in use, it chokes turn-around-time for other apps or large chunks of data. This isn't necessarily indicated by the ping and packetloss display either, because of how those things work. I guess it's a result of the way cablemodems do handshaking. (Never saw it with my Async DSL connection.)
FWIW, I'm also an old Wing Commander/X-Wing/Tie ace. I even play-tested Wing Commander and Privateer many years ago for Origin. Heh, I've probably shot more starfighters out of the sky than anyone, which is sad when you think about it.
I do see the anomolies you mention, but they seem to be very rare (~5 times in 16+ hours of combat), so I'm fairly certain it's network or network-hardware related.
My 2 cents.
Something to try: if something is using your upstream bandwidth in the background, close it. Verify that your bandwidth wasn't taken over by spyware. I developed a simple bandwidth monitor that may help you see what's going on: http://www.zweebo.com/techware
I know with my cablemodem, if my upstream bandwidth is in use, it chokes turn-around-time for other apps or large chunks of data. This isn't necessarily indicated by the ping and packetloss display either, because of how those things work. I guess it's a result of the way cablemodems do handshaking. (Never saw it with my Async DSL connection.)
FWIW, I'm also an old Wing Commander/X-Wing/Tie ace. I even play-tested Wing Commander and Privateer many years ago for Origin. Heh, I've probably shot more starfighters out of the sky than anyone, which is sad when you think about it.
I do see the anomolies you mention, but they seem to be very rare (~5 times in 16+ hours of combat), so I'm fairly certain it's network or network-hardware related.My 2 cents.
Transig
Wed Feb 02, 2005 5:35 am
#98
I've read about half of the posts (5 pages is a lot to read) but i get the general idea that some think it is just bad piloting,(imay not be as good as the originall poster but i would certainly give him a run for his money),latency problem or a bug.
Not sure about the last two for myself as i can go hours without a single problem but today i sat right in front of disabled ship firing at different points , the moment i registerd a hit i concentrated on that point but no further damage move another hit then nothing.Soa non moving target plus a non moving player (me) is out of sync for two minutes(other ship self destucted after that) i'm rather surprised i can hit anything if thats the case.
If you are wondering what conection i have it's this:
netgear 108 wireless conecting to a 54 d link WAP cabled toa router cabled to another router then on to a company (i live and work in a hotel) server conected to broadband , I get approx 250 ping ms though i have been up to 2049.
In short is it my conection (if so i'll play when it is good and not when it is bad) or is ther an intermitant bug that kicks in every once in awhile just to make life interesting?
Page 8 of 8