Pilot Archive

---

ActiveNick wrote:

---

Nacoa wrote:

---

ActiveNick wrote:
But if the game shows me a hit, it should be a registered hit that deals damage. I never meant to say the targeting reticle was off, it's supposed to be.

But registered hit should deal damage. Period.

---

There are 2 types of hits. Glancing blows will light up the target's shields, for example, but will not do damage. Direct hits will actually do damage. It's much easier to land a glancing blow, which means you're off by just a little bit.

---

I hit square in the middle from the back or from the side very often and still get no damage. This ain't no glancing blow. And then a few seconds later, after the server resync with the speed drop to zero and then full back up, the exact same shot on the same spot that did no damage 10 seconds before now blows up the target.

Conclusion: bug.

Solution: fix!

---

It sounds like you actually lost your link to SWG briefly. Back during beta when one of the space servers would go down, you could still fly around and shoot at NPCs that were still flying around, even with the "Connection to SWG Lost" sign up.

Unfortunately, that's not a bug as far as SOE is concerned. If your link gets disrupted, then there's nothing they can do since the problem is somewhere between you and SOE's servers. That may also explain why most people don't appear to have this problem, because they're not running over whatever borked router is between you and SOE's servers.

I really wish SOE did something like provide a "traceroute server" at their co-los. That way we might have a chance of figuring out the problem. As it is, you've got to run a packet sniffer to find the server to tracert to.

---

vnicula wrote:

"To the other guy who posted above, he should know that a 1.7 GHz Centrino processor is a rough equivalent of a 3 GHz P4."

NO, the performance of a 1.7 Ghz Centrino is 64%-66% compared to a rusty 3Ghz P4.

Anyway many of you don't need/want help, just a little attention.

YOU CANT BULLSEYE SHOT IN JTL.FIRE A LOTAND ADJUST YOUR POSITIONUNTIL YOU DEAL DAMAGE.

thats how i made it to imp 4433 in 12 hrs.

---

Check out this benchmark at Intel: http://www.intel.com/products/benchmarks/notebook/

It clearly shows how a 1.7 GHz centrino is faster than a 2.6 GHz pentium 4... besides, this is not a debate on CPUs, I was merely stating that my laptop easily meets the recommended hardware requirements, nothing more. I won't respond to further CPU debate claims, this is beside the point of this thread.

And why can't I bullseye in JTL ifI have the skill to actually hit the ship on the first try? I agree you cannot do it *now*, but we should be able to. If my shot misses, then so be it, but ifI anticipate my target's movement and aimed right and I hit the ship, then I should deal damage... how many times do I have to repeat this?

As for wanting attention, my discussion involves talking about a common problem many have, nothing more. Then you show up, contradict what others say without offering an constructive feedback, and then boast you got to pilot 4433 in 12 hours... congratulations.I give you credit and validation. Now let us continue this adult discussion that seems to affect so many of us.

---

Mejowepra wrote:Some other random comments:

The network monitor is not correct. Mine shows 130 ms/0 packet loss. Always. I have a fast connection (World of Warcraft has a 40-50 ms latency showing, and pings are always a lot lower than 130 ms for example), so 130 ms seems high.

---

Your ping time is based on the network topology between you and the server. WoW's servers are topographically closer to your system than the galaxy you play on. Given your ping time, I suspect you're on one coast (say, California) and playing on a server hosted on another coast (say, Virginia). However you may have a strange topology between you and the server that slows it down. As an example, I'm in NC. To connect from home to one of the servers I use at work, my packets are routed through Washington DC, then back to NC (our ISPs plug into different backbones).

---

Also yesterday I had some downloading/uploading going which I forgot about and I couldn't hit a single thing in my new and shiny X-wing. Latency still said 130 ms although it obviously was way higher. After stopping the bandwidth usage, I could hit things again and my ping was STILL 130 ms. So I wouldn't believe that number at all.

---

That's because your ping time should only be marginally affected by your decreased bandwidth. You're still able to get a tiny ICMP packet out to the server and back in 130ms. However, your decreased bandwidth means you're not getting all the game-related updates in a timely manner since those are a lot bigger than an ICMP packet and are a lower priority to the network.

An example: If I've got a 128kbps DSL that's the same distance topographically from SOE's server as a T-3, they both will have almost the same ping time.

---

Cha0sl0rd wrote:

FYI there is no such thing as a 1.7Ghz centrino CPU.

Its called 1.7 Ghz pentium m.

Centrino is just a label Intel slaps on machines that fulfill certain demands.

Sory to hijack your thread ActiveNick.

I have not had this bug happen to me, but i still hope they fix it

Fisla

---

Hehe, I know... but thanks for the clarification, and the support to our thread.

---

CavScout2003 wrote:

Another thing I'd like to mention (if it hasn't been already), is when I'm running an escort or patrol mission and I'm unable to fire on enemy targets besides those that are part of the mission. The mission enemy is outlined in a red box (thanks, otherwise I would have been attacking teh other guys and not getting anywhere - literally). There was one time I was doing an escort, and about 3 other guys were also doing the Imp Tier 1 escort - so we had this convoy of freighters, and my targets would engage another freighter (didn't notice if they scored hits or not .. percentage wise - they looked like they were hitting), before I got in among them and shortened their lifespan. But, me trying to help out a fellow imp? Won't happen. Not that I wouldn't like an extra bit of XP, and possible loot (components, not credits ... heh), but because if it wasn't my mission - it was invulnerable.

And why is that? Why can't I assault any NPC fighter (especially my own side)?

-Cav

---

This is to prevent the kill stealing that was rampant in beta. I f you are in agroup with you fellow imps then you all will be able to attack. This is how me and my guildes got to 3/3/3/2 but be carefull the higher up spawns are hard.

Back on topic I have this issue also and it is real. I live on the east and play on a west coast server and it some times take 5 mins of flying around in a circle to kill something that I can see that I'm hitting. Pls fix this

---

Mejowepra wrote:

Some other random comments:

The network monitor is not correct. Mine shows 130 ms/0 packet loss. Always. I have a fast connection (World of Warcraft has a 40-50 ms latency showing, and pings are always a lot lower than 130 ms for example), so 130 ms seems high. Also yesterday I had some downloading/uploading going which I forgot about and I couldn't hit a single thing in my new and shiny X-wing. Latency still said 130 ms although it obviously was way higher. After stopping the bandwidth usage, I could hit things again and my ping was STILL 130 ms. So I wouldn't believe that number at all.

---

Yeah, I heard of this as well. I now wonder what my true ping is. Any idea on how to find out?

I still can't believe how such a big issue is not getting dev attention. Wait until people PvP more and ships do/don't get destroyed because of this... then you'll see an uproar. Let's not wait until then devs, *now* is the time to fix it. Push some tentative fixes on TC, I play there too and I'll be the first to test it and provide feedback on it.

Oh, and if you have this problem or posted to support me above, please 5-star me again to counter the people who have nothing else to do than 1-star constructive posts.

Message Edited by MonteBruno on 11-02-2004 12:48 PM

I have the same issues with the targeting. I've adjusted to it, but it bothers
me that the orientation to the targeting recticle changes from ship to ship.
I have two machines that I am running JTL on:


1: AthlonXP 2800
1 GB PC3200
128 MB FX5600


2: Dual PIII 1.0 GHz
1.5 GB PC133
128 MB Radeon 8500


Both of these run off of a 3.0+ Mb cable connection.
My connection is lightning fast, so that's no the issue. I have one of the best
connections I've seen to date.


I make a living as a desktop tech, so I know my machines run beautifully. I also
know there is no virus/spyware interference.
I'd like to see a solution to this. Even if the recticle is off-target, we need to
know that if a shot looks like it hits, it really hits.


Oh, and one last thing:


VNICULA -- "Side note: dont even think that your low level laptop is a system for jtl,
we all use 3.2Ghz or better processors with 800Mhz FSB and high end video cards."


Dude, don't be a jerk. You may be surprised to find out that a vast majority of the
PC game players in the country DO NOT have 3 GHz+ machines and high end video cards.


Often, people will go buy new and overpriced equipment to stay at the top of the heap
because they don't know how to properly configure the machine they have to run
optimally.
That's only some people, though.

Message Edited by Zocima on 11-02-2004 02:50 PM