Very jerky movement at high framerates

[Niosop]

I'm not sure when this started happening. Whenever I move around in the editor using WSAD, the movement is VERY jerky. It seems like it's moving forward X amount then back X/3 the next frame. I tried to get a video of it, but FRAPS decreased the framerate to about 30 at which time the jerkiness disappears. If I turn on vsync it goes away. Becomes very noticeable at 100 FPS and the higher the FPS is the worse it gets. Adjusting the movement speed or smoothing doesn't help any. It doesn't happen when using the scroll wheel to zoom in or out, only when using the keyboard to move forward/backward or pan. It does NOT affect game mode at all, regardless of framerate, only movement in edit mode.

 

Anyone else affected by this or have suggestions?

[Scott Richmond]

This is just a complete hunch, but if you're using KeyHit() / KeyDown maybe the keyboard isn't being polled quick enough. What I mean to say is, KeyHit() captures the key that was hit and then resets afterward. So at a speed of 100FPS, you might be finding that some frames turn up an empty KeyHit() because it hasn't polled the keyboard yet.

[Niosop]

Well, I'm not actually using anything I'm just trying to edit a scene. But I doubt it's that because it's actually moving backwards every other frame or something. If I have an oildrum or something in the scene and try and move around, I'll see two of them, both somewhat translucent as if it's drawing it one frame, then the camera is jerked backwards for the next frame, then forwards a little more than the initial frame, etc.

[Marleys Ghost]

Well, I'm not actually using anything I'm just trying to edit a scene. But I doubt it's that because it's actually moving backwards every other frame or something. If I have an oildrum or something in the scene and try and move around, I'll see two of them, both somewhat translucent as if it's drawing it one frame, then the camera is jerked backwards for the next frame, then forwards a little more than the initial frame, etc.

 

 

How complicated a scene Niosop? am trying to recreate your problem but can't, not sure if I have enough "stuff" in it

[cocopino]

I've seen similar behavior after trying to save with ctrl+S. When hitting S again and immediately releasing it (or ctrl, can't remember) the editor started working again properly. In that case, the problem probably has to do with keyup() not being registered. But if it only occurs at framerates > 100... Run the editor in 1920x1080, turn on all posteffects and jam more stuff into your scene

[Marleys Ghost]

I've seen similar behavior after trying to save with ctrl+S. When hitting S again and immediately releasing it (or ctrl, can't remember) the editor started working again properly. In that case, the problem probably has to do with keyup() not being registered. But if it only occurs at framerates > 100... Run the editor in 1920x1080, turn on all posteffects and jam more stuff into your scene

 

1280 x 1024 is my max resolution. but even with all post FX (which I had on already), keeping the frame rates above 100 .. with a lot of stuff already I can't replicate the issue.

[Niosop]

How complicated a scene Niosop? am trying to recreate your problem but can't, not sure if I have enough "stuff" in it

 

It does it with a totally empty scene. I can just throw in an oildrum for reference and it'll do it. Only thing I haven't tried is restarting my computer (which should have been the first thing I tried), should be able to reboot first thing tomorrow.

[Marleys Ghost]

It does it with a totally empty scene. I can just throw in an oildrum for reference

 

it will take some work but I think I can manage to emulate that scene trying it now..

[Niosop]

Well, if you don't see it when you have >100 FPS, then it's probably isolated to just me. I was seeing it in all the included maps (when I was in a position to get >100 FPS) and in ones I built myself.

 

It's not a big deal, I can just turn on vsync and the problem goes away, just curious if anyone else was seeing it.

[Marleys Ghost]

Well, if you don't see it when you have >100 FPS, then it's probably isolated to just me. I was seeing it in all the included maps (when I was in a position to get >100 FPS) and in ones I built myself.

 

It's not a big deal, I can just turn on vsync and the problem goes away, just curious if anyone else was seeing it.

 

 

Nope sorry m8, I don't get the problem, thats not to say I wont, but have not yet managed to.

[TylerH]

This is the same problem I am getting, which is casing the animation issues in Weaponwerks.

[ZeroByte]

Same problem here too, vsync on it's smooth, vsync off jerky.

[Scott Richmond]

Okay. You guys might want to post full config details - resolution, SSAO/HDR/etc.

[Niosop]

Doesn't matter, any resolution, any options on/off as long as they don't cause the framerate to drop below 80 or so. At that point it still happens, but it's not really noticeable. At around 60 you don't notice it at all. And only in the editor in edit mode for me. If I go into game mode inside the editor, it goes away even at high FPS.

[TylerH]

I still get it in game mode, it affects anything to do with AppTime or AppSpeed or intense physics, i.e. animation.

[Niosop]

I was finally able to reboot my system and the movement problem in the editor went away....go figure.

[TylerH]

Yeah, restarting fixes it.

[diedir]

just discover this topic and i was concerned too with this

can confirm that after reboot problem disappear

[TylerH]

This would lead me to believe that over time Leadwerks Editor is like clogging your VRAM or something that gets cleared on a restart or shutdown?

 

This has existed since the first version of Sandbox, atleast for me, so that makes the most sense.