New version of Infinite Screen Extension (1.1.1.379)

[Tage Borg]

Yes, I’ve reset the controls to KB+M and tried that.

The log ends with “Joystick Acquired!”,so not much to go by there. Further up I see something that looks like partial stack traces about keyboard and mouse as well, ut the messages are tagged with “WARN” rather than “ERR”.

I have spent the evening reinstalling ED:H, the X52 and EyeX (the latter using the Steelseries software since it’s really a Sentry). All to no avail. I cannot get the gaze trace to overlay in the game (after setting the game to borderless mode) so I can see that the device is active while I play the game. But no “camera following my gaze”.

I guess the device->ED:H communication is just a matter of ED:H reading data from a device driver. But which one?

I had a short weird episode where I trued to bind the enable/Disable key in ISE to ‘x’, but ISE registered this as ‘Joy_27+x’. My X52 was “idle” (i.e. no input from any buttons or the throttle). Does this ring a bell? I got rid of that by switching USB ports for the X52 and now (of course) I cannot reproduce it.

Currently I have two hypotheses:

1. My X52 is interfering with my Sentry in some way. I have tested LOTS of things by now. But I am not 100% certain I have tested uninstalling the X52 drivers, restarting the computer and then testing ED:H with the Sentry. I am not sure I can be arsed to do this tonight; I want to play, too 🙂

2. I am a special case in that I never owned the “base” ED. Perhaps the version of ED:H that I have therefore is missing something that people who upgraded form ED have. If this is the case, I am out of luck.

My whole setup is very basic since I do not use Windows for anything but gaming. My only USB devices are a plain keyboard a plain mouse, the X52 and the Sentry. Oh, and one monitor is plugged in as well as a hub, but nothing is connected to it. I do not have any other software than Steam (and games in Steam), Chrome (for downloading drivers without needing to touch IE), the Tobii stack and since today also the Steelseries bloatware. For antivirus, I use MS’s own antivirus whatsname. The MS firewall is also enabled but I cannot see how that would interfere.

[Tage Borg]

I meant “I *can* get the gaze to overlay the game”.

[Tage Borg]

Ok, perhaps I’ve got something for you.

1. Start ED:H from the desktop shortcut Steam creates. This way, the launcher will give the option to start one of:
a) ED:H 64-bit
b) ED 32-bit
c) ED 64-bit
d) ED: Arena 64-bit
e) Single Player Combat Training
2. Start ED 64-bit; start training/target practice. No eye tracking.
3. Start ED:H 64-bit; start training/target practice. Still no eye tracking.
4. Start ED 32-bit; start training/target practice. YES! EYE-TRACKING!!1!eleven!
5. Start ED:H 64-bit; start training/target practice. Nope, nope, nope.

InfiniteScreen Process Monitor seems to run as a 64 bit process according to my task manager details tab, but most if not all other Tobii processes are 32 bit (including GazeNative which I have active currently).

Another thing I noted is that I have never installed an older version of ISE than 1.1.1.379. IS an upgrade different from true virgin installation?

Ok, now I really need to shoot some space boats. Thanks for getting back to me here, Henrik. I do have a support ticket open as well and perhaps it will get a response soon. And now I think I have something for them to follow up if you can’t.

[Henrik [Tobii]]

2. Start ED 64-bit; start training/target practice. No eye tracking.
3. Start ED:H 64-bit; start training/target practice. Still no eye tracking.
4. Start ED 32-bit; start training/target practice. YES! EYE-TRACKING!!1!eleven!

This most likely means that the ProcessMonitor doesn’t detect the process launch of EliteDangerous64.exe, which is interesting in it’s own right.

Quit ISE and then run Tobii.Oem.Gaming.InfiniteScreen.ProcessMonitor.exe. It will output the started and closed processes it can detect to the console. So you if for example start Notepad should see something like:
{“ProcessEventType”:0,”ProcessInfo”:{“Id”:6004,”MainModulePath”:”C:\\WINDOWS\\system32\\notepad.exe”,”Name”:”notepad”},”Timestamp”:”\/Date(1457647606318)\/”}

Try launching ED:H 64-bit while the process monitor is running and check if an “EliteDangerous64.exe”-entry shows up.

[Tage Borg]

I have two 32-bit versions of Elite in subdirectories of C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\. One for the single player training and one for Elite Dangerous (not Horizons). Is ISE waiting monitoring the process list for those instad of the EliteDangerous64.exe that I actually play with?

[Tage Borg]

Missed your last post yesterday night, sorry. Here’s the output of a quick test from my just-booted computer for what I think is the whole life cycle of EDLaunch and it’s child processes. EliteDangerous64.exe is in there…

{"ProcessEventType":0,"ProcessInfo":{"Id":5028,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steam.exe","Name":"Steam"},"Timestamp":"\/Date(1457678844342)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":6704,"MainModulePath":"C:\\Program Files (x86)\\Steam\\bin\\steamwebhelper.exe","Name":"steamwebhelper"},"Timestamp":"\/Date(1457678848214)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5684,"MainModulePath":null,"Name":"SteamService"},"Timestamp":"\/Date(1457678848525)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":4300,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\EDLaunch.exe","Name":"EDLaunch"},"Timestamp":"\/Date(1457678854935)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":4040,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\HardwareReporter.exe","Name":"HardwareReporter"},"Timestamp":"\/Date(1457678856663)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":6836,"MainModulePath":"C:\\Windows\\System32\\dxdiag.exe","Name":"dxdiag"},"Timestamp":"\/Date(1457678856868)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":1584,"MainModulePath":null,"Name":"PresentationFontCache"},"Timestamp":"\/Date(1457678857991)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":6836,"MainModulePath":"C:\\Windows\\System32\\dxdiag.exe","Name":"dxdiag"},"Timestamp":"\/Date(1457678860530)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":4040,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\HardwareReporter.exe","Name":"HardwareReporter"},"Timestamp":"\/Date(1457678863638)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5508,"MainModulePath":null,"Name":"GoogleUpdate"},"Timestamp":"\/Date(1457678866829)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8056,"MainModulePath":null,"Name":"svchost"},"Timestamp":"\/Date(1457678866939)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5508,"MainModulePath":null,"Name":"GoogleUpdate"},"Timestamp":"\/Date(1457678866939)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8016,"MainModulePath":null,"Name":"sppsvc"},"Timestamp":"\/Date(1457678867250)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":6820,"MainModulePath":"C:\\WINDOWS\\system32\\svchost.exe","Name":"svchost"},"Timestamp":"\/Date(1457678867459)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":684,"MainModulePath":"C:\\WINDOWS\\system32\\backgroundTaskHost.exe","Name":"backgroundTaskHost"},"Timestamp":"\/Date(1457678872316)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":684,"MainModulePath":"C:\\WINDOWS\\system32\\backgroundTaskHost.exe","Name":"backgroundTaskHost"},"Timestamp":"\/Date(1457678872419)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5288,"MainModulePath":null,"Name":"SearchFilterHost"},"Timestamp":"\/Date(1457678874156)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5248,"MainModulePath":"C:\\WINDOWS\\system32\\SearchProtocolHost.exe","Name":"SearchProtocolHost"},"Timestamp":"\/Date(1457678874157)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":6024,"MainModulePath":null,"Name":"SearchProtocolHost"},"Timestamp":"\/Date(1457678874157)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":3260,"MainModulePath":null,"Name":"WmiPrvSE"},"Timestamp":"\/Date(1457678875585)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":1560,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\WatchDog64.exe","Name":"WatchDog64"},"Timestamp":"\/Date(1457678875992)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":1924,"MainModulePath":"C:\\WINDOWS\\system32\\conhost.exe","Name":"conhost"},"Timestamp":"\/Date(1457678875994)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":3904,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\EliteDangerous64.exe","Name":"EliteDangerous64"},"Timestamp":"\/Date(1457678876107)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":8056,"MainModulePath":null,"Name":"svchost"},"Timestamp":"\/Date(1457678877124)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":516,"MainModulePath":"C:\\Windows\\System32\\GamePanel.exe","Name":"GamePanel"},"Timestamp":"\/Date(1457678879059)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":7496,"MainModulePath":"C:\\WINDOWS\\system32\\backgroundTaskHost.exe","Name":"backgroundTaskHost"},"Timestamp":"\/Date(1457678881091)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":4992,"MainModulePath":null,"Name":"SearchFilterHost"},"Timestamp":"\/Date(1457678883537)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":7908,"MainModulePath":"C:\\WINDOWS\\system32\\SearchProtocolHost.exe","Name":"SearchProtocolHost"},"Timestamp":"\/Date(1457678883538)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":7496,"MainModulePath":"C:\\WINDOWS\\system32\\backgroundTaskHost.exe","Name":"backgroundTaskHost"},"Timestamp":"\/Date(1457678883639)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":516,"MainModulePath":"C:\\Windows\\System32\\GamePanel.exe","Name":"GamePanel"},"Timestamp":"\/Date(1457678884660)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":8016,"MainModulePath":null,"Name":"sppsvc"},"Timestamp":"\/Date(1457678897333)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":6892,"MainModulePath":null,"Name":"TiWorker"},"Timestamp":"\/Date(1457678903490)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":6824,"MainModulePath":null,"Name":"TrustedInstaller"},"Timestamp":"\/Date(1457678903490)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8120,"MainModulePath":null,"Name":"wermgr"},"Timestamp":"\/Date(1457678925182)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":8120,"MainModulePath":null,"Name":"wermgr"},"Timestamp":"\/Date(1457678926198)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":2012,"MainModulePath":null,"Name":"svchost"},"Timestamp":"\/Date(1457678943448)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":3260,"MainModulePath":null,"Name":"WmiPrvSE"},"Timestamp":"\/Date(1457678966408)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5032,"MainModulePath":"C:\\Windows\\System32\\bcastdvr.exe","Name":"bcastdvr"},"Timestamp":"\/Date(1457678981705)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":1924,"MainModulePath":"C:\\WINDOWS\\system32\\conhost.exe","Name":"conhost"},"Timestamp":"\/Date(1457678982215)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":1560,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\WatchDog64.exe","Name":"WatchDog64"},"Timestamp":"\/Date(1457678982216)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":3904,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\EliteDangerous64.exe","Name":"EliteDangerous64"},"Timestamp":"\/Date(1457678982216)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5032,"MainModulePath":"C:\\Windows\\System32\\bcastdvr.exe","Name":"bcastdvr"},"Timestamp":"\/Date(1457678983759)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8056,"MainModulePath":null,"Name":"wermgr"},"Timestamp":"\/Date(1457678985217)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":6064,"MainModulePath":null,"Name":"wsqmcons"},"Timestamp":"\/Date(1457678985219)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":2304,"MainModulePath":"C:\\WINDOWS\\system32\\taskhostw.exe","Name":"taskhostw"},"Timestamp":"\/Date(1457678985222)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":656,"MainModulePath":null,"Name":"SIHClient"},"Timestamp":"\/Date(1457678985225)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8156,"MainModulePath":null,"Name":"conhost"},"Timestamp":"\/Date(1457678985227)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":2400,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678985230)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":872,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678985233)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":8088,"MainModulePath":"C:\\Windows\\System32\\InstallAgent.exe","Name":"InstallAgent"},"Timestamp":"\/Date(1457678985235)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":1080,"MainModulePath":null,"Name":"conhost"},"Timestamp":"\/Date(1457678985343)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5840,"MainModulePath":null,"Name":"schtasks"},"Timestamp":"\/Date(1457678985448)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":6064,"MainModulePath":null,"Name":"wsqmcons"},"Timestamp":"\/Date(1457678985548)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5840,"MainModulePath":null,"Name":"schtasks"},"Timestamp":"\/Date(1457678985549)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":7036,"MainModulePath":null,"Name":"WMIADAP"},"Timestamp":"\/Date(1457678985653)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":8056,"MainModulePath":null,"Name":"wermgr"},"Timestamp":"\/Date(1457678985653)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5624,"MainModulePath":null,"Name":"DeviceCensus"},"Timestamp":"\/Date(1457678985862)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":2400,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678985863)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":6908,"MainModulePath":null,"Name":"sppsvc"},"Timestamp":"\/Date(1457678985966)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":3692,"MainModulePath":null,"Name":"svchost"},"Timestamp":"\/Date(1457678986172)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":656,"MainModulePath":null,"Name":"SIHClient"},"Timestamp":"\/Date(1457678986378)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":1080,"MainModulePath":null,"Name":"conhost"},"Timestamp":"\/Date(1457678986379)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":5692,"MainModulePath":null,"Name":"dllhost"},"Timestamp":"\/Date(1457678986800)\/"}
{"ProcessEventType":0,"ProcessInfo":{"Id":1612,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678988232)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5624,"MainModulePath":null,"Name":"DeviceCensus"},"Timestamp":"\/Date(1457678988232)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":1612,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678988334)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":872,"MainModulePath":null,"Name":"CompatTelRunner"},"Timestamp":"\/Date(1457678988435)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":8156,"MainModulePath":null,"Name":"conhost"},"Timestamp":"\/Date(1457678988436)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":4300,"MainModulePath":"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\EDLaunch.exe","Name":"EDLaunch"},"Timestamp":"\/Date(1457678988942)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":2304,"MainModulePath":"C:\\WINDOWS\\system32\\taskhostw.exe","Name":"taskhostw"},"Timestamp":"\/Date(1457678990975)\/"}
{"ProcessEventType":1,"ProcessInfo":{"Id":5692,"MainModulePath":null,"Name":"dllhost"},"Timestamp":"\/Date(1457678991895)\/"}

[Tage Borg]

Quick Q before I leave: what does ISE try to match? The just path in the HID input settings file or something computed based on the settings?

Guess-asking another question based on my outside understanding of ISE: is there any reason ISE does not generate controller output all the time rather than waiting for specific processes to start?

[Omri Goldblat]

Hi, I am having an issue where ISE starts, then either crashes imidiatly or after a few seconds or after a min or so, It says that it stopped responding & windows will close the program, anyone got ideas ???
installation went fine, no problems or errors, just keeps failing all the time…
I am using the SteelSeries Sentry

[Tage Borg]

@henrik: here’s a gist instead https://gist.github.com/tageborg/07201b48951a7f7754e6#file-ed-h-64-lifecycle-process-list sorry about the spammy post.

[Henrik [Tobii]]

@henrik: here’s a gist instead https://gist.github.com/tageborg/07201b48951a7f7754e6#file-ed-h-64-lifecycle-process-list sorry about the spammy post.

Thought I already answered your last post… must have forgotten to click Submit…

Anyways – it looks like the ProcessMonitor is working just fine.

This entry:
{“ProcessEventType”:0,”ProcessInfo”:{“Id”:3904,”MainModulePath”:”C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\EliteDangerous64.exe”,”Name”:”EliteDangerous64″},”Timestamp”:”\/Date(1457678876107)\/”}
means that it has detected the process start of EliteDangerous64.exe and this one:

{“ProcessEventType”:1,”ProcessInfo”:{“Id”:3904,”MainModulePath”:”C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\EliteDangerous64.exe”,”Name”:”EliteDangerous64″},”Timestamp”:”\/Date(1457678982216)\/”}
means that is has detected a process close of EliteDangerous64.exe.

This makes me suspect that there might actually be something wrong with ED detecting FreeTrack in 64-bit. When ISE is running, make sure that the registry key “HKEY_CURRENT_USER\SOFTWARE\Freetrack\FreetrackClient” points to the install location of ISE (probably “C:\Program Files (x86)\Tobii\Tobii InfiniteScreen\”). Also make sure that you have both a “FreeTrackClient.dll” and a “FreeTrackClient64.dll” in this directory.

[Henrik [Tobii]]

Hi, I am having an issue where ISE starts, then either crashes imidiatly or after a few seconds or after a min or so, It says that it stopped responding & windows will close the program, anyone got ideas ???
installation went fine, no problems or errors, just keeps failing all the time…
I am using the SteelSeries Sentry

Check the last entry in the latest ISE log file under:
“%PROGRAMDATA%\Tobii\Tobii InfiniteScreen\Logs”

Also, make sure to uninstall any SteelSeries software related to the eye tracker.

You only need to install:
http://developer.tobii.com/?wpdmdl=181
and
https://files.update.tech.tobii.com/InfiniteScreen/download.html

[Tage Borg]

The plot thickens… HKEY_CURRENT_USER\SOFTWARE\Freetrack\FreetrackClient has (REG_SZ)Path==C:\Program Files (x86)\Tobii\Tobii InfiniteScreen\ which is exactly where FreeTrackClient.dll and FreeTrackClient64.dll live.

I actually tried replacing .dll with 64.dll earlier today to see if ISE was loading the wrong one. Didn’t help. But I consistently get eye tracking in the 32-bit ED client. Can I enable even more debug output somehow? My logs look fine as far as I can tell.

Extra-weird idea: would you like me to drop by with my computer next week to test on-site? My work situation is currently such that I could do that during office hours.

With regards to Omri’s problems, the Tobii software cannot get his screen bounds as per logs posted in a separate thread. No idea about how to solve that, but it sounds like problems to me.

(SWE) F.ö. sjukt koolt att du svarar fredag kväll såhär dags. Grymt engagemang – stort tack för det!

[Henrik [Tobii]]

Sorry for not replying sooner, busy days I’m afraid.

The plot thickens… HKEY_CURRENT_USER\SOFTWARE\Freetrack\FreetrackClient has (REG_SZ)Path==C:\Program Files (x86)\Tobii\Tobii InfiniteScreen\ which is exactly where FreeTrackClient.dll and FreeTrackClient64.dll live.

I actually tried replacing .dll with 64.dll earlier today to see if ISE was loading the wrong one. Didn’t help. But I consistently get eye tracking in the 32-bit ED client. Can I enable even more debug output somehow? My logs look fine as far as I can tell.

That is very strange. There’s currently no way of enabling more verbose logging I’m afraid.

Extra-weird idea: would you like me to drop by with my computer next week to test on-site? My work situation is currently such that I could do that during office hours.

That’s very nice of you to offer but perhaps it would be better (just so you don’t travel all the way out here for nothing) if we start with a remote session? Our support department should be able to schedule one for you.

(SWE) F.ö. sjukt koolt att du svarar fredag kväll såhär dags. Grymt engagemang – stort tack för det!

Det är otroligt kul med all repons och feedback vi får så – ingen orsak :).

[Austin Bond]

i managed to fix my issues with avast. if anyone has issues with avast always starting process monitor in deepscreen mode you need to reinstall avast, because for some reason upgrading the program from one version to another has a chance to break certain options in the settings menu. after reinstalling i was able to disable deepscreen and get the program running

[Tage Borg]

Update: one day after an unsuccessful attempt at solving my issues with a screen sharing session, my problem “spontaneously” vanished. I suspect that Elite Dangerous received a software update that made the game load freetrackclient.dll properly (since it did not do so during the support session). I now have glorious eye tracking in ED:H!

A small thin tarnishes the experience and that is that when centering the viewpoint using a hotkey set in ISE, the view is not perfectly centered. But I believe this is a know defect that will be fixed in th next version of ISE.

Mad props to the Tobii support staff (Emelie, in my case) and Henrik for all the help!

[Author]

Posts