Forum Replies Created
-
Posts
-
First please make sure that your antivirus definitions are up-to-date.
If that does not help already, you can simply update to the latest vorpX version with your web installer, so vorpX doesn’t launch the updater anymore.
If you didn’t keep the installer, you can get a new one here.
BTW: If you use a third party AV program, consider getting rid of it. Windows Defender comes free with Windows 10 and is very good these days without being as invasive as some third party AV programs.
If you found it, you can already play around with it a bit if you want. It’s not official yet though, also swapping shaders is DX9 only for now. Early stages, a lot will change until the feature becomes official.
vorpX itself cannot do that, but there are programs that can display desktop windows in any VR app. OVRdrop comes to mind for SteamVR, not sure if something similar exists for native Oculus. If not, you can simply use vorpX in SteamVR mode with your Rift S.
Update: According to this Reddit thread, you might be able to pin a desktop window using Oculus Dash. Never tried that though.
First please try to enable ‘Alternative Hooking’ in the vorpX config app (General page > Misc). Note that this should only be used in case of hooking issues with a specific game, not generally. It’s not better, just different. If in doubt always try both methods.
If that does not help, please thouroughly check for programs on your PC that might cause an injection conflict. You can find more detailed information on the matter and a list of potential candidates in the trouble shooting guide.
Looks as if the game now has some SteamVR detection built in. Fails to load even with only SteamVR running but not vorpX.
There is an easy workaround though: closing SteamVR before lauching the game should do the trick. It will auto start when vorpX initialises the headset.
I’ll try to find an automated solution. If that that should prove unfeasible, I’ll add an according start hint to the next vorpX version.
My answer would pretty much have been the same as yours.
vorpX uses a certain amount of the CPU while checking for newly started programs, but under normal circumstances that should be below 10%. The OP’s 25% may not be as bad as it looks though. Modern CPUs clock down heavily when idling, so if those 25% are shown in a clocked down idle state, it’s still almost nothing.
If not, closing vorpX or pausing the watcher is indeed the best thing to do.
BTW: While running games with vorpX the watcher always pauses, so no CPU cycles are wasted while playing games.
Please disable antialising in the game options and in your graphics driver control panel if you have forced it there. Ultra low Bioshock FPS are caused by antialising.
I’m not 100% sure currently whether enabling AA ingame works, so you might want to try that, but forcing AA through the graphics driver definitely doesn’t for some odd reason.
Keep in mind that vorpX has to render everything twice, once for each eye, which basically cuts the framerate in half. To enhance the framerate you can either reduce graphics details in the game options or switch to Z3D in the vorpX menu. Z3D is faster, but doesn‘t look as natural. With your machine you should be able to achieve a decent framerate with G3D and reduced graphics settings though.
Might also make to sense to lower the refresh rate in SteamVR, which reduces the work required to render the game to the headset.
More detailed information on performance (and a few extra tweaks) can be found in the „Performance Optimization“ section of the vorpX help. You can access the help from the config app.
The scan has to be run every time. In some games vorpX can cache the scan results, but not in Skyrim and Oblivion (at least not fully) since the memory location for the camera rotation changes with each program start.
If you see the restart hint every time you launch the games, please make sure that you have write access to their .ini files and that no other program changes the ini files. E.g. some mod launchers may write protect the ini files and/or change them. Try starting the games without the mod launcher running in that case.
This issue has to be resolved by BitDefender, there is no way to fix it on our end. Their software FALSELY considers each new vorpX version malicious, probably because it hooks into other programs. Please report the issue as false positive to BitDefender so they can fix the problem.
Such things are quite common with AV programs, hence most AV vendors provide a way to let their customers/users report false positives.
Alternatively to reporting the issue as a false positive to Bitdefender you can either:
1. Exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) from BitDefnder. Make sure to also exclude it from BitDefender’s so called “Advanced Threat Protection”, which apparently flatout blocks certain Windows functions vorpX uses to hook into games.
2. Switch to Windows Defender, which comes free with Windows 10. Windows Defender in most recent tests is as good as third party AV programs, but less invasive than some of those. It kicks in automatically when you uninstall your third party AV program. Not much reason to use a third party AV program these days anymore.
The scanner works, but automatic FOV and some other tweaks are not applied automatically since that is done via ini editing. vorpX does automatic ini editing a lot (for more than 200 games), so you should expect similar issues with more, if not all, Windows Store games.
If I can get hold of the required information for a game, I will consider the Windows Store paths for future profiles, but for now not a single profile considers the Windows Store paths for automatic ini edits.
This is a false positive.
If updating to the latest Defender definitions does not help already, please report this issue to Microsoft as a false positive.
To avoid such issues altogether you can exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) From your AV scanner.
You can also update vorpX manually using your web installer.
Just a little heads-up that it makes sense to get the Steam version of games for vorpX if possible. In this case for example that would grant you automated FOV handling and some other auto tweaks through DirectVR.
Typically it’s more likely to get advanced functionality like automated ini edits for non-Windows Store versions, Windows Store games may use unusual ini-paths that vorpX is not aware of.