![]() ![]() The rest of the ports on this board are 3.1/3.2 and/or Type C sockets. ![]() 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. 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 would post a screenshot of the error, but, as it happens, there are no errors reported in Windows just now. 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. The CL Eye Platform Driver provides users a signed hardware driver which exposes supported cameras to third party applications such as. Which normally doesn't even seem to stop the camera from functioning in Opentrack, but sometimes it does. I followed all their instructions on first installation to a T and everything seems to work fine - most of the time.įrom time to time however, I will get a driver conflict warning message for the camera in Windows' "devices and printers"-panel. If it fails to work, try connecting the camera onto a USB 2.0 or a USB 3.0 controller that you havent used yet. There's another PS3 Eye driver by Code Laboratories that seems to take a similar approach to this driver in that it provides a custom DirectShow source filter instead of using the default wrapper. 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. Thus if the source filter is only provided as a 32 bit library the camera can only be used by 32 bit applications. Since my TrackIR5 is in storage in another city, I had to switch to a new solution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |