Forum Replies Created
-
Posts
-
It’s either on or off.
Same for FullVR mode now BTW. At the time I thought it was a good idea to treat EdgePeek different and always have the ambience background during EdgePeek, but it’s just confusing. Intuitively one would expect the selected background to be applied regardless of EdgePeek or not, which is the case now. The ambience background is still the default, but if you don’t like it and turn it off, it’s always off now.
Since this seems to be a rather popular request I changed my mind and will provide greater control for the immersive screen screen. In the next vorpX (out in a few days) you will find a ‘More Settings’ button in the menu similar to the one in cinema mode. Pressing that provides options for background selection and screen curvature adjustments.
That way those of you who want greater control will have it without sacrificing the originally intended simplicity of the immersive screen UI too much.
You should be able to set the resolution on the DirectVR page of the vorpX menu. Try that first, with the other method below you will lose all automatic settings, which is undesirable.
If the above not work for some reason, disable automatic settings for the game on the same menu page and set a 4:3 resolution (e.g. 1600×1200 or 1920×1440) in the game’s options.
I haven’t been able to reproduce it either when I checked it a year ago or so. Probably related to some game setting.
The profile was made years ago with the (back then) regular version. Never tried the train ride since then though, so this issue must have been introduced in the meantime. Sometimes I wish I could turn back the time to the pre-internet era, when games didn’t get dozens of updates stretched over 10 years…
Anyways, fixed it today. The updated profile will be included in the next vorpX. Hope you can wait a little longer. I could backport the profile to the current release and upload it to the cloud, but the next vorpX will be out in a few days anyway.
The HUD is supposed to be scalable by vorpX, but apparently the shaders used to identify it changed (again) with some recent game update, so that’s not working ATM. Will take a look at it.
vorpX does not change the resolution in Half-Life 2. Whenever it does you see a notification stating that in he top left corner of the game window.
It should switch to native after a successful DirectVR scan.
Background: some games (including Fallout 76) do not allow mouse and gamepad to be used at the same time. Since prior to a successful DirectVR scan vorpX emulates a mouse for head tracking the gamepad cannot be used natively while that is the case, so vorpX overrides it with its built in gamepad to mouse/keyboard mapper.
After a succesful DirectVR scan vorpX does not have to emulate a mouse for head tracking anymore and turns off the override. You can then use your gamepad natively.
Some games do not allow mouse and gamepad to be used at the same time. Since vorpX needs to emulate a mouse for head tracking in such cases it overrides the gamepad with its built in gamepad to mouse/keyboard mapper. You can freely configure that to your liking on the input page of the vorpX menu.
There is no general need to turn off AA. Be aware though that ‘modern’ AA techniques like FXAA. TAA etc. blur the image, so in such cases you have to decide what you consider more important. Good old true multi sampling AA (MSAA) can (and should) safely be enabled if available for a game.
Unfortunately AMD graphics cards are less than ideal when it comes to custom resolutions since normally only resolutions as high as your monitor’s native res will work. NVidia GPUs are way better in that regard. There some tools that presumably allow to add resolutions the AMD graphics control panel rejects, but I never tried that. Search for CRU or Custom Resolution Utility. Also make sure to add the resolutions listed in the vorpX Custom Resolutions guide.
btw: please make sure to always read all messages that vorpX shows in the headset.
1) Skyrim does not need any custom resolutions. You can set the resolution as high as you want on the DirectVR page of the vorpX menu by choosing a preferred quality. Go for something like 1440p or above for good image quality. Keep an eye on performance though. Higher resolutions cost performance. It’s all about finding the right balance here.
2) If you encounter graphical glitches, try another 3D mode. If currentlly you have sleceted Geometry 3D , try Z3D or vice versa. Make sure to restart the game afterwards, just in case. Z3D doesn’t look as natural, but is a lot faster.
3) Memory scanner: See my reply in your other thread.
4) Do not use supersampling in SteamVR with vorpX! That has (almost) no effect on image quality, but may cost performance. The right way to enhance image quality in vorpX is raising a game’s resolution like you would do when you play a game on your monitor. If vorpX can handle it, you can do that on the DirectVR page of the vorpX menu. Whenever that is case, you see an according message in the top left corner of the game window. If vorpX cannot handle it, games usually allow to set the resolution in their options.
I sent you another installer which uses a newer DotNet version. It should not be affected by your broken DotNet 3.5 install.
Would be great if you could provide a bit more detailed information about your issue. Difficult to say anything useful otherwise.
If you carefully follow each step in the custom resolution instructions, there sholdn’t much that can go wrong. For nVidia: double check especially the steps 2. and 4. Without doing these you won’t be able to add resolutions. For AMD: keep in mind that the AMD driver does allow to add resolutions higher than your monitor allows.
The scan may sometimes fail although it “thinks” it succeeded. That would typically yield the result you saw. If the scan does not work for you in this game, stick to mouse based tracking. Scanning the whole memory of a game for one particular value is a rather delicate matter and may not always be 100% reliable. Hence the message in that regard that is shown during each scan.
No problem here with both the regular and alternative hooking method. The only reason why vorpX would need admin rights for hooking a game is the game running as admin itself. That would be the case if for example you are Steam running as admin.
I would gladly take a look at the issue if someone could provide a savegame from a location where the issue occurs, unfortunately noone did so far. Please send it to support |at| vorpx com.
Before you do that try to reset the profile to default and check whether the issue still occurs with default vorpX settings.