HW conflict question for Opentrack/PS3Eye users

[1Sascha]

Since my TrackIR5 is in storage in another city, I had to switch to a new solution. TIR5 prices are even worse over here than they were when I bought my example, so I went with the Delanclip pack, which uses Opentrack and includes a modified PS3Eye camera for the tracking.

 

I followed all their instructions on first installation to a T and everything seems to work fine - most of the time.

 

From time to time however, I will get a driver conflict warning message for the camera in Windows' "devices and printers"-panel. Which normally doesn't even seem to stop the camera from functioning in Opentrack, but sometimes it does. Then the camera won't get recognized in either Opentrack or CL-Eye-Test and I have to re-plug it until it works again. I would post a screenshot of the error, but, as it happens, there are no errors reported in Windows just now.. I can't be 100% certain of this, but I *think* that the error only appears here (where the camera is simply reported as a USB camera), not in Windows device manager where it is IDed as a Sony PS3Eye camera.

 

I did plug the camera into a one of the two 2.0 ports on my motherboard (as per their instructions) - I also tried the other port already, but that didn't help. The rest of the ports on this board are 3.1/3.2 and/or Type C sockets ...

 

Anyone got any ideas what this might be and if there's a solution to this?

 

S.

[jollyjack]

check for unused old USB drivers (white) with USBdeview, and uninstall them ...

[Addict]

the new version of opentrack has its own drivers and does not need the CL Eye drivers of the camera. Maybe you have a conflict there.

[1Sascha]

28 minutes ago, Addict said:

the new version of opentrack has its own drivers and does not need the CL Eye drivers of the camera. Maybe you have a conflict there.

I think I'm using those already:

 

 

Then again... I'm pretty new to Opentrack. Only received my delanclip-pack a few weeks ago and had been using TrackIR 5 before.

 

When I installed everything a couple of weeks ago, CL Eye was still part of Delan's installation-procedure on their website.

 

Speaking of errors ... it's happened again. But it's not for the PS3-camera, but an associated USB audio-device?

 

 

I'm confused... ?

 

S.

[No_85_Gramps]

Two things, the area circled in green is just a profile for the tracking, not the driver. Also, the PS3 eye-cam has a built in microphone which may be the root of the problem.

[GO63]

Try the built-in Opentrack PS3 Eye open driver. It does not depend on Windows Updates:
https://github.com/opentrack/opentrack/wiki/PS3-Eye-open-driver-instructions

 

[1Sascha]

2 hours ago, No_85_Gramps said:

 Also, the PS3 eye-cam has a built in microphone which may be the root of the problem.

 

Ahh... that would explain quite a lot. Like how usually even with the driver error reported, the camera will work just fine in Opentrack.

 

43 minutes ago, GO63 said:

Try the built-in Opentrack PS3 Eye open driver. It does not depend on Windows Updates:

Thanks for that... never even thought to check in there. Eye open driver was listed, so I switched to that. Let's see what happens...

 

S.

[Dusty_Steppes]

In case you are interested I am using a C920 webcam with AITrack v0.6.4-alpha and Opentrack-2022.1.1. AITrack is a face tracking software that does not require InfraRed. I have the C920 configured with its software to use a black and white filter, to help improve the face tracking, with an overhead light approximately 1 meter behind my monitor and approximately 2 meters above floor level for proper face illumination.  The C920 is centered on top of a 27 inch monitor and the distance from my eyes to the monitor is approximately 65 cm. The hardest part to setup was the mapping on OpenTrack. I have it working pretty well but I can't resist making minor adjustments to find that perfect sweet spot.

Edited April 7, 2022 by Dusty_Steppes

[1Sascha]

Still getting error messages and just now had to re-plug the camera after turning on the PC to get it to work. When it showed back up after that, I went into the devices tab, selected the USB audio-device (which is, presumably, the camera's microphone) and deactivated it. The error message and triangle-icon went away right after that.

 

I hope that is a permanent deactivation, not just one that'll last until the next system re-start, but if it isn't and the problem persists, I guess I could always uninstall/remove the device from the same Windows dialogue. Don't need the mic and the camera seems to work just fine with it de-activated.

 

EDIT: It is indeed a permanent deactivation. The mic still shows up but is now listed as deactivated after a complete restart.

 

 

S.

Edited April 8, 2022 by 1Sascha