Jump To Lightspeed Archive

Has anyone brought this up in the "bug of the day" threads? Or brought it to Tiggs's attention?

I mentioned this in the Privateer ship Firday Feature and grabbed TH's attention.
Maybe we have hope of an update or something. (crossing fingers)

http://forums.station.sony.com/swg/board/message?board.id=lightspeed&message.id=169565

Look for TH's response on this in this thread guys.

Great job SanRa! Finally took someone with a special tag of some sort to get some sort of notice. Let's just hope it gets somewhere from this.

Hey, I'm just a simple person trying to make my way through the galaxy.....

Without my targets jumping all over the place!!!!


Hope I've been able to help. We'll see how it goes. '05 looks to be interesting from a development standpoint with this game.

OK...I know that no one wants to hear this. I've been studying this problem since day 1. And guess what, day 1 was before any patch or upgrade to the game. I finally brought home a carrier line analyzer from work to test my theory and it seems to be true. I'm not saying that a software problem is completely impossible but I have enough evidence now to say with a high level of certainty that: The warping issue is directly related to an interruption in the continuous data stream that is required for space ships to move about your screen smoothly. I've verified the phenomenon on DSL(1 line), Dial-up(4 lines), and ISDN(1 line). Sorry, no cable-modem data, but just for your information....cable is very fast but is the most unreliable data delivery method available. Please don't argue this point. We've been designing and building cable modems since 1995. There are a million ways that your data stream can be interrupted and 999,998 of them are not the game code or servers. It doesn't have to be your service provider either....crap just happens on the internet between your data termination equipment and the server's DTE. The reason you don't notice this on the ground is because the ground game is not based on real-time action. In the ground game, your computer sends a command, the server processes it and sends you the results back, your machine updates your view accordingly, and in the meantime, the stuff on your screen moves around a little to make it seem more fluid. JTL does not operate this way. Continous position data is required all the time. In all 4 of the dial-up tests, the phenomenon occurs for an additional reason(aside from the uncontrollable interruption). With dial-up, if the amount of data required for all the NPC's and players in your viewing area exceeds your DCE rate, you will see a very similar "rubber-banding" effect. In this case, the effect will clear if you fly away to a less populated area of the system.
Additionally, this phenomenon always occurs at low data rates whenever a "batch" of new ships(4-10 or so) appears at the same time(as in a duty mission). The rubber-banding will occur until the initial burst of data is recieved and only the position and "hit" data is being exchanged. V.32, V.34, V.90 and V.92 modems will also attempt to re-negotiate(retrain) the connenction when the slightest change in line conditions occur. This will also cause an interruption....and the reasons go on and on. I wish these things were not true, as JTL is my favorite part of the game....but that's the way the data squirts out. Good luck and have fun.

Here is my experiences with fixing the drunken bee syndrome.

I have two computers on a home network routed through a d-link Airplus Extreme G (DI-624) wireless router. The desktop computer is wired and the laptop is wireless. When I first installed JTL both systems worked fine - no drunken bee - but after installing some software on the desktop I all of a sudden got the drunken bee problem. Just to make sure it wasn't the web connection, I tested both my chars in space on the laptop and there was no issues.

I decided to uninstall some software and my firewall. I uninstalled Apple iTunes and then my firewall. The uninstall for the firewall locked up on me and I had to reboot. Then my home network on the desktop wasn't working at all! After pulling my hair out for about 2 hours trying different things I decided to do a system restore point. By luck my system had created one late last night. The restore was successful...it reinstalled the firewall which is not running right now...and I fired up JTL. Much to my suprise the bee problem was gone! I don't know if it will come back or not but as of right now both computers are running JTL just fine.

Note - iTunes runs services in the background and it IS installed on the laptop with no issues.

Was it the act of doing a system restore? Was there some kind of compatibility issue with iTunes and my desktop hardware? I will never know...and I don't care to reinstall iTunes to find out...I just want all my SWG stuff to work!

Here is my hardware: AMD XP 2500+, 1GB Mushkin pc2700 RAM, 2 Hitachi 170GB 7200 RPM HDDs in RAID 0, Asus a7n8x motherboard, Nvidia 6800GT

Motherboard drivers are what shipped with it, probably not the latest, running Omega drivers on the vid card.

I just thought I would throw this out on this thread...maybe someone with my similar config can try uninstalling iTunes and/or doing a system restore.

I take no responsibility if you bork your system out after tring something on your computer because of this post.

Good luck to all of you on killing the bee. I only had to deal with it for like 2 days and it ws driving me nuts...mad JTL unplayable.

look it might be a syncing problem but it looks like the models are gotting ahead of the center of rotation of the rotatien information thats being provided for each model, so the effect is a model swung around as though attached to a manuvering invisable model by a long stick of increasing length.
warping from system to system dosnt fix it sometime unplugging and replugging the joystick will do it. sometimes i can just patch drict x or video drivers and do it but iv turned off and off all the detail all the mouse acceleration and im too the point where im holding sayonces tarot reading and burning offerings. this is some intermitent bug. dont they people play there own game?
dont they have testors.

---

openploper wrote:
OK...I know that no one wants to hear this. I've been studying this problem since day 1. And guess what, day 1 was before any patch or upgrade to the game. I finally brought home a carrier line analyzer from work to test my theory and it seems to be true. I'm not saying that a software problem is completely impossible but I have enough evidence now to say with a high level of certainty that: The warping issue is directly related to an interruption in the continuous data stream that is required for space ships to move about your screen smoothly. I've verified the phenomenon on DSL(1 line), Dial-up(4 lines), and ISDN(1 line). Sorry, no cable-modem data, but just for your information....cable is very fast but is the most unreliable data delivery method available. Please don't argue this point. We've been designing and building cable modems since 1995. There are a million ways that your data stream can be interrupted and 999,998 of them are not the game code or servers. It doesn't have to be your service provider either....crap just happens on the internet between your data termination equipment and the server's DTE. The reason you don't notice this on the ground is because the ground game is not based on real-time action. In the ground game, your computer sends a command, the server processes it and sends you the results back, your machine updates your view accordingly, and in the meantime, the stuff on your screen moves around a little to make it seem more fluid. JTL does not operate this way. Continous position data is required all the time. In all 4 of the dial-up tests, the phenomenon occurs for an additional reason(aside from the uncontrollable interruption). With dial-up, if the amount of data required for all the NPC's and players in your viewing area exceeds your DCE rate, you will see a very similar "rubber-banding" effect. In this case, the effect will clear if you fly away to a less populated area of the system.
Additionally, this phenomenon always occurs at low data rates whenever a "batch" of new ships(4-10 or so) appears at the same time(as in a duty mission). The rubber-banding will occur until the initial burst of data is recieved and only the position and "hit" data is being exchanged. V.32, V.34, V.90 and V.92 modems will also attempt to re-negotiate(retrain) the connenction when the slightest change in line conditions occur. This will also cause an interruption....and the reasons go on and on. I wish these things were not true, as JTL is my favorite part of the game....but that's the way the data squirts out. Good luck and have fun.

---

Here are the problems I have with your reasoning:

1. I've been playing online games for years and have never ever had a recurring issue like this. I've had connection problems before, but they never lasted. They were the exception, not the norm. The opposite is true in JtL. Rarely do I have an entire session go smoothly. If my connection (with my consistent 0% packet loss and 105ms ping) is the problem then they need to optimize their code. Maybe they could talk to the people working on Planetside. Even World War II Online ran better for me.

2. I have two computers right next to each other. My brother plays on one, I play on the other. He has never had this problem. Ever. Not one single time. He is on the same internet connection as me, behind the same firewall, connected to the same switch. I always have this problem. He never has this problem. We will be grouped together fighting in the same dogfight and it happens to me, while still being 100% playable for him.

I tried it on an older computer I had and it ran well. The problem is this computer is much, much slower than the computer I'm currently using. My framerates were horrible, but at least I could actually hit something.

I don't know what's causing it, but the one thing I am certain of is that it's not my connection.

---

ClabeBobea wrote:

My cable modem doesn't have a firewall, and I do not believe my router has one either. Since its only a piecer D-link

---

actually, a NAT/Firewall is pretty much standard for the D-Link.....

Sorry for the bump but people are still having this issue, and it seems to be motherboard related. However, somebody said this (http://forums.station.sony.com/swg/board/message?board.id=Techsupport&message.id=223141) might fix it. I've also seen people saying that when they have dxdiag open in the background the problem is severely reduced.