Forum Replies Created
-
Posts
-
vorpX cannot work correctly if another DLL also hooks into the game. d3d9.dll is a system dll that normally only should be present in the Windows system folder as part of the OS. Overriding it with a DLL in the game folder will likely make vorpX stop working, hence you see the warning about that.
I haven’t tried Fallout 3 on Windows 10 yet myself, but if there is no other way to make the game work on Windows 10 than copying a d3d9.dll to the game folder, you may be out of luck in this case.
How a game translates mouse movement to camera rotation depends indeed on the game. One things that often can improve things is disabling mouse acceleration, which can be done on a per game basis in the vorpX ingame menu (input page).
Game FPS is the value that the game runs with, it’s the one that needs to show 45fps for smooth gameplay. If you use a Vive, Direct Mode FPS should always show 90fps, otherwise you will get serious judder.
What resolution you can run a game with depends on your PC. The default suggestion of 1280×1024 is a compromise between quality and speed. Quality wise 1600×1200 or 1920×1440 are better, but whether your machine can handle that I cannot know.
Achieving a decent Game FPS of at least 45fps is absolutely paramount for smooth VR gameplay. That is the most important thing to keep an eye on when you tweak quality and resolution in any game.
Please make sure that the game runs fast enough if you experience any severe lag. You can check the current frame rate by pressing [ALT][F]. Do not ignore warnings that vorpX may show in this regard. For smooth gameplay you need 45fps, Skyrim can easily drop below that with highest settings.
Depending on your PC, choose either the “High” or “Medium” preset in the Skyrim launcher. “High” should work fine on high end GPUs like GTX1070/1080, “Medium” is the right choice for VR minimum specs GPUs (GTX970). Alternatively switch to Z-Buffer 3D in vorpX, which doesn’t look as good but is a lot faster.
If you use mods, remove all of them, especially graphics enhancing (“ENB” etc.) mods and hires texture packs. Add them back one by one to sort out the ones with a high impact on frame rate.
Hands can be fixed by setting fDefault1stPersonFOV under [Display] in your Skyrim.ini to something in the range of 120-140. Caveat: to apply the value you need to open the “star menu” and/or map once. After that the value will stick.
The next vorpX will have a bunch of improvements that make this easier and also remove one frame of extra latency on Vive, but Skyrim will stay a game where you have to keep an eye on your settings for a smooth frame rate.
No, you don’t need a cloud profile. Changing the FOV via an .ini tweak is COMPLETELY INDEPENDENT from vorpX. As said above, the optimizer *may* fail. That’s why I explained in detail the settings you have to set manually a few posts above. And if I understood you correctly you changed them and saw an effect when you started the game on your monitor.
If you see a larger FOV on your monitor after changing the ini file, you also get that larger FOV in your headset with vorpX. 100%, always, no exceptions. vorpX itself does not alter the FOV beyond what you set in the ini. If the ini edit has an effect on your monitor, you also see that effect in your Vive.
I really don’t know how to explain it different, sorry.
Also do never use extended mode with vorpX. Not sure how you even got it to display anything this way. vorpX only works in direct mode!
If the FOV is changed without vorpX running, it also is changed with vorpX running. This does not depend on the headset you use. The FOV is changed completely independent from vorpX or your headset if you change it in the ini of the game either with the optimizer or manually. The game ALWAYS uses this changed FOV regardless whether you play it on your monitor or your headset.
vorpX takes the image as rendered by the game and then displays it on your headset. So if you see a changed FOV without vorpX running, you also get the exact same changed FOV with vorpX running. There is no chance that it works any other way on your headset.
If you think the values set by the optimizer (or manually by yourself in the in ini) are still too low, you can use a higher FOV at any time, of course. The suggested value (120° horizontcally) is normally the right one for a natural looking image though.
Setting the FOV in the ini files of the game like done by the optimizer has nothing to do with vorpX running or not. It also works when you start the game without vorpX. Please check whether that is the case.
If editing the .ini does not change the FOV (with or without vorpX running), something is severely wrong. Maybe try reinstalling the game then. Not sure what to recommend else, sorry.
Sometimes the optimizer may fail if it can’t find the directory where the ini is stored for a game or the file itself is write protected. Some mod managers for Bethesda games for example can cause that. Another potential cause of failure may be GOTY editions of games, which sometimes use different storage locations that the Optimizer does not know.
For Outlast the ini is expected to be [Documents]\My Games\Outlast\OLGame\Config\OLGame.ini. If it is stored in a different location in your case, the Optimizer will fail.
The FOV related ini-values the optimizer changes for this game are: DefaultFOV, RunningFOV, CamcorderNVMaxFOV, CamcorderMaxFOV.
If the optimizer fails for some reason, set the first two to 130 manually and the camcorder ones to 110.
You can create copies of existing profiles on the local profiles page. To do that select an existing profile and then click the button labeled “Create a new profile based on this one”. Doing that with a random profile before you exit vorpX will suffice to save all settings to disk that you made before. You can safely remove the newly created copy again afterwards.
For Outlast the Game Optimizer should be able to handle FOV, Battlefield 4 only takes the ini setting into account in multiplayer. Single player FOV can not be changed unfortunately, Flawless Widescreen might help with single player.
4 gig is too much for an unmodded Skyrim, maybe not all textures got removed when you removed your mods. With an unmodded Skyrim you should see something around 3 gigs at highest settings normally. At least that’s what I get here.
Yes, please try again. And ideally provide an alternative reply mail address in case you can’t receive mails from us for some reason with your primary address!
Battlefield 4 only supports FOV adjustment int multiplayer for some weird reason. Single player mode stays unaffected from any changes made to the .ini file unfortunately. With a bit of luck Flawless Widescreen can help by hacking into the game’s memory.
What you can do in regard to FOV heavily varies from game to game. While for quite a few games the Game Optimizer works well, for others you may have to use an extarnal tool like the one linked above.
Can’t promise anything yet, but it will be looked into. Given the restrictions in regard to access rights etc. that Windows Store apps introduce there is a chance though that something like vorpX won’t work at all.
You can circumvent the settings not saving bug by performing any action theat writes the settings database to disk in the config app before closing vorpX. Just creating a copy of a random exisiting profile and deleting it again afterwards will suffice. The underlying issue will be fixed with the next vorpX version.
The Game Optimizer changes FOV and other related settings directly in game .ini files or the Windows registry. A handful of games may overwrite those changes again if you change game options ingame afterwards, so ideally avoid adjusting video options in such cases after applying the Optimizer settings. For games without the option to adjust the FOV with the Optimizer you either have to use the workarounds vorpX provides, edit ini files manually or use an external tool. Flawless Widescreen hacks into the memory of games that don’t allow to adjust to FOV officially.
Unsupported games: Try to create a new profile based on an existing one in the config app (Local Profiles page) for games that vorpX does not support. For Team Fortress 2 a Source engine profile like Left For Dead 2 or Portal 2 might do the trick. There is no guarantee that profiles created this way will work, but that’s always worth a try.
>> Help me Obi-Wan! You’re my only hope! ;
I’m slowly getting old for sure, but not that old yet!
In contrast to the everlasting struggle between the Empire and the rebellion unfortunately there is no black and white here, just grey and vague answers.
A lot depends on the game. SLI might not help at all if it doesn’t work for a game with vorpX or your headset. Oculus for example didn’t in the past, not sure whether that is the case still.
Regarding CPU-affinity: Since vorpX runs inside the games, it’s main work is done within a game’s main render thread, so nothing you could manually assign to a different core here. The only thing you could assign to a core yourself is the vorpX Control app which watches for new programs getting started, but that’s more or less negligible. A few percent while vorpX isn’t active, even less while it is running in a game.
So all in all not much to gain by assigning something to an extra core, probably nothing. Since the 6/8 core i7 CPUs usually have a lower max. clock rate than the quad core units, I would even guess that you are better off with a fast quad core i7 model for gaming (which provides 8 logical cores with Hyper Threading enabled).
On a sidenote: not something you can do yourself, but I experimented with assigning the direct mode render thread manually to a dedicated core some time ago within the vorpX source code. In the ~10 games I tested with that there was absolutely zero difference, which pretty much also is in line with the majority opinion among programmers on the matter: in most cases the OS task scheduler simply is better or at least as good at balancing workload than anything a programmer can come up with.