Forum Replies Created
-
Posts
-
I have received your e-mail!!! And will take a look at your savegame, provided I can load it here!!! Thanks!!! :)
You can run games at every resolution/aspect ratio you want. However, different aspect ratios make sense for different things.
If vorpX can handle that for a game, let it do its thing. It knows what aspect ratio is best under which circumstances.
If vorpX can’t handle it for a game, use the below rule of thumb:
For ‘Play Style’ set to ‘Immersive Screen’ or ‘Cinema’ widescreen resolutions (16:9/16:10) are typically what you want.
For ‘Play Style’ set to ‘Full VR’ choose 4:3 resolutions unless you have to reduce the ‘Image Zoom’ slider a lot to compensate for missing FOV. Widescreen resolution otherwise are a waste of GPU power with ‘Full VR’ since a lot would get rendered that never is visible in the headset.
If it worked before and now suddenly doesn’t, there must have been some change on your system that causes it to fail. If you happen to have the Windows system restore functionality enabled, the easisest way to trouble shoot this would be going back to an earlier restore point. Unfortunately on Windows 10 the restore point functionality is off per default, but if you happen to have it enabled, that would be the first thing to try.
Apart from that I would suggest to reset both the vorpX profile (can be done in the config app) and the game options to default, just in case you made some change you can’t remember right now that causes your issue.
Hooking issues are most of the time cuased by conflicts with other programs on your PC that also hook into games.
There isn’t really much to suggest in case of hooking issues that isn’t already covered in the pinned trouble shooting guide above. If you haven’t done so already, please go through it thoroughly. Especially the part about potential conflicts with other programs on your PC.
Apart from that trying the ‘Alternative Hooking’ method in the config app might be worth a shot. Don’t forgot to switch back later, even if that helps. Some games require default hooking.
For RDR2 things won’t change, DX12 is something else entirely. Maybe the next ‘big’ vorpX update will bring changes here since I’m currently working on a full DX12 backend troughout the whole pipeline. Currently DX12 uses a DX12/11 hybrid approach, rendering to the headset is still DX11. Can’t tell yet whether the DX12 only backend will affect performance in any way though.
DX9/10/11 and OpenGL are the APIs affected by this change. DX9 games for the most part are fast enough these days, here you will most of the time see the 10-15% that are to be expected (provided games don’t run at 90fps anyway). The big surprises are some games and/or special conditions under DX11.
Still, typically expect the 10-15% that I originally expected without much variation everywhere. The 20-30-40% cases will not be the norm. They are pleasent surprises though.
One more observation: apparently there are situations where the current headset sync mechanism holds back things massively, way beyond the 10-15% that are to be expected. You will see huge benefits in some DX11 games when the GPU is the limiting factor, not the CPU. Typically this would be Z3D with high resolutions. With this combination the performance gain can be up to 40% compared to the prior default. Measured on a GTX 1080 Ti in Fallout 4 and AC:Origins at 4K resolution and 3D at ‘Z-Normal’.
Don’t expect something like that with every game at 4K/Z3D, but with some the difference can be huge under these conditions.
The profile default is definitely ‘Full VR’, just double checked to be sure there is no accidental misconfiguration.
After some more testing with various headsets and a couple more games I’m now fairly confident that the whole thing will work out. Unless you guys find something next week that I overlooked, you will all be able to enjoy some nice 10-15% performance boost almost across the board pretty soon. G3D as well as Z3D in almost any game, with only some exceptions where it doesn’t really change much. There are also exceptions on the other end of the spectrum, e.g. Monster Hunter World with about 20%, Kingdome Come Deliverence (with some luck all CryEngine 3 games) 25% or Witcher 3 with almost unbelievable 33% in my test run. This is getting better and better. Your mileage may vary based on resolution, game settings etc.
The old sync method won’t go away, so if with one or the other game it turns out to be the better choice for whatever reason, that won’t be a problem.
@ dellrifter: didn’t check AC:Odyssey, but in AC:Origins the plus is somewhat north of 10% for me. Odyssey should be pretty much the same.
Anyone who wants to check this prior to release still can simply shoot me a mail to support at vorpx com. I’ll send out links to the beta build Tuesday, maybe Monday.
I’d have to take a look at that. Please provide a savegame from the location where the glitch occurs. Unless this is one of those games that bind their savegames to a user account, that would allow me to check the matter.
You can find the savegames in C:/Users/[user]/Saved Games/Respawn/JediFallenOrder. Please send the savegame in question to support at vorpx com.
Difficult to say. Sounds as if all works as intended. If you see the res in the game’s graphics menu, it should run with it.
To be 100% sure you could create a vorpX trouble shoot data archive after running the game and then check the log file in it. Search for a line that starts with ‘INF: D3D11 Manager: Buffer Resolution:’ the resolution shown in that line is the resolution the game is running with.
You might also want to apply some mild sharpening in the vorpX menu (‘Image’ page). Don’t overdo it, about 1.0 should typically be fine. Especially with high resolutions like the one you are using that can do wonders.
The install procedure won’t differ from any normal update install, but you will be able to go back to the current regular version anytime by reinstalling the regular one. Profile databases will be fully interchangable.
There shouldn’t be much reason to go back though. I’ll backport the according changes from my dev branch to the current release branch. The beta basically will be the current stable build plus the new sync implementation which can be turned on/off in the menu.
Thanks so far to everyone who wants to participate. For now we have half a dozen of participants, which is great but a bit disappointing. I’m sure you can do better. Come on guys, doing a little test with the games you play anyway costs almost no time at all. Nothing to lose here, you can only gain a 10% performance plus.
Every once in a while someone comes in here who can muster incredible amounts of energy for discussing some feature they deem absolutely essential for themselves. Show me that you can also invest five minutes of your time for a little test and writing an e-mail afterwards when it comes to help actually implementing one. :)
To those who already expressed their interest: I’ll get back to you on Tuesday.
Nier Automata is a tough case framerate wise in Geometry 3D mode in its more open areas. Try to reduce graphics details if you want to improve things. Never will be great though, it’s just one of those cases where the G3D performance hit is larger than average. The only other option would be switching to Z3D instead.
vorpX takes care that 30fps are still playable though (unless you happen to use a WMR headset), so maybe you can get accustomed to it. Most native VR apps would typically end up being a jittery mess when you try that.
I’m not really sure whether I understand the issue. The profile is set up for FullVR mode per default. You should only have to set the game’s camera field of view to its highest possible value as indicated by vorpX.
Since the FOV can’t be set high enough to completely match your headset’s FOV unfortunaly there will be some bars above/below the image, that’s unavoidable in this case.
If you already changed any settings in the vorpX menu, please reset the profile to default in the config app and then just raise the game’s field of view to max. That is all that has to be done.