Forum Replies Created
-
Posts
-
Try making a vorpx game shortcut for BF4, run it prior to joining a server… Whenever mine does what you describe, running that shortcut before joining a game fixed it.
I would like to find a way to get BF4 working with 3d as well (hell I would even be happy with just Z-3d, but currently it does nothing, looks the same as “off”), but unfortunately, renaming it seems like it is not an option. I just went a tried, and if bf4.exe (or bf4_x86.exe) is not named bf4.exe(or bf4_x86.exe), it won’t launch, origin will pop up an error saying that the game is not installed… And I can’t seem to find a way to point origin towards a renamed .exe.
I really hope BF4’s 3d issues get fixed in the next Vorpx update.
Not quite sure what you mean here… Do you mean it’s not showing the same image to both eyes (one image across the whole screen, each eye is looking at one half of the image)
If you’re having trouble with it showing two different images to each eye, try playing the game via the 32 bit client (Right click BF4 in Origin, hit “Game Properties” and change the dropdown menu “when launching this game” to X86).
If you want to run it in 64bit, make a vorpx shortcut to BF4’s 64 bit .EXE (to make a shortcut, right click on the little vorpx icon on your taskbar, hit “Create Desktop Shortcut” and find “bf4.exe” in your origin games/battlefield 4 folder). I’ve found this usually makes the game work properly if you start vorpx, start origin, run the shortcut(which won’t actually start the game, it just tries to make Vorpx recognize BF4 64 bit as a useable process), and then join a game via battlelog… Sometimes it doesn’t work, just have to close BF4 and run the shortcut again, and then join another game.
You will have to do this every time you want to play BF4… If you don’t want to go through all that, just run it in 32 bit.
Interesting development…
Ok so, context first: I forgot to mention in my first post, the mouse worked fine the first time I started Planetside 2 in Vorpx, but upon closing and starting again later, it ceased to function properly, no settings changed that I was aware of, but it had been a day since I first played it.
Now fast forward to today, when I just remembered that Planetside 2 has a 64 bit and 32 bit client… I had forgotten because well, the 64bit use to be disabled, now it just auto chooses one based on your OS. It’s a bit of a pain to get PS2 to start using the other client, but it can be done, so I went and tried the 32 bit client.
Lo and behold, the mouse worked! I thought I had it fixed, and then I remembered that this is what it did last time… So, for the sake of a controlled experiment, I shut the game off and then started it again immediately, changing no settings anywhere. Mouse doesn’t work.
Somewhere, somehow, something is making Vorpx and Planetside 2 hate each other after the first run, and I am lost, just so damn lost… I have no idea what the hell would do this… Even tried doing a clean reinstall of the game, no dice.
Side note, mouse connected with the game fine the first time I tried it, closed the game, opened again changing nothing, now the mouse refuses to work.
My problem is I can’t get the mouse to interact with the game when using Vorpx, in windowed mode or not… No problems launching the game and getting vorpx to hook, mouse just refuses to interact with it after the fact… Can’t even hit the button to select my soldier and enter the game, or open the options menu.
I’ve noticed this too, Berrers, 3d doesn’t really seem to work in BF4… I can’t seem to find a difference between the Z modes and off, and in the Z modes, image separation adjustment doesn’t appear to change anything :(
Titan Z is a dual GPU card but only one of the GPUs will work in vorpx, Right now the best card for VR is a 780 Ti.
Are you sure dual GPU doesn’t work? I just went and checked BF4 and Skyrim with Vorpx on my DK2, both GPUs on my 7990 are seeing equal usage.
It’s the game, more than Vorpx I imagine, the game likely has something in it’s code that simply conflicts with the way Vorpx does things by default.
Unfortunately, that didn’t do it either :( I also tried it with only hiving the Rift connected as a display with no luck.