Forum Replies Created
-
Posts
-
<P>Is your DK2 set to primary or secondary screen in desktop/VGA setings?</P>
I’ve tried both primary and secondary, and forcing dk2 in vorpx also. Same crash in the same place each time. Starting to think there is no way this is going to work for me :(
Still zero progress. I’ve clean reinstalled my AMD drivers, and even tried the new omega driver to no success. I’ve tried all the methods here and still nothing. I see the sbs vorpex view for a split second, which then switches back to standard view when the progress bar comes up followed by an immediate crash with no explanation.
Tried windowed and full screen, the x86 and x64 version of the occulus service, admin and none admin vorpx and farcry. I even tried using uplay removed versions of the executables, but nothing has worked :(
As I said, vorpx works great in outlast and skyrim, just zero luck in farcry 4 so far. Going to try a different machine next as this has to be an environmental issue.
Forgot to add the list of things I’ve tried. Offline and overlays for uplay are amongst them :( . The things I’ve tried so far :
•Disabling UPlay overlays
•Uplay offline mode
•Vorpx as Admin
•Direct and extended mode (direct crashes at splash, extended allow the game to start but crashes when loading, way before the main menu)
•Applying the vorpx optimisations for fc4
•Removing optimisations
•OVR service running and disabled
•AMD Catalyst drivers, both beta and stableI’m on windows 8.1 x64 with latest updates running an AMD 290X with latest drivers. Rift is connected via DVI and the adapter, screen via hdmi. Other games run fine both with and without vorpx