Forum Replies Created
-
Posts
-
hey if your still having this problem, i had same issue at first
what i did was i had to run bf4 without vorpx first with oculus connected and set it to the second display on the oculus (without vorpx running on bf4) then save settings and then quit to desktop, then run bf4 with vorpx it should then grab it (at least it did with me) if not you may want to check if your runing vorpx as an admin that can also cause issues (especially considering windows 8’s retarded notion that even if you are an admin user programs that you start don’t always have admin rights, also make sure that if any kind of UAC is on, turn it off)also as for star citizen are you running in direct mode or no?
as far as i know star citizen does not work nor like to see the oculus in direct mode
i have had it work relatively consistently in star citizen with vorpx you do however have to make sure BEFORE you run it with vorpx that the gfx settings are as low as you can get them and at 1080p resolution otherwise i have noticed graphics issues causing frequent crashes.
though i doubt before long that you’ll need to worry about this the SC devs have already pledged to include native oculus support before release (i would read that as the near future; judging by their track record thats prolly going to be withing 4-6 months if thatit might be because that the skse launcher is launching the skyrim exe instead of the skyrim launcher i dont know what program vorpx looks for as a game launch pointer, if its the launcher then that would make sense (an easy-ish way to figure that out would be launch the launcher and then run the skse launcher) if it is not looking for the launcher first then i could only assume that vorpx is looking at the program signature when it tries to hook into skyrim if thats the case then skse launching skyrim could feasibly change the signature because of how skse works.
i have skyrim and skse installed so i’ll take a look at screwing around with it
and see if i can tell what method it usesya sorry
i figure it out it was the IPD bug i was not aware of it and was using the oculus config’s profile
consequently i have found that either the measurement function of the config utility is either wrong or vorpx’s is wrong the oculus utility says i’m 71.4 on the IPD while that same number in vorpx seems a bit blurry while a range of 62.8 to 63.6 seems perfect in vorpx