Greg Aring

@HelenXR You may be missing some dependencies if only copying driver_osvr.dll and driver_osvr.lib. My builds from source work if I copy over the entire osvr folder from the Install directory.

Can confirm this shows the correct resolution per eye now: 

Good question @JeroMiya. @rpavlik What is the current status with this? It looks like if I use the following config file, there is no head/neck model: ``` JSON "display": "displays/OSVR_HDK_1_1.json",...

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...

Can we merge this? Will also want to update when ATW is working. How about client prediction, are we leaving that out for now?

@russell-taylor are the settings in these RenderManager config files what we want to ship by default with the OSVR installation?

Should prediction be in there by default? Is that working with all client apps?

Updated OSVR_HDK_1_3_with_mesh to use built-in distortion mesh v2 and new FOV values. Updated default renderManagerConfig settings -- enabling/disabling vsync settings for direct/extended modes, decreased renderOverfillFactor from 1.5 to 1.2. I...

@demonixis it sounds like there is consensus to make this change, so you could prepare a pull request. To disable server-side prediction, add: `"aliases": {"/me/head":"/com_osvr_Multiserver/OSVRHackerDevKit0/semantic/hmd"}` to any HDK server config...

You'd want to edit all the HDK configs in the sample-configs directory which have a renderManagerConfig in them or reference an external renderManagerConfig with prediction enabled, like this one: https://github.com/OSVR/OSVR-Core/blob/master/apps/sample-configs/osvr_server_config.HDK13DirectMode.sample.json#L4...