Jump To Lightspeed Archive
Thread: Fix for at least ONE of the invulnerability bugs!
Message Edited by Kiashia on 12-04-2004 05:25 PM
to another ship and destory it, the ship that was disabled, will not take damage until it is targeted. If I just shoot at it without it being targeted nothing, no damage occurs.
This probem seems to have more then one cause. Great post!
Gruug wrote:
Very good post. I first came in to read this expecting to see someone complaining about this particular bug (again). Have heard this one since beta and I myself have never experienced it...and that was on three different computers of varying RAM and CPU. Therefore, in my thinking anyway, I was of the opinion it was something on the users end and not the fault of SOE. Imagine that!
Sorry to tell you, but this bug isn't tied to anything the user does, did, or may do next. Before the 11.2 publish, I experienced the bug only twice. Had I changed anything in my system or game config? No, I hadn't. I figured it to be internet lag at the time, since the problem went away, on it's own, without me changing a single setting. Now, however, it's here to stay. Even with the various tricks suggested, the best I can do is minimize the effects of this bug. I still don't fully eliminate it. It's a game or server fault (I'm leaning towards the game), plain and simple. Other games don't have these issues on the same systems that are seeing it in this game. Can you honestly say it's a user error and not a game error? They are calibrating a software timing loop (something that is needed, and I accept that) based on a technique or system timer that is not reliable. The fact that this problem was made worse for many of us with the 11.2 publish seems to suggest that they tweaked that code while fixing the collision detection problems. It is also funny that proximity to the object plays an important role in this bug. Space stations dont' jump around on me like ships do (yes, I know, it's actually me that is bouncing around, somehow), yet while I'm at a good distance, we stay at a constant distance from each other. Up close, it's another story. Freighters are fun to watch, though. Those of us with the bug are the ones who are actually bouncing around, supposedly. Explain how I can sit still with the stars, planet(s), and nebulae sitting still with me, while freighters are twisting, turning, and jumping around like they have ants crawling all over them? It's really funny when you have a tier 1 Y-Wing, sitting still, shooting you in the aft shield when you're behind him and facing his ship. Shouldn't that hit be on the front shield? Well, yes, but since I can't hit him, he's not really in front of me, is he. His true position is behind me at the time.
Again, I believe this hasa lotto do with code they changed for the 11.2 publish. Proximity to target effects it, and collision detection tweaking would be based on proximity.
MadcowwithSARS wrote:
What is amazing though is games built in the early 90s didnt have a invulnerability bug. Oh wait that was back when they debugged stuff fully before putting it on the market. I shot for had to be 30 seconds last night into the top of an imperial gunboat and no damage to nothing, shields were already down but still no damage to systems or anything. They need to put this at the top of the list for JTL not goofy loot revamps that dont work or nerfing Droid interfaces. These guys have their priorities about as organized as a teenager on the virge of scoring and not caring that he has no protection.
While this is true in many areas, it's not entirely true. However, complexity has little to do with priority for the programmers. If a bug effects anyone, it is capable of effecting everyone. New features should not be added until known bugs are addressed. It's only a matter of time before people get something new in their system that "breaks" the calibration for client/server sync. For some of us, nothing needed to be changed at all for the sync issue to come and go. The problem is, generally speaking, most programmers assume that their product is the only thing that will be running. Sadly, this line of thought seems to be true for programmers of games, apps, drivers, and even operating systems.
Epitaxial wrote:
Games were less complex back then. Expecting perfection in a game as complex as SWG or any other PC game released is impossible. All complex PC games are "put on the market" with bugs - why do you think patches are released? If you want less buggy games - go fire up a console game. Unlike PC computes, console platforms have a specific set of hardware which never change = controlled situation = better debugging before the product ships.
Kiashia wrote:I been getting ticked ALL day long, I could not hit anything and when i hit i was doing no damage. easy battles where taking forever... harder ones where impossable to finish. For me it was not always that way. just started happening... so i thought what changed. well.. new direct x but i was fine after that, ATI drivers where new ... but thats not what the issue was... one last thing i changed was i set my self to windowed mode borderless window. THAT is what caused it. In windowed mode i could fire at a stationary target and not hit it.... once i changed it back to full screen everything was fine i could hit normally again.This fixed it for me I hope it helps others that may be in that boat cause man it is ANOYING!Message Edited by Kiashia on 12-04-2004 05:25 PM
Hmm.. maybe, but I don't think it has anything to do with the client side at all. I use both borderless window mode and full screen mode and I don't see a difference in the warping/invulnerability problem.