Forum Replies Created
-
Posts
-
Not actively worked on ATM, but I won’t rule it out. The desktop app will definitely receive further updates, how far that will go feature wise depends on a few variables.
Sorry if I didn’t say that clear enough: As far as I’m aware they don’t support the DK1 after 0.7 officially anymore, but right now it is still supposed to work. Mostly wanted to express that DK1 support probably won’t be there forever, which shouldn’t surprise anyone as these are development kits and not consumer products.
The actual DK1 vorpX issue will be looked into shortly, I just wanted a bit of feedback regarding different runtime versions before that. The issue is quite strange, as vorpX doesn’t work any different with a DK1 connected than with a DK2, so this has to happen in the runtime somehow.
Hope that clears things up.
Did you apply the Game Optimizer Setting in the vorpX config app for VLC?
It sets the output to OpenGL, which is the preferred mode. If OpenGL does not work for you for some reason, you could try to select the DirectX video output in the VLC video options.
Just saw that your order was from earlier today. You should not only have received the MyCommerce mails long ago, but also a reminder sent from us directly.
If you did not get any of these mails, please double check your spam folder.
If you can’t find the mails there, please provide us with an alternative mail address, since apparently there is an issue sending mails to your primary address then. Thanks.
There should have been a link shown on the last page of your order process.
You will receive a mail from MyCommerce containig it shortly. Unfortunately this can take up to 20 minutes sometimes. Please also make sure to check your spam folder.
If you are sure that your order went through and you do not receive the mail from MyCommerce within an hour, please report back here.
I removed your mail address above, so it doesn’t fall prey to spam bots.
Could anyone with a DK1 try different runtime versions? This will be looked into here shortly, but it would be great to get some test results before that.
Would be great if some of you guys with a DK1 could check 0.6/0.7/0.8 and report back here.
Also please keep in mind that while it still works, the Oculus runtime does not really support the DK1 from 0.7 onwards officially IIRC.
There is no technical way to combine both. There has to be a 32bit program that hooks 32bit games and a 64bit program for 64bit games.
I’m sure you checked everything you can think of thoroughly, but there really has to be something on your machine that is different from the vast majority of others without this issue. In all likelihood some other program that creates a conflict with the 64bit part of vorpX.
The mirror window works only if a game is run windowed. If you run a game fullscreen you can usually display the normal mono-view of the game, but when you run a game windowed you get a new option on the display page of the vorpX menu that allows you to open a mirror window that shows what you see in the headset.
One issue with windowed apps like video players is that it’s easy to loose mouse/keyboard focus on the window. Many of the “menu does not show” cases are probably related to that. Make sure to click into the player window, so that it has mouse focus.
MPC-HC: please make sure that ideally you download the latest nightlies from the MPC-HC website, it contains a small addition for vorpX that allows for better data exchange between both players.
For both VLC and MPC-HC please also make sure to apply the vorpX Game Optimizer setting in the vorpX config app.
Not sure what to recommend here unfortunately. You could try to switch between 32bit and 64bit, but that’s just guesswork. Maybe one works better than the other.
Do you have the latest drivers for your graphics card installed? On nVidia graphics cards something like this could sometimes happen with very demanding games. Not just with vorpX, but any Rift app. With the latest drivers this is almost gone.
If that does not help, you may have to lower the game’s graphics settings further. Witcher 3 is a very demanding game. To get it run good, you have to play it on medium, better low settings, even on a highend machine.
Don’t let’s drag this on forever. Of course everyone has a higher FOV than the Rift, BUT the screen corners are usually occluded by the lens edges, maybe unless your eye balls are practically touching the lenses. This has nothing to do with one having a higher FOV than the Rift or not.
As said above, I’ll see what’s possible.
Very, very odd indeed. While you have a 180° fov, the screen corners are still hidden by the edge of the lens normally. I’ll see how much of the corners can be regained in the next version for you. You seem to have an exceptionally unusal, to not say strange, field of vision. No promises though.
Also be aware that the black bars that slide in from the edges when you move your head fast at low framerates won’t go away. As said above, they are an inherent artifact of the timewarping.
The black bars that move in from the outer edges when you sway your head are a side effect of the timewarp. It may be possible to reduce them a bit down the road, but in general they are an artifact of the timewarp.
Disabling the async setting doen’t disable the timewarp, it just synchronizes it to the game rendering and usually makes matters worse as the framerate goes down. This setting will be removed shortly.
If you really can see that outer part of the screen corners, you would also have to be able to look a fair bit beyond the top/bottom screen egdes, as the vorpX vignette is an exact circle with half the screen height as radius. Also to me it looks like AI is severely cropped at the left/right edges, which would be *really* bad, as you have less image space in that direction anyway, but maybe that’s an issue with the screenhot.