EDTracker not working in the game in Windows 10

simonCGN · Jun 5, 2016

Hello,

I had the EDTracker operating fine in Win 8. Since I have upgraded to Win 10 the tracker is not recognised in the game. When I try to configure the axis, the game does not get any input.

The tracker itself is recognised by the calibration software which I have downloaded from the EDTRacker page but not within the game.

Do you have any ideas what I could do to resolve that issue?

Kind regards

simonCGN

brumster · Jun 5, 2016

Check the windows USB game controller in control panel - it will be listed as EDTracker, and will appear to be a 3-axis joystick to Windows. Are the axes moving ok when you move the device there?

simonCGN · Jun 6, 2016

It shows like this: http://imgur.com/jG8428Z

brumster · Jun 7, 2016

Odd that the COM port is showing up as a joystick, but maybe that's just Windows 10 (I don't have it myself to check).

If you find the joystick device in "USB Game Controllers" (or whatever Windows 10 calls it), can you see the axes moving when the device moves? You have to highlight the device and click "properties" and it will show you some crosshairs.....? Do they move when the device moves?

simonCGN · Jun 7, 2016

I had to unplug and replug it an and got the EDTracker recognised as a Game controller. And yes, the crosshairs move when I move the device. Still no input in the game though.

Jukelo · Jun 8, 2016

Hey simonCGN, have you tried using Opentrack instead? Opentrack comes in between the EDtracker and the game, taking input from the EDT and converting it to the Freetrack protocol, which is a lot more responsive in the game than using the EDT as joystick to move the view around. And if your game has trouble communicating with the EDT itself, maybe it will have less trouble communicating with Opentrack instead.

brumster · Jun 8, 2016

simonCGN said:
I had to unplug and replug it an and got the EDTracker recognised as a Game controller. And yes, the crosshairs move when I move the device. Still no input in the game though.

Ah ok, this sounds like a known issue with the Arduino drivers on Windows 10. You could try updating to the latest ones but people's experiences seem a bit marginal on whether it fixes it or not. Some people report success, others not so much. You could try using a tool like USBDeview to remove the old drivers and make sure everything is clean before installing the new ones.

Jukelo said:
Hey simonCGN, have you tried using Opentrack instead? Opentrack comes in between the EDtracker and the game, taking input from the EDT and converting it to the Freetrack protocol, which is a lot more responsive in the game than using the EDT as joystick to move the view around. And if your game has trouble communicating with the EDT itself, maybe it will have less trouble communicating with Opentrack instead.

...or this suggestion

. I'm not sure it's "more responsive" but it's certainly more configurable and a lot of people go this route

brumster · Jun 8, 2016

The drivers on our website are taken from the 1.6.7 IDE which was a release for Windows 10, so they should be OK. However I'll download 1.6.9 now and check if there are any differences, and if so I'll push up the drivers (only) to the EDTracker.org website...

edit: Looks like they've just added a new MKR1000 board, but in case there are binary changes, I will update our site to be on the safe side. But I don't think there's any material difference from a Leonardo perspective.

simonCGN · Jun 9, 2016

Just tries with open track. Does not work either.

- - - - - Additional Content Posted / Auto Merge - - - - -

After plugin it out and back in again it is recognised as EDTracker properly and I can also calibrate it.

It is still not recognised by the game.

Here are pics of how it all looks
http://imgur.com/a/wfdUg

simonCGN · Jun 10, 2016

So, after I got win10 I got it to recognise EDTracker by unplugging and plugging it back in I have found the culprit.

In Win8.1 the game recognised the movements of the tracker with normal movements of the head you would also expect to do in the game. In win10 I needed to move my head all the way face down for the game to recognise a movement and map it. Why that is I do not know. But now I will use open track to adjust for that.

thanx for the help

Globusdiablo · Sep 17, 2016

I have the same problem but with no solution..

It registers fine in windows 10 but doesn't seem to activate in E: D.

Globusdiablo · Sep 17, 2016

picommander said:
Similar issues here, also on Windows 10. Meanwhile I thought I'd make some progress as I figured the com port had a different number after re-plugging the USB connector. I managed to force Windows to use this number even without re-plugging. This works thus far in the EDTracker UI but ED still does not recognize the device. I've still to re-plug to make it work despite nothing visible would change (same com port). If that isn't a strange issue..

Do you have other headtrackable games to test on? I don't.

Globusdiablo · Sep 17, 2016

picommander said:
Me neither. And I'm surely not going to install Euro Truck Simulator just for a small test.

[video=youtube;-3nh0MvCqSI]https://www.youtube.com/watch?v=-3nh0MvCqSI[/video]

Zaggeron · Sep 17, 2016

I was watching a guy who was using Track IR while streaming ED and he mentioned that if you are using Win 10 you need the Track IR software on your boot drive or ED won't recognize that it is there. Maybe that is the problem.

Globusdiablo · Sep 17, 2016

Zaggeron said:
I was watching a guy who was using Track IR while streaming ED and he mentioned that if you are using Win 10 you need the Track IR software on your boot drive or ED won't recognize that it is there. Maybe that is the problem.

I only have one "big" c-drive, a 500 gb ssd. Edit: and one partition.

And I can't get E: D to recognise EDTracker at all, no matter what I do.

Zaggeron · Sep 17, 2016

picommander said:
If you really meant "boot drive" I've got a problem here cause I'm dual booting via grub which is sitting on my Linux harddrive while all the rest is on my SSD, so installing the software on my "boot drive" wouldn't make any sense. Or did you by any chance mean "root partition" instead? Howsoever, to me it seems as if Windows 10 and the Tracker UI are very well recognizing the device, but ED only after a re-plug. This pretty much looks like a glitch on ED's part, what do you think?

Yes I meant the drive or partition that contains your currently running OS. Sorry about the confusion. I really don't know what to say if that doesn't work -- the guy just mentioned that reinstalling the Track IR software on his OS drive solved (what looks to be) this exact problem. Perhaps not being on the OS drive is sufficient but not necessary for these issues.