Forum Replies Created
-
Posts
-
If you use any other antivirus than Windows Defender, please try to uninstall it for testing. Some of these programs do not allow their users to fully disable them. One example would be BitDefender, where you would also have to exclude vorpX from the so called “Advanced Threat Protection”, another one is Comodo, and there likely are others that behave similarly odd.
If vorpX can’t hook into anything, some software conflict is by far the most likely explanation.
One other thing: if you are using a dual GPU system, please make sure that your monitor and your headset are plugged into the same GPU.
I’d like to check myself, unfortunately the Oddyssey is not available here in Europe. But since other WMR headsets apparently work fine and so does the Vive, of course, it’s quite unlikely that vorpX is the culprit here. However as said above, as an Odyssey owner I currently would definitely wait.
I’d like to learn more about this though, so if you are willing to act as a guinea pig, send me a mail to support |at| vorpx com and we talk more.
Nothing to announce regarding native WMR support at this time. I will evaluate the options for vorpX in this regard early next year and then decide whether native support makes sense or not.
Currently Steam VR is the way to go. However, a lot seems to depend on the headset vendor’s Steam VR drivers. Judging from the posts here so far, Samsung seems to be more problematic, while others, e.g. Lenovo, seem to work fine. That’s based on a fairly small amount of feedback though, so take it with a grain of salt. As an Oddyssey owner I would currently wait until Samsung’s Steam VR implementation matures a bit more.
CryEngine usually uses vertical FOV values. If that was the case, 95 should almost suffice for a full image, but judging from your description that doesn’t seem to be the case here.
I haven’t tried yet, but with some luck they use a horizontal FOV in a way that is affected by the game’s aspect ratio, so setting a 4:3 resolution (or something even more narrow) is worth a shot.
Doesn’t have to help, but might.
Not even I do know that list. There are a lot of user profiles in the cloud based on existing ones that were never tested here. No problem if you want to help, but if you do a list that wants to be complete and precise, please make sure it is.
On a side note: there are a lot of 2D profiles in the cloud, so I think it’s safe to say that apparently those who uploaded these profiles found them worthwile to play. No such games were ever (and will never be) mentioned as supported, of course. Your bare minimum however is not the bare minimum of everybody else.
I don’t want to linger on 2D games too long as that is obviously far from perfect, but I’m not sure if I get how you could even call anything else close to fairly well for 2D games considering the minimum standard you apparently expect from vorpX. It’s quite safe to say that even for playing in 2D vorpX is the best solution by a huge margin: 1. head tracking, 2. various options to account for missing FOV, 3. no need to force games to windowed mode, 4. direct hooking into games instead of capturing the output, 5. VR controller support, 6. automatic headset audio. I think you get the idea. I could probably come up with at least five more reasons if I contemplated about it a bit.
I’ll have to look into it. Has not been checked for a long time, so I can’t rule out that there is some issue with the game.
There have been two similar cases yesterday with other games, which could be solved by a factory reset/reinstall. Probably an issue with a corrupt database.
Before you do anything: I’d really like to look into this. It would be great if you could ZIP the contents of your vorpX data folder and send me the archive to support |at| vorpx com, so I can take a look at the underlying issue.
The folder in question is: C:\ProgramData\Animation Labs\vorpX
The ProgramData folder is hidden per default, “Show hidden files” has to be enabled in the Windows Explorer options.
Many thanks in advance!
There might be a general incompatibility or maybe it’s something that doesn’t occur with the final build. Either way, for now please go back to stable Oculus 1.2.
—
Update 2018/01/18
An updated desktop viewer that works with Oculus Home 2 beta is now available and will be included in the upcoming vorpX 18.1.0 release.
For now please unpack the archive linked below to your vorpX program folder, overwriting the existing vorpDesktop.exe. The vorpX program folder usually is C:\Program Files (x86)\Animation Labs\vorpX.
First you should consider the original DX9 Skyrim, which is the better choice in multiple ways for vorpX. Better performance in most cases and doesn’t use the blurry post-fx antialiasing of the SE. If you don’t have a specific reason to use the SE and also have the original, following this advice most likely makes sense.
Apart from that:
For both Skyrim games you can simply select a preferred quality (1080p-1680p) on the Direct VR page of the vorpX menu, click OK & Save and restart. That’s all.
Keep an eye on performance though when you raise the resolution (ALT+F), games ideally should not dip below 45fps for good VR gaming.
———–
General resolution hint (containing additional steps for other games):
Since the latest version can set an optimized resolution based on a preferred quality you choose. To take full advantage of this new feature add all resolutions listed in the “Custom Resolutions” section of the vorpX help (or the according sticky thread here in the “General” forum) to your graphics driver and after doing so select a preferred graphics quality on the “Direct VR” page of the vorpX ingame menu.
For games that do not support this new feature 1600×1200 or 1920×1440 are good resolutions when using vorpX.
Very unusual. Try to exclude the vorpX program folder (C:\Program Files (x86)\Animation Labs\vorpX) from your virus scanner.
General rule of thumb: first suspect for any injection/scanning issue that suddenly occurs after an update is always an overzealous virus scanner.
If you have that at the very beginning of the game (the school/hospital floor, can’t remember exactly), please play through this sequence in EdgePeek mode. FOV will be correct after this short intro. Normally a notification is shown about that.
Please also make sure to restart the game once (or maybe twice) when you are prompted to do so, to make sure the right FOV is actually applied.
If you make sure that there is a way to link the key request to the purchase, e.g. by mentioning the purchase name, it should be OK.
Will take a little while though (usually a few hours max.) since such a key request can’t be auto processed.
With a larger FOV more has to be rendered which affects performance. Half sounds pretty extreme, but I would assume that is what you see.
There have been no changes to the desktop viewer in the recent release. Only thing that comes to mind is an injection conflict, specifically a virus scanner issue, which can happen after an update although all was working fine before.
To check that, please exclude the vorpX program folder from scanning (C:\Program Files (x86)\Animation Labs\vorpX).