Rubberbanding since Spring Festival Update when using Crossover 19

[Gwendeil]

So, since the update that brought in the Spring Festival, I've been experiencing aggressive rubberbanding where I suffer through it at least twice every five minutes. I have to give corners a wide berth or I will find myself behind it again. I redownloaded this game already and it didn't help. Standing Stone Customer Service couldn't help.

Does anyone have any tips on how to fix this? Or do I have to wait until the next update? Has anyone else been suffering through this? Please help!

[Tralfazz]

So, since the update that brought in the Spring Festival, I've been experiencing aggressive rubberbanding where I suffer through it at least twice every five minutes. I have to give corners a wide berth or I will find myself behind it again. I redownloaded this game already and it didn't help. Standing Stone Customer Service couldn't help.

Does anyone have any tips on how to fix this? Or do I have to wait until the next update? Has anyone else been suffering through this? Please help!

Hi, Gwendeil!

Rubberbanding occurs when there is a desync between the client and the server. The server decides what is "really" happening but the client "guesses" what is happening until the next update packet is received from the server. When the guess doesn't match the packet data, or the packet data is delayed, the player experiences a pause, or "jump", or rubberbanding. It isn't a problem with your game files or your Crossover bottle. It is usually a result of server overload or local network issues. It can also occur when your CPU is bottlenecked and can't keep up with all the demands being made on it.

If people you are playing with or, if you're playing alone, other folks on your server in your general area aren't also complaining about rubber banding, then the issue is on your end. And it is most likely due to a local network issue although it could be due to some process demanding priority from your CPU.

Let's do the simple thing first and reset your local network: Starting from the furthest "downstream" device, which would be your computer, shut everything down. So first your computer, then your router/wifi device, then your ISP link point (for most people that is their cable modem). You might have one or two other things in between but most people have computer->router->cable modem. Once everything is off, wait two full minutes. Then starting from the most "upstream" device, which in most cases is the cable modem, turn everything on. Turn everything on one thing at a a time, allow each device to fully boot before moving on to the next device downstream. You can tell when a device is fully booted by checking its status lights or, if you can't read the status lights for some reason, just give each one two full minutes before moving on to the next one.

Next, check your computer for things that could be mucking things up: Do you have a virus checker? Turn it off or uninstall it. You don't really need one on a Mac, anyway, certainly not full time. Do you use MacKeeper or MacCleaner or Mac-whatever-supposed-to-make-your-Mac-better? Definitely disable it and, better, uninstall it because all of these things are garbage.

Finally, while you're running Crossover and LOTRO, quit out of any other applications. Check your menu bar, some applications won't appear in your Dock but can be managed from the menu bar. Most applications are well-behaved and won't use too many processor cycles when they're idle and in the background. Others are either poorly coded or are purposely coded to sometimes run a high-priority process which will prevent other applications from getting their fair share of CPU time. If you usually have some voice chat program running while you play, try running without it for a little while to test whether it might be the cause of your problem. Last thing to try in this category is to run LOTRO in ScreenMode=Windowed with Activity Monitor open and sort running processes by %CPU descending. When you get some rubberbanding, look for the name of a process which causes your %CPU to go very high – perhaps even over 100%.

Hopefully a simple local network reset will do the job for you! If not, one of the subsequent steps. If you try everything I suggest above and you continue to get rubberbanding, report back here and include your exact model of Mac, the amount of RAM you have, the version of MacOS you are using, and the version of Crossover you are using.
edit: It will also be helpful to know if you are running the 32-bit or 64-bit excecutable; if you don't know, look in your UserPreferences64.ini file for the line GameClientType=X where X is the numeral 1, 2, or 3 – 1 is the 32-bit, 3 is the 64-bit.