Road Hog Full Boar Wing Problem

my apologies, my physical resources are limited and i don't have a machine that has paired to a 2216-based controller from which to pull a known-working config for comparison. perhaps the community at large can provide such a config?


since i'm stuck on that, i'll share what i can:

i would agree that your unit is physically functioning; of all the possibilities, your two laptops sharing a trackpad manufacturer is a more likely cause than anything that would require your wing to be RMA'd.

if running Hog3PC\EloVa.exe starts a calibration sequence, the drivers are installed and working correctly; were they not, you'd instead see "No Elo Touchscreen Found".



so if: the hardware works, the drivers work, and touching causes any movement (*beep*), the issue's got to be in one of two places:
[INDENT]the mathematics behind the touchscreen-to-"expanded desktop" coordinate scale transform: the essential variables are stored in what we're calling the config. EloVa might be writing incorrect values to the registry, or elomoufiltr might be reading / applying those values incorrectly. either way, bad math could be a cause, and certainly fits with your "wing as primary, drifts from top-left" finding.

emitting correctly-calculated mouse instructions: there may be one or more additional and completely unrelated filter drivers in the HID chain, asserting their own control over where the pointer lands; you might see if reverting those trackpad drivers to generics (and restarting) makes any difference.

[/INDENT]i do think it's a config problem, and right now i'm looking specifically at your WindowsMonitorNumber=65538. i'd expect 1 or 2, certainly not 65538 or even -2. but i do notice x/y MonLocn and VirtScrCoord are correct, which leads me to believe that EloVa acquires the correct monitor number and correctly produces MonLocn and VirtScrCoord based off of that correct monitor number, but writes it incorrectly, so when elomoufiltr tries to match touchscreen->monitor->virtual desktop, it fails and defaults to monitor 1. (technically - it looks like the value for the DWORD type, 0x00010000, has ben AND'd to the value for monitor 2, 0x00000002, resulting in WindowsMonitorNumber=0x00010002 instead of WindowsMonitorNumber=0x00000002. see Appendix A-B)


which Windows monitor number is reported in the Elo control panel > Properties 1? does the Elo "Identify Monitor" button identify the monitor with the same number in the Windows Display control panel?


if your wing is assigned to be monitor 2, and is arranged to the left of monitor 1, do you see any change in behavior after:[LIST=1]
calibrating
using device manager to disable the Elo device
setting WindowsMonitorNumber = 2
re-enabling the Elo device
again, sorry i don't have an actual answer. or a lab full of gear. but i hope you find that something helps.

my apologies, my physical resources are limited and i don't have a machine that has paired to a 2216-based controller from which to pull a known-working config for comparison. perhaps the community at large can provide such a config?


since i'm stuck on that, i'll share what i can:

i would agree that your unit is physically functioning; of all the possibilities, your two laptops sharing a trackpad manufacturer is a more likely cause than anything that would require your wing to be RMA'd.

if running Hog3PC\EloVa.exe starts a calibration sequence, the drivers are installed and working correctly; were they not, you'd instead see "No Elo Touchscreen Found".



so if: the hardware works, the drivers work, and touching causes any movement (*beep*), the issue's got to be in one of two places:
[INDENT]the mathematics behind the touchscreen-to-"expanded desktop" coordinate scale transform: the essential variables are stored in what we're calling the config. EloVa might be writing incorrect values to the registry, or elomoufiltr might be reading / applying those values incorrectly. either way, bad math could be a cause, and certainly fits with your "wing as primary, drifts from top-left" finding.

emitting correctly-calculated mouse instructions: there may be one or more additional and completely unrelated filter drivers in the HID chain, asserting their own control over where the pointer lands; you might see if reverting those trackpad drivers to generics (and restarting) makes any difference.

[/INDENT]i do think it's a config problem, and right now i'm looking specifically at your WindowsMonitorNumber=65538. i'd expect 1 or 2, certainly not 65538 or even -2. but i do notice x/y MonLocn and VirtScrCoord are correct, which leads me to believe that EloVa acquires the correct monitor number and correctly produces MonLocn and VirtScrCoord based off of that correct monitor number, but writes it incorrectly, so when elomoufiltr tries to match touchscreen->monitor->virtual desktop, it fails and defaults to monitor 1. (technically - it looks like the value for the DWORD type, 0x00010000, has ben AND'd to the value for monitor 2, 0x00000002, resulting in WindowsMonitorNumber=0x00010002 instead of WindowsMonitorNumber=0x00000002. see Appendix A-B)


which Windows monitor number is reported in the Elo control panel > Properties 1? does the Elo "Identify Monitor" button identify the monitor with the same number in the Windows Display control panel?


if your wing is assigned to be monitor 2, and is arranged to the left of monitor 1, do you see any change in behavior after:[LIST=1]
calibrating
using device manager to disable the Elo device
setting WindowsMonitorNumber = 2
re-enabling the Elo device
again, sorry i don't have an actual answer. or a lab full of gear. but i hope you find that something helps.