Forum Replies Created
-
Posts
-
No it is not normal in general, but under some circumstances you may see a larger drop than expected, which is what I tried to explain in my first reply to your question and several times afterwards.
I cannot explain that in any other way than I did above. You have to take my word for it if my attempts at explaining were not good enough. Sorry.
I perfectly understand that you would prefer to get a different answer, unfortunately I only have the one I gave you several times above already:
In a nutshell:
1. There is nothing vorpX can do when the Oculus runtime decides to throttle down to half the headset refresh rate although theoretically there is still enough headroom left for vorpX to handle things with its own timewarp. That’s not really something to be concerned about though.
2. If you want to improve performance in demanding games, your best options are dialing down settings/resolution and/or switching to Z3D.
Hope that helps.
If I new a better way to explain this to you, I would, trust me.
The Oculus runtime is the “driver” for the headset. It takes an image from a game, applies lens distortion, Oculus’s versin of timewarp, etc. During this process it may decide to throttle down the headset framerate if it thinks that makes sense.
Quote from above:
Like said above, the main “issue” (which isn’t really one) here is that the Oculus runtime may decide at will to throttle down to half the headset’s refresh rate although there is still headroom left for vorpX to handle things with it’s own space warp implementaion. Nothing vorpX can do about that, but also not really something to be concerned about.
Again: I can’t give you any other answer to your question than I gave you twice above already. I’d like to give you different one just as much as you would like to get a different one. Thanks for your understanding.
I understand that you would prefer to get a different answer than the one I gave you twice above, unfortunately I don’t have another one.
Monster Hunter World is an extremely demanding game. If you want to improve your framerate, you can try to dial down settings or alternatively switch to Z3D.
How huge the actual gain will be depends on your settings, your GPU etc. The typical gain with the fast sync method would be about 10%. Under some circumstances it might be larger, in other cases it might also not change anything at all.
I think I answered your other question twice already above, in the backgound the Oculus runtime also does its thing when you select SteamVR in vorpX, SteamVR internally also uses the Oculus runtime.
The beta is finished, sorry. The next vorpX release will be available shortly. Don’t expect wonders from it though. Per default everytging will be as before, but with a new optional fast sync implementation you can typically gain a few percent.
Like said above, the main “issue” (which isn’t really one) here is that the Oculus runtime may decide at will to throttle down to half the headset’s refresh rate although there is still headroom left for vorpX to handle things with it’s own space warp implementaion. Nothing vorpX can do about that, but also not really something to be concerned about.
No problem here with hooking into the game. If you suddenly encounter hooking issues with a game, there probably was a change to your system that created a conflict with some other program on your PC that also hooks into games like vorpX.
if you haven’t done so already, please check the trouble shooting post on top of this sub forum. It pretty much has all relevant information regarding conflicts with other programs.
Running vorpX in generic mode is fundamentally different since there is no second thread running that pushes the final image to the headset. In theory this second thread should ideally run at your headset refresh rate and only cause a little overhead, but in practice depending on the headset runtime and your GPU load the headset runtime may decide to throttle down to half. The Oculus runtime often does this despite enough headroom left for vorpX’s internal time warp unfortunately.
Not really a problem though since in that case the Oculus runtime internally interpolates the missing frames instead of vorpXˋs own time warp. In other words: Your game may run at half the headset’s refresh rate, but the Oculus runtime creates the missing frames.
BTW: Reducing the frame rate to half the headset refresh isn’t necessarily a bad thing. Interpolating from steady 45 to 90 can feel smoother than interpolating from fluctuating 60-80 to 90. That’s a bit of a matter of taste, but you can even enforce this with vorpX’s ‘Fluid Sync’ option if you want.
The game is quite popular and not known to be probelematic in any way as far as hooking is concerned. Almost certainly a conflict with some other program on your PC that also hooks into games.
If you haven’t done so already, please check the trouble shooting post on top of this sub forum. It contains pretty much all relevant information in regard to hooking conflicts.
Apart from that: the next vorpX version will come with a third hooking mechanism that should resolve most potential hooking conflicts except invasive AV programs by ensuring vorpX is always first.
Both options are available since cinema mode has been implemented years ago. There is a ‘More Settings’ button below the basic screen settings.
This is a false positive. Seems to be some problem with the latest Chrome/Firefox version, the web installer is the same for several years…
FYI, here’s the scan result for the installer from VirusTotal, which checks files with multiple AV scanners.
Result: 0/64 AV scanners consider the file malicious.