Jump To Lightspeed Archive
Thread: Enemies warping, still in from Beta!!
Thunderghost1
Mon Nov 15, 2004 10:56 am
#235
Ok...annoyed now!! I hook up and old joystick to my old comp (my new one doesn't have a gameport) and it took me less than two mins to kill all three TIE's (first reb mission out of Tyrena)
Oh and yeah, I had the drunken bee on the old comp too when using my Logitech Strike force 3D stick.
So in my case it does seem like it's a problem between the game and my logitech stick.
I'm gonna buy a new stick (non-logitech) and see if it works on my new comp.
Meanwhile, I urge SOE to look at the problem with this in mind.
Oh and yeah, I had the drunken bee on the old comp too when using my Logitech Strike force 3D stick.
So in my case it does seem like it's a problem between the game and my logitech stick.
I'm gonna buy a new stick (non-logitech) and see if it works on my new comp.
Meanwhile, I urge SOE to look at the problem with this in mind.
mattygb
Mon Nov 15, 2004 11:58 am
#236
I had a bit of a crash last night, so I did a scandisk. This corrupted some xp files on my computer. After this, no jumping ships. And I am still using my Logitech stick. This whole weekend was playable for me, and I finished my first set of mission on both of my toons.
That, and when I couldn't play JTL, I logged into the WoW beta test for some good ol blizzard gaming. I do love Blizzard. (I hope this doesn't get this post deleted)
I also was able to start stocking my ship vendors, since I was grounded. So if you're on Sunrunner, stop on by.
Landorin
Mon Nov 15, 2004 4:24 pm
#237
Okay, I just tested jtl with a different joystick (usb) as well as without any joystick. Result was all the same: warping all around still. 
Maybe someone should go to the dev chat on the 16th (see dev tracker for details) and ask them if they are aware of this issue and when they start working on a fix or at least when they start investigating this (since I guess the crashes have higher priority now).
Maybe someone should go to the dev chat on the 16th (see dev tracker for details) and ask them if they are aware of this issue and when they start working on a fix or at least when they start investigating this (since I guess the crashes have higher priority now).
TalonKarrdeTN
Mon Nov 15, 2004 10:28 pm
#238
I have some what I hope potentially is very good news: in the patch notes for tomorrow where it says warping/rubberbanding has been reduced, this seems to be the case at least with the 'drunken bees'. I started a new TC character tonight and spent about 45 minutes as a newbie Rebel pilot in Corellian sector flying around fighting anything and everything at random, and not *once* in all that time did the drunken bees infect me with their inebriated stupor. 
Now, I'm just one person, and this doesn't mean the problem will be solved for everyone, but.....I have been seeing it like over half the time I've been playing in live, and as I said I never saw the 'drunken bees' effect once in beta myself. But I'm hoping this means this issue has been resolved and will be stable again in live. Flight and combat was so smooth overall in fact I was able to consistently take down those Tier 3 "Terror Kreetle" Dunelizards in my starter ship Headhunter with zero problems at all.
Now, I'm just one person, and this doesn't mean the problem will be solved for everyone, but.....I have been seeing it like over half the time I've been playing in live, and as I said I never saw the 'drunken bees' effect once in beta myself. But I'm hoping this means this issue has been resolved and will be stable again in live. Flight and combat was so smooth overall in fact I was able to consistently take down those Tier 3 "Terror Kreetle" Dunelizards in my starter ship Headhunter with zero problems at all. One note on overall 'rubberbanding' though.......the single-rubberband bug where you stop in your tracks and instantly accelerate back again is still in however. THAT bug has been around through it all though, even in beta....and it's a totally separate problem/issue than the 'drunken bees' bug. It's not much more than an annoyance though, it's by no means a game-breaker like the drunk bees issue is. Anyway, cross your fingers peeps, hopefully this patch tomorrow solves most of this anyway.
Landorin
Tue Nov 16, 2004 2:55 am
#239
Thanks, Talon, that sounds very promising. When I was on TC I didn't experience the drunken bees either but the ships kept warping (as well as the 0 zero engine warp bug you mentioned). I didn't test extremely long, however. Let's hope this issue will be resolved.
Yet thinking of my theory (that it is us jumping around and not the npc) still makes me wonder whether they really fixed that... but I put up my hopes high for this.
Maybe someone should ask the devs in the stratics chat today whether they really fixed the drunken bees.
And we'd really like to know what exactly happened when this occured from a technical point of view lol
Yet thinking of my theory (that it is us jumping around and not the npc) still makes me wonder whether they really fixed that... but I put up my hopes high for this.
Maybe someone should ask the devs in the stratics chat today whether they really fixed the drunken bees.
And we'd really like to know what exactly happened when this occured from a technical point of view lol
Landorin
Tue Nov 16, 2004 10:13 am
#240
Well... as I already feared, the latest publish did not fix the drunken bees problem.
Same with the reply from swg support... now they blame it on NAT, router and firewall although the 2nd computer has the same connection and doesn't have the problem. That is just real bad way of support.
I'm currently wondering whether I should complain about the guy writing these replies.
But somehow I guess our problem is not taken seriously and they think instead the problem is on our end only - the thread still hasn't been stickied, that might show how important they consider this...
I guess I can also stay on the ground from now on.
Someone has to ask them about this issue in the dev chat tonight (it'll be 2 AM my time when the chat starts so I can't be around).
Same with the reply from swg support... now they blame it on NAT, router and firewall although the 2nd computer has the same connection and doesn't have the problem. That is just real bad way of support.
I'm currently wondering whether I should complain about the guy writing these replies.
But somehow I guess our problem is not taken seriously and they think instead the problem is on our end only - the thread still hasn't been stickied, that might show how important they consider this...
I guess I can also stay on the ground from now on.
Someone has to ask them about this issue in the dev chat tonight (it'll be 2 AM my time when the chat starts so I can't be around).
Message Edited by Landorin on 11-16-2004 06:46 PM
TalonKarrdeTN
Tue Nov 16, 2004 10:42 am
#241
Landorin wrote:
Well... as I already feared, the latest publish did not fix the drunken bees problem.
Same with the reply from swg support... now they blame it on NAT, router and firewall although the 2nd computer has the same connection and doesn't have the problem. That is just real bad way of support.
Well, when I get home from work if it's still doing it with me in live it obviously can't be that, because it would happen to me both on Tarq and on Test Center then. I'll be sure to note that in the TC bug thread if that turns out to be the case.
Landorin
Tue Nov 16, 2004 10:48 am
#242
Well, due to the two PC story I even KNOW it can't be that, but swg support just blames it on firewall and such. 
And either it was coincidence or the problem got even worse now. I tried to dogfight a syck fighter (duty mission for Storm Squadron on Endor) and it was a drunken bee more times than ever before.
And either it was coincidence or the problem got even worse now. I tried to dogfight a syck fighter (duty mission for Storm Squadron on Endor) and it was a drunken bee more times than ever before.
Landorin
Tue Nov 16, 2004 11:44 am
#243
It's getting better and better... now I tried the live support chat... the only answer I got was "contact in game support" and "or [email protected]" (although I told him in advance that I already did that).
So now I go for the in game support and I bet my text won't be even read completely as it was the case in the live chat too.
So now I go for the in game support and I bet my text won't be even read completely as it was the case in the live chat too.
Dragoslaf
Tue Nov 16, 2004 2:27 pm
#244
I've canceled my account due to this issue and the fact that there is no actual content whatsoever after master. JTL is a failure.
Riftwing
Wed Nov 17, 2004 3:38 am
#245
I've had this problem ever since last weekend. Before then though, everything was working perfectly... seems like somthing in one of the patches borked it to me.
Bumping this back up to the top, its about time SOE took proper notice i think...
SpawnUSAF
Wed Nov 17, 2004 4:43 am
#246
Problem was mostly resolved for me after the patch yesterday...I was able to complete a few missions yesterday until I had to leave...it's a little choppy in space, however...every so often it would seem like the game froze for like 1-2 seconds, then it'd pop back into place and start moving, again...this was the only issue I could think of that I was having yesterday in space...I don't know if they actually fixed the problem, or maybe fixed 1 variation of this problem, but they fixed it for me 
...I'm thinking that there are multiple variations/causes of this problem and it just so happens that they seem to be causing the same issue...so, it seems that the devs ARE working on it, slowly, but surely...ttyla...
...I'm thinking that there are multiple variations/causes of this problem and it just so happens that they seem to be causing the same issue...so, it seems that the devs ARE working on it, slowly, but surely...ttyla...
Landorin
Wed Nov 17, 2004 12:34 pm
#247
Well, what can I say... after swg email and live chat support both failed in answering my questions, I was quite happy to see that a CSR responded to my CSR ticket and actually answered my question; she was honest enough to admit that they did hear of this issue but right now there isn't any workaround and a fix hasn't been found yet but we should /bug it with as many details as possible.
I'm glad at least someone was courageous enough to be honest and tell us there isn't a fix yet but at least they know about the issue. That's a start and means they will take care of it sooner or later in my opinion. I feel very relieved now even though it didn't solve my problem.
Thanks again, CSR!
I'm glad at least someone was courageous enough to be honest and tell us there isn't a fix yet but at least they know about the issue. That's a start and means they will take care of it sooner or later in my opinion. I feel very relieved now even though it didn't solve my problem.
Thanks again, CSR!