Forum Replies Created
-
Posts
-
Half-Life 2: Please empty the scanner cache on the DirectVR page of the vorpX menu and re-run the scanner. For HL2 the scanner needs to find several memory locations to work corerectly. If not all are found, it would still signal success, but not work fully. If that does not help, please disable DirectVR positional tracking on the DirectVR page. Default positional tracking will still be available.
Bioshock Infinite: In this game DirectVR gets disabled below a certain draw call threshold to avoid crashes during loading screens etc. So if the issue only occurs while you for example look into the sky or at the ground, it’s probably what is to be expected. However, during normal gameplay this shouldn’t really occur. If it still does, please also disable DirectVR positional tracking on the DirectVR page. Default positional tracking will still be available.
I checked New Vegas after you original post, but could not reproduce your issue here. I’ll try again. If I find anything this time I’ll let you know. As far as vorpX is concerned there is no difference between Rift and Rift S at all. vorpx uses the Oculus runtime in the exact same manner for both headsets, there is not a single line of code that is different for Rift and Rift S.
That said: Please try to disable DirectVR positional tracking on the DirectVR page of the vorpX menu. You will still have positional tracking after doing that, just not the DirectVR pos tracking anymore.
Mods: if you have mods installed for a game, please always try without any mods as the very first thing if you encounter issues. Most mods don’t cause an issue, but there are always some that could potentially. Obvious candidates would be for example image enhancing mods that hook into the render pipieline and any camera related mods, but there might be others. So whenever you use mods, removing them should be the very first thing to try in case of issues.
General sidenote: I always do what I can to help and will continue to do so whenever you have a problem, but having paid $40 years ago for some software (plus free updates ever since) does not entitle to personal support for the rest of your life, neither here nor anywhere.
If you don’t need anything more special than typical reading glasses, there is a relatively easy way to solve your problem without knowing the exact lens focus distance: to figure out how strong the glasses need to be for each eye you would just have to buy a bunch of cheap ones from the supermarket/internet roughly within the range of diopters you suspect should fit. That way you could easily try yourself what works best for each eye and then let your optician make the actual pair based on that information.
Any larger supermarket should have cheap reading glasses in .25 diopters increments. Provided your eyes don’t require anything more special a handful of them within the suspected range should be enough to figure out what works.
BTW: If you don’t want to wear glasses in VR, you can also buy prescription lens inserts for all major headsets online. Personally I use inserts from vroptician.com for all headsets and am quite happy with them.
Out of curiosity I searched a bit myself yesterday and found some related papers/projects. At least one even including code and training data. Not a simple point and click solution, but if you want to invest serious time and effort it might be worth a closer look. Googling ‚2d 3d conversion movie neural network‘ should get you started.
The regular version should work normally if you start the game without SteamVR running. The latest vorpX/profile version should display an according message in the top left corner of the game window.
I don‘t really have much more I can suggest to you, sorry. The trouble shooting guide pretty much covers all basic stuff. That‘s what it‘s for. If your crashes would be caused by an error within vorpX, they would almost certainly happen at the same location every time, which your logs clearly show is not the case.
If you want, you can send a trouble shoot data archive to support at vorpx com, so I can take a look at your system config and running processes. Maybe you overlooked something when you disabled background processes.
A more feature rich image post processing pipeline would certainly be nice to have, it actually is even designed to add any amount of additional effects quite easily. The only thing missing are according shaders, but at this point that is not really a priority to be honest.
In that I case I would suspect a conflict with some other program on your PC that also hooks into games. Judging from the logfile each crash happens at a different point in time before the first frame is finished which is a pretty strong indication for some external factor causing the issue.
You can find more detailed information on the matter in the pinned trouble shooting guide on top of this sub forum.
You would have to ask yours headset’s manufacturer at which distance the focal point of their lenses lies. I‘m not really the right person to answer that question. I‘m pretty sure that it‘s typically within the range you mention, i.e. something between one and two meters, but I can‘t really say anything more precise.
If your eye sight isn‘t good enough anymore to get a sharp image at that distance, you should be able to counteract that with mild prescription lenses just like the ones you probably use for reading, just less strong. Before buying new ones it’s worth to check whether you maybe still have an older, less strong, pair stored away somewhere that happens to work.
However, if you want/need precise information, your headset manufacturer is the only one who can answer your question.
Did you disable the internal GPU like suggested above? That’s probably your issue.
Gaming laptops typically have a GPU built into the CPU for less demanding tasks and a dedicated GPU for games, which probably is the one that your headset is connected to. With some luck your laptop allows to disable the integrated GPU either with a tool or in the BIOS. Doing that can prevent potential issues if a game for some reason runs on the internal GPU while the headset is connected to the external GPU.
As explained above some games do not allow mouse/keyboard and gamepad input at the same time. So whenever vorpX emulates a mouse for head tracking in affected games it overrides the gamepad and switches to its built in gamepad to mouse/kb mapper.
There is nothing to solve here, on the contrary vorpX’s gamepad to mouse/kb mapper actually is the solution for head tracking issues in games that do not allow gamepad and mouse/kb input at the same time. If it wouldn’t exist, you would not be able to use your gamepad at all together with mouse based head tracking in affected games.
You don’t have to wait for the next update to play Black Mesa. Only their new DX11/9 hybrid menu doesn’t work currently, the game itself works just fine. You can work around that by adding -oldgameui to the game’s launch options in Steam, which brings back the original DX9 menu.
I’m not 100% sure whether I understand the question, but the stereoscopic focus (convergence) plane is typically set to infinity in VR, meaning left and right image match in the background and are farthest apart close to the camera. vorpX always does that in FullVR mode, in immersive screen/cinema mode you can change it, but as the message suggests that appears when you do so, that should be done extremely carefully, if at all.
If you have trouble focusing foreground objects, you have set the 3D-Strength too high.
Apart fom that artificial stereoscopy in general is somewhat odd for your brain since it doesn’t fully emulate what happens in reality, which is one of the reasons why some people consider stereoscopy generally uncomfortable. Most importantly accommodation (for thr sake of simplicity imagine it as the real world counterpart of a depth of field effect) doesn’t work as your brain expects.
I don’t think I’m able to fully explain that well enough in a few sentences, I’m not really a great teacher. If you want to learn more: the Wikipedia articles about stereoscopy and depth perception are good starting points.
Some 3D TVs had algorithms built in that tried to guess a depth map by figuring out what is foreground and what is background via analyzing motion and/or color/contrast, but those never really worked well. Except for special cases like e.g. a horizontically panning camera, which happens to contain the stereo information a few frames apart, you will mostly get odd results using such methods. Trying to guess information that just isn‘t there is more or less bound to fail more often than not.
Sounds like a potentially good application for an accordingly trained neural network (AKA ‘AI’) though. I’m not sure if such a thing exists, especially freely available, as training such a network until it’s good enough would clearly be a pretty huge task. Nonetheless searching for a neural network based solution is probably your best bet, maybe someone was crazy enough to try.