Dream Air keep asking for USB 3

not sure if this is a dream air only issue, but just got my SLAM version this week. it worked a couple times but now will not. Dream Air is saying it can’t track because i need to be using USB3.0 . funny because that is what it is plugged into. tried two different computers.

this seems to be happening on Version 2.0 pimaxplay. i did try reverting back but there are tones of hidden files that their un-install does not fix. lets just say things went to hell in a hand basket fast.

after a long day i’m back to version 2.0 but a Brick for a headset untill they figure out the usb3.0

Pimax has files in the “AppData” and on your C drive as well that you will need to delete. With the files in the C: drive you will need to use your admin privileges to delete them. Did you try going back to the 1.43.9 update and click “Clean install” when you are installing it? Here is a link to older Pimax software updates Blog

1 Like

unfortunately i did try and things just kept going down hill from there. just in case it matters, i am a software engineer so i do know computers. while i did have the headset working when i got it on version 1.44, the SLAM keeps going out of track in game play and you couldn’t recenter it. when it went out of wack, the image was upside down, or behind you etc. so you could just recenter it. you literally had to take it off to go to the monitor and restart it. i do think the headset will be great once they figure out all the software issues.

just hope we don’t have to wait months for these fixes. i already waited 4 months to get my expensive brick.

1 Like

also that’s a great link!!!, I’ll try that in a day or two when I’m ready again to in-flick self pain.

1 Like

I personally didn’t like the performance of the 1.44.2 software with my Super UW. Felt like it killed about 30% of my performance. I moved back to 1.43.9 and everything felt better for me with that headset. I am now on the Pimax beta 2.0.1 update with my Dream Air and did the new 1.0.3 firmware update with it and it feels stable. I don’t know why they are simultaneously updating two different versions, especially with different firmware in each one forcing users to have to try and find a way to get back to the beta version without any direct download links to it.

1 Like

This is really good to know, I was hoping to find this info. I’m on 143.9 with the Dream Air and unsure if going to 1.44.x or Beta 2.x with the firmware update would make things better or worse. I feel performance is worse than it should be.

I’ll consider PP 2.0.1 and FW 1.0.3 with it and see if things improve.

this image shows that the dream will not find the USB 3.0. However from the usb tree you can see that its on 3.0. So i’m not sure what is going on. if any of you see something or think i need to perfrom a test let me know. right now i just have a expensive brick

things worked fine for me when i first installed everything. then the headset wanted a update and after that thins worked 1 time, after i came back the next day nothing woudl connect or work.

not sure what the issue really is.

2 Likes

Did you get any of these errors? My first Dream Air basically died after the 1.0.2 update on 1.44.1 update right after I got it and plugged it in. I troubleshooted it for about 4-5 hours on my end and tried it on another one of my PC’s and both PC’s it gave me a USB error and wouldn’t work. Submitted a ticket and got approved for an EMA pretty quickly after I overloaded them with my troubleshooting efforts and it took about 10-12 days to get another Dream Air headset in. My 2nd Dream air works great so far after about 2 weeks of use.

1 Like

so no errors like you showed. just the one in my image where it says the “sensor can’t track headset”

when you click on “learn more” that is where it says i need to connect to a USB 3.0 which i think i have shown its connected to.

sine the software upgrade it also did a firmware upgrade on the headset so I’m thinking that maybe the firmware might be out of syn now?

if i remember correctly, i also had issues that even when i had a timeout for screen off, that the headset never turned off. so maybe i have a bad one.

Have you tried connecting the headset to a different USB port?

Also, please make sure UVC camera permissions are enabled. Then check whether HAGS is enabled. If it is, try disabling it and see if that helps.

yes i have tried multiple ports and multiple PC. the support team is now sending me a new headset so if that does not work, then that mean the two PC’s need fully rebuilding augh!. The team however looked at both PC logs and they think the headset has an issue. time will tell and i’ll get back to everything once i have the new headset and test. thank you all for the suggestions and help!!

also last night i did all the UVC stuff but no help. Also HAGS is off .

No worries. Please keep me posted once you receive the replacement unit.

I’ve had this issue as well. From memory I think I fixed it by unplugging it, restarting the computer, then plugging it back in again…

thanks I’ve tried three computers now and still they all have the same issue.

when i get the replacement headset I’ll do some test to see if it the headset, power box or connector where the speakers are.

at this point I’m dead in the water till i get a replacement.

thanks

If you didn’t hear from the support about the replacement, please let me know.

thank you, they said 1-2 weeks. So i am in holding.

will let you know

1 Like

ok got the replacement today and hooked it up. took a whole lot of fiddling to get it to work but it seems to work ok…

since it worked, that does determine the old headset simply died. one thing i did notice on the old one is the junction box behind the headset was not getting warm, so maybe that is the failure point.

one thing i did notice on the new headset is that the “desktop” and toolbars inside the pimaxplay 2.0 app seem to be a little bit blurry. i understand you can change the desktop screen res that helps in desktop view, but nothing clears up the toolbar.

Also the home screen is a bit blurry too. Is this normal?

Blurry? Is the QV enabled?