Original thread - http://forums.station.sony.com/ps2/...s-the-other-problems-flying-everywhere.87669/ Purpose of this thread is simple, collate information about the desync issues and list the currently known work arounds. This is the issue. The issue appears to be at least largely related to CPU clock instability, whether this comes from OCing, or windows constantly slightly changing the clock speed. Its not clear and seems to differ slightly in each case. credit to SonicXVe for first noting this. What then happens is the gamespace the client 'thinks' and the sever progressively get more and more out of sync. to the point where relative to each others frame of reference, the player experiencing the issue and/or the world around him can quite literally be all over the place. stuff flashing in and out of existence, people warping across the sky, rubberbanding, the game giving you a pain field as the server registers you as in the enemy spawn despite being 40 meters away. Its also worth noting that, even if you don't overclock. Windows/your motherboard can sometimes make small changes to your CPU's clock speed It also often results in a rather nasty case of 'FPS destroying, flashing world bug' (I had this happen a few times, but not always). N.B CAREFUL research the **** out of any OC or bios changes BEFORE you do them, be confident you know what your doing and how to reverse it if things go wrong, your an idiot if you don't just spend 10 minutes googling something before fiddling around with your computer. Also make no mistake, this is a bug, the development team are aware of it, and are trying to fix it. These are work arounds not fixes. Work arounds- confirmed to be helping some people at the moment. 1) Either engaging a downclock (this Is what i've been doing running my fx 8350 at 4.1) or forcing a stable overclock in your bios. 2) If you have a asus board, disabling epu-6 if said board has it. Also any similar features to do with dynamic power saving on the motherboard could be what is causing trouble in the game engine, try disabling it. 3) Making sure your computer is using high performance or gaming mode in windows power plan (this alters CPU clock speed). 4) One we are currently experimenting with (and if people could post their experiences that would help). http://forum.notebookreview.com/asu.../568525-setfsb-game-timing-problem-g60jx.html Credit to BenYeeHua here. It appears to force the Windows OS to use a more reliable method of measuring the CPU clock, this appears to be helping people for whom 1-3 have not worked.