-
Search Results
-
Hello there,
I havent played first person shooters with VorpX because of the motion sickness i initially had experienced.
Now since this seems to be gone i ran into a little problem with Depth Settings in a Game running with G3D.
I dont know (yet) if any other 1 rst person game behaves like that too.
I mainly set 3D Strengh to a value where everthing looks natural, keeping this value to 0 makes the game 3D but still kind of flat compared to lets say a value of 2 or 3. I set this value at maximum depth without destroying the normal gun view.
Most 1st person shooters have a sniper mode where you lift the gun in front of your head for shooting. Here is where the problems occurs. The convergence of the stereo image moves behind my head so i cant use the sniper mode, left and right at gun view is too much separated while distant objects remain ok. In normal mode ( a bit further away from the eye ) guns look all right.
Now if i want to use the sniper mode i must set 3D Strenght to 0 which in return makes the 3D effect not so nice.
Is this normal in 1 st person shooters or can this only be adjusted with internal tools ? If you own Call of Duty 1, you can use my profile from the cloud to see what i mean.
After the latest Oculus Core 2 update I encounter a pretty severe issue here and like to know whether that is something that happens for everyone. To check you have to 1. be signed into the Oculus public test channel, 2. have the new Oculus Home enabled.
What happens here is that I can’t launch any DX9 fullscreen games anymore as soon as Oculus Home 2 is running. Running games windowed still works, fullscreen fails (black screen), games have to be closed via CTRL+ALT+DEL/task manager. It doesn’t matter whether vorpX is running, this is purely caused by the new Oculus software.
All you need to do for testing is making sure the new Oculus Home is running and then start two or three DX9 games in fullscreen mode. Leave vorpX off to take it out of the equation. If you are affected, the issue occurs with or without vorpX.
It would be great if a few of you could let me know what happens (or not) for you and whether you are using an nVidia or an AMD GPU. Thanks in advance for your feedback!
BTW: A fix is already being worked on and working well, before I release it I’d just like to know whether this is a general issue with the latest Oculus 2.0 beta or some rare glitch that only affects a small minority. Strikes me as a bit odd that noone reported this so far.
