Forum Replies Created
-
Posts
-
Thanks for the ass kissing. ;)
There was one report earlier that sounded quite similar to what you are experiencing. Turned out the the issue was caused by forcing Ambient Occlusion through the nVidia driver, which doesn’t work in conjunction with vorpX in Geometry 3D mode. So that might be something worth to check.
Regarding 3D modes: This has to be done game by game and is a fairly complex process. Technically it’s not hardcoded in the sorce code, but it’s not something that can be done by a user. So in a way you could indeed call it hardcoded.
In modern Windows OSes only drivers can cause BSODs. vorpX itself is technically incapable of doing so. It might however create a condition where a driver causes a BSOD.
Please try first without overclocking and voltage manipulation of both your CPU and GPU. Using vorpX is more taxing for both your CPU and GPU than running a game normally, so it may be the case that this is just too much for your overclocking settings.
Since there have been no other reports of something like that so far, I would say that’s not unlikely.
No reports at all in this regard until now. Maybe a very odd conflict with something else you may have installed.
The documentation has a few general hints in the trouble shooting guide what sort of programs can cause conflicts with vorpX, but such conflicts do not create BSODs normally.
Sorry for the inconvenience. We received one registration request from you last Monday, which was answered instantaniously. Besides that we only received your original request in February, 2014, no other mail.
Please check your spam folder if you didn’t receive the activation key that was sent on Monday. I will also resend it right now, just in case.
If you reinstalled vorpX using your web installer last Mondey, you already have the latest version BTW.
I assume you are using a DK1? Apparently a few DK1 users are experiencing this. Please try to (re)install the latest Oculus runtime (0.41) from the Oculus website. Normally it should have been installed with vorpX, but maybe that failed in your case.
If that doesn’t help, please send a mail to support |at| vorpx com to get a rollback option to vorpX 0.64.
Skyrim’s UI can also be scaled with vorpX (display page of the ingame menu or [ALT] + mousewheel).
Personally I don’t really like that, immersion is far better without an UI in front of your face. But that’s just my opinion, of course.
That is normal. Bethesda game disable the mouse when a gamepad is connected.
No big deal though. When you disable the gamepad in the game, vorpX’s internal gamepad emulation takes over, so you can still use your gamepad. You can adjust button mappings to your liking in the vorpX ingame menu.
Hello Renifizzle,
Arma III is currently buggy. Probably just a profile issue, but I’m not quite sure yet. Apart from the temporary fix you already found I can’t offer an instant solution unfortunately.
I will take a look a independent head tracking when I search for the bug, No promises though. You might be able to get independent head tracking with an external tool like OpenTrack, which can emulate TrackIR input with the Rift.
Sounds like some basic configuration isn’t right. Did you go through the DK2 setup guide in the documentation? In case of issues please use the most compatible setting mentioned there (DK2 as primary display, “Use system settings” display wise in vorpX,details are in the guide).
Please follow the guide completely. Every step is important.
I’ll revisit the game before the next update and will fix or disable shadows if possible. At least the latter is possible in most, but not all, cases.
Just in case: Please check whether you use an Oculus profile in the config app. That is buggy currently.
Check whether the game is set to a resolution of 1920×1080
Also make sure to select the correct eye cup setting. Selecting A-Cups produces an image that fills the screen vertically completely and is much larger horizontically. Physically impossible to get more image space.
Unfortunately there still seems to be an issue for some with Portal 2 that is completely impossible to reproduce here. Not on a single machine. I am aware that this doesn’t help you at all, but in most cases the game works fine.
Since the issue isn’t reproducible here, it’s also not possible to begin searching for a fix.
About 3/4 of the games on the supported games list are Geometry 3D games.
Creating profiles for games is a fairly complex process, for both Z-Buffer and Geometry 3D. Right now there is no tool that would be usable even by an advanced user. I may look at something like that later, but it’s not a priority right now TBH.
Did you go through the DK2 setup guide in the documentation? It has all necessary information about the basic DK2 and vorpX setup.
Also please make sure to run all games at the native resolution of your DK2 (1920×1080). This is highly important.
Last but not least, make sure to not use an Oculus Profile with the current vorpX version, there is a bug that causes an wrongly scaled image, which may lead to problems converging the stereo image.
I suppose this is still Skyrim related? You should disable the controller in the Skyrim options. When a gamepad is active in Skyrim (and other Bethesda games), head tracking does not work.
vorpX has its own gamepad emulation that takes over when the gamepad is disabled in Skyrim. In this mode the right stick controls the vorpX cursor in the vorpX ingame menu, that is by design. You can remap keys to your liking in the vorpX ingame menus.