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