Forum Replies Created
-
Posts
-
If 3D is working, that’s probably as far as it gets. Field of view (‘zoomed in’) is typically handled by automatic .ini tweaks in official Unreal Engine 4 profiles if possible for a game. These things are game specific and do not carry over when you create a user profile unfortunately, so for your custom profile you have to deal with FOV some other way. Typically the PC Gaming Wiki is a good source of information in that regard, but the Everspace 2 entry is still empty. Probably the game is too new.
For now it seems you will have to rely on vorpX’s ‘Image Zoom’ option to deal with the matter. Simply lower the ‘Image Zoom’ value until the image doesn’t appear zoomed in anymore and that’s it. That way can you resolve a zoomed in view for pretty much any game within seconds. Not a perfect solution as setting the actual game FOV would be since it will introduce black bars above and below the image, but that’s clearly better than a too low FOV.
I’m probably the most untypical Skyrim user ever, so nothing anyone has to care about when deciding what they want to use, but I actually still fairly often wander around near Whiterun in the original DX9 Skyrim for 10 minutes after a long day of work, marveling at northern lights (alternatively slaying a bunch of wolves if it was a bad day). Never could warm up to the odd colors of the Special Edition.
Was one of the first things I did with vorpX about eight years ago before it was even called vorpX, and will probably also be one of the last things I’ll do with it at some point.
Funny enough I never really played the game except for the first five hours or so although I loved Morrowind and Oblivion before and wanting to play Skyrim on my pre-Rift DIY VR headset was one of the major driving forces behind starting with what later became vorpX. Working with the game on a regular basis for a fairly long time somehow spoiled playing it for me in the end.
OK, so far so good. I’m not 100% sure what the performance increase will be in every single game, most of the time it’s the expected ~10% with the observed best case being almost 20%, although that’s not something to expect in general. In some cases surprisingly it doesn’t change much at all. Long story short: since this change would affect basically everything and theoretically may have side effects, I don’t really feel comfortable implementing it without broader testing. That’s where you come into play if you want.
All you would have to do is playing your games as usual while occasionally switching between the regular and the beta headset sync and letting me know if you encounter anything noteworthy with the new method (jitter, no difference in framerate at all, cat dying, etc.). That would be a tremendous help in letting me decide whether it’s worth it or not.
Shoot me a mail to support |at| vorpx com if you are interested, I’ll prepare a beta version for early next week.
Windows 7 is always a bad idea when it comes to VR, Windows 10 has a bunch of VR related under-the-hood improvements. Oculus doesn’t support Windows 7 at all anymore, Valve (SteamVR) don’t care anymore if things work with it or not according to their own support. I don’t think that’s the reason for your issue, but it’s time to say Goodbye to Windows 7 anyway, as many valid reasons as you may have for sticking to some 10 years old OS.
Try resetting everything to default first though, it’s more likely that there is some settings related issue. The performance impact of Z3D should usually be fairly small, no matter what OS you use.
Indeed, with Z3D performance should be better. I would suggest to reset everything to default, game options as well as vorpX profile (can be done in the config app) and check whether that makes a difference. Maybe you have some option enabled somewhere that causes a huge performance hit.
If you have Geometry 3D enabled, probably yes. Keep in mind that everything has to be drawn twice with G3D, roughly cutting the framerate in half. Also vorpX increases the field of view of the game to match the FOV of your headset, which also involves extra work since more stuff has to be drawn. On top that there is a little overhead for rendering to the headset due to some snycing between headset and game.
All this extra work typically makes demanding games CPU limited with Geometry G3D, although at 4K you might also be GPU limited. If you are OK with that, switch to Z3D in the vorpX menu, which is way less demanding since it comes without the need to draw everything twice. If you want G3D and higher framerates with a game that demading, there is no way around reducing graphics details further.
BTW: Although not exactly comfortable, vorpX makes it possible to play at framerates below half the headset’s refresh rate if you can stand it. Most native apps would end up in a jittery mess when you try that.
Unfortunately I was never able to replicate this issue. Did you try the ‘alternative hooking’ method in the config app? That can sometimes help without getting to the bottom of a hooking conflict. Don’t forget to switch back though later even if it helps, some games require default hooking.
Did you add the custom resolutions to your display driver like suggested above? After doing so you can run games fullscreen with a higher resolution. Wether you want to do that manually or let vorpX do it doesn’t matter.
That can happen in some (many) games if you run a game windowed with the window being larger than your desktop res. You could address that by adding a custom resolution instead and then run the game fullscreen. You can find detailed instructions in that regard in the vorpX help under ‘Custom Resolutions’.
BTW: In case you disabled automatic settings for the game, please re-enable that feateure. That will not only allow you to set the resolution through the vorpX ingame menu, it also ensures that vorpX can apply some tweaks that are useful for playing the game in VR.
So far no actual reason to intervene here, so just in case, out of experience: please keep any “Skyrim VR” vs “Skyrim vorpX” discussion civil. Those seem to have a tendency to escalate.
Skyrim VR is great and a perfectly valid choice, but apparently there are still some people who prefer to use Skyrim plus vorpX for individual reasons, which neither makes them idiots nor does it invalidate anyone’s choice of Skyrim VR over vorpX. The same is true vice versa, of course. So no reason for potential flame wars at all.
True Northmen argue about the next country to pillage, not about the right way to play Skyrim with a VR headset! ;)
A little update: after trying a few more ‘difficult’ cases, i.e. games that make heavy use of multithreading, I’m not fully optimistic anymore about the whole thing, but nothing is off the table yet.
Thanks for the work you put into providing those links, which gives me the opportunity to explain one more time why no additional screen options will be implemented at this point. The key here, again, is finding the right balance between keeping the amount of options sensible and fulfilling everyone’s wishes, which unfortunately isn’t always the same.
Since the original cinema mode was introduced the feedback you linked above has actually helped to make the screen feature what it is now. A whole new ‘Play Style’ option in the form of ‘Immersive Screen Mode’ has been implemented based on the feedback you linked above.
At this point however, after years of user feedback and refining, there is everything available option wise in that regard that is important when focusing on a VR experience. I always listen to suggestions, otherwise a lot of what you see currently in the menu in regard to screen customization wouldn’t exist. Pretty much only simulating a TV like small screen, like you prefer, isn’t really a priority. If anything, some people wanted the screen to be even larger as you can see for yourself in the posts you linked, which has been addressed by ‘Immersive Screen Mode’.
vorpX’s main focus is and remains VR. I always keep one eye on the dwindling stereo enthusiast community as well, e.g. not too long ago vorpX got SBS output due to (semi) popular demand, but occasionally keeping things focused on VR might collide with one or the other wish of a hardcore stereo 3D enthusiast. Sorry again for that.