Updated HDK Server file to disable server side prediction

[demonixis]

This PR is related to the issue #441

[rpavlik]

Thanks for this - I asked Russ for a clarification because I was under the impression that while yes, we technically are doing client side prediction in extended mode, we don't actually have the frame timing data to do it correctly there, and so in my eventual future plans of doing this one myself I was going to turn off (or perhaps just reduce to a single-eye on 1.x) client side prediction in the extended mode RM configs.

[DuFF14]

I haven't compared server-side vs extended client-side , but I will put it on my list.

Does the fusion plugin handle server-side prediction? Will removing this section impair positional tracking accuracy?

"aliases": {
        "/headSpace": {
            "translate": [0.0, 0.0, 0.04141],
            "child": "/org_osvr_filter_videoimufusion/HeadFusion/semantic/fused"
        },
        "/me/head": "/headSpace"
    }

[russell-taylor]

As I commented on Ryan's question on the issue, I think I set the extended mode prediction to be half a frame longer than the direct-mode prediction so that we're using the expected delay. Of course, actual delay will depend on application rendering time. The client-side timing info returns 0 in the case of no information, so kind of auto-disables itself in that case.

[demonixis]

Hi, any news about this PR? Performances are critical for new users and the current configuration is not adapted.