Jump To Lightspeed Archive
Thread: Drunken Bumble Bees's
Page 1 of 2
Kattrinna
Mon Mar 07, 2005 4:08 pm
#1
I have seen numerous threads talking about this, but I never saw anything in a way of resolution. I have tried so many things to try and resolve it, but I am just not having any luck at all.
Just to bring it in perspective, in as soon as you bring your target to bear in the redicle it starts jumping all over the place like a mexican jumping bean, or bumble bee with one too many sherries.
It will last for 5-10 minutes, then all of a sudden it will be ok, then 5-10 mins more and its right back again. And while this is going on, they can hit you, but you can't hit them. So in a heavy battle you get wtfpwned.
I have 3 machines, it does it on all three. I have tried bypassing the router, even trying a different router. I don't use a joystick, so It ain't that. I just don't know. The ground portion of the game seems to be just fine. It is just space.
Any ideas?
Sar-larid
Mon Mar 07, 2005 4:17 pm
#2
You sure you aren't on the edge of a space sector when this happens?
Jantara
Mon Mar 07, 2005 7:09 pm
#3
I know eaxactly where you are coming from with the "Flight of the BumbleBee" Syndrome. I put up with it since beta and had gotten progressively worse for me as patches occurred. I searched the the Techincal support forum and located a thread about others having this issue and we all seemed to have the same type of hardware in our machines:
AMD AthlonXP 2800 processor
Asus A7N8X Motherboard
Radeon 9800Pro graphics cards
(I personally was running 1 gig of ram, but it was mixed speeds as I hadn't saved up for matched sticks yet)
One poster said that after an upgrade from the above equipment to the new 64bit platform, the bumblebee ships were gone. I had access to a P4 set up and completed switching over my PC a couple days ago. I was running the above set up, but now I have this:
Intel P4 3.0ghz Processor
Asus P4C800 motherboard
Radeon 9800Pro GPU
(Still have 1 gig of ram, but the change prompted a shopping trip because the P4 wouldnt post with my mismatched sticks)
The result is no more bumblebee ships. I cannot explain what eactly was the cause of the wonky ships, but getting away from the A7N8X MB and AthlonXP CPU has given me the results I was hoping for.
I dont know how this helps you with your solution, but maybe something I've done will spark an idea that will create a more effective cure than replacing your MB/CPU combo 
Jantara
Kattrinna
Tue Mar 08, 2005 7:04 pm
#4
That is very interesting. My main machine uses that exact Mother Board. Asus A7N8X-E Deluxe. I have the same processor too, but i really can't see how that would do it. I bet it is either chipset issue, or the onboard Nvidia LAN module. One thing I can try is to use the Marvel LAN GIG-E port instead of the Nvidia one. The E verison of this board has 1 of each. That would rule out the LAN port at least.
I really would hate to go drop 400 bucks on a New Mobo and Ram for this one silly issue. I have zero issues with anything else I play.
Very odd indeed, but it at least gives me a direction to try.
Both systems I have do it, and the only thing they share in common is the Mobo.
I will post my results.
Kat
Kattrinna
Wed Mar 09, 2005 12:11 pm
#5
Well, i changed NIC Adapters as I intended and that had no affect on the issue. Short of replacing the motherboard I have nothing else to try.
I don't think I can justify purchasing a new motherboard just because 1 game out of 20 some odd that I play off and on has some obscure issue. This really seems like a client/driver/chipset issue.
Of course the standard mode of SOE is deny all knowledge of an issue and it will magically go away. So I guess I shouldn't expect to get any attention about this.
Any one else have any ideas.
Kat
Jantara
Thu Mar 10, 2005 2:06 pm
#6
I'm glad it worked. I'm sad you had to spend money to fix it. It really is a boggle as to why this particular MB combo causes drunken bumblebee ships though. I wish I was more knowledgeable to help pinpoint the problem with that MB. I'm sure there are lots of others in the same boat that would appreciate a fix that didnt require changing the MB. At the moment we seem to have a "shooting moquito with Cannon" fix. 
JT
Kattrinna
Fri Mar 11, 2005 1:12 am
#7
Well i solved the problem. But I had to do exactly what I didn't want to do, spend money. Got rid of that ASUS A78NX-E Motherboard. Installed a new one from Giga-byte and problem magically is gone now.
I am not sure if it was either the board itself or the nForce 2 chipset on it. Had to be one of the two.
SoI ended up going to Athlon 64 Socket 939 3500+ and a board, transplanted everything else, and things run great. Even better on the ground then before.
This is what I had:
AMD Athlon 2800+ CPU
ASUS A78NX-E Deluxe Mobo
1 Gig DDR 400mhz Ballistix Ram (dual channel)
BFG 6800 GT OC
With that setup I thought things ran pretty darn good. After installing the new Mobo and Chip, man was that old setup CPU limited for that Video Card.
The new setup:
AMD Athlon 64 3500+ CPU
Giga-Byte GA-K8NS Ultra 939
1 Gig DDR 400mhz Ballistix Ram (dual channel)
BFG 6800 GT OC
Anyway, I only had that Asus board for 6 months, wha a dumper.
Kat
padren
Fri Mar 11, 2005 9:53 pm
#8
I am glad something was found that fixed it...I have an asus board and that chip set and the bees drive me nuts. I really hope they try to diagnose the problem (now that it appears to be narrowed down) and find a means by which code can remedy it. I only just bought this board to replace my old defective Soyo board.
JamesHighwest
Mon Mar 21, 2005 7:50 am
#9
I, too, have an ASUS motherboard with the nForce2 chipset and I am experiencing this problem as well. I will NOT throw money at the problem as I fully expect SOE to diagnose this problem and fix it. There has to be a way to solve this problem.
padren
Mon Mar 21, 2005 8:23 am
#10
It is a fact that it has to be fixable. They work sometimes and not others on any system, so there is already working code and broken code. The hardest thing for the staff is if they can't find out how to reproduce it, but it appears to be consistent with this type of motherboard/chipset config so they should be able to debug it.
Is there any way to find out if the staff are working on bugs or officially report them etc? It would be nice to hear a "yeah we know about it, and are working hard on a patch to fix it as soon as possible, expect it in 2-3 weeks" or even "we are too busy" would be better than being left hanging.
Have staff ever commented on this bug before?
Is there any way to find out if the staff are working on bugs or officially report them etc? It would be nice to hear a "yeah we know about it, and are working hard on a patch to fix it as soon as possible, expect it in 2-3 weeks" or even "we are too busy" would be better than being left hanging.
Have staff ever commented on this bug before?
psikobunny
Mon Mar 21, 2005 2:00 pm
#11
I'm pretty sure the "bug" had more to do with the internet between you and the swg servers than your mobo or chipset. Reason behind that is, I've seen it happen to every pilot now and again, myself included. The ships jump like mad because you're not getting accurate position info, and in return we would see you jumping like mad because we're not getting position info. On the ground the symptoms may be different, but I highly doubt you've never lagged before. Bummer you decided to spend money on it, but I really think you're problem will return, the next time there's a traffic issue.
Zeon_Zaku
Mon Mar 21, 2005 3:33 pm
#12
I see people complaining about this often, but for some reason I've never really noticed it. Maybe it's because my ships are naturally slow, but I always manage to stay on my target without missing much.
Of course, I don't really fight many tier 5's. Mostly tier 4 and below... 'cause the B-Wing can't really stand up to tier 5's. Heh...
Of course, I don't really fight many tier 5's. Mostly tier 4 and below... 'cause the B-Wing can't really stand up to tier 5's. Heh...
SanRa_Ledav
Wed Mar 23, 2005 1:51 am
#13
I had this issue pop up last night.
No definitive fix for the drunken bee Syndrome for 6 months now.
I say we start posting in the bug threads until resolved.
No definitive fix for the drunken bee Syndrome for 6 months now.
I say we start posting in the bug threads until resolved.
Page 1 of 2