Forum Replies Created
-
AuthorPosts
-
jhondidfoolParticipant
Thanks for the answers, Ralf :)
I’ll tinker with it some more.jhondidfoolParticipantTurns out that, for GTAV, it was because for some stange reason the game was set to rn in DX10.1. Now it works on Oculus, but on SteamVR it gives me this in the log and I get infinite black screen with loading sandclock:
WRN: OpenVRDirectModeManager Submit Error: 101 101 0
Apr 20, 2016 at 7:46pm in reply to: Star Citizen alpha 2.3.1 / Oculus SDK v1.3.0 / VorpX 16.1.2 working #101233jhondidfoolParticipantCrashes for me. I can’t get it to work for the life of me and I don’t understand why.
jhondidfoolParticipantSame as feather623
I’m running W10PRO x64
Works with some games (ESO and Star Citizen don’t. SC has a profile, suposedly, it won’t let me create one for it).jhondidfoolParticipant@ Ralf : A few seconds, yes. A few minutes… not so much. In fact, I have not been able to run the desktop even after 15 minutes waiting.
Latest drivers NV 980, DK2
jhondidfoolParticipantNews. This may be interesting; I’ve managed to fix the problem by manually generating new game .inis and then I compared the variables. Some shadow map resolution values were not powers of 2. That may have been the cause.
jhondidfoolParticipantI fixed it myself. turns out SKSE was calling TESV_Old, not TESV
jhondidfoolParticipantI fixed the skyrim problem running VorpX as administrator *_*
On the Star Citizen side, I have to make rift my primary and render to primary. It does away with all my icons and desktop. It’s a mess. I guess I’ll have to wait for native implementation. -
AuthorPosts