Forum Replies Created
-
Posts
-
I’ll check again, but not sure where to look TBH. Until someone else reports something similar, I can only assume that it’s some system specific issue. SWBF2 obviously has been used heavily for 17.3.0 to create the profile, SWBF also doesn’t show anything comparable here.
What you could try is switching on/off raw input in the game options. Normally it should be on.
You can change the weapon FOV separately from the world FOV on the Direct VR page of the ingame menu. That can somewhat mitigate the issue if you are bothered by it heavily, but the only real fix is using a camera mod.
Showing the image on the monitor does not cost any performance.
Do you still have this issue? Just checked Battlefront 2015 without a gamepad connected but could not reproduce it. Some FrostBite games behave rather odd when both gamepad and mouse are used, mouse only however should not cause any glitches.
Sounds as if the game might have lost mouse focus. ALT-TAB out and back into the game can help with something like that.
Again nothing really useful in the log files unfortunately. Your graphics card might be a factor here too. Try switching to Z3D and check whether that helps. G3D would overstrain your GPU anyway unless you can cope with framerates <30fps.
BTW: Leave the 1440x1080 custom res in the control panel, it's probably the best resolution you can get for vorpX on your system.
The log file doesn’t really show anything useful except that the game exits again just after starting, so I can’t really recommend anything specific.
Condsidering your rather old gfx card the only thing that comes to mind is lowering the game’s graphics to minimum and check whether that helps. Maybe it’s an gfx memory issue.
Let vorpX handle that. If you want to enhance the image quality, choose a higher “Resolution Quality” on the Direct VR page of the vorpX ingame menu.
BTW: Makes sense to set the graphics detail to “medium” in the game’s launcher. Also keep an eye on performance when you raise the resolution (ALT+F).
A short test shows the exact opposite behavior here, which is what is to be expected since there is a fix in 17.3.0 that explicitely addresses flames/torches. The torch in the start cell looks now perfectly correct while before it was glitchy. Odd.
Please try without any mods. If that does not help, let me know what edition of the game you are using (DVD/Steam/GoG/GotY or not etc.).
You can safely ignore the “Restore Game Settings” crash. It only occurs while there isn’t anything to restore. As soon as you played games where vorpX actually changed settings, the crash disappears.
You can safely ignore this crash. It only occurs while there isn’t anything to restore. As soon as you played games where vorpX actually changed settings, the crash disappears.
There is no either-this-or-that in regard to new and old users. Both groups have to be considered, and I think the latest update did exactly that.
For those who are new to vorpX things got a lot easier for a lot of games. What may be trivial for you, could look like a major hurdle to a new user. This had to be addressed for more games and it was by unifying the prior Game Settings Optimizer and Direct VR, which is not a ‘cosmetic’ change. It is a long overdue and quite fundamental improvement touching the very core of vorpX in many ways.
You can still do everything manually, but instead of new users having to learn how to use certain features, they now “just happen” and experienced users have to disable them if they want more manual control, which makes a lot more sense than doing it the other way around.
There also are new profiles for users like you waiting for something new to play with, also G3D was added to quite a few existing profiles, so I think it’s safe to say that existing users have been considered just as well as new users. What you should take into account is that 3D graphics 2017 are a lot more complex than 3D graphics were 2007, so what kind of 3D is possible depends a lot more on an individual game than it did in the past. Not even nVidia has G3D for every new game anymore in their stereo drivers.
TLDR: interests of existing and new users have both been taken into account with this release. That is how it has to be done, and that is how it will be done in the future too.
The issue is not that vorpX can’t hook into games, that works as it should.
The issue is that the games start on your internal Intel GPU (which probably is the one you have your monitor connected to) while your headset is connected to the nVidia GPU. Such a configuration does not work since vorpX cannot copy images from one GPU to another.
Connecting monitor and headset both to the nVidia GPU would almost certainly solve the issue.
For some additional info please check the mail I sent you.
Windows Defender should not be a problem. Please try to start a few games, then open the config app and create a trouble shoot data archive (Trouble Shooting page). Send that to support |at| vorpx com. Maybe I can spot something you overlooked.
No promises, but something is definitely wrong on your machine. With a bit of luck the trouble shoot data shows what that may be.