Print Page - Cavalry rubberbanding with WSE2

I've been having a really severe rubberbanding problem when playing cavalry with WSE2 beta enabled, ever since reinstalling cRPG around the end of December. I've had the warband cav desync bug before, where you warp around the map until you let go of all your keys, but this is different.

Basically, once the problem starts, my character (this starts on horseback but if I get dismounted will continue on foot) will cease moving client-side and just perform the run (or horse rear, or whatever) animation in-place. When I push down a new key, I teleport to wherever I'm actually supposed to be on the server. This affects basically everything my character does, including typing. I can type out a message, but if I don't tap a movement key, it won't appear server-side (at least as far as I can tell). Also, when typing, whenever I hit the 'n' key, I get the 'too off balance to quick draw' message. Once I'm dead, I can move my camera and spectate as normal. The only caveat is that if I died while stuck, everything I type while dead won't show up until the round ends, even if I move the camera around.

I have never had this problem without getting on a horse. Once I get on and it starts, however, I have to disconnect from the server to get it to stop entirely. It will go away if I run into an object and wait a little bit, but it inevitably comes back once I start moving around again, regardless of whether I'm on foot or on a horse. This includes (at least last time I checked) round changes. I should note that this problem isn't intermittent. It happens every time I get on a horse and have WSE2 enabled.

I've uninstalled, reinstalled, changed ports, forwarded ports, changed firewall settings, done packet loss tests to my router to Google, and to c-rpg.net, and haven't found a problem. I also ran the game without WSE2 and didn't have an issue. As I thought this was a network issue originally, I took some network graph screencaps while I was playing with nothing network heavy in the background:

(click to show/hide)

I went ahead and screwed around with the iUdpReceiveBufferSize and iUdpSendBufferSize parameters in the config file, lowering them to 32768 from 262144. I didn't take a network graph, but it seemed to smooth out the network performance a little bit. It unfortunately didn't help with the rubberbanding thing.

The only other potentially relevant thing I can think of is that I know I'm not the only one to get this, I believe Brontosaurus_FIDLGB mentioned having the same issue.

I'm also attaching the IRC log between me, Tydeus, and a couple other people as we tried to figure this out just in case I forgot any details.

(click to show/hide)

This is cray.
Then only rubberbanding I get as cav is when I slow down, it will rubberband for ~5 seconds most of the time. It happens most often when enemies are near, so this is pretty gol'dern irritating.

Well, that was enlightening. I tried to FRAPS the problem, and just couldn't do it. It wouldn't happen even though up to this point it has occurred every time I've been on a horse with WSE2 enabled.

I noticed something, though. My look sensitivity is much, much lower when running FRAPS. My framerate drops from 50 to 30. That leads me to believe that the game logic loop and render loop in the engine aren't separate.

So... I turned off FRAPS. The bug appeared within maybe five seconds. I turned on FRAPS hoping that it would stick around but once my framerate dropped from recording it went away again. I did catch a single teleport at the beginning of the video, though:

http://www.youtube.com/watch?v=LoVohqMZ2Y4

Up until recently I hadn't had the problem (it used to happen 6+ months ago). It happened again a few times yesterday while playing. It only happens when you collide with something (or run over infantry), or brush past another horse.

Yeah I noticed collision seems to trigger it. I haven't been able to pin down exactly how, but it seems different from the native horse collision bug. It also seems to (occasionally) happen with regular terrain and just general changes in horse speed, too.

yeah I don't think it's necessarily the collisions that trigger it, I'd guess it's the change in horse speed as well.

Try a different (or no) router dawg

At least try setting up a DMZ on your router, that fixes tons of stupid shit for me in online games

It's the game dawg, wasn't happening for months and started recently (only noticed it a couple times). Also before it started originally happening I had played (same hardware and network connection) for over a year without ever encountering the issue (riding a horse the whole time). It only started after WSE2 came out, and it was fixed for at least 6 months. Specifically I think it happened after they tweaked all the charge values of horses. I only ride a courser, so only noticed it on my courser. I know some other people posting were not on destriers or armored horses (they were also on light horses), so maybe it's a light horse issue only.

There's been quite a few threads with lots of people saying that it has happened to them. It's only really noticeable when riding a horse, and after colliding with something, and most of the time when you collide with infantry or brush past a horse, it doesn't happen (at least when it was a problem that was the case).

this bug happens to me often when I bump people, and ALWAYS when I use the swing animation of the long hafted blade on horse back.

I tried 2h cav with morningstar and shortened military scythe last week and I just wouldn't stop rubberbanding like crazy all the time. Unplayable.

Quote from: Torben on January 27, 2014, 09:46:25 pm

this bug happens to me often when I bump people, and ALWAYS when I use the swing animation of the long hafted blade on horse back.

Yeah the main time I see it, is after I've bumped an infantry player. But again, most of the time it doesn't happen. If it's going to happen, that's usually when it happens. The other time I notice it, is when I "brush up" against another horse when we're going pretty fast (just barely miss each other).

So came back to testing again today. Came into the server, got the bug, flipped on vsync, bug remained, disconnected, tried to rejoin, got an application crash, relaunched, verified vsync was still on, joined the server, and I've been fine ever since.

Yay!

so we activate vsync in graphics options and cross fingers?

Quote from: Torben on January 30, 2014, 01:08:37 pm

so we activate vsync in graphics options and cross fingers?

Yeah. This seems similar framerate compensation rubberbanding bug that happened way back when WSE2 was first released. Really variable framerate is what caused the bug the first time around, though I had a locked and stable 50 FPS, so I'm not sure what was triggering it now. Vsync fixed it for me. One of my friends (who didn't have the bug) turned vsync on and had the problem start happening to him, so he switched back.

I'd try it and see if it helps.

You're right. VSync fixes it. Thanks for sharing.

vsync made it happen for me. can play the game on high res again, almost no problems. less then ever actually. yay xol!

In-game VSync makes the game unplayable for me (so slow as if the screen were "sedated") and forcing vsync with third-party program won't fix the cav rubberbanding. I hope there's another way to fix this issue.

Edit: I think that it's just EU_7 lagging, because I just got rubberbanding on foot without ping changes, and the server has crashed like 5 times since yesterday.

Forcing Vsync with 3rd party program works just fine too.

cRPG

Beta => WSE2 Beta => Topic started by: Xol! on January 27, 2014, 04:46:15 am