Forum Replies Created
-
Posts
-
You shouldn’t have to adjust the FOV manually for Bioshok (or any other game in the beginner’s list). vorpX does that automatically for Bioshock and about 150 more games.
For the original version the FOV is adjusted by the DirectVR memory scanner. For the remaster by auto editing the game’s ini file.
Reset the profile to default in the config app and afterwards make sure to follow any instructions that vorpX might display when you start the game.
BTW: The best way to play Bioshock with vorpX is the original version using DX9.
BTW2: Always read all messages that vorpX displays in the headset and the top left corner of the game window! These messages usually contain vital information, e.g. the above hint regarding the memory scanner if supported for a game.
I can’t replicate the issue here, so there is nothing specific I could recommend.
All I have are general hints that red as a fairly experienced user probably tried already: running the game windowed/fullscreen, with or without antialiasing, reseting the game’s graphics settings to default, resetting GPU driver settings to default, resetting the vorpX profile to default and/or doing a factory reset.
Two of the three games (Soma and Crisis Warhead) aren’t officially supported. Unsupported games always open in ‘Immersive Screen Mode’ per default. vorpX does not automatically turn every game you throw at it into a perfect VR game.
If you haven’t done so already, check the ‘Essential Hints Guide’ in the help. It explains a few basic concepts. Reading that saves a lot of unnecessary frustration.
You may also want to check the ‘Good FullVR Games for Beginners’ list, which contains a compilation of games that vorpX has profiles with a high degree of automation for. Good for hopping right into the action without understanding how to make unsupported games work yourself in the best possible way.
Some games change/recreate the depth buffer texture during gameplay, which can be diffiult to detect. I don’t recall FFXV to be such a case, but I’ll check it. No promises though, such issues can’t always be reliably fixed.
What you could try on your end is checking whether running the game windowed/fullscreen makes a difference. Same for with/without antialiasing.
You can change the brightness (gamma) on the image page of the vorpX menu.
The game is not officially supported, but with some luck you may find a user profile in the cloud.
If noone did a profile yet, you can try to create your own by making a copy of a profile that uses the same 3D engine. No guarantee that it will work, but worth a shot. If you don’t know which engine your game uses, check the game’s Wikipedia page. It might contain this info in the fact box.
If you have a basic profile working, you can then try to isolate the HUD and make it scalable using vorpX’s shader authoring tools.
Doing so requires basic understanding of how 3D games work. If you already have that or aren’t afraid to learn a bit, check the ‘User Profiles’ section in the vorpX help. The second part of this section explains briefly how to get started with shader authoring.
I can’t really answer this question yet. A lot depends on how the VR runtime vendors will handle their Windows 10 only transitions in the end.
A reinstall should fix that. If you kept your web installer, you can simply use that to reinstall. If you didn’t keep it, you can get one here: http://www.vorpx.com/request-new-download/
At some point you will get left behind if you want to continue to use a 10 years old OS that not even its manufacturer supports anymore. That’s just the nature of things, sorry.
From a VR developer’s perspective supporting Windows 7 doesn’t make too much sense anymore. The latest Oculus hardware survey shows only 0.4% of VR users are still on Windows 7, a number that doesn’t really justify the extra work for testing and potentially applying Windows 7 specific fixes. So if you want developers to provide you with the newest versions of their software, at some point you finally will have to say Goodbye to Windows 7.
Can’t say yet when exactly that will happen in case of vorpX, but it sure will.
Probably not. Judging from the Cemu website they are using OpenGL for their 3D rendering. vorpX should be able to display most OpenGL games in the headset, but stereo 3D is limited to rather old OpenGL versions, unlikely that Cemu is based on a version that old.
I may look into stereo for more recent OpenGL versions at some point, but there just aren’t enough OpenGL games out there to justify making this a proiority. Always way to many other things that need attention.
I somehow doubt that it would have such a huge impact, but I have to admit that anime themed games are clearly underrepresented as far as official profiles are concerned. As always no promises, but I’ll check it.
Sounds as if you accidentally selected ‘Generic VR Headset’ or ‘Generic 3D Display’ in the config app, which would both render the image side-by-side on your monitor. Selecting ‘SteamVR’ (or ‘Oculus’ for Oculus headsets) as your headset on the ‘General’ page of the config app should help.
Should be fixed now. Under some circumstances the server script only returned user settings with the newest available version number.
Thanks for the heads-up!
Most UWP apps can’t be easily hooked like normal Win32 apps since they are typically protected against hooking into them.
I can answer this one: there seems to be an issue with database queries when listing cloud profiles. dellrifter’s settings are still in the database, but for some odd reason not all settings are listed anymore when using the cloud search.
I’ll take a look at it. If it can be solved on the server side, a fix will be made available within the next few days, otherwise it will be included in the next update.