Forum Replies Created
-
Posts
-
Did you also add the 16:9 custom resolutions? That should do the trick in this case normally.
Your other question has no simple answer unfortunately. In this particular case, given that you didn’t apply an FOV hack and that you didn’t change any vorpX settings, the best FullVR aspect ratio is 16:9. In other games, where the actual game FOV is closer the the headset FOV, a 4:3 or 8:9 aspect ratio is best. That will also probably be the case with the next vorpX version for CP2077 once I have added an FOV hack. Figuring all this out automatically without you having to know anything about it is pretty much what the auto resolution feature is for.
Just in case you didn’t see that already: you can move the screen closer towards you. At -1.0 it fills pretty much exactly the entire view vertically when you look straight ahead. That doesn’t really make too much sense without raising the game FOV though!
The steps look correct.
BattlyEye is on per default. You have to disable it in the launcher.
If it still does not work without BattleEye, please check for potential conflicts with other programs on your PC that also hook into games. That’s by far the most likely cause of hooking problems. The pinned trouble shooting guide on top of this sub forum has more details on the matter.
I already have it working as intended again, classic over-optimization that in the end does the opposite of optimizing in some cases. Will be fixed in the next update.
Short supplement:
As a base for profile for DX11 SBS games the Dolphin Emulator, Shadow of the Tomb Raider or VLC profiles should work, for DX9 SBS games the MPC-HC profile is currently the only one if memory serves right, for OpenGL the Dolphin Emulator profile *might* work.
I will add SBS base profiles to the profile list to make this easier for you guys. Not sure why I never thought of that before.
TrackIR has to be supported by the game. Typically vorpX will detect that and show an according hint in the top left corner of the game window. There may be games however where it has to be enabled in the game options somewhere before vorpX will be able to detect it is supported.
Never heard of that, but I’ll look into it. The desktop viewer shouldn’t even be able to start multiple instances, I think. Not 100% sure though.
Please just don’t use it for the time being. It’s not really necessary.
Arma III only works when launched without BattleEye, unfortunately it blocks vorpX. You can disable BE in the Arma III launcher.
If you encounter framerate issues after setting the resolution higher, the best you can do is setting it back to the value that worked before. At 1440p the GPU has to push almost 2x the amount of pixels, which might just have been too much.
Also not only the game will get rendered at a higher res, vorpX also raises the resolution that is used for sending the final image to the headset in that case, so you are basically raising two resolutions at the same time. That has an even greater impact on Quest since the Oculus software does some video compression/decompression for Quest.
Can’t put my finger on this currently, but I did make some changes to the ‘Headset Sync’ ‘Fast’ method. I’ll take a look at that later today.
For the time being please set it to ‘Safe’ whenever you encounter stutter that wasn’t there before the last update. Will be fixed ASAP.
Does this happen for you when you enter the first house after starting the game? Just checked that part of the game, but couldn’t replicate the issue. The transition into the house worked perfectly fine.
BTW: completely unrelated, but you might want to set the ‘Headset Sync’ option to ‘Safe’ for this game. The default ‘Fast’ caused some stutter for me, which went away after switching to ‘Safe’.
Please follow the hint shown in the top left corner of the game window and enable TrackIR in the game’s camera options. That should help. TrackIR also has to be enabled in the vorpX. Should be the case per default, but worth to check that too.
Alternatively you could disable TrackIR in the vorpX menu for mouse only head tracking.
I’m not sure how much you customized your game settings, but for the default settings (game FOV 100.0, vorpX ImageZoom 0.62) the best aspect ratio is 16:9 as set by vorpX automatically. The resolution you have chosen would only be right if the game FOV would be high enough to exactly match your headset FOV. If in doubt, just let vorpX do its thing instead of setting the resolution manually. The DirectVR auto resolution feature is there to handle stuff like this without you having to care about it by factoring in all vorpX settings that affect the ideal aspect ratio.
Borderless window mode is probably still a good idea to avoid potential issues when switching modes. I’ll take a look at that and might force it with the next update if actual fullscreen causes issues.
BTW: If you applied an FOV hack, be aware that a higher game FOV can have a fairly huge impact on performance, a higher FOV means more has to be rendered, which means less FPS.
I believe Shadow PC (or comparable services) are indeed the only cloud gaming services where that would be possible since vorpX would have to be installed on the PC that runs the game. That is definitely not possible with Stadia, not sure about GeForce Now. I don’t really know how that works, i.e. whether you have your own virtual PC there or not.
It can also ‘work’ in a way with Stadia, but that would mean just grabbing the streamed 2D image + head tracking, so it largely defies the purpose of vorpX.
I have checking whether that would be possible (and a substantial improvement over the built-in sharpening (image page of the menu)) on my rainy-sunday-list for quite a while, but can’t say currently when I will get to that.