If you want set the resolution manually, disable auto resolutions on the DirectVR page of the vorpX ingame menu.
Alternatively you can simply select a quality preset on the DirectVR page of the ingame menu. vorpX then figures out the closest matching resolution that the game allows and is available on your system (including added custom resolutions). This is often the better/safer way.
That should not happen anymore with the latest vorpX version 18.2.4.
If you have this version and the issue still occurs, try to unplug/plug the gamepad after the DirectVR scan and check whether the gamepad is enabled in the game’s input options.
Hi,
Did you ever resolve your issue with the Xbox controller not working after the DirectVR scan? I was also having this problem previously but never got it to work properly.
Thanks.
This functionality is part of the DirectVR settings optimizer for Crysis 3 and only applies to the actual Crysis 3 profile.
When you make a copy of that profile to try an unsupported game, the routines doing the image zoom/fov calculations aren’t invoked.
I used to play DoDS just fine with vorpX a year ago, though in testing today I get the same result as you. Game attempts to load, but stops seconds later. Starts fine without vorpX.
I think there is a conflict with recent updates to either the HL2 profile, or the game itself (had a game update today even).
After messing around some, I found error calls to sourcevr.dll found in the “Day of Defeat Source\bin” folder. So I simply removed sourcevr.dll to an external folder, and was able to hook with vorpX.
(Steam may attempt to reinstall the dll upon launch, but so far I’ve only had to remove it twice and it has stopped)
I’ve learned that you must launch DoDS through steam client to get servers to show in the browser. Launching via hl2.exe directly wont populate the browser.
I am unsure about DirectVR at this point, but can say that the game can hook with working Geometry 3D. You just might need to do some scale and fov adjusting in game.
I’m new to this forum and hope to make some contributions.
First, I want to know more about the general compatibility with HL2 mods, as the one I’m having some troubles with now: DoDs. I try before HL:Source and was a bit frustrating at first, DirectVR not always work and some areas make the fov change somehow. Sure there are some optimizations available for this game not yet implemented, I hope Ralf can take a look on it.
The issue with DoDs is it does not start at all, the steam loading window appears and seconds laters disappears, nothing else, and I can’t find any log that can help me locate the problem. I was pretty sure this game will work, and I thought it was a mistake in my end. But after sometime searching, I didn’t find anything related to VorpX-DoD in internet or this forums. It may not work for anyone else,
or i have some setup wrong.
Thank you very much.
The FOV is handled automatically for Battlefront 2. vorpX sets it to a value that is perfectly calculated. Setting the FOV manually in games where vorpX can do that automatically can cause comfort issues for more sensitive people rather than avoiding them since even small deviations from the correct FOV may be irritating for them.
Caveat: the game is a bit special, FOV adjustment is only possible in multiplayer. If you want to play the campaign, it’s better to play in immersive screen mode like dellrifter (and the vorpX startup message for the game) suggests.
Image quality: you can run games at any resolution with vorpX. Check the “Custom Resolutions” section in the vorpX help, it explains how to add resolutions to your PC that it normally cannot display. Afterwards you can select a preferred quality on the DirectVR page of the vorpX ingame menu in Battlefront 2.
Having a wide enough Field of View is important to avoid getting dizzy. Running a DirectVR scan during gameplay can help this if available. Otherwise you’ll need to find ways to greatly increase FOV in a games settings.
Battlefront 2 has FOV slider in the video options. For fullVR you generally want it somewhere between 100-130.
If you are still having trouble getting used to the headtracking of FullVR mode, maybe try out the cinema modes from the Delete key menu to see how that feels. You can adjust the size of the screen, and also the strength of the 3D depth and still get an immersive experience. There are also sliders for sharpness and brightness, this can help make it less blurry.
If you want an example of this, search my name on the Cloud Profiles of vorpX config app and import my SWBF2 profile (not the beta one). In game set FOV around 95 and see if it feels ok.
directVR works with oblivion!, this is news to me, how well does it work.
There is no way to get stereo 3D for newer No Man’s Sky versions, can’t be changed with a different profile. Newer NMS versions partially use a way to transform geometry that vorpX’s OpenGL pipeline does not handle.
The game still has DirectVR FOV calculation though, so at least it’s easily playable in 2D Full VR – provided you can live that.
Regarding the more general question: official profiles cannot be removed by design. This may look like an unnecessary restriction, but it ensures that beginners or uncareful users cannot erase profiles by accident, which had to be ranked higher in this case than total freedom for power users.
Hi,
I’m using DirectVR with 112 FoV and oblivion looks great!
But every time I talk to someone the FoV gets reset to 75 or 95(not sure which).
I have to manually type in fov 112 in console every time or Alt-V or run DirectVR again.
Is there a way to stop it from changing FoV? Or at least properly reset after conversation?
……and it looks like my version of BioShock is BioShockHD :), so that explains that.
Witcher3 is crashing after I hit ‘Play’ now on the launcher (during the title screen). It has loaded a few times before so I must have borked something. I tried loading from steam, loading from the exe, not sure what I am doing wrong there.
Portal2 loads and has the DirectVR Scan option so excited about that! Only issue there has been flickering screen while playing so need to play with some setting to get that to stop.
Thanks again for the help and quick replies,
Thump.
Skyrim and Bioshock are supposed to have a DirectVR scan option. If you don’t see it in these games, something is wrong. Might be worth to check whether you maybe have renamed the .exe files for some reason which would prevent the profile from loading correctly.
Caveat: for Bioshock please use original DX9 version of the game, the remastered version (Bioshock HD) currently is not supported.
Just a little heads-up that the FOV mod should not be required normally since the game is supposed to have DirectVR FOV.
Unfortunately that doesn’t work anymore since two or three vorpX versions due to a pretty stupid bug. Will be fixed for the next update.
Thanks for the assist. I just tried Portal 2 and the VRDirect Scan option is there (on the main menu btw). I guess those other game’s profiles do not support DirectVR Scan.
I was under the impression that the option would be there regardless, but the scan would then determine what VRDirect support there was.
Lots to learn and thanks again!
Thump.