British_Dragon_14 Posted October 30, 2024 Posted October 30, 2024 Hi, I loaded up DCS yesterday and noticed that the rendered box wasn't following my eyes after I loaded up a quick start mission. I then uninstalled Pimax and reinstalled (the same version: V1.33.02.01.03 ) and the 'eye chip' in Device Manager was still greyed out and the IR lights were off in the HMD. I then updated Windows 11 and tried multiple USB cable combinations, even unplugging everything except both the Pimax cables, black into red, blue to blue. To see if it was an underpowered USB issue. I only have Blue plugged into Blue usually as I have a USB power box for prolonged Crystal battery life. So the black cable is just left hanging unplugged and I have a powered USB cable plugged into the right side of the HMD. I have tried re-seating the lenses and nothing I've tried from the internet seems to work. I did get it working briefly when I re-installed the Pimax software. I double checked with my camera phone and all the lights around the lenses were on, I re-calibrated my eye tracking with the Pimax software, loaded DCS up and the eye tracking seemed to work in the DCS menu until I loaded up the quick mission in the F-5 Tiger II 'Cold Start: Syria' and the eye tracking stopped working. I've been trying to figure this out all day today and last night. British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Calvin.Pimax Posted October 30, 2024 Posted October 30, 2024 Seems like it's related to the USB. Have you tried to switch the 3.0 port?
British_Dragon_14 Posted October 30, 2024 Author Posted October 30, 2024 I have 3.2 ports. Red and blue. I think the red ones are faster but I read that the cable doesn't like the red inputs. My Crystal has been working fine since I've set it up, until yesterday. I tried switching to every port where it would fit on the Z690 Auros Master. It's always worked on the top left one. I've followed the instructions on the Pimax website as well: Crystal Eye-Tracking Troubleshooting Steps : Pimax Support I know the lenses are properly seated because they are auto detected as 35PPD Glass. I'm just about to send a ticket with an export log attached.null British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Calvin.Pimax Posted October 30, 2024 Posted October 30, 2024 If you haven't heard from our support team, please let me know. They will review the log files to analyze why the eye-tracking cuts off after some time; the error should be recorded in the log files.
British_Dragon_14 Posted October 30, 2024 Author Posted October 30, 2024 The IR lights and Eyechip just came on as I took every USB cable out. I then started to tactically put the rest of my cables in whilst leaving the Crystal USB cable in it's own HUB (blue left side) on the motherboard. The lights were still on until I went to calibrate my eyes and it turned off again. Thanks. British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Nuggetz Posted October 30, 2024 Posted October 30, 2024 I don’t know why but I also experienced problems with eye tracking dropping out. The fix that worked for me was not to plug the Crystal USB 3.0 cable into a USB 3.0 socket on my PC, but to plug into a USB 2.0 socket instead which continues to work normally. HTH Ryzen 9800X3D, MSI RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C.
Nedum Posted October 30, 2024 Posted October 30, 2024 (edited) Hi, I had a similar issue. The only thing that helped me was to uninstall the whole Pimax Software, restart the PC, and install all the Pimax SW again. That did it for me. But you did that already, so I would really like to read if and how you can fix it. Edit: Perhaps you can try a Windows repair. With that, you have the possibility to only reinstall all the drivers. For me, it looks like there is a driver conflict. Try to check step by step if there is one USB Device which fight the Pimax drivers. I can't believe that this has something to do with the Pimax Hardware. Edit 2: Have you tried only the Pimax without any other USB Device? No Stick or other USB stuff, only M+T and Pimax. Cheers Edited October 30, 2024 by Nedum CPU: AMD Ryzen 7950X3D, System-RAM: 64 GB DDR5, GPU: nVidia 4090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal, OS: Windows 11 Pro, HD: 2*2TB Samsung M.2 SSD HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick Rudder: WinWing Orion Metal
British_Dragon_14 Posted October 30, 2024 Author Posted October 30, 2024 12 hours ago, Nuggetz said: I don’t know why but I also experienced problems with eye tracking dropping out. The fix that worked for me was not to plug the Crystal USB 3.0 cable into a USB 3.0 socket on my PC, but to plug into a USB 2.0 socket instead which continues to work normally. HTH I have a picture of all my USB inputs that I have access to further up. They are all 3.2. My Crystal worked fine since I set it up months ago. Now all of a sudden the eye tracking has stopped. 10 hours ago, Nedum said: Hi, I had a similar issue. The only thing that helped me was to uninstall the whole Pimax Software, restart the PC, and install all the Pimax SW again. That did it for me. But you did that already, so I would really like to read if and how you can fix it. Edit: Perhaps you can try a Windows repair. With that, you have the possibility to only reinstall all the drivers. For me, it looks like there is a driver conflict. Try to check step by step if there is one USB Device which fight the Pimax drivers. I can't believe that this has something to do with the Pimax Hardware. Edit 2: Have you tried only the Pimax without any other USB Device? No Stick or other USB stuff, only M+T and Pimax. Cheers I tried unplugging absolutely every USB wire and trying every port with the Crystal wire multiple times and I did get the IR lights to come on once yesterday but they turned off as soon as I lifted the HMD up and put it to my face to do the eye calibration. I've been at this for the third day in a row now. I'm going to try to repair Windows 11. I would re-install Windows 11 but I haven't enough space to back up my C drive. British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
British_Dragon_14 Posted November 1, 2024 Author Posted November 1, 2024 Just to let you know and anyone else in the future. It is fixed and it was the Display port cable. Someone told me from Pimax that I should try and bypass the cable on the left side and plug it straight into the HMD directly. The IR lights came on straight away! I have just been testing it in quick missions on Syria and Nevada for a couple of hours just to make sure and it's now fine. I would never have guessed that it was the Display port cable that goes into my GPU. I guess I just need to zip tie the cable to the side now. I've also tucked the unused cable behind it's port to keep it from hanging down. British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Chief_Biv Posted November 1, 2024 Posted November 1, 2024 I don't quite understand what you did differently. I thought there is only one way to connect the Crystal to the Display port on the GPU. What have you done differently to fix this that is different from normal method? nullnull PC Hardware: i9-12900k, RTX 3080 10GB, 32GB DDR5 4400MHz, NVME.2 Drives, Alienware 38" 3840x1600 144MHz Monitor, TrackIR Pro Clip, Pimax Crystal Flight Controls: Winwing Orion 1 FA-18 Stick and Throttle HOTAS / Logitech Rudder Pedals DCS Modules: Too many to list after the 15 year sale
MrOrangePZ Posted November 6, 2024 Posted November 6, 2024 On 11/1/2024 at 2:00 AM, British_Dragon_14 said: Just to let you know and anyone else in the future. It is fixed and it was the Display port cable. Someone told me from Pimax that I should try and bypass the cable on the left side and plug it straight into the HMD directly. The IR lights came on straight away! I have just been testing it in quick missions on Syria and Nevada for a couple of hours just to make sure and it's now fine. I would never have guessed that it was the Display port cable that goes into my GPU. I guess I just need to zip tie the cable to the side now. I've also tucked the unused cable behind it's port to keep it from hanging down. I am having the same issue, what exactly did you do? I do not understand your description. As the poster before me I only know this way to do it
Solution British_Dragon_14 Posted November 8, 2024 Author Solution Posted November 8, 2024 (edited) On 11/1/2024 at 2:06 AM, Chief_Biv said: I don't quite understand what you did differently. I thought there is only one way to connect the Crystal to the Display port on the GPU. What have you done differently to fix this that is different from normal method? nullnull I unplugged the Display port that goes in to the head sets extended cable that is on the left side of the HMD and I then plugged it in directly into the HMD, bypassing the extender. The cable isn't in that picture. It is what the furthest left cable plugs in to, on the left side of the HMD.null Edited November 8, 2024 by British_Dragon_14 The tiny cable extension is missing from the picture. 1 British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Hawkeye_UK Posted November 8, 2024 Posted November 8, 2024 Had the Crystal for 7 months, didn't even know that the plug on the left side on the frame was an extension! Will be checking mine when back home, is this a bug or something with this patch, how come a few people reporting this? 1 --------------------------------------------------------------------------------------------------------------------------- DCS & BMS F4E | F14B | AV-8B | F15E | F18C | F16C | F5E | F86 | A10C | JF17 | Viggen |M2000 | F1 | L-39 | C101 | Mig15 | Mig21 | Mig29 | SU27 | SU33 | F15C | AH64 | MI8 | Mi24 | Huey | KA50 | Gazelle | CH47 | OH58D | P47 | P51 | BF109 | FW190A/D | Spitfire | Mossie | CA | Persian Gulf | Nevada | Normandy | Channel | Syria | South Atlantic | Sinai | Kola | Afgan | Iraq Liquid Cooled ROG 690 13700K @ 5.9Ghz | RTX3090 FTW Ultra | 64GB DDR4 3600 MHz | 2x2TB SSD m2 Samsung 980/990 | Pimax Crystal/Reverb G2 | MFG Crosswinds | Virpil T50/CM3 | Winwing & Cougar MFD's | Buddyfox UFC | Winwing TOP & CP | Jetseat
British_Dragon_14 Posted January 9 Author Posted January 9 On 11/8/2024 at 2:55 AM, Hawkeye_UK said: Had the Crystal for 7 months, didn't even know that the plug on the left side on the frame was an extension! Will be checking mine when back home, is this a bug or something with this patch, how come a few people reporting this? I don't know if it's a recent bug but it seems that the eye-tracking wasn't working with the side mounted extension for some reason. I would personally recommend that people just plug it in directly. Their has been quite a few Pimax Play updates recently and I haven't been in VR for over a month now. I've only just purchased the VR controllers so I'm hoping to try it again ASAP. Maybe with some other VR Contoller type games too. I just received an E-Mail from Pimax. This is just to say that my issue was resolved by doing the above, which was bypassing the extension. Thankyou! British Dragon - Simulation Based Training 2 - YouTube Call sign: Albion 1-4| Dragon AKA British Dragon
Recommended Posts