Jump To Lightspeed Archive
Thread: An Update About Warping(Rubber-banding)
Page 2 of 2
Lomier
Sun Jan 16, 2005 8:12 pm
#14
Kylroi wrote:
Funny you should say that. I've been doing tech work for more than 10 years (I predate the 486 in the tech world and remember when the 386 was the new kid), and more than 50% of the time, it's an Intel chipset that I do have to get working right. Now, that's a mix of percentages (more Intel based systems being used versus other brands) and poor choice of platform for the application. As you did point out, though, speed isn't always the important factor. Thus the reason I said servers are best on Intel. They are, typically, more dependant on raw staying power than speed. Most hardcore gamers, however, are more about squeezing every extra frame per second out of their system as they can.
Trust me, I wish it was as simple as a chipset issue here, or a connection issue. The fact that does hold true for this is that we all broke with a game update (some of us broke at different hotfixes or publishes). No hardware has been found in common with everyone suffering from this. No software appears to be common, either. Connection type varies, and seems to not matter as some users have noted systems both having and not having this issue while both use the same internet connection. The fact that changing external (to the game) software/drives can and has corrected the problem is what really bothers me. The only thing I can think of that would allow that sort of change to influence things is if SWG (and other software, for that matter) are using certain regions of memory space or specific system calls that should not be directly used. I would just like to see the exact cause narrowed down with some sort of workaround or fix.
Ah yes I do have fond memories of my AMD 386DX 40MHz system.
Those were the days... Anyway I do agree that it would be nice to have aresolution to this problem. It will be interesting to see what the final solution is.
Those were the days... Anyway I do agree that it would be nice to have aresolution to this problem. It will be interesting to see what the final solution is.
hobieone
Mon Jan 17, 2005 12:39 pm
#15
S-1-l2-H-C wrote:i agree 100% this is caused by a connection issue.but i have used dialup dsl and cable and BY FAR my cable is the most reliable. ive never had any trouble with my cable connection.
i also agree it must connection also adisagree about cable connection being unreliable i move to a new apartment recently had to switch to dsl and a ihate the dsl connection. the cable connection not only was faster it was heell of alot more stable than this dsl.
SanRa_Ledav
Mon Jan 17, 2005 3:16 pm
#16
Can't be a connection issue guys.
My wife and I are on a LAN sharing the same cable connection.
We have identical machines except she is running Windows 2000, and I am running XP.
Also, she has had a GFFX 5200LE card for quite some time.
At first launch of JTL she had the warping issue, and I didnt.
Her machine was overdue for a reformat and re-install. She's never had the issue since.
We've played at the same time to test if it was a connection issue.
She runs smooth, and since I went from my GF3 Ti200 to the GFFX 5900XT, I get the drunken bees far too often nowadays for JTL to be worth anything other than cheap travel between planets.
Maybe I'll bring my machine to work and hook it into the OC-192. We'll see what happens.
My wife and I are on a LAN sharing the same cable connection.
We have identical machines except she is running Windows 2000, and I am running XP.
Also, she has had a GFFX 5200LE card for quite some time.
At first launch of JTL she had the warping issue, and I didnt.
Her machine was overdue for a reformat and re-install. She's never had the issue since.
We've played at the same time to test if it was a connection issue.
She runs smooth, and since I went from my GF3 Ti200 to the GFFX 5900XT, I get the drunken bees far too often nowadays for JTL to be worth anything other than cheap travel between planets.
Maybe I'll bring my machine to work and hook it into the OC-192. We'll see what happens.
JAtMtracer
Mon Jan 17, 2005 9:57 pm
#17
Just a note on a previous fix that has worked for some people (was posted in the tech support forum a week or 2 ago). It turns out, that in some cases, such as mine where I would the dreaded bumble-bee, if you open up dxdiag and let itn run in the background, it takes care of the problem 99% of the time....I rarely get out of sync using this method. I'm running a Giga-byte 6800 atm, but my ati 9500 pro had the bumblebee effect as well... Another note is that the in/out can go above 2000 and I still can keep the sync intact, whereas before if I ventured that high the bumblebee would appear.
Page 2 of 2