Forum Replies Created
-
Posts
-
I believe if you are using a Rift you MIGHT need to have Oculus Home running if it wasn’t already. I think you only need Steam VR running if you’re using the Vive (I have to run it with my Vive that way, anyway, and I’ve never tested VorpX with my DK2 so I’m not too sure there.) The other big thing, though, might be to make sure you try disabling things like any security software you have running to see if that might be interfering. Do you have something like Comodo or AVG running, by chance? Those can cause issues in certain configurations (especially if you’re running Comodo and you notice any windows with your application that have a green border added to them which indicates Comodo has “sandboxed” that application which would definitely prevent something like vorpX from working.) That’s different from the firewall, though, so just disabling the firewall probably won’t fix the problem.
FYI, the compatibility list would be the same no matter what platform you were using, Rift or Vive. The only thing about the Vive that might be different would be use of the controllers, which I can’t really see how Ralf would ever be able to implement that within vorpX. However certain games could potentially be modded to allow motion controls. GTAV, in particular, has someone already working on exactly that, for example, and some folks have done similar for Skyrim but I want to say that in both cases they were done for the Raze Hydra, maybe? That kind of work should be translatable to the Vive controllers, though. That’s really up to the modding community for those particular games, however, not really a vorpX thing, I don’t think.
The only other thing of note for me using vorpX has been that many games don’t really handle full positional tracking, it’s really just head look (you can look right and left, up and down and cocking the head but not leaning forward and back or moving side to side or up and down.) This can cause VR sickness, or at least discomfort, for me but you can kind of work around that a little by running in the big screen mode and just moving the screen closer to fill your field of view more. That way your motions are still tracked in that virtual theater so it can be a little more comfortable.
I had to revert to using the vorpX Web Installer again because I don’t feel like hooking up my DK2 again for vorpX to recognize a headset to it will update (Ralf, it might be nice if the updater worked even without a connected headset if possible). A quick check after the install and the Vive appears to work great! Now to play around with it some more… Thanks Ralf!
Ralf would have to verify, but I’m pretty sure there won’t be two separate versions of vorpX (a Rift version and a Vive version). You should be able to buy it now if you like and it will work with your Vive when that ability becomes available. That being said you might want to wait just because the software installation or at least the upgrading process has, at least previously, relied on a working headset being connected and presumably at this point it won’t recognize your Vive as that working headset until it supports it. So it may just go smoother for you if you waited.
Metalsech, I think you misread me. Despite the error everything seems to be working. Try running ESO and see if it starts up in vorpX for you.
I just remembered I have Mass Effect 3 installed and ready to go so I started it up (without the Desktop Viewer running, mind you, as I saw Ralf suggest in another thread) and it popped up perfect! The black smear is as bad as usual, but that’s a DK2 issue. ;) So at least in quick testing vorpX does seem to be working just fine (outside of the oddities on startup mentioned above.) Yay!
Just ran the update (the Oculus runtime also had an update today) and I think maybe we’re sort of looking at behavior as expected. With the latest update now if I start vorpX it goes to Please Wait (without the mountains icon) but shortly thereafter gives a message of “Sorry, we’re having trouble loading vorpControl.exe. Please take off your headset and check your computer for error messages. You may need to close vorpControl.exe or address windows associated with it in order to get back to VR.” However… if I then do something like start the vorpx Desktop Viewer it start up just fine. I haven’t tested other games yet (I’ll do that when I get a chance and report back) BUT it seems likely that the error we are seeing in the DK2 isn’t really an error at all, it just means vorpX is waiting for something to send to the HMD. So everything may very well be working just fine and we just need to try and run stuff to get it to display!
Also once you exit Desktop Viewer it the DK2 just goes black. It’s still on (the blue light is on) but the actual display goes off, which I like and is actually something I expected might be expected behavior for vorpX. Starting it back up works just fine, too. So, Ralf, I think your latest fix probably did the trick it may just be a question of finding a way to handle that initial display of that error message instead and whether or not you intended to completely displace the Oculus Home display when vorpX isn’t otherwise doing anything (which I have no problems with, mind you, I think having the screen turn off is just fine.) Great job!
I don’t have the other runtimes installed so I don’t think that’s it. I did notice in this thread, however, that another person with the same issue, edo, is having the same problem but noticed that “ok got a few games to run, eg skyrim, batman, fallout 4, however I never get rid of that “Please waiting” screen which launches as soon as I start vorpx.”
I do have Skyrim so I may try to see if vorpX interfaces with it correctly later. He did state that GTAV and the vorpX Desktop (I have tried the latter) did NOT work from him, though. I think Ralf may have also misinterpreted his claims of the grey screen sowing up as being the disclaimer screen rather than the “Please Wait…” screen. So we’re definitely seeing something hang. Ralf did mention in that thread that you can contact support [at] vorpx.com to get the previous version of vorpX that runs with the 0.8 runtime if you really want to get up and running right away. Personally I’m fine sticking it out and seeing if we can figure out what’s happening, though. So far I think we are seeing a common thread here of Windows 10, GTX 980 cards and using the DK2. I do have a CV1 on the way, but I’m a :45 order so I suspect I won’t see it until probably May so I can’t be much help on seeing if that makes a difference for us.
Playing around a bit more I was looking at the Devices section in the Oculus Home app. and everything looks fine (connected, no errors) but when I start vorpX the Sensor flags a warning and when I switch to it the warning shows “Poor tracking quality (?)” clicking on the (?) then shows “Sensor sync cable disconnected”. Which I believe is what is causing the errors in the Application logs. However I also found this which leads me to believe it’s just a common issue of using the DK2 in general so it may not be related to vorpX at all. In other words I think that part is just a red herring, I’m sorry to say. Back to the drawing board…
Agreed, but they don’t crop up with normal usage, just when I started vorpX, so I’m guessing it may just be that. I’ll try a reinstall, though, and let you know.
One last note, I have dual 980s running in SLI mode. I tried disableing SLI just to see if that might be the issue but that made no difference either.
Not sure if it helps but I am seeing some Warning errors in the Windows Application log when I start vorpX such as the following:
“The description for Event ID 0 from source OculusVR cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
15:29:40.735 {WARNING} [HW:Health]
Hardware health is BAD.
0100 202FYX07CJGR: 0x0 (0): ovrSuccess
IMU Stats
per total
Messages 2497 216467
Samples 4994 474458
Lost 0 356
Interpolated 0 0
HMD Avg Latency 2
p95 Latency 2
CPU Avg Latency 71
p95 Latency 977
Set FR Failures 0
Get FR Failures 0
Last FR Failure Time 0.0
Report Rate 500
Temperature (C) 31.20087 212FYX07CJGR: 0xfffffffffffff05b (-4005): ovrError_ExcessiveFrameTruncation Sensor truncated a higher than acceptable number of frames in the last time period (expected <= 1, got 2)
Frame reception stats
per total
Complete Frames : 298 25380
Truncated Frames : 2 76
Skipped Frames : 2 78
Recovered Frames : 0 0
JPEG Errors : 0 0
Sensor Die Temp : 0.00
Near USB Controller Temp : 0.00
Near CCM Temp : 0.00
USB Speed : 0x0200
Driver Stats:
Frames Delivered : 25456
Iso Reads Submitted : 141451
Iso Reads Completed : 141446
Iso Reads Failed : 0
Iso Read NtStatus : 0x00000000
Iso Read UsbdStatus : 0x00000000
Iso Read No Requests: 19
Iso Read Cmpl Bytes : 9292408964
Iso Read Total Bytes: 9227004764
Bad Iso Packet Ctr : 202
Last Bad IsoPkt Stat: -1073545216
Last Bad IsoPkt Time: 583303
Current Time : 589729.835327the message resource is present but the message is not found in the string/message table”
Followed by an Error:
“The description for Event ID 0 from source OVRServiceLauncher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
[SetProcessGPUPriorityClass] Target process did not respond in time
the message resource is present but the message is not found in the string/message table”
Loath as I am to do that (I’ve never had issues with vorpX and Comodo before, then again I have a clue how to configure it…) I went ahead and did a full uninstall of it. Made no difference, though. Still just sticks at “Please wait…” If I stop the vorpX service with the right-click on the vorpX icon on the tray it does go straight to the Oculus Home screen without any issues.
Same set-up (Win 10, GTX980, DK2) and same issue here. Oculus Home version is 1.3.0.198914 (1.3.0.202883). I’ve set it for running as administrator as well as completely disabling Comodo (firewall/internet security/anti-virus software) which vorpX never had any issues with before but I thought I would try that just in case. I even tried just right-clicking vorpX with Run As Administrator that was as well, but no difference. It just goes to the disclaimer screen and when clicking past it just “Please wait …” endlessly. :(