Telanor

If you play the animation instantly it will appear to happen quickly. If you wait for the server to confirm new entities the arrow will appear mid-air which might not even be noticeable.

Hmm, I suppose that is true. I'll give it a try and see how it works out.

I think you just need to read through some different techniques and choose the one you like the most there tons of tutorials and examples out there. My personal favorit is Variance Shadow Mapping:
http://www.punkuser.net/vsm/
It is easy to implement and easy to combine with CSM or Parallel Splits or whatever you choose and gives the possibility to use linear filtering methods, gauss and even MSAA.

I worked on point light shadow maps a while ago and I was using VSM. It works fine for directional lights, which is what every single tutorial in the world implements, but then when I tried to make it work for point lights, I couldn't figure out how to apply the Gaussian blur to the cubemap. I tried Dual Paraboloid Shadow Mapping but never got it working for some reason, I don't remember what it was now. But dual paraboloid has very noticeable seams (skyrim seems to have used that technique and the seams stood out very clearly), so I'd rather avoid that technique.

Aren't screen space reflections only suited to smaller indoor areas? And how would you use a single cubemap work for all the different reflections?

It's not so much flowing water we're trying to deal with but rather lots of flat pools of water on different planes. How do you get proper reflections for all of them without having to render the scene for each pool individually?

Wow, it actually works. I think that last line, the worldPos /= worldPos.w was the key. The depth /= (NearPlane*FarPlane/(FarPlane-NearPlane)) line doesn't seem to have any effect that I can notice though. Thanks for you help!

Ok so I guess since we're not doing a fully deterministic simulation, we'll have to wait on the server for random based stuff, but the rest of it should be predicted.

The light seems to behave exactly the same with or without the negative. I have to be inside the radius to see it and it moves around weirdly when I look around.

Doesn't seem to be working for me. What is PSIn.ProjPos? Is it the screen position? I have this on the first line of my pixel shader:

input.ScreenPosition.xy /= input.ScreenPosition.w;

Is that still correct to do? Also, this is how my depth is written:

output.Position.z = log(0.001 * output.Position.z + 1) / log(0.001 * FarPlane + 1) * output.Position.w;

That's in the vertex shader for the GBuffer rendering. Is that the same as what you're using?

And to answer your question, I think the vertex density for our world is high enough that we don't really get that issue. If you stick your face into a block, then you see it, but anyone doing that deserves some visual glitches . We're not using a 32bit buffer even, just the standard 24 bit one

Yep, it's the only tool I can currently use.  Unfortunately it doesn't support texture arrays, mipmaps, doesn't seem to have performance metrics, randomly tries to open some render targets in photoshop (which appear pure black), and fudges number values during shader debugging (it 's shown me 0.000 for a number that was actually a QNAN).  Overall it's about the worst debugging tool of the ones available, but the only one that will even run.

Wouldn't both of those require manually writing the depth from the pixel shader and losing all the early-z culling? I feel like there should be a way to do it without that...

AMD perf studio, Nvidia NSight, and PIX all crash on load for DX11.1 applications

 

This is what the depth is coming out as after reversing it:

 

Mind you it is being run through the HDR/bloom pipeline, but that pretty much seems to match what I'm seeing with the fog settings (requiring me to set it to go from 0.001 to 0 in order to get anything reasonable).  It certainly did reverse it, but without any precision gain what-so-ever.

I couldn't find any actual tutorials on how to do reversed z-depth so I just tried switching the near and far values on the viewport and changed the depth comparison to GreaterEqual. DirectX promptly yelled at me for having a viewport with a MinDepth > MaxDepth. It renders but fog stopped working and if I look at the depth buffer in the debugger, it's just pure black (though who knows if it's actually even showing me the right thing, the debugger is so buggy I wouldn't be surprised if it isn't). Reversing the fog distance values (from .999-1 to 0.1-0) results in a 100% fog covered scene.

I also tried the suggestion from that blog for the log depth, I couldn't get that to work either. I'm not really sure when/if I'm still supposed to do the position/w part. I tried it with and without, in different places, among other things. Pretty much all I get is a light that is invisible until your actually inside its radius, and then you see some not-very-correct shading.

Pressing ctrl+shift+c in Intel GPA doesn't do anything either. It's pretty much as if the program isn't running at all.

It's not that I'm trying to make things perfect. If you saw how the game is acting currently, you'd understand. It's simply unacceptable, no one would want to play with this amount of jittering on a local connection. Every other game runs nearly flawlessly under ideal network conditions, I don't see why ours shouldn't.

HPlus: About the dejitter buffer, I gave it a try before and it seemed to make it a bit worse, but it's probably because I screwed something up. I'll look at it some more and see if I can find what I did wrong.

Well, we switched to a much speedier compression algorithm, offloaded the decompression on the client to a thread and fixed a loading bug that made the server hit 100% cpu usage. And yet there's still issues with the prediction. If you rapidly tap A and D, you jitter around a lot. The ticks are still going out of sync a little bit once in a while but it still has issues even when there hasn't been a desync for a little while.

In the log below you can see it goes for a couple seconds without a desync and yet continues to have prediction errors fairly frequently. Is a de-jitter buffer and/or locking input a requirement for fixing this up, even though this is happening locally?

[12/17/2012 11:24:29 PM]: Tick offset for tick 8165 was -1
[12/17/2012 11:24:29 PM]: Adjusting.  Current = 8169, New = 8170
[12/17/2012 11:24:29 PM]: Tick offset for tick 8166 was -1
[12/17/2012 11:24:30 PM]: Tick offset for tick 8167 was -1
[12/17/2012 11:24:30 PM]: Tick offset for tick 8168 was -1
[12/17/2012 11:24:30 PM]: Tick offset for tick 8170 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8170.  Client: [X:1069.422 Y:1000 Z:-1055.922], Server: [X:1070.326 Y:1000 Z:-1074.743], Diff: [X:-0.9041748 Y:0 Z:18.82068]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8171 from [X:1070.25 Y:1000 Z:-1073.157] to [X:1071.154 Y:1000 Z:-1091.978]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8172 from [X:1069.517 Y:1000 Z:-1057.908] to [X:1070.422 Y:1000 Z:-1076.729]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8173 from [X:1068.696 Y:1000 Z:-1040.802] to [X:1069.6 Y:1000 Z:-1059.622]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8171 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8171.  Client: [X:1071.154 Y:1000 Z:-1091.978], Server: [X:1071.925 Y:1000 Z:-1108.034], Diff: [X:-0.7711182 Y:0 Z:16.05652]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8172 from [X:1070.422 Y:1000 Z:-1076.729] to [X:1071.193 Y:1000 Z:-1092.785]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8173 from [X:1069.6 Y:1000 Z:-1059.622] to [X:1070.371 Y:1000 Z:-1075.679]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8174 from [X:1069.582 Y:1000 Z:-1059.261] to [X:1070.354 Y:1000 Z:-1075.318]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8172 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8173 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8174 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8174.  Client: [X:1070.354 Y:1000 Z:-1075.318], Server: [X:1069.526 Y:1000 Z:-1058.094], Diff: [X:0.8272705 Y:0 Z:-17.22363]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8175 from [X:1070.148 Y:1000 Z:-1071.042] to [X:1069.321 Y:1000 Z:-1053.818]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8176 from [X:1069.515 Y:1000 Z:-1057.863] to [X:1068.688 Y:1000 Z:-1040.639]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8177 from [X:1068.763 Y:1000 Z:-1042.213] to [X:1067.936 Y:1000 Z:-1024.99]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8175 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8176 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8177 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8178 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8178.  Client: [X:1067.966 Y:1000 Z:-1025.608], Server: [X:1066.328 Y:1000 Z:-991.5042], Diff: [X:1.638184 Y:0 Z:-34.1037]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8179 from [X:1067.217 Y:1000 Z:-1010.029] to [X:1065.579 Y:1000 Z:-975.9248]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8180 from [X:1067.136 Y:1000 Z:-1008.342] to [X:1065.498 Y:1000 Z:-974.2383]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8181 from [X:1067.136 Y:1000 Z:-1008.342] to [X:1065.498 Y:1000 Z:-974.2383]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8179 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8180 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8181 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8182 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8183 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8184 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8184.  Client: [X:1067.097 Y:1000 Z:-1007.527], Server: [X:1067.927 Y:1000 Z:-1024.796], Diff: [X:-0.8295898 Y:0 Z:17.26898]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8185 from [X:1067.845 Y:1000 Z:-1023.104] to [X:1068.675 Y:1000 Z:-1040.373]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8186 from [X:1068.676 Y:1000 Z:-1040.389] to [X:1069.505 Y:1000 Z:-1057.658]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8187 from [X:1069.419 Y:1000 Z:-1055.867] to [X:1070.249 Y:1000 Z:-1073.136]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8185 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8186 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8186.  Client: [X:1069.505 Y:1000 Z:-1057.658], Server: [X:1068.735 Y:1000 Z:-1041.622], Diff: [X:0.7703857 Y:0 Z:-16.03638]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8187 from [X:1070.249 Y:1000 Z:-1073.136] to [X:1069.479 Y:1000 Z:-1057.1]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8188 from [X:1070.231 Y:1000 Z:-1072.771] to [X:1069.461 Y:1000 Z:-1056.734]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8189 from [X:1070.975 Y:1000 Z:-1088.262] to [X:1070.205 Y:1000 Z:-1072.225]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8187 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8187.  Client: [X:1069.479 Y:1000 Z:-1057.1], Server: [X:1070.326 Y:1000 Z:-1074.738], Diff: [X:-0.84729 Y:0 Z:17.63806]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8188 from [X:1069.461 Y:1000 Z:-1056.734] to [X:1070.308 Y:1000 Z:-1074.372]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8189 from [X:1070.205 Y:1000 Z:-1072.225] to [X:1071.052 Y:1000 Z:-1089.863]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8190 from [X:1070.255 Y:1000 Z:-1073.265] to [X:1071.102 Y:1000 Z:-1090.903]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8188 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8189 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8190 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8190.  Client: [X:1071.102 Y:1000 Z:-1090.903], Server: [X:1072.725 Y:1000 Z:-1124.681], Diff: [X:-1.622559 Y:0 Z:33.77771]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8191 from [X:1071.121 Y:1000 Z:-1091.284] to [X:1072.743 Y:1000 Z:-1125.062]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8192 from [X:1070.371 Y:1000 Z:-1075.674] to [X:1071.993 Y:1000 Z:-1109.452]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8193 from [X:1069.548 Y:1000 Z:-1058.543] to [X:1071.17 Y:1000 Z:-1092.32]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8191 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8192 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8192.  Client: [X:1071.993 Y:1000 Z:-1109.452], Server: [X:1073.516 Y:1000 Z:-1141.149], Diff: [X:-1.522583 Y:0 Z:31.69714]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8193 from [X:1071.17 Y:1000 Z:-1092.32] to [X:1072.693 Y:1000 Z:-1124.017]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8194 from [X:1071.141 Y:1000 Z:-1091.698] to [X:1072.663 Y:1000 Z:-1123.395]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8195 from [X:1070.228 Y:1000 Z:-1072.697] to [X:1071.75 Y:1000 Z:-1104.394]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8193 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8194 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8195 was 0
[12/17/2012 11:24:30 PM]: Tick offset for tick 8196 was 0
[12/17/2012 11:24:30 PM]: Position error for tick 8196.  Client: [X:1071.683 Y:1000 Z:-1102.996], Server: [X:1069.526 Y:1000 Z:-1058.095], Diff: [X:2.15686 Y:0 Z:-44.90027]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8197 from [X:1070.936 Y:1000 Z:-1087.443] to [X:1068.779 Y:1000 Z:-1042.543]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8198 from [X:1070.214 Y:1000 Z:-1072.402] to [X:1068.057 Y:1000 Z:-1027.502]
[12/17/2012 11:24:30 PM]: Adjusting position at tick 8199 from [X:1069.392 Y:1000 Z:-1055.3] to [X:1067.235 Y:1000 Z:-1010.4]
[12/17/2012 11:24:30 PM]: Tick offset for tick 8197 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8198 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8199 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8200 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8201 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8202 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8203 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8204 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8205 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8206 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8206.  Client: [X:1068.765 Y:1000 Z:-1042.243], Server: [X:1067.927 Y:1000 Z:-1024.802], Diff: [X:0.8378906 Y:0 Z:-17.44116]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8207 from [X:1069.588 Y:1000 Z:-1059.385] to [X:1068.75 Y:1000 Z:-1041.944]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8208 from [X:1070.415 Y:1000 Z:-1076.597] to [X:1069.577 Y:1000 Z:-1059.155]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8209 from [X:1071.18 Y:1000 Z:-1092.521] to [X:1070.342 Y:1000 Z:-1075.08]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8207 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8208 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8209 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8210 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8210.  Client: [X:1070.365 Y:1000 Z:-1075.551], Server: [X:1071.135 Y:1000 Z:-1091.58], Diff: [X:-0.7700195 Y:0 Z:16.02966]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8211 from [X:1071.23 Y:1000 Z:-1093.553] to [X:1072 Y:1000 Z:-1109.583]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8212 from [X:1071.887 Y:1000 Z:-1107.237] to [X:1072.657 Y:1000 Z:-1123.266]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8213 from [X:1071.942 Y:1000 Z:-1108.375] to [X:1072.712 Y:1000 Z:-1124.404]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8211 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8212 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8213 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8213.  Client: [X:1072.712 Y:1000 Z:-1124.404], Server: [X:1073.525 Y:1000 Z:-1141.331], Diff: [X:-0.8131104 Y:0 Z:16.92664]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8214 from [X:1072.645 Y:1000 Z:-1123.016] to [X:1073.458 Y:1000 Z:-1139.942]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8215 from [X:1071.871 Y:1000 Z:-1106.901] to [X:1072.684 Y:1000 Z:-1123.827]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8216 from [X:1071.129 Y:1000 Z:-1091.463] to [X:1071.942 Y:1000 Z:-1108.389]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8214 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8215 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8216 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8217 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8217.  Client: [X:1071.871 Y:1000 Z:-1106.911], Server: [X:1070.326 Y:1000 Z:-1074.742], Diff: [X:1.545288 Y:0 Z:-32.16858]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8218 from [X:1071.095 Y:1000 Z:-1090.756] to [X:1069.55 Y:1000 Z:-1058.588]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8219 from [X:1071.143 Y:1000 Z:-1091.742] to [X:1069.597 Y:1000 Z:-1059.573]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8220 from [X:1071.143 Y:1000 Z:-1091.742] to [X:1069.597 Y:1000 Z:-1059.573]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8218 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8218.  Client: [X:1069.55 Y:1000 Z:-1058.588], Server: [X:1070.326 Y:1000 Z:-1074.738], Diff: [X:-0.7758789 Y:0 Z:16.1499]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8219 from [X:1069.597 Y:1000 Z:-1059.573] to [X:1070.373 Y:1000 Z:-1075.723]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8220 from [X:1069.597 Y:1000 Z:-1059.573] to [X:1070.373 Y:1000 Z:-1075.723]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8221 from [X:1069.684 Y:1000 Z:-1061.388] to [X:1070.46 Y:1000 Z:-1077.538]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8219 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8219.  Client: [X:1070.373 Y:1000 Z:-1075.723], Server: [X:1069.526 Y:1000 Z:-1058.094], Diff: [X:0.8469238 Y:0 Z:-17.62952]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8220 from [X:1070.373 Y:1000 Z:-1075.723] to [X:1069.526 Y:1000 Z:-1058.094]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8221 from [X:1070.46 Y:1000 Z:-1077.538] to [X:1069.613 Y:1000 Z:-1059.908]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8222 from [X:1070.491 Y:1000 Z:-1078.183] to [X:1069.644 Y:1000 Z:-1060.553]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8220 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8221 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8222 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8223 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8223.  Client: [X:1069.71 Y:1000 Z:-1061.923], Server: [X:1071.925 Y:1000 Z:-1108.035], Diff: [X:-2.215088 Y:0 Z:46.11157]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8224 from [X:1070.484 Y:1000 Z:-1078.032] to [X:1072.699 Y:1000 Z:-1124.143]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8225 from [X:1070.444 Y:1000 Z:-1077.201] to [X:1072.659 Y:1000 Z:-1123.312]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8226 from [X:1069.714 Y:1000 Z:-1062.011] to [X:1071.93 Y:1000 Z:-1108.123]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8224 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8224.  Client: [X:1072.699 Y:1000 Z:-1124.143], Server: [X:1071.925 Y:1000 Z:-1108.039], Diff: [X:0.7736816 Y:0 Z:-16.10425]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8225 from [X:1072.659 Y:1000 Z:-1123.312] to [X:1071.885 Y:1000 Z:-1107.208]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8226 from [X:1071.93 Y:1000 Z:-1108.123] to [X:1071.156 Y:1000 Z:-1092.018]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8227 from [X:1071.81 Y:1000 Z:-1105.641] to [X:1071.037 Y:1000 Z:-1089.537]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8225 was 0
[12/17/2012 11:24:31 PM]: Position error for tick 8225.  Client: [X:1071.885 Y:1000 Z:-1107.208], Server: [X:1072.725 Y:1000 Z:-1124.684], Diff: [X:-0.8394775 Y:0 Z:17.47571]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8226 from [X:1071.156 Y:1000 Z:-1092.018] to [X:1071.995 Y:1000 Z:-1109.494]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8227 from [X:1071.037 Y:1000 Z:-1089.537] to [X:1071.876 Y:1000 Z:-1107.013]
[12/17/2012 11:24:31 PM]: Adjusting position at tick 8228 from [X:1070.993 Y:1000 Z:-1088.628] to [X:1071.833 Y:1000 Z:-1106.104]
[12/17/2012 11:24:31 PM]: Tick offset for tick 8226 was 0
[12/17/2012 11:24:31 PM]: Tick offset for tick 8227 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8228 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8229 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8230 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8230.  Client: [X:1072.586 Y:1000 Z:-1121.794], Server: [X:1071.126 Y:1000 Z:-1091.391], Diff: [X:1.460449 Y:0 Z:-30.40393]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8231 from [X:1073.401 Y:1000 Z:-1138.761] to [X:1071.941 Y:1000 Z:-1108.357]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8232 from [X:1073.432 Y:1000 Z:-1139.399] to [X:1071.971 Y:1000 Z:-1108.995]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8233 from [X:1072.708 Y:1000 Z:-1124.323] to [X:1071.247 Y:1000 Z:-1093.919]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8231 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8232 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8233 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8233.  Client: [X:1071.247 Y:1000 Z:-1093.919], Server: [X:1072.725 Y:1000 Z:-1124.683], Diff: [X:-1.477783 Y:0 Z:30.76343]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8234 from [X:1071.328 Y:1000 Z:-1095.611] to [X:1072.806 Y:1000 Z:-1126.375]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8235 from [X:1072.068 Y:1000 Z:-1111.001] to [X:1073.546 Y:1000 Z:-1141.765]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8236 from [X:1072.843 Y:1000 Z:-1127.147] to [X:1074.321 Y:1000 Z:-1157.91]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8234 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8234.  Client: [X:1072.806 Y:1000 Z:-1126.375], Server: [X:1071.925 Y:1000 Z:-1108.036], Diff: [X:0.8809814 Y:0 Z:-18.33862]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8235 from [X:1073.546 Y:1000 Z:-1141.765] to [X:1072.665 Y:1000 Z:-1123.426]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8236 from [X:1074.321 Y:1000 Z:-1157.91] to [X:1073.44 Y:1000 Z:-1139.572]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8237 from [X:1074.212 Y:1000 Z:-1155.636] to [X:1073.331 Y:1000 Z:-1137.297]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8235 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8236 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8237 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8238 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8239 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8239.  Client: [X:1072.554 Y:1000 Z:-1121.118], Server: [X:1073.525 Y:1000 Z:-1141.329], Diff: [X:-0.9709473 Y:0 Z:20.21155]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8240 from [X:1071.809 Y:1000 Z:-1105.611] to [X:1072.78 Y:1000 Z:-1125.823]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8241 from [X:1070.985 Y:1000 Z:-1088.458] to [X:1071.956 Y:1000 Z:-1108.67]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8242 from [X:1070.163 Y:1000 Z:-1071.348] to [X:1071.134 Y:1000 Z:-1091.56]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8240 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8241 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8241.  Client: [X:1071.956 Y:1000 Z:-1108.67], Server: [X:1071.126 Y:1000 Z:-1091.392], Diff: [X:0.8299561 Y:0 Z:-17.27844]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8242 from [X:1071.134 Y:1000 Z:-1091.56] to [X:1070.304 Y:1000 Z:-1074.281]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8243 from [X:1071.036 Y:1000 Z:-1089.534] to [X:1070.207 Y:1000 Z:-1072.255]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8244 from [X:1070.272 Y:1000 Z:-1073.623] to [X:1069.442 Y:1000 Z:-1056.344]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8242 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8242.  Client: [X:1070.304 Y:1000 Z:-1074.281], Server: [X:1071.126 Y:1000 Z:-1091.388], Diff: [X:-0.8217773 Y:0 Z:17.1062]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8243 from [X:1070.207 Y:1000 Z:-1072.255] to [X:1071.028 Y:1000 Z:-1089.362]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8244 from [X:1069.442 Y:1000 Z:-1056.344] to [X:1070.264 Y:1000 Z:-1073.451]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8245 from [X:1069.465 Y:1000 Z:-1056.822] to [X:1070.287 Y:1000 Z:-1073.928]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8243 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8244 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8244.  Client: [X:1070.264 Y:1000 Z:-1073.451], Server: [X:1068.727 Y:1000 Z:-1041.447], Diff: [X:1.537354 Y:0 Z:-32.0033]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8245 from [X:1070.287 Y:1000 Z:-1073.928] to [X:1068.75 Y:1000 Z:-1041.925]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8246 from [X:1070.22 Y:1000 Z:-1072.533] to [X:1068.682 Y:1000 Z:-1040.53]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8247 from [X:1069.469 Y:1000 Z:-1056.899] to [X:1067.932 Y:1000 Z:-1024.896]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8245 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8246 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8247 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8247.  Client: [X:1067.932 Y:1000 Z:-1024.896], Server: [X:1066.328 Y:1000 Z:-991.506], Diff: [X:1.603882 Y:0 Z:-33.38995]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8248 from [X:1068.05 Y:1000 Z:-1027.361] to [X:1066.446 Y:1000 Z:-993.9715]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8249 from [X:1068.806 Y:1000 Z:-1043.109] to [X:1067.203 Y:1000 Z:-1009.719]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8250 from [X:1069.522 Y:1000 Z:-1058.015] to [X:1067.919 Y:1000 Z:-1024.625]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8248 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8249 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8250 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8250.  Client: [X:1067.919 Y:1000 Z:-1024.625], Server: [X:1068.727 Y:1000 Z:-1041.446], Diff: [X:-0.8079834 Y:0 Z:16.82141]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8251 from [X:1068.037 Y:1000 Z:-1027.092] to [X:1068.845 Y:1000 Z:-1043.913]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8252 from [X:1067.267 Y:1000 Z:-1011.064] to [X:1068.075 Y:1000 Z:-1027.886]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8253 from [X:1066.385 Y:1000 Z:-992.6888] to [X:1067.193 Y:1000 Z:-1009.51]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8251 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8252 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8252.  Client: [X:1068.075 Y:1000 Z:-1027.886], Server: [X:1069.515 Y:1000 Z:-1057.867], Diff: [X:-1.440186 Y:0 Z:29.9812]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8253 from [X:1067.193 Y:1000 Z:-1009.51] to [X:1068.633 Y:1000 Z:-1039.491]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8254 from [X:1067.157 Y:1000 Z:-1008.768] to [X:1068.597 Y:1000 Z:-1038.749]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8255 from [X:1067.985 Y:1000 Z:-1026.018] to [X:1069.426 Y:1000 Z:-1055.999]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8253 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8254 was 0
[12/17/2012 11:24:32 PM]: Tick offset for tick 8255 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8255.  Client: [X:1069.426 Y:1000 Z:-1055.999], Server: [X:1067.938 Y:1000 Z:-1025.029], Diff: [X:1.487671 Y:0 Z:-30.96985]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8256 from [X:1069.334 Y:1000 Z:-1054.101] to [X:1067.847 Y:1000 Z:-1023.131]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8257 from [X:1068.632 Y:1000 Z:-1039.488] to [X:1067.145 Y:1000 Z:-1008.518]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8258 from [X:1067.886 Y:1000 Z:-1023.958] to [X:1066.399 Y:1000 Z:-992.988]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8256 was 0
[12/17/2012 11:24:32 PM]: Position error for tick 8256.  Client: [X:1067.847 Y:1000 Z:-1023.131], Server: [X:1069.526 Y:1000 Z:-1058.094], Diff: [X:-1.679443 Y:0 Z:34.96252]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8257 from [X:1067.145 Y:1000 Z:-1008.518] to [X:1068.824 Y:1000 Z:-1043.48]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8258 from [X:1066.399 Y:1000 Z:-992.988] to [X:1068.078 Y:1000 Z:-1027.95]
[12/17/2012 11:24:32 PM]: Adjusting position at tick 8259 from [X:1066.456 Y:1000 Z:-994.1709] to [X:1068.135 Y:1000 Z:-1029.133]
[12/17/2012 11:24:32 PM]: Tick offset for tick 8257 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8258 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8259 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8259.  Client: [X:1068.135 Y:1000 Z:-1029.133], Server: [X:1067.127 Y:1000 Z:-1008.152], Diff: [X:1.007935 Y:0 Z:-20.98187]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8260 from [X:1068.024 Y:1000 Z:-1026.817] to [X:1067.016 Y:1000 Z:-1005.836]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8261 from [X:1068.711 Y:1000 Z:-1041.119] to [X:1067.703 Y:1000 Z:-1020.137]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8262 from [X:1069.702 Y:1000 Z:-1061.75] to [X:1068.694 Y:1000 Z:-1040.768]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8260 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8261 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8261.  Client: [X:1067.703 Y:1000 Z:-1020.137], Server: [X:1066.339 Y:1000 Z:-991.7363], Diff: [X:1.36438 Y:0 Z:-28.401]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8262 from [X:1068.694 Y:1000 Z:-1040.768] to [X:1067.33 Y:1000 Z:-1012.367]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8263 from [X:1068.699 Y:1000 Z:-1040.866] to [X:1067.334 Y:1000 Z:-1012.465]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8264 from [X:1068.1 Y:1000 Z:-1028.394] to [X:1066.735 Y:1000 Z:-999.9934]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8262 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8263 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8264 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8264.  Client: [X:1066.735 Y:1000 Z:-999.9934], Server: [X:1068.715 Y:1000 Z:-1041.214], Diff: [X:-1.980225 Y:0 Z:41.22034]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8265 from [X:1066.771 Y:1000 Z:-1000.733] to [X:1068.751 Y:1000 Z:-1041.953]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8266 from [X:1066.01 Y:1000 Z:-984.8849] to [X:1067.99 Y:1000 Z:-1026.105]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8267 from [X:1066.709 Y:1000 Z:-999.4551] to [X:1068.69 Y:1000 Z:-1040.676]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8265 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8265.  Client: [X:1068.751 Y:1000 Z:-1041.953], Server: [X:1067.127 Y:1000 Z:-1008.153], Diff: [X:1.623657 Y:0 Z:-33.79968]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8266 from [X:1067.99 Y:1000 Z:-1026.105] to [X:1066.366 Y:1000 Z:-992.3055]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8267 from [X:1068.69 Y:1000 Z:-1040.676] to [X:1067.066 Y:1000 Z:-1006.876]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8268 from [X:1068.511 Y:1000 Z:-1036.96] to [X:1066.887 Y:1000 Z:-1003.161]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8266 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8267 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8268 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8269 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8269.  Client: [X:1066.92 Y:1000 Z:-1003.848], Server: [X:1067.946 Y:1000 Z:-1025.2], Diff: [X:-1.025757 Y:0 Z:21.35236]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8270 from [X:1066.918 Y:1000 Z:-1003.799] to [X:1067.944 Y:1000 Z:-1025.152]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8271 from [X:1066.15 Y:1000 Z:-987.8042] to [X:1067.176 Y:1000 Z:-1009.157]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8272 from [X:1065.289 Y:1000 Z:-969.8939] to [X:1066.315 Y:1000 Z:-991.2463]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8270 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8270.  Client: [X:1067.944 Y:1000 Z:-1025.152], Server: [X:1068.727 Y:1000 Z:-1041.446], Diff: [X:-0.7827148 Y:0 Z:16.29443]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8271 from [X:1067.176 Y:1000 Z:-1009.157] to [X:1067.958 Y:1000 Z:-1025.451]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8272 from [X:1066.315 Y:1000 Z:-991.2463] to [X:1067.098 Y:1000 Z:-1007.541]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8273 from [X:1066.254 Y:1000 Z:-989.9637] to [X:1067.036 Y:1000 Z:-1006.258]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8271 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8272 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8272.  Client: [X:1067.098 Y:1000 Z:-1007.541], Server: [X:1067.927 Y:1000 Z:-1024.795], Diff: [X:-0.8288574 Y:0 Z:17.2547]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8273 from [X:1067.036 Y:1000 Z:-1006.258] to [X:1067.865 Y:1000 Z:-1023.513]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8274 from [X:1067.026 Y:1000 Z:-1006.034] to [X:1067.854 Y:1000 Z:-1023.289]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8275 from [X:1067.042 Y:1000 Z:-1006.387] to [X:1067.871 Y:1000 Z:-1023.642]
[12/17/2012 11:24:33 PM]: Tick offset for tick 8273 was 0
[12/17/2012 11:24:33 PM]: Tick offset for tick 8274 was 0
[12/17/2012 11:24:33 PM]: Position error for tick 8274.  Client: [X:1067.854 Y:1000 Z:-1023.289], Server: [X:1068.727 Y:1000 Z:-1041.445], Diff: [X:-0.8721924 Y:0 Z:18.15625]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8275 from [X:1067.871 Y:1000 Z:-1023.642] to [X:1068.744 Y:1000 Z:-1041.798]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8276 from [X:1067.836 Y:1000 Z:-1022.915] to [X:1068.709 Y:1000 Z:-1041.072]
[12/17/2012 11:24:33 PM]: Adjusting position at tick 8277 from [X:1067.011 Y:1000 Z:-1005.742] to [X:1067.884 Y:1000 Z:-1023.898]

I doubt any physics engine would be able to handle rewinding in our situation. We have a dynamic world. Rewinding would mean saving and recreating the world itself. It's already expensive enough just creating it the first time. Recreating it several times in a single tick.... would be impossible. Not to mention the memory requirement of storing the world state.

I feel that a delta correction could certainly work in our situation *if* we could reliably get a list of all positions the client has moved through between the time the calculation error occurred and the time it received the proper location from the server. I just can't figure out how to do that given the client's tendency to have the current tick jump around. I guess part of the problem is that I don't know what issues it should be able to handle and what issues are external problems that need to be fixed in order for this system to work correctly.

How would you handle this situation then?

S: 3, C: 6 - Client moves from X = 5 to X = 7
S: 4, C: 7 - Client moves to X = 9
S: 5, C: 8 - Client moves to X = 11
S: 6, C: 9 - Server receives move command, new client pos = 7
S: 7, C: 10 - Server receives move command, new client pos = 8
S: 8, C: 11 - Server receives move command, new client pos = 10
S: 9, C: 12 - Client receives position = 7 from server for tick 6. Matches, no action taken
S: 10, C: 13 - Client receives position = 8 from server for tick 7. Warps player back to X = 8
S: 11, C: 14 - Client receives position = 10 from server for tick 8. Warps player to X = 10

Let's just assume the player is moving fast enough that they need to be warped. Normally the suggestion is to record the player input, rewind, correct, and reapply the input. Since I can't rewind, and you suggest not using deltas, how else can you deal with this without having never-ending warping? Even if you're not warping them, how can you 'nudge' the player in the right direction without knowing where they need to be *now*. The server is only telling you where they should have been several ticks ago.