Forum Replies Created
-
Posts
-
You can exclude programs from vorpX in the config app.
The easiest way to do this:
1. Start the program that vorpX is not supposed to hook.
2. Open the vorpX config app.
3. Go to the “Excluded Programs” page
4. Click the “Add Process” button and select the program you want to exclude.Please make sure to select a 4:3 resolution to minimize the possibility of flicker, that should remove whole image flicker almost entirely. Occasional weapon flicker may remain, especially on CPUs with ‘only’ 4 logical cores (i5).
I don’t have any other info on this than anybody else at this point. Before MS releases the patch, it’s impossible to say anything Windows specific.
However, the benchmarks in the article linked above show virtually zero impact in all games that were tested. Those were Linux/OpenGL tests, so some uncertainty remains, but I wouldn’t expect much of a difference on Windows. Don’t worry.
I’m sure we’ll see plenty of Windows gaming benchmarks as soon as MS patches Windows.
The patch for the Intel-CPU-flaw will mostly impact applications with many I/O operations, disk/database access and similar things. Gaming performance apparently is not affected much, if at all. Probably nothing to worry about.
This article has a few initial (Linux) pre/post-patch gaming benchmarks.
vorpX 17.3.1 has been released. This is a maintenance update that fixes a couple of issues with the initial 17.3 release.
For details please check the original post of this thread.
Please make sure that you use the D3D11 version of the game. Should be the default when you start the game from Uplay.
If that does not help, do a factory reset in the vorpX config app to ensure that the profile database is up-to-date.
Issue is confirmed and will be fixed ASAP with a hotfix. Actually a regression, ie. an issue that was fixed in an earlier build but was re-introduced in 17.3.0.
Until the hotfix is released, disabling the Origin in-game overlay should reliably fix the problem.
Update:
vorpX 17.3.1 is now available and should address this issue.
Windows Defender does not cause issues, if you use another virus scanner disable/uninstall it.
Apart from that please follow the advice above and disable everything that is running in the background, except vorpX, of course.
If you can’t solve the issue, please send a mail to support |at| vorpx com with a trouble shoot data archive that you can create in the config app.
The issue has been identified, thanks for your help! It is related to importing profiles from the cloud (or profile files), which can lead to Direct VR settings being stripped from the profiles under certain circumstances.
A permanent fix will be in the next vorpX version. If you experience this again in the meantime, resetting a profile to default in the config app helps.
The watcher has to be enabled, otherwise vorpX cannot detect whether a game is running.
If you have the same issue with other games too there probably is an injection conflict with some other program on your PC. Many programs also hook into games and can cause such an issue. Not all of them are obvious.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot this is to disable/uninstall every program running in the background.
vorpX only has to run, there is nothing else to do to show the image in the headset.
Please check the blelow things:
1. “Steam VR” is slected as your headset in the vorpX config app.
2. vorpX is running (indicated by a tray icon in your taskbar).
3. Steam VR is in direct mode (which is the default setting).Please check with other games (or the vorpX desktop) viewer whether vorpX in general.
That was fixed with the initial 17.3.0 release.
Just in case: try to reset the profile to default in the config app or do a full factory reset. if for some reason a pre 17.3.0 profile is active, you would still have the fire glitches.
In your post above you write that you use extended mode. Extended mode does not work. Only direct mode works.